PDF Security: How to Protect Your Documents

Protecting a PDF means doing four separate things, and most people only do one. You encrypt the file so it cannot be opened without a password. You redact sensitive content so it is genuinely gone rather than hidden. You strip the metadata that travels with the file whether you know about it or not. And you sign it so any later tampering shows.

Here is the uncomfortable part. Encryption is the bit everyone does, and it is the bit that almost never fails. The leaks that end up in the news are nearly always documents that were shared with the sensitive text still sitting in the file, under a black rectangle somebody drew on top of it.

What are you actually protecting a PDF from?

Worth answering before you reach for a tool, because the four risks need four different fixes and a password only addresses one.

• Someone opening a file they should not have. An email sent to the wrong address, a laptop left on a train. This is what encryption solves.
• Someone reading content you meant to hide. Redacted names, salary figures, account numbers. Encryption does nothing here, because the person opening it is allowed to.
• Someone learning things from the file itself. Who wrote it, when, on what machine, what the earlier draft said. That is metadata, and it survives everything except deliberate removal.
• Someone altering the document after you sent it. Changing a figure in a quote or a date on a contract. That is what signatures are for.

Match the fix to the risk. A password on a document whose redactions are fake protects nothing that matters.

How strong is PDF encryption really?

Genuinely strong, and this is the good news.

Modern PDF encryption uses AES, the Advanced Encryption Standard. That is not a PDF invention. It is a US federal standard, published by NIST as FIPS 197, which specifies three members of the Rijndael cipher family: AES-128, AES-192 and AES-256, each working on 128-bit blocks with the number naming the key length.

The detail worth knowing is the timeline. FIPS 197 was published on 26 November 2001 and last updated on 9 May 2023, and that update made no technical changes to the algorithm at all. Editorial improvements only. An encryption standard that has needed no cryptographic revision in more than twenty years of public scrutiny is about as reassuring as this field gets.

So when a tool offers you AES-256 for your PDF, the maths behind it is sound. Your password is the weak link, not the cipher. A short or reused password undoes all of it, because an attacker does not need to break AES if they can guess what you typed. Our guide to password protecting a PDF free walks through the actual steps and the AES-256 versus AES-128 choice.

Why do permissions passwords fail?

Because they are a request rather than a lock, and this catches people out constantly.

PDFs support two different passwords. An open password stops the file being opened at all, and it is backed by real encryption. A permissions password, sometimes called an owner password, leaves the file openable by anyone but marks it as not-for-printing, not-for-copying or not-for-editing.

The problem is that honouring those flags is a choice each PDF reader makes. Mainstream software respects them. Plenty of other software does not, and stripping them is trivial. So a permissions password stops a colleague casually copying a paragraph. It does not stop anyone who actually wants the content.

Use permissions if you want to signal intent. Never rely on them to protect anything you would mind losing.

Why does black box redaction leak your text?

Because a black rectangle is a drawing placed on top of the page, and the words are still underneath it in the file.

This is the single most common serious PDF mistake, and it is common enough that courts warn about it explicitly. Guidance from the United States District Court for the Eastern District of California puts it plainly: edits made by graphic and commenting tools which black out, cover over or remove sections of text can still be removed by anyone to reveal the text underneath.

That is a court telling filing lawyers that their black boxes are not redaction. Anyone can select the text through the rectangle, copy it, or open the file in a different program and read it straight off.

What actually works:

• Use a real redaction function. Tools that mark for redaction and then apply it delete the underlying content rather than covering it. The word to look for is apply, not annotate.
• Run a remove hidden information step afterwards. Redaction handles the visible text. Sanitising handles what is left elsewhere in the file.
• Or take it out of the digital layer entirely. The same court guidance notes that for paper, physically cutting out the text or covering it with opaque tape before scanning is 100 percent effective. Crude, but it cannot leak, because the data was never in the file.
• Verify before sending. Open the finished file, try to select the redacted area, and search the document for a word you removed. Thirty seconds, and it catches the mistake every time.

That last step is the one to build a habit around. Everything else depends on trusting your tool did what you asked.

What is your PDF telling people without you knowing?

More than the page shows, and it travels with the file everywhere it goes.

