“Protecting a PDF” sounds like one task. It’s at least four, and they solve completely different problems. Most of the mistakes I see come from reaching for the wrong one — usually a password, because it’s the option everyone knows about.
This is a practical guide to picking the right tool. It assumes no security background and won’t ask you to install anything exotic.
Start with the actual question
Before choosing anything, work out which of these you’re worried about. They’re genuinely separate.
| Your concern | What you need |
|---|---|
| Someone who shouldn’t read this might get the file | Encryption with a user password |
| They should read most of it, but not one section | Redaction — real redaction |
| The file might reveal more than what’s on the page | Metadata removal |
| The recipient must know it’s genuinely from me | Digital signature |
| I don’t want people editing or printing it | Permissions — and manage your expectations |
Answer that first and the rest of this article is mostly detail.
1. Encryption: the only one that really locks the door
A user password encrypts the contents. Without it, the document cannot be opened. This is the real protection and the only option on the list that stops a determined stranger.
Three things to get right:
Use a passphrase, not a password. Four unrelated words beat eight characters of punctuation. Length is what defeats password-guessing tools, and cracking software tries the clever short patterns first.
Choose modern encryption. If your software offers a compatibility setting, pick AES-256 over anything labelled RC4 or 40/128-bit.
Never send the password with the file. A protected PDF and its password in the same email thread is the most common mistake in this area, and it reduces the protection to zero. File by email, password by phone.
More detail in how safe is a password-protected PDF.
2. Permissions: a polite request, not a lock
The owner password sets restrictions — no printing, no copying, no editing. The document still opens for anyone. Those restrictions are honoured only because reader software chooses to honour them, and free tools remove them in seconds.
That’s not a flaw being exploited; there’s genuinely nothing to break. Use permissions to stop honest people making honest mistakes. Never use them to stop someone who doesn’t want to be stopped.
3. Redaction: the one people get most dangerously wrong
This deserves emphasis because the failure is silent and total.
Drawing a black rectangle over text does not remove the text. Neither does highlighting it in black. The words are still in the file, underneath a shape, and anyone can select and copy them — or simply extract the text with a free tool. Documents have been released this way by law firms, government departments and newspapers, repeatedly, for two decades.
Real redaction deletes the content and then flattens the page. Use a tool with an actual redaction function, apply it, and then verify: open the result, try to select the text under the black box, and search the document for a word that should be gone. If either finds something, it didn’t work.
The same trap applies to images. Cropping a picture in some editors hides the edges rather than discarding them.
4. Metadata: what the file says when you’re not looking
Every PDF carries information about itself that isn’t visible on any page: who created it, which software was used, when it was made and last modified, and often the original filename and folder path.
That’s usually harmless and occasionally revealing. A document submitted as fresh work whose creation date is three years old. A tender response whose author field carries a competitor’s name because it started life as their template. A file path showing an internal project codename.
Removing metadata takes seconds and is worth doing for anything that leaves your organisation. Check it the easy way first — File → Properties in any reader shows the author, the dates and the producing software immediately.
What none of these protect against
Worth stating plainly, because it’s where expectations drift furthest from reality.
Every measure above protects a file while it’s out of the recipient’s hands. None of them survive the moment a legitimate recipient opens the document. They can screenshot it, photograph the screen, print it, retype it, or forward it along with the password you sent separately. No PDF setting has ever prevented any of that, and products claiming otherwise are describing a different technology entirely.
That isn’t a reason to skip protection — it’s a reason to be clear about what you’re buying. Encryption stops the wrong person opening a file. It doesn’t stop the right person behaving badly. If your concern is the second one, the answer is contractual and organisational, not technical.
5. Signatures: proving where it came from
A digital signature doesn’t hide anything. It proves the document came from a particular certificate holder and hasn’t changed since.
Useful for contracts, invoices and anything where forgery is the risk. Less useful than people assume, because a valid signature says nothing about whether the certificate belongs to who you think, and because content added after signing can still slip past a careless check. See is a signed PDF really safe.
The order of operations, which matters
These steps interfere with each other, so do them in this sequence:
- Redact what shouldn’t be there
- Remove metadata
- Sign, if the document needs proof of origin
- Encrypt, last
Get this wrong and you undo your own work. Encrypt first and you’ll have to decrypt to redact. Sign before redacting and the redaction invalidates the signature. Merging or converting a signed document breaks the signature too — which is the signature working correctly, but a surprise if you weren’t expecting it.
Five mistakes worth avoiding
Protecting the copy but not the original. The encrypted version goes out; the unprotected one sits in your Downloads folder, gets backed up, and syncs to a shared drive.
Reusing the same password for every client document. One leak exposes everything you’ve ever sent.
Assuming “flatten” means “sanitise”. Flattening merges layers and can help with form data. It is not redaction and it does not remove metadata.
Uploading the sensitive version to a website to protect it. Encrypting a document through an online service means sending the unprotected file to a stranger’s server first. If it mattered enough to encrypt, it mattered enough not to upload.
Believing protection is permanent. Encryption protects a file at rest. Once a legitimate recipient opens it, they can screenshot, print, forward or retype it. No PDF setting prevents that.
A five-minute routine before sending anything sensitive
- Redact what shouldn’t be visible — with a redaction tool, not a black rectangle
- Verify: try to select text under the redaction, and search for a word that should be gone
- Strip the metadata
- Encrypt with a passphrase of four or more words
- Send the passphrase by a different channel
- Delete or secure the unprotected working copy
PDF Manipulator handles the middle of that list — encryption, metadata, page-level editing — on your own machine, with nothing uploaded. It’s free and the source is public, so “nothing leaves your computer” is something you can check rather than something you have to trust. It won’t choose your passphrase, and it won’t stop a recipient forwarding the file. Those parts stay yours.
The short version
Work out which problem you actually have before reaching for a tool. Encryption locks the door; permissions merely ask. Black rectangles are not redaction. Metadata talks when you don’t. And whatever you do, don’t send the password in the same email as the file.
Encrypt, redact pages and clean metadata locally — PDF Manipulator is free →
