How to protect a PDF document from copying (and what actually works)

What "copying" actually means

People use the word for three different things, and the fix is different for each.

1. Copying the text or images out, by selecting and pasting them somewhere else.
2. Copying the file, by saving it, forwarding it or uploading it elsewhere.
3. Copying the look of it, by screenshot or by pointing a phone at the screen.

The first is what PDF settings try to block. The second is a distribution problem, and I've covered it separately in how to stop people forwarding a PDF. The third can't be stopped by any software, so I'll deal with it plainly further down rather than pretend.

Password and permission settings only go so far

Most PDF editors let you set two kinds of password. One is needed to open the file at all. The other restricts what a reader can do once it's open, such as printing, editing or copying text.

The open password is real protection, with a catch I'll come back to. The permissions password is a request, not a lock. It works because the reader software agrees to honour it, and plenty of readers and tools don't. Anyone with a minute and a search engine can usually strip those restrictions, and Adobe's own help pages are upfront that third-party software may ignore them.

I used to rely on this. In growth roles I'd tick the "disable copying" box on a proposal, feel clever, and send it. It stopped nobody who wanted the text, and it irritated the people who had a good reason to copy a figure into their own notes. If you're tempted, I wrote about the other side of this in changing a secured PDF.

The open password has a people problem

A password that's needed to open the file does stop a stranger reading a forwarded copy. The weak spot is the human. The password usually goes in the same email as the file, or in a follow-up that sits right underneath it. Once someone has both, they have everything, and so does anyone they forward it to.

It's still worth using for a file that's going through an inbox you don't trust. Just don't mistake it for control over what the recipient does next.

Rights management is the strong option, with a cost

Certificate-based encryption and enterprise rights management do tie a document to named people, and they keep the restrictions attached as the file travels. If your organisation already runs one, use it for the genuinely sensitive stuff.

The cost is on the other end. Every recipient needs the right software, licensing or digital ID. That's workable for internal staff and nearly impossible for a prospect, an investor or a client you're trying to impress. A document that takes twenty minutes of setup to open doesn't get read.

Limit access rather than lock the file

This is the approach I'd pick for nearly every business document: stop handing over a copy and share access instead. Put the PDF behind a link you control, so what the recipient has is permission to view it, not a file that lives on their laptop forever.

With a link, the levers change. You can limit who can open it, set it to expire, and revoke it later if the deal dies or you sent it to the wrong person. A forwarded link can be shut off. A forwarded attachment can't be recalled.

That's the model behind sharing a PDF as a link, and it's the one I built LiveDocument around. It works with PDFs and images, you share one link, you can expire or revoke it, and you can see page-level activity, so a document that suddenly gets read by someone you've never heard of shows up. If you want the tracking side in more detail, that's under PDF tracking.

To be clear about what that does not do: LiveDocument doesn't add watermarks, it doesn't gate access behind an NDA, and it can't stop someone typing out what they see or photographing the screen. It reduces how many uncontrolled copies exist and tells you what happened. It doesn't make the content uncopyable, and I'd distrust any tool that claimed to.

The screenshot problem has no technical fix

Anything a person can read on a screen, they can capture. A screenshot, a screen recording, a phone camera, or just retyping the three numbers they care about. No PDF setting, viewer or platform gets round that, and the ones that claim to usually only cover one of those routes.

So the useful question stops being "how do I prevent copying" and becomes "how much damage would a copy do, and would I know?" For a pitch deck or a proposal, the answer is usually that a copy is annoying but survivable, as long as it isn't sitting in an inbox somewhere for years. For something genuinely damaging, a PDF probably isn't the right format, and the better route is a more controlled setup, like those covered in the best way to share confidential documents, with identity checks on every reader.

A sensible setup by document type

Match the protection to what the document is worth rather than layering everything on.

• A proposal, deck or report you want read: share a link, expire it when the decision window closes, and keep tracking on so you know who opened it. Skip the permissions password.
• A file that has to travel as an attachment: use an open password, send the password by a different channel, and accept that the recipient holds a copy.
• Something regulated or highly sensitive: use proper encryption or rights management with named recipients, and check the wider points in secure file sharing for business.
• Something you'd be badly hurt to see leaked: ask whether it should be a PDF at all.

FAQ