You can password protect a PDF in about 30 seconds inside Adobe Acrobat, macOS Preview, or the free desktop version of PDF24, and all three support the same two-layer protection: an open password that blocks viewing and a permissions password that blocks printing, copying, and editing. The catch most guides skip is encryption strength. Older tools still default to 128-bit AES or weaker, so the protection you get depends entirely on which method you use and which encryption level you select.
What an Open Password and a Permissions Password Actually Do
An open password, sometimes called a document open password or user password, encrypts the file so nothing renders until the correct string is typed. A permissions password, also called an owner password, leaves the file readable but locks printing, text copying, and editing behind a restriction flag.
The two layers fail in different ways. A permissions password does not scramble the contents. Anyone with a third-party PDF editor can strip printing and copying restrictions in seconds, so treat that layer as a deterrent against casual sharing, not a security control. An open password does scramble the contents, and its real strength comes from the encryption algorithm behind it.
Adobe's own Acrobat documentation describes the available levels as 128-bit RC4, 128-bit AES, and 256-bit AES, with 256-bit AES the only option that meets the current PDF 2.0 standard. If a tool offers you the choice, pick 256-bit AES every time; the extra processing cost on a modern laptop is negligible for files under a few hundred megabytes.
One practical boundary matters before you start. In Acrobat on Windows, 256-bit AES requires Acrobat 9 or later and Adobe Reader 9 or later on the receiving end, which is not a limitation in 2026 but is worth knowing if you send files to organizations running locked-down legacy software. If a recipient cannot open the file, downgrading to 128-bit AES is the standard fix.
Before You Encrypt: Fix the Two Mistakes That Lock People Out
The first failure case is not choosing a weak password. It is encrypting a file that is already broken. If the PDF has a corrupt cross-reference table, some tools will still wrap it in encryption and produce a file that fails to open even with the right password. Open the PDF in a viewer first, scroll to the last page, and confirm it renders cleanly before you protect it.
The second mistake is losing the password. There is no recovery path built into PDF encryption by design. Adobe's documentation states plainly that if you forget an open password, you cannot recover it, and Adobe support will not help. A permissions-only password is different: tools like PDF24 and several paid utilities can remove restrictions without the owner password because the content was never encrypted.
Build a naming habit before you touch any tool. Save the unprotected original under a name like contract-draft.docx-source.pdf, then export the protected copy as contract-final-protected.pdf. That single step means a forgotten password costs you a re-export, not a lost document.
Method 1: Adobe Acrobat Pro in Eight Clicks
Acrobat Pro is the paid reference implementation, and its path is the one every other guide copies. The current desktop layout uses the Tools tab rather than the old File menu, which is where most outdated instructions go wrong.
1: Open the PDF in Acrobat Pro and select Tools in the upper-left toolbar. 2: Choose Protect from the tool panel, then click Protect again inside that panel. 3: In the dialog, select Encrypt with Password and click Yes when prompted to confirm. 4: Tick Require a password to open the document and type the open password. 5: Set the Compatibility dropdown to Acrobat 9.0 and later to unlock 256-bit AES. 6: Tick Restrict editing and printing if you need a permissions password, then choose what to allow. 7: Click OK, retype the password to confirm, and save the file with File > Save As. 8: Close and reopen the file to verify the password prompt appears.
Step eight is the one people skip. Reopening confirms the encryption actually applied, because a failed save leaves the original unencrypted while the menu still shows a lock icon.
If Acrobat refuses to save, the usual cause is a digitally signed document or a file with usage rights attached from a previous DRM export. Strip those first with File > Save as Other > Optimized PDF, then retry. Acrobat Pro is included in Creative Cloud All Apps, and a standalone Acrobat Pro subscription exists separately; confirm current pricing on Adobe's site, since plan structure changes.
Method 2: macOS Preview and the 128-Bit Limitation
Preview ships free with every Mac, and it is the fastest route for a single file. Open the PDF, choose File > Export, and tick the Encrypt checkbox in the export dialog. Enter the password twice, then click Save.
Preview's limitation is the one to remember: according to Apple's Preview documentation, the export dialog applies 128-bit AES encryption and offers no selector for 256-bit. That is adequate against casual access, but if your organization's policy names 256-bit AES as the floor, Preview fails the audit even though the file opens with a password.
The same export dialog offers no permissions controls at all. You cannot block printing or copying from Preview, so anyone who opens the file can do whatever a normal PDF allows. For a boarding pass or a personal tax form, that gap rarely matters. For a client contract with a no-print clause, it does.
On iPhone and iPad, the Files app can password protect a PDF through the same export flow, with the identical 128-bit ceiling. Test the protected file on a Windows machine before sending it to a mixed-platform team, because the most common Preview complaint is a recipient on an older reader seeing an error rather than a password prompt.
Method 3: Free Desktop Tools That Still Offer AES-256
The free route has improved considerably, and two desktop tools now cover most needs without a subscription.
PDF24 Creator for Windows is the strongest free option. Open the PDF in PDF24, choose the Protect PDF tool, enter a password, and select the encryption level from the dropdown; the tool exposes AES-256 as a selectable option rather than forcing a legacy default. It also supports separate open and permissions passwords in the same dialog.
LibreOffice Draw handles the job if you already use the suite. Open the PDF in Draw, choose File > Export as PDF, and in the export dialog expand General to find Encrypt with open password and Set permissions password. LibreOffice's export dialog labels its encryption level under the security tab; confirm the AES-256 option is selected rather than assuming the default.
The free tools share one honest drawback: their interfaces change between versions, and menu labels drift. If the steps above do not match your installed version, look for the terms "open password" and "encryption level" in the security or export dialog rather than hunting for an exact button name. That search habit survives every update.
Method 4: The iPhone and Android Route, Including the Scan Trap
On iPhone, open the PDF in Files, tap the share icon, choose Options at the top of the share sheet, then turn on Password and enter it. The protected copy saves back to Files. This is genuinely useful for scanned documents, and it inherits Preview's 128-bit encryption.
Android's native Files by Google has no PDF encryption feature as of the current release. You need a third-party app; Adobe Acrobat Reader for Android includes password protection behind an in-app subscription, and several PDF apps offer it free with ads. Confirm the encryption level inside the app's settings before trusting it with anything sensitive.
The scan trap catches people weekly. If you scan a document with your phone and email the scan directly, the scan app often sends an unprotected PDF before you ever get a chance to protect it. Scan to Files first, protect the file, then share the protected copy. Check the outgoing attachment's name for a "protected" suffix before you hit send.
How Long a Password Actually Holds: The Brute-Force Math
Encryption strength is meaningless against a weak password. A PDF protected with 256-bit AES and the password "1234" falls to a dictionary attack faster than a 128-bit AES file with a 20-character passphrase, because attackers target the password, not the cipher.
Do the arithmetic. A password of six lowercase letters has 26 to the sixth power, or roughly 309 million combinations. A password of twelve characters drawn from upper case, lower case, digits, and symbols has 94 to the twelfth power, which is about 4.7 times 10 to the 23rd combinations. That gap of roughly 15 orders of magnitude is the entire security story, and it dwarfs the difference between 128-bit and 256-bit AES.
A twelve-character random passphrase generated by a password manager is therefore the practical target. For files you send to people outside your password manager's reach, use a passphrase you can dictate over the phone, and send it through a different channel than the file itself. Sending the password in the same email as the attachment defeats the point.
Which PDF Protection Tool Fits Your Situation
The right tool depends on who receives the file and what policy applies, so compare on the dimensions that actually differ.
| Tool | Cost | Max encryption | Permissions password | Platform |
|---|---|---|---|---|
| Adobe Acrobat Pro | Paid subscription | 256-bit AES | Yes | Windows, Mac |
| macOS Preview | Free with macOS | 128-bit AES | No | Mac, iPhone, iPad |
| PDF24 Creator | Free | 256-bit AES | Yes | Windows |
| LibreOffice Draw | Free | 256-bit AES (selectable) | Yes | Windows, Mac, Linux |
| Acrobat Reader mobile | Subscription | 256-bit AES | Yes | iOS, Android |
The verdict splits cleanly by use case. If a compliance policy names 256-bit AES and you need permissions control, pay for Acrobat Pro or use the free PDF24 on Windows. If you are protecting a personal document on a Mac and only need an open password, Preview is faster than any alternative and the 128-bit ceiling is acceptable for the threat. If you work across platforms, LibreOffice Draw gives you 256-bit AES and permissions for zero cost, at the price of a clunky export dialog. The one real drawback of the free picks is support: when a dialog moves, you are reading release notes, not calling Adobe.
Sending Protected Files Without Breaking the Recipient's Workflow
Protection fails at the handoff more often than at the encryption step. Three recipient scenarios account for most of the complaints.
Recipients using automated intake systems are the sharpest edge case. Many contract management platforms, court filing systems, and HR portals reject password-protected PDFs outright, because their parsers cannot open encrypted files. If a portal accepts your upload and then shows a processing error, remove the open password and rely on the portal's own access controls instead.
Recipients on mobile often cannot type a complex passphrase comfortably, and some mobile mail clients strip attachments they cannot preview. Send a one-line message naming the file, then send the password separately by text or phone.
Recipients who need to extract text for accessibility tools hit the permissions wall. A file locked against copying cannot be read by screen readers in some configurations, which can create an accessibility compliance problem. If the recipient uses assistive technology, grant copying permission while keeping the open password.
Always keep the unprotected original until you have confirmation the recipient opened the file. That single habit converts every handoff failure into a two-minute fix.
When PDF Passwords Are the Wrong Control Entirely
Password protection is a per-file control, and some situations need a different mechanism. If you are sending more than a handful of documents to the same group, a shared encrypted archive or a document portal with user accounts beats fifty individually password-protected PDFs, because password distribution becomes the weak link.
Regulated data changes the calculus. Health records, financial account statements, and documents containing government identifiers often fall under rules that specify encryption standards and breach-notification duties. The article cannot tell you which rule applies to your jurisdiction, your industry, or your organization's policy. Confirm the required encryption level and retention rules with your compliance officer or a qualified professional before you send anything regulated.
The same caution applies to legal documents. A permissions password that blocks printing is not a legally binding execution control, and no PDF setting substitutes for a proper signature workflow. If a contract needs enforceable signing, use a dedicated e-signature service rather than a locked PDF.
FAQ
Does password protecting a PDF actually encrypt the file?
Yes, when you set an open password, the document contents are encrypted with the algorithm you selected, so a viewer cannot render anything without the key. A permissions-only password does not encrypt the content; it writes restriction flags that compliant readers honor. That difference is why an open password survives an attacker with a hex editor and a permissions password does not.
Can I remove a PDF password if I forget it?
You cannot remove an open password without the password, and Adobe states this explicitly in its documentation. A permissions password is different: because the content was never encrypted, restriction-removal tools can clear printing and copying locks without the owner password. Plan for the open-password case by storing the passphrase in a password manager before you export.
Is 128-bit AES good enough, or do I need 256-bit?
128-bit AES remains computationally infeasible to break by brute force, so the cipher is not your weak point. The practical reason to choose 256-bit is compliance: many organizational policies and standards name 256-bit AES as the required floor, and a 128-bit file fails that audit regardless of its real strength. Match your recipient's stated policy.
Why won't the recipient open my protected PDF?
The most common causes are an older reader that does not support the encryption level you chose, a mistyped password from a mobile keyboard, or an automated intake system that rejects encrypted files. Re-export at 128-bit AES compatibility for the first case, send the password by a separate channel for the second, and remove the open password for the third.
Can I protect a PDF on my phone for free?
On iPhone and iPad, yes, through the Files app's share sheet password option, which applies 128-bit AES encryption at no cost. On Android, the built-in Files app has no encryption feature, so free protection requires a third-party PDF app, and you should verify its encryption level before using it on sensitive documents.
Does a password-protected PDF stop someone from screenshotting it?
No. No PDF permission setting prevents a screenshot, a photograph of the screen, or a copy made by a viewer that ignores restriction flags. Permissions passwords deter casual misuse and support policy compliance; they are not a leak-prevention control. Treat any file you send as potentially reproducible.
How much does Adobe Acrobat Pro cost for this job?
Acrobat Pro is sold as a subscription, and Adobe restructures its plans periodically, so confirm the current price and whether Acrobat Pro sits inside Creative Cloud All Apps or as a standalone plan on Adobe's site before buying. If password protection is the only feature you need, the free PDF24 or LibreOffice route covers the identical encryption standard at zero cost.
What happens if I password protect a PDF that is already digitally signed?
Signing and encryption interact badly in several tools. Applying an open password after signing can invalidate the signature or lock the file against further signature validation, depending on the signing service. Protect the file before signing, or use the signing service's own access controls, and verify the signature still validates after any encryption step.