PDF Protect Plus
FR EN

You have forty statements to send to forty clients, and each client must only be able to open their own file. So you need to password protect multiple PDFs with a different password for each one, and you would rather not do it forty times by hand. This guide compares three ways to get there: the PDF editor you already have, a short script for people who are comfortable with a command line, and a spreadsheet-driven batch in PDF Protect Plus. Each has its place. The right one depends on how many files you send, and how often.

Why not one password for everyone?

It is the quickest option, and it is the reason people go looking for something better. If one client forwards their email or shares the password, every other client's file is now protected by a secret that is no longer secret. A shared password also tends to be guessable, because it has to be easy to tell forty people. A different password per client keeps one person's slip from becoming everyone's problem.

First, decide where the passwords come from

Whatever the tool, the method that holds up over a year is the same: one fixed password per client, written down once in a spreadsheet. The client learns it once and uses it for every document you send them. You stop inventing passwords on the day of the mailing, and nobody calls to ask which one it was this time.

A workable password is at least 12 characters long. Three or four unrelated words joined by hyphens, plus a number, are easy to dictate over the phone and hard to guess. Avoid anything a stranger could work out: the client's name, a date of birth, the firm's name followed by the year.

Keep that spreadsheet as carefully as you keep your client files. It holds every password in plain text.

Method 1: the PDF editor you already have

Most offices own a general-purpose PDF editor, and most of those editors can add a password. For a single file, that is perfectly good: open the document, choose the protection option, type the password twice, save.

The trouble starts with a batch. The batch feature of these editors applies one security setting to every file in the run, which means the same password for all of them. To give each client their own, you are back to one run per client, or one file at a time.

What that costs in practice:

Use it when you send a handful of protected documents a month and the software is already paid for.

Method 2: a qpdf script, for the technically minded

qpdf is an open-source command-line tool that can encrypt a PDF with AES-256. With a few lines of script around it, it will password protect multiple PDFs with a different password for each file, reading the pairs from a CSV. If you have never opened a terminal, skip to method 3: this one is for the colleague who writes the office macros.

Create a file named passwords.csv in the same folder as your PDFs, with two columns:

file,password
dubois-2025-statements.pdf,Blue-Harbor-Lamp-47
oakridge-2025-statements.pdf,Quiet-Maple-River-82
carter-2025-statements.pdf,Amber-Stone-Kite-19

On macOS or Linux, this loop writes the protected copies to a protected folder and leaves the originals alone:

mkdir -p protected
tr -d '\r' < passwords.csv | tail -n +2 | while IFS=, read -r file password; do
  qpdf --encrypt "$password" "$password" 256 -- "$file" "protected/$file"
done

On Windows, the same idea in PowerShell:

New-Item -ItemType Directory -Force protected | Out-Null
Import-Csv passwords.csv | ForEach-Object {
  qpdf --encrypt $_.password $_.password 256 -- $_.file "protected\$($_.file)"
}

It works, and it costs nothing but your time. Before you rely on it, know its sharp edges:

Use it when someone in the office is comfortable with scripts, the file names are clean, and you can test on copies first. Always open two or three of the protected files with their passwords before you send anything.

Method 3: a CSV spreadsheet and a batch in PDF Protect Plus

This is the method we built, so read it with that in mind. PDF Protect Plus is a paid desktop app for Windows and macOS. Its Batch protection tab does the same job as the script, with the checks the script lacks.

The spreadsheet has one row per client: their name, their password and, only when needed, the exact file name.

client,password,file
Martin Dubois,Blue-Harbor-Lamp-47,
Oakridge Plumbing LLC,Quiet-Maple-River-82,
Jane Carter,Amber-Stone-Kite-19,2025-statements-JC.pdf

Then four steps:

  1. Drag your PDFs into the tab, up to 200 per batch, and choose My clients' passwords.
  2. Import the CSV, or drop it in together with the PDFs.
  3. Check the orange rows. The app matches each file to a client by looking for the client's name in the file name, and it flags what it is unsure of: To confirm when two clients could match, Client not found, or Too weak for a password under 12 characters.
  4. Choose a folder and protect. The copies are encrypted with AES-256 and numbered; your originals are not touched.
Imported spreadsheet: 38 files matched, one orange line to confirm and one weak password
Method 3: each file finds its client in the spreadsheet; the orange rows are settled before anything is encrypted — Actual PDF Protect Plus interface · fictional documents

Three things differ from the script. Nothing is encrypted until every row is settled, so a mismatch is caught before a file leaves, not after. The batch is created in full or not at all. And the app can write a sending summary, a list of which client gets which file, with no passwords in it, to tick off as you send the emails.

All 40 files matched, with the vault and sending summary options
Every file is matched; the sending summary lists who gets which file, with no passwords — Actual PDF Protect Plus interface · fictional documents

Everything runs on your computer: neither the PDFs nor the spreadsheet are sent to our servers. Only your account and license need an internet connection.

“40 files protected successfully” window, passwords saved in the vault and summary created
A batch of 40 files, each with its own password, protected in one run — Actual PDF Protect Plus interface · fictional documents

Use it when protected mailings come back every month or every tax season, and the person doing them should not need a terminal. The full walkthrough, screen by screen, is on the batch protection page, and the pricing page lists the plans.

Which method should you pick?

Whatever you choose: three rules for sending

  1. Never put the password in the same email as the PDF. Send it by text message, or give it once by phone at the start of the engagement. Our guide on how to send a PDF password separately has wording you can copy.
  2. Test before you send. Open a few protected files with the passwords from your spreadsheet.
  3. Keep the originals and the spreadsheet apart from the protected copies. What you email is the copy; what you archive is yours.

Try the spreadsheet method on a test batch

If method 3 fits your office, download PDF Protect Plus and run a batch of five or six sample files during the 7-day trial. For the full accountant's workflow, from naming the files to the sending summary, see how to batch-protect client PDFs with one password per client. And if your spreadsheet does not exist yet, this guide shows how to create it.

Related reading