Batch Remove PDF Passwords

The four realistic methods

Pick based on your volume, tooling budget, and whether the password is known. The rest of this article covers each in detail.

Method 1: Adobe Acrobat Action Wizard

Acrobat Pro's Action Wizard is the go-to for teams without scripting experience. You build a reusable "action" once and apply it to an entire folder. The workflow:

1. Open Acrobat Pro DC. Go to Tools and pick Action Wizard.
2. Click New Action. Add the Encrypt step and configure it with No Security. Save as "Remove Password Protection."
3. Click Add Files > Add Folder, point at the folder of locked PDFs, and set an output directory.
4. Run the action. When a file prompts for its password, enter it once and Acrobat will remember it across the batch for any file sharing that password.

This method caps out around 500 files before UI sluggishness becomes a problem. Acrobat's JavaScript engine runs each file through its parser, which is thorough but not fast. For larger batches, move to command-line tooling.

Method 2: qpdf command line

qpdf is an open-source PDF transformation tool and the fastest reliable way to batch-decrypt. It's available on every major platform and has no GUI overhead. Install it once:

# Windows (Chocolatey)
choco install qpdf

# macOS (Homebrew)
brew install qpdf

# Linux (Debian/Ubuntu)
sudo apt install qpdf

A single file decryption looks like this:

qpdf --password=MyPass123 --decrypt input.pdf output.pdf

To batch a whole folder with a shared password, use a bash loop on macOS/Linux:

mkdir -p unlocked
for f in locked/*.pdf; do
  qpdf --password=MyPass123 --decrypt "$f" "unlocked/$(basename "$f")"
done

On Windows with PowerShell:

New-Item -ItemType Directory -Force -Path .\unlocked | Out-Null
Get-ChildItem .\locked\*.pdf | ForEach-Object {
  qpdf --password=MyPass123 --decrypt $_.FullName ".\unlocked\$($_.Name)"
}

qpdf exits with code 0 on success, 2 on warning, and 3 on error. Check $LASTEXITCODE (PowerShell) or $? (bash) if you need to log failures for manual review.

Method 3: per-file passwords from a CSV

If each PDF has its own password, maintain a mapping file. A simple CSV with filename and password columns is enough. Save it as passwords.csv:

filename,password
2024-Q1-report.pdf,Finance!2024
2024-Q2-report.pdf,Budget#Q2
2024-Q3-report.pdf,Audit$Q3

PowerShell loop that reads the CSV and applies each password:

Import-Csv .\passwords.csv | ForEach-Object {
  $in = ".\locked\$($_.filename)"
  $out = ".\unlocked\$($_.filename)"
  qpdf --password=$($_.password) --decrypt $in $out
  if ($LASTEXITCODE -ne 0) {
    Write-Warning "Failed: $($_.filename) (exit $LASTEXITCODE)"
  }
}

Store the CSV in an access-controlled location. A plaintext list of passwords is as sensitive as the PDFs themselves. Delete it after processing, or store it in a secrets manager if the mapping needs to be retained.

Method 4: managed recovery when passwords are unknown

When a batch contains files with unknown passwords (mergers, departed employees, legacy archives), scripted removal will not work. You need recovery. Our service handles batch recovery with volume pricing; single-file pricing starts from our home page, and volume deals for 50+ files are negotiated via contact.

Expected costs scale with encryption:

• 40-bit RC4 (Acrobat 3-4 era): near-guaranteed recovery. See 40-bit PDF recovery. Volume price typically $3-10 per file.
• 128-bit AES: probabilistic. Volume price typically $10-20 per file with a "pay only on success" model.
• AES-256: depends heavily on password strength. Volume price $20-50 per successful recovery.

ROI for business batch processing

Let's run the numbers for a realistic scenario: a finance team with 1,000 password-protected bank statements from a predecessor system, all using the same departmental password that has been recovered.

For known shared passwords, qpdf scripting beats every other option on cost. For unknown passwords, the managed service is the only option that produces any output at all.

Common pitfalls

Automation beyond the one-shot script

For recurring workflows (monthly bank statements, quarterly reports), wrap the qpdf loop in a scheduled task:

• Windows Task Scheduler: run the PowerShell script nightly, pointed at a "drop" folder; move completed files to an archive.
• macOS launchd / Linux cron: same idea with a bash wrapper.
• Azure Functions / AWS Lambda: event-triggered on S3/Blob upload, call qpdf in a container, write decrypted output to a different container. Works well for 100k+ files.
• Power Automate: if your team already uses the Microsoft stack, a flow can monitor a SharePoint folder and trigger a local qpdf run via on-premises gateway.

In all of these, store the password in a vault (Azure Key Vault, AWS Secrets Manager, or equivalent) and inject it at runtime rather than hardcoding it in the script.

Frequently asked questions