How to Remove a PDF Password You Already Know
Unlock is appropriate when you know the password and need an authorized unencrypted copy. It is not a way to discover a forgotten password or repair every PDF that a viewer describes as locked.
Verify access before removing encryption
Check the original
Confirm the password opens the source in your viewer and that you are authorized to modify it. Keep that original available.
Enter the current password
Select the file in Unlock PDF and enter the known password. The interface requires a nonempty password; it does not try guesses or a recovery service.
Save and reopen the result
After success, download the copy and open it afresh without a password. Check the pages and required features before distributing an unencrypted document.
What the engine does
The handler passes the supplied password and a decrypt instruction to qpdf WebAssembly. It requires a successful exit status and a nonempty output before exposing a download. Removing supported encryption removes that password barrier from the copy; it does not turn image-based text into editable paragraphs or repair signatures.
Separate access errors from other failures
| Symptom | Useful next check |
|---|---|
| Security engine cannot load | Check connectivity and restrictions affecting the jsDelivr WASM download. |
| Nonzero qpdf status | The password may be wrong, or the input damaged or unsupported. The wrapper cannot always distinguish the cause. |
| File opens but editing is unavailable | Check the viewer and document structure. Unlock does not provide a text editor or form designer. |
| No known password | Ask the sender or consult your records; PDFcraft provides no cracking or recovery path. |
The output needs different handling
An unencrypted copy should not be distributed on the assumption that the old opening password still protects it. Decide where to store it and who may receive it. Controlled Node checks exercised a Protect-to-Unlock workflow and observed text/field values, not interactive form behavior, signature preservation or universal compatibility.
Local decryption still loads a runtime
The document and password are supplied to the local qpdf runtime rather than a PDF-upload service. The runtime is downloaded from jsDelivr. Temporary runtime files are removed and the input buffer cleared afterward, without a guarantee of erasing every copy from browser memory.
Choose the next operation
Frequently asked questions
Should I enter a made-up password for an unencrypted PDF?
No. That is not a repair procedure. Identify why the file cannot be edited or saved instead of treating every restriction as encryption.
Will the unlocked copy retain a valid digital signature?
Signature preservation is not verified. Keep the signed original and use a workflow that explicitly validates signatures when that matters.