Drag & Drop a PDF file here
or click to choose a PDF from your device
✅ PDF Files · One File at a TimeLock a PDF with a document-open password and optional printing, editing and copying permissions. Create an encrypted PDF copy directly in your browser while keeping the original document unchanged.
Choose a PDF, create a strong opening password, review optional permissions, and download a newly encrypted copy. Passwords and document bytes are processed in your browser.
Drag & Drop a PDF file here
or click to choose a PDF from your device
✅ PDF Files · One File at a TimeThe encrypted file was created locally. Test it with the opening password before sharing.
A focused browser tool for adding access control to documents before emailing, uploading, archiving or sharing them.
Create a protected copy while keeping the original PDF untouched.
PDF security combines encryption, passwords and viewer permissions. Understanding the difference helps you choose settings that match the real risk.
To protect a PDF file with an opening password means the document is encrypted so that a PDF viewer must derive the correct encryption key before it can display protected strings and streams. This is materially different from placing a password in a file name, hiding a download link or adding a visible “confidential” watermark. An encrypted PDF is designed to keep the document unreadable when the opening password is unknown.
QPDF explains that the PDF standard security handler can use a user password and an owner password to recover the document encryption key. The user password is normally the one a recipient enters to open a protected PDF. The owner password can permit full access or allow security settings to be changed in applications that follow the standard behaviour. You can review the technical concepts in the official QPDF encryption documentation.
The most important setting is the password required to open the document. If that password is strong and the PDF uses modern encryption, it creates a genuine access barrier. Printing, editing and copying controls are different. They are flags that tell conforming readers which actions a user should be allowed to perform after opening the file. QPDF's documentation notes that software capable of reading an encrypted file possesses the encryption key and could be modified to ignore permission restrictions. Therefore, permission flags are useful workflow controls, but they are not absolute DRM.
Adobe's current desktop guidance similarly separates password protection for viewing from password controls for editing, printing or copying. Its documented workflow allows a user to choose protection for viewing or editing before applying the password. See Adobe's official Add passwords to PDFs guide for the Acrobat approach.
Older PDFs may use 40-bit RC4, 128-bit RC4 or 128-bit AES encryption. QPDF recommends using 256-bit encryption unless there is a strong compatibility reason not to. Its security documentation describes 40-bit encryption as easily brute-forced and RC4 as insecure, while 256-bit PDF encryption uses AES. This page therefore presents one clear modern option rather than encouraging weak legacy settings.
Password protection does not prove who created the PDF, confirm that the document has not changed, redact visible information, remove metadata, scan for malware, or prevent an authorised reader from taking screenshots or photographs. Digital signatures, redaction, metadata cleaning, access-control systems and organisational policies solve different problems. Use the correct combination for the sensitivity and legal context of the document.
These controls work together, but they do not provide identical protection.
| Security Control | Main Purpose | Who Uses It? | Important Limitation |
|---|---|---|---|
| Document-open password | Encrypts access to PDF content | Every authorised reader | Strong access control when password is secret |
| Owner password | Manage or override permissions | Document owner or administrator | Must be stored safely and preferably be different |
| Printing restriction | Requests full, low-resolution or no printing | Conforming PDF viewers | Viewer-enforced, not absolute DRM |
| Modification restriction | Controls editing, forms, comments and assembly | Conforming PDF editors | Behaviour varies by application |
| Extraction restriction | Discourages copying text and graphics | Conforming readers and editors | Cannot stop screenshots or deliberate bypass |
Encryption strength matters, but the practical security of a protected PDF often depends on the password and how it is shared.
Use at least 12 characters and preferably 16 or more for sensitive files. A sequence of unrelated words can be easier to remember than a short complex password.
A PDF password should not be the same as your email, cloud-storage, banking or workplace sign-in password.
Do not use the recipient's name, invoice number, date of birth, company name or the word “password” unless mixed into a much stronger random phrase.
A reputable password manager can generate and store a long random password, reducing the temptation to reuse weak credentials.
Do not place the password in the same email as the protected PDF when the document is genuinely sensitive. Use another verified channel.
Open the downloaded PDF in a separate reader, enter the password manually, and verify all pages, links, forms and attachments.
Password protection is useful when a document must leave its normal storage environment but should not be openly readable.
A password is one control in a wider process. Use these steps when the document contains material that should not be publicly accessible.
Redaction permanently removes content from the released copy. Password protection encrypts access to whatever remains in the file. If a page contains information that the recipient should never receive, redact or remove it before adding the password. Drawing a black rectangle over text is not necessarily secure redaction because underlying text may remain extractable.
A digital signature helps recipients evaluate document integrity and signer identity; an opening password limits access. Because encryption rewrites PDF structures, the safest sequence is usually to prepare and protect the PDF before applying the final digital signature. Organisational or regulatory workflows may have specific requirements, so test the order with the actual signing platform.
A protected PDF remains protected after download, but cloud platforms may also offer link expiry, authentication, view-only access, audit logs and remote revocation. For highly sensitive documents, a managed portal can provide stronger lifecycle control than attaching a standalone file. The PDF password can still serve as an additional layer when permitted.
The document is handled by browser APIs and a WebAssembly build of QPDF, so a normal server-side conversion upload is not required.
The selected file is read into browser memory, written into the temporary file system exposed by the QPDF WebAssembly module, encrypted, read back as output bytes and downloaded as a Blob. The page loads program code from a content-delivery network, but the conversion logic does not need to post your PDF to that network.
WebAssembly processing depends on available device memory, browser security policy and access to the required QPDF runtime files. Very large PDFs may exhaust memory on mobile devices. Close other demanding tabs, use a current desktop browser, and process only documents you are authorised to protect. If the encryption engine cannot load because a content-security policy blocks the runtime, use a trusted desktop PDF application instead.
Local conversion reduces exposure during the protection step, but the security of the final workflow also depends on where you save the file, how you transmit it, who receives the password, whether devices are compromised, and whether backups are protected. A strong password cannot correct a message sent to the wrong recipient.
Most problems are caused by an invalid source file, an existing password, browser memory limits or blocked WebAssembly resources.
Renaming another file to .pdf does not create a valid PDF. Open the source in a PDF viewer or export it again from the original application.
Enter the current authorised source password. The tool cannot bypass an unknown password or recover access to a document you do not control.
Passwords are case-sensitive and may contain spaces. Retype the password carefully and check the show-password control.
Network filtering, script blockers or a restrictive content-security policy can block the QPDF JavaScript or WebAssembly file. Allow the required CDN resources or use a desktop tool.
Large scans and image-heavy PDFs can require several times their file size in working memory. Try a desktop device and close other tabs.
Printing, editing and copying permissions depend on reader compliance. Rely on the opening password for access control, not on permission flags alone.
Prepare the document before protection so the final encrypted copy contains only the pages and information you intend to share.
Clear answers about passwords, encryption, owner controls, permissions, privacy, compatibility and secure sharing.
Choose a PDF, create a strong opening password, set optional permissions and download a protected copy from your browser.
🔒 Open Protect PDF Tool ↑