Two jobs here, and they are different. If your PDF asks for a password to open, enter it and you get the same document back with the password removed — useful when you are tired of typing it every time you open your own bank statement. If your PDF opens freely but refuses to let you print or copy, leave the password field blank: those restrictions are permission flags, a note in the file rather than a lock, and stripping them needs no password because there was never any encryption behind them. What this does not do is recover a password you do not have. It decrypts what you can already open. Everything runs in your browser, which is the only sensible place for it — uploading an encrypted document together with its password to have the protection removed would be an odd thing to do.
| Symptom | What it is | Password needed |
|---|---|---|
| Asks for a password to open | Real encryption | Yes — yours |
| Opens, but printing is greyed out | Permission flag | No |
| Opens, but text will not copy | Permission flag | No |
| Forgotten the opening password | Real encryption | Cannot be done |
No. It decrypts a document you can already open, which means you have to supply the correct password. There is no recovery, no cracking and no bypass — AES-256 does not have one, which is the entire point of it.
Because those restrictions are not encryption. A PDF that opens without a password but forbids printing carries a permission flag — a note asking viewers to disallow it. Well-behaved readers honour it; anything else ignores it. Since nothing cryptographic is holding it, saving the file without the flag needs no password.
No. Both stay in your browser. Sending an encrypted document and its password to a server so the server can strip the protection is a strange trade, and it is not one you have to make here.
For your own documents, or ones you are authorised to use, yes — that is the normal case, and removing a password from a file you already have the password for changes nothing about who can access it. Circumventing protection on someone else's document is a different matter and in many places unlawful. This tool cannot help with that anyway, since it needs the password.
No. Pages are copied rather than re-encoded, so text stays selectable, images are not recompressed and the file size is essentially unchanged.
A PDF with no password at all — anyone holding the file can open it. If you need it protected again with a different password, the Password Protect PDF tool does that.
There are two quite different things this handles, and conflating them is how these tools get misdescribed. A PDF with a user password is genuinely encrypted: supplying the correct password decrypts the content streams, after which the document is saved with no encryption dictionary at all. Supplying the wrong one fails, and no amount of trying makes it work — this decrypts what you can already open and does not attempt, and could not perform, any kind of password recovery. The second case needs no password: a PDF that opens freely but blocks printing or copying carries only permission flags, which are a note in the file rather than a lock, enforced solely by viewers that choose to honour them. Loading such a file with encryption ignored and saving it writes those flags away, because there was never anything cryptographic holding them. The distinction is surfaced in the interface rather than buried, since a tool that silently handles both invites the assumption that it cracks passwords. Output is written with pdf-lib, which copies the original page objects rather than re-encoding them, so text stays selectable and images are not recompressed. Files and passwords are processed entirely in your browser — uploading an encrypted document and its password to a server to have the protection removed would be a strange thing to do.