A typical PDF carries the author name pulled from whatever account created it, the software and version that generated it, and creation and modification timestamps. Depending on how it was made it can also hold the original file path on your machine, comments and tracked changes from earlier drafts, hidden layers, and image data that was cropped out of view rather than deleted.

None of that appears when you read the document. All of it appears in the file properties, and a lot of it appears to anyone who opens the file with the right tool.

The practical risks are mundane rather than dramatic. A tender document revealing which competitor's template you started from. A job application showing you last modified it at 3am from a work laptop. A cropped screenshot where the crop is a view setting and the full image is still in there.

Before anything sensitive leaves your hands, check the document properties and run whatever sanitise or remove hidden information function your tool offers. Converting the file can help too, since a round trip often drops the accumulated history. Our compression guide covers rebuilding a file, and the PDF to text guide is useful when you want the words with none of the container.

Do digital signatures make a PDF secure?

They solve a different problem, and it is worth being clear which one.

A digital signature does not hide anything. Everyone can still read the document. What it does is bind the file to a signer and to its exact contents at the moment of signing, so that if a single character changes afterwards the signature breaks visibly.

That makes signatures the right tool for integrity and attribution, not confidentiality. A signed contract that anyone can open is doing exactly what it should. If you need both, you sign and then encrypt, in that order.

Our digital signature guide covers how to sign free, the difference between digital and electronic signatures, and where they stand legally.

How should you send a confidential PDF?

Five steps, in this order. The order matters, because cleaning after encrypting means re-encrypting.

1. Redact properly. Real redaction, applied, not a rectangle. Then search the file for a term you removed to confirm it is gone.
2. Strip hidden information. Metadata, comments, tracked changes, hidden layers. Check the file properties afterwards rather than assuming.
3. Sign it if authenticity matters. Contracts, quotes, anything the recipient might need to prove came from you unaltered.
4. Encrypt with a strong open password. Long and unique. Not the recipient's surname, not your company name, not a password you have used before.
5. Send the password by a different channel. Text it, call, use a separate app. A password in the same email as the file is not a password, it is a label.

One more habit worth having. If you process a sensitive document, prefer tools that work in your browser without uploading. Every file you send to a server is a copy you no longer control, sitting on infrastructure you cannot audit. All of our PDF tools run locally in the browser for exactly that reason.

What else do people ask about PDF security?

Is a password enough to secure a PDF?

For keeping a document away from casual readers, yes. An open password encrypts the file, and modern PDFs use AES, the standard NIST published as FIPS 197. But a password does nothing about text you thought you had redacted, or metadata sitting in the file properties. Most real PDF leaks are not broken encryption. They are documents that were never properly cleaned before being shared.

Why is drawing a black box over text not real redaction?

Because the text is still in the file underneath. Federal court guidance in the Eastern District of California warns that edits made by graphic and commenting tools which black out or cover over text can still be removed by anyone to reveal the text underneath. Anyone can select it, copy it, or open the file in another program. Use a genuine redaction tool that deletes the content.

What metadata does a PDF store about you?

Usually the author name, the software that created it, and creation and modification timestamps. Depending on how it was made it can also carry the original file path, tracked changes, comments, layers, or cropped-away image data. None of that is visible on the page, and all of it travels with the file.

What is the difference between an open password and a permissions password?

An open password stops the file being opened at all and is backed by real encryption. A permissions password only asks readers not to print, copy or edit, and most PDF software will honour it while plenty of other software simply ignores it. Treat permissions as a polite request, not a security control.

How do you send a confidential PDF safely?

Clean the file first, then encrypt it, then send the password by a different channel. Remove hidden information, redact properly rather than covering, set a strong open password, and text or call the recipient with it rather than putting it in the same email. A password emailed alongside the file protects nothing.

Sources: National Institute of Standards and Technology, FIPS 197, Advanced Encryption Standard, originally published 26 November 2001 and updated 9 May 2023 with no technical changes to the algorithm. United States District Court for the Eastern District of California, redaction requirements guidance, on graphic and commenting tools failing to remove underlying text and on physical removal before scanning. This is general information about document handling, not legal advice. If a filing or disclosure has legal consequences, check the rules that apply to it.