Open a PDF and try to copy a paragraph, only to find the text won't highlight. Hit print and the button is greyed out. The file isn't broken, it's carrying permission flags, a small set of instructions baked into the document that tell your PDF reader what you are and aren't allowed to do. This guide explains exactly what those permissions are, how they're enforced, and which of them a permission-removal tool can actually clear.
The two kinds of PDF password
Almost all confusion about "locked" PDFs comes from mixing up two completely different passwords. The PDF specification (ISO 32000) defines them separately:
- Document Open password (user password): Required to open and read the file at all. Without it, the content is genuinely encrypted and unreadable. This is the strong lock.
- Permissions password (owner password): Does not stop anyone from opening the file. It only governs what actions are allowed once the file is open, printing, copying, editing, and so on. This is the restriction lock.
A single PDF can have neither, one, or both. The important insight: a file that opens instantly but refuses to print or copy has only an owner password. A permission-removal tool addresses exactly this case. A file that demands a password just to open has a Document Open password, and no legitimate tool can bypass that without the correct credentials.
What each restriction controls
When an owner password is set, the creator can toggle a specific list of allowed actions. Here is what each flag actually does in practice:
| Permission | What it blocks when disabled |
|---|---|
| Printing | Sending the document to a physical or virtual printer. Some files allow only low-resolution printing. |
| Content copying | Selecting and copying text or images to the clipboard. Also blocks text extraction by other software. |
| Editing / modification | Changing text, images, or page content in an editor. |
| Document assembly | Inserting, deleting, rotating, or reordering pages. |
| Commenting / annotation | Adding notes, highlights, or markup. |
| Form filling | Typing into interactive form fields. |
| Accessibility extraction | Screen readers pulling text for people with visual impairments (thankfully rare to disable now). |
Why a file you own can still block you
Permission flags are enforced by the reader, not by your account or your ownership of the file. Adobe Acrobat, Preview, Chrome, and Edge all honour these flags as a matter of convention. That means the restriction follows the file everywhere it goes, including back to the person who created it.
The most common real-world scenario: months ago you exported a report from your accounting software or a design app and ticked "restrict editing" with an owner password. Today you need to reprint it or copy a table into a new document, but you've long forgotten the password. The file is yours, the content is yours, yet the flag stands in your way. This is the textbook case where clearing the owner password is both legitimate and trivial.
What a permission-removal tool can and cannot do
Understanding the boundary keeps your expectations realistic:
- Can do: Clear the owner password and reset every permission flag to "allowed" on a file that opens without a password. After processing you can print, copy, edit, and reassemble freely.
- Can do: Rebuild a permission-free copy when you already know and supply the Document Open password.
- Cannot do: Guess, crack, or bypass an unknown Document Open password. Strong encryption (AES-256) makes that computationally infeasible, which is by design and a good thing.
- Cannot do: Remove third-party DRM layers wrapped around commercial ebooks or subscription documents.
For a deeper look at the encryption that backs the Document Open password, see our guide on how PDF encryption works. If the word "unlock" itself is tripping you up, our explainer on what unlocking a PDF really means untangles the terminology.