What does PDF Unlock do?
It creates a separate unencrypted PDF when you provide a valid current password for a compatible encrypted document.
Select an encrypted PDF, enter the password that opens it, and download a separate unlocked file.
Preparing the editor...
The guide and instructions on this page are available while the tool loads.
PDF Unlock creates a separate PDF that no longer asks for the password you already know. Provide a valid current password for a document you own or are authorized to modify. The tool does not recover, guess, crack, or bypass an unknown password.
Choose one PDF, wait while the page checks whether an open password is required, then enter that password. Unlocking can start from the Unlock PDF button or from the automatic retry that begins shortly after you finish typing. QPDF WebAssembly decrypts the file in the browser and downloads a new copy with an -unlocked suffix.
Successful decryption writes an unencrypted PDF rather than rendering pages as images. The workflow does not intentionally resize, reorder, flatten, or recompress pages. Still review forms, annotations, bookmarks, attachments, layers, and other advanced features in the downloaded file, because every edge case has not been verified.
The PDF bytes and password stay in the browser during decryption. No unlock API route and no unlock analytics event were found. The site may still load normal page assets and the QPDF WebAssembly file needed by the engine.
Compatibility depends on the encryption method and password type supported by QPDF. Incorrect passwords fail without producing an unlocked file. Files that already open without a password usually do not need this workflow. Rewriting typically invalidates certificate-based signatures, and permissions-only restrictions without a usable password are outside the current interface.
Typical tasks this tool is built for.
PDF unlocking runs locally through QPDF WebAssembly in your browser. The selected PDF and the password you enter are not uploaded to DevToolKit for decryption. This workflow has no identified unlock-tool analytics event. The page may still fetch ordinary site assets, the QPDF WebAssembly binary from /wasm, or general diagnostics; those requests do not include the password, filename, document text, or raw PDF bytes from this tool.
Practical tips before you download or share the output.
PDF Unlock accepts one PDF up to 50 MB and requires a non-empty current password. It does not recover forgotten passwords and does not crack encrypted files. Compatibility varies across encryption methods and owner-password-only cases. Already-unlocked PDFs usually do not need this step. Successful QPDF --decrypt output is saved without the supported open-password encryption; residual permission behavior can still depend on the source file and reader. Rewriting invalidates certificate-based signatures. Output uses an -unlocked.pdf suffix. While a protected source stays locked, the preview shows a placeholder; after success, the unlocked copy can appear in the iframe. Progress messages are shown, but there is no cancel control once decryption starts. Keep the original and verify the download before relying on it.
Longer reads that pair well with this tool.
PDF guide
Match your PDF task to the right DevToolKit tool — merge, split, compress, convert, secure, or edit — and check processing labels before you upload.
PDF guide
Step-by-step In-browser PDF compression: raster downsampling, structural repacking, and how to treat scanned versus text-heavy files — with no quality guarantee.
Common next steps after using this tool.
Combine whole PDF files into one document that follows the order shown in your file list.
Reduce one PDF using JPEG page rasterization or a non-raster structure repack, then download a separate -compressed.pdf.
Encrypt one PDF with a required open password, optional owner password, and viewer permission presets or custom print, copy, edit, and annotate controls.
Build an editable DOCX from the PDF text layer, with optional Page N headings and best-effort Word tables.
Turn PDF text into an editable XLSX workbook with page sheets, detected-table sheets, or one combined data sheet.
Recognize printed text on scanned or image-based PDF pages locally, then export a TXT or Markdown working copy for proofreading.
Situations where this workflow saves time.
It creates a separate unencrypted PDF when you provide a valid current password for a compatible encrypted document.
Yes. A non-empty password that opens the PDF is required. Without it, unlocking cannot proceed.
No. The tool does not recover, estimate, or reset forgotten passwords.
No. There is no guessing, brute-force, or bypass feature.
Local. Decryption runs in the browser through QPDF WebAssembly. There is no unlock API route.
No. The selected PDF stays in the browser for this task. The page may still load ordinary assets and the QPDF WebAssembly binary.
No unlock upload, analytics event, URL storage, or persistent password storage was found. The password exists only in temporary page state while you use the tool and is passed to the local QPDF process.
One PDF at a time.
One PDF up to 50 MB. Larger or complex files can need more browser memory.
Support depends on what QPDF WebAssembly can decrypt with the password you provide. The tool does not claim universal compatibility with every encryption revision or security handler.
Many AES-encrypted PDFs work with QPDF, but success is not guaranteed for every AES-256 or custom-protected file. Test the download when encryption details matter.
Unlocking fails, no unlocked file is produced, and you can correct the password. The same failed password is not auto-retried until you change it.
An unencrypted PDF usually does not need this workflow. The interface still requires a password field value, and QPDF may report that the file is not encrypted.
Successful QPDF decryption saves an unencrypted PDF and typically clears encryption-tied restrictions. Permissions-only cases without a usable password are outside the current UI, so verify restriction behavior in your PDF reader.
A successful -unlocked.pdf copy is intended to open without the removed open password. Always test the download before deleting the original.
The process decrypts the PDF structure rather than re-rendering pages as images, so visual quality is not intentionally reduced.
No intentional rasterization occurs during unlock.
The unlock workflow does not intentionally resize or reorder pages.
The app does not intentionally strip title or author fields, but QPDF rewriting can change technical metadata. Inspect the output if metadata integrity matters.
Saving a new unlocked PDF rewrites the file and typically invalidates existing certificate-based signatures. Keep the signed original when signature validity matters.
The download uses the source base name plus -unlocked.pdf. The original file is left unchanged.
There is no dedicated cancel control once decryption has started. You can change the file or start another unlock after the current attempt finishes.
Browse related tools or open the full workspace.