How to Password Protect a PDF (Free & Paid Methods)

Which One Are You?

• Individual user: you have one PDF, maybe a handful, and you want it locked before you send it. 
• IT admin / enterprise: you’re protecting dozens or thousands of files, across departments, on a deadline, and someone’s asking about audit logs. 

Individual User: Password Protect a PDF for Free

Quick answer: Mac users can do this natively with Preview. Windows and Linux users can do it for free with LibreOffice or the open-source command-line tool qpdf. None of these require installing anything shady, and none of them cost money.

Try the Trial Download →

What “Password Protecting” actually means

A PDF has two separate passwords, and mixing them up causes most of the confusion:

• Open password (user password): Encrypts the file. Nobody can even view it without the password.
• Permissions password (owner password): Doesn’t encrypt anything. It restricts what a viewer can do print, copy text, edit, but any halfway-decent PDF tool can strip these restrictions in seconds. Don’t rely on it to protect anything sensitive.

If you actually need privacy, you want an open password with AES-128 or AES-256 encryption. Anything less is a speed bump, not a lock.

Method 1: macOS Preview

Preview has had this built in for years, and it still works the same way in the current macOS release.

1. Open the PDF in Preview.
2. Go to File > Export.
3. Check the Encrypt box.
4. Type your password twice to confirm.
5. Click Save.

Preview uses AES-128 encryption. It’s fine for personal files. It won’t help you if you have 40 PDFs to protect before 5pm, there’s no batch mode.

Method 2: LibreOffice Draw

This is free, cross-platform, and actively maintained, so it isn’t going away. One catch: it works best when you export a document to a protected PDF for the first time. If you already have an unprotected PDF and need to lock it, open it directly in LibreOffice Draw instead of Writer, Draw can open existing PDFs.

1. Open the PDF in LibreOffice Draw (File > Open).
2. Go to File > Export As > Export as PDF.
3. In the export dialog, click the Security tab.
4. Click Set Passwords, enter an open password (and an optional permissions password), then confirm.
5. Click Export.
   

If your source file is a Word document rather than a finished PDF, skip Draw and export straight from Writer, same Security tab, same steps.

Method 3: qpdf (Command line, Free, Batch-Capable)

If you’re comfortable with a terminal, qpdf is the fastest free option and the only one on this list that handles more than one file without manual clicking.

qpdf --encrypt <user-password> <owner-password> 256 -- input.pdf output.pdf

Replace 256 with 128 if you need broader compatibility with older PDF readers. To loop through a folder on macOS or Linux:

for f in *.pdf; do
  qpdf --encrypt mypassword "" 256 -- "$f" "protected_$f"
done

On Windows, the same loop works in PowerShell with minor syntax changes. This is genuinely the free method IT admins reach for, see the next section.

Where the Free Methods Break Down

• No error recovery: If a PDF is even slightly corrupted, qpdf and LibreOffice both fail with a raw error message and no fix.
• No password auditing: You have no record of which file got which password, so six months later nobody remembers.
• No permission granularity in bulk: Setting “allow printing but not editing” across 200 files means writing your own script for each variation.
• Google Docs can’t do this at all: Exporting to PDF from Google Docs strips out any password option entirely, there’s no workaround inside Docs itself, you have to protect the file after export using one of the methods above.

When to Reach for the Tool Instead

If you’re protecting one file a month, the free route is genuinely fine, use it. If you’re protecting client deliverables regularly and you’d rather not remember qpdf syntax every time, PDF Protection Tool gives you the same AES-256 encryption in a GUI: pick files, set a password, done. Preview before you pay, so you know it works on your actual files first.

Download the Free Trial →

Where Protected PDFs Fit in your Workflow

Once a PDF is encrypted, it behaves like any other file for storage and sharing, Google Drive, OneDrive, Dropbox, or straight email attachment all work, because the encryption lives inside the file itself, not in the storage layer. The one thing to check: some company email gateways scan attachments for malware and can’t open encrypted files to do that scan, so a few IT departments block password-protected PDFs at the gateway. If your recipient reports the file “didn’t come through,” that’s usually why ask them to check with their IT team before assuming the file is broken.

Individual User takeaway: if you send sensitive PDFs occasionally, LibreOffice or Preview costs you nothing. If it’s a weekly habit, a dedicated tool saves you the repeated manual work and the mistakes that come with it.

IT Admin / Enterprise: Bulk PDF Password Protection

Quick answer: For under ~20 files, qpdf scripted in a loop works and costs nothing. Past that, you’re maintaining a script, and the failure modes – corrupted files, inconsistent permission sets, no audit trail become your problem at 2am. That’s the point where a dedicated bulk tool earns its license fee.

Why Manual Scripting doesn’t Scale

A qpdf loop works until one of these happens, and eventually one of them always does:

• A file in the batch is corrupted or has an unusual internal structure, and the whole loop stops or silently skips it.
• Someone needs a different permission set for HR files versus finance files, so you’re now maintaining two scripts, then five.
• Legal asks which files were protected, when, and by whom, and you have no log because the script never wrote one.
• A new hire needs to run this next quarter, and they don’t know what qpdf is.

None of this means qpdf is bad, it’s a solid tool for a one-off job. It means a one-off script isn’t infrastructure, and treating it like infrastructure is how you end up debugging a batch job during a compliance audit.

Batch Protecting with qpdf at Scale

If you’re staying manual, at minimum wrap the loop with logging and error handling:

This gets you closer to audit-ready, but you’re still writing and maintaining this yourself, and it still can’t set different permission tiers by folder without more branching logic.

Bulk Protection with PDF Protection Tool

PDF Protection Tool handles the parts the script doesn’t: it processes an entire folder in one pass, flags files it couldn’t process instead of silently failing on them, lets you set open and permissions passwords per batch, and gives you a completion report you can hand to compliance without editing it first. Preview the batch results before you pay for a license, so you’re not buying blind.

Manual vs. Tool: Head-to-Head

Compliance Considerations

Password protection alone doesn’t make you GDPR or HIPAA compliant, it’s one control among several (access logging, retention policy, breach notification process are separate requirements). What it does do: it satisfies the “encryption of data in transit and at rest” line item that most internal security policies and several regulatory frameworks require for documents containing personal or financial data. If your policy specifies a minimum encryption standard, confirm it’s AES-256 before you standardize on a method, some older free tools still default to AES-128 or the weaker RC4 standard.

Licensing and Rollout

SysInfoTools offers volume licensing for teams protecting files across multiple machines or departments, worth asking about if you’re rolling this out past a single admin’s laptop. Every purchase includes a money-back guarantee, and the trial version lets you run it against your actual files before any purchase conversation happens, so procurement isn’t approving something nobody’s tested.

Email Sales for Volume Pricing →

IT Admin takeaway: script it yourself if the job is small and occasional. Once you’re protecting files as a recurring process with compliance requirements attached, the audit trail and error handling you’d have to build yourself are exactly what you’re paying for.

Frequently Asked Questions

About The Author:

Simran Bhatia

Simran Bhatia is a technical content writer engaged in writing clear, concise, and SEO-optimized content. With a background in computer science and a passion for writing, I thrive to deliver complex technical content in simple layman terms.