Can each merged PDF have a different password?

Yes. Passwords are generated from a template that references spreadsheet columns. For example, [[lastName]]-[[birthYear]] produces a unique password for each recipient — Chen-1990, Martinez-1988, etc. Every PDF gets a different password automatically.

What encryption does Mergram use?

Mergram uses RC4 128-bit encryption, which is compatible with all standard PDF readers including Adobe Acrobat, macOS Preview, Google Chrome, Mozilla Firefox, and Microsoft Edge.

Are passwords stored anywhere?

No. Passwords are generated on-the-fly during the merge process from your template. They are never stored in the database, logs, or API responses.

What happens if a recipient forgets their password?

Since passwords are derived from data the recipient already knows (like their last name and birth year), they can reconstruct it. You can also re-generate a specific PDF at any time.

Can I combine password protection with email delivery?

Yes. Send encrypted PDFs as email attachments. Each recipient gets their own password-protected PDF — they can only open their own document, not anyone else's.

Does encryption work with combined PDFs?

Password protection works with individual PDFs (each gets its own password). Combined PDFs use a single password for the entire document.

Password-Protected PDF Mail Merge

What Is Password-Protected PDF Mail Merge?

Password-protected PDF mail merge generates personalized PDFs where each document is encrypted with a unique password derived from your spreadsheet data. Instead of sharing a single password across all documents — or worse, sending sensitive files unencrypted — every recipient gets a PDF they can only open with their own credentials.

You define a password template using column names from your spreadsheet. During the merge, Mergram evaluates the template for each row, generates a unique password, and encrypts the corresponding PDF. The process is automatic and transparent.

Who Uses This?

HR and payroll teams — Distribute pay stubs and salary statements that only the intended employee can open
Legal departments — Send contracts, NDAs, and settlement agreements with per-party encryption
Healthcare providers — Deliver patient records, test results, and billing statements securely
Financial services — Issue account statements, tax documents, and investment reports privately
Insurance companies — Send policy documents, claims, and benefit summaries to individual policyholders
Educational institutions — Distribute grade reports and transcripts confidentially

How to Encrypt Merged PDFs

Step 1 — Design Your PDF Template

Upload your PDF template and place data fields exactly as you would for a standard mail merge. The template can include any field type — text, QR codes, barcodes, or images.

The password protection is applied after the merge, as a separate encryption step. It does not affect how you design or place fields.

Step 2 — Choose a Password Template

In the merge settings, define a password template that references columns in your spreadsheet. The template uses the same [[ColumnName]] syntax as field placement.

Common password templates:

Template	Example Output	Best For
`[[employeeId]]`	`EMP-42178`	Employee-specific documents
`[[lastName]]-[[birthYear]]`	`Chen-1990`	Documents where recipients know their own data
`[[invoiceNumber]]_[[zipCode]]`	`INV-0042_90210`	Client-facing financial documents
`[[memberId]]`	`MBR-7721`	Membership documents
`[[policyNumber]]`	`POL-2024-5531`	Insurance policies

Choose a password recipients can derive

Use data the recipient already knows — last name, birth year, employee ID, member number. This way they can open their PDF without you needing to communicate a separate password. Avoid random or generated passwords unless you have a secure channel to share them.

Step 3 — Preview the Results

Before generating the full batch, preview a few rows to verify the password template resolves correctly. Each row in the preview shows the generated password so you can confirm the pattern produces the expected values.

Check for edge cases:

Missing data — If a column value is empty, the password may be shorter than expected. Consider using columns that are always populated.
Special characters — Values with spaces, hyphens, or accents are included as-is in the password.
Case sensitivity — PDF passwords are case-sensitive. Verify the case of your spreadsheet data.

Step 4 — Generate Encrypted PDFs

Click Merge to start the job. Mergram processes each row:

Renders the personalized PDF with all field data
Evaluates the password template for that row
Encrypts the PDF with the generated password using RC4 128-bit encryption
Uploads the encrypted file for download or email delivery

Encryption standard

Mergram uses RC4 128-bit encryption, the most widely supported PDF encryption standard. Encrypted PDFs open correctly in Adobe Acrobat, macOS Preview, Google Chrome, Mozilla Firefox, Microsoft Edge, and all major PDF readers on iOS and Android.

Use Cases

Pay Stubs and Salary Statements

Distribute monthly pay stubs to hundreds of employees. Each employee receives a PDF encrypted with a password derived from their own data — such as [[employeeId]] or [[lastName]]-[[birthYear]]. No employee can open another employee’s pay stub.

Contracts and Legal Agreements

Send executed contracts, NDAs, and service agreements to multiple parties. Each party receives their own encrypted copy. Use a password template based on party-specific data like [[contractId]] or [[partyName]]-[[signDate]].

Healthcare Records

Deliver patient records, lab results, and billing statements securely. HIPAA requires protected health information to be encrypted in transit. Password-protected PDFs add an extra layer of security beyond TLS. Use patient-specific data like [[patientId]] or [[lastName]]-[[dateOfBirth]] as the password.

HIPAA compliance

Password-protected PDFs are one component of a HIPAA-compliant workflow. Consult your compliance team for full requirements, including email encryption, access controls, and audit logging.

Financial Statements

Send account statements, tax forms, and investment reports to clients. Each document is encrypted so only the account holder can view it. Combine with email delivery for a fully automated distribution pipeline.

Insurance Documents

Issue policy documents, claims summaries, and benefit statements to policyholders. Use the policy number or member ID as the encryption password — the policyholder has this information already.

Combining Password Protection with Other Features

Encryption + Email Delivery

The most common workflow: generate encrypted PDFs and send them as email attachments. Each recipient gets their own password-protected PDF in their inbox. This eliminates the need to share download links or communicate passwords separately.

Encryption + Custom Filenames

Name each encrypted PDF with a descriptive filename using a template: PayStub_[[employeeId]]_[[period]].pdf. Recipients see a clear filename when they download or receive the attachment.

Encryption + QR Codes

Add a verification QR code to each encrypted PDF. The QR code can link to a verification page that confirms the document’s authenticity. Even if the PDF is shared, the QR code provides a way to validate it.

Best Practices

Use data the recipient already knows — Avoid passwords that require separate communication. Last name + birth year, employee ID, or policy number are ideal because the recipient can derive their password without contacting you.
Verify the password column is always populated — Empty cells produce weak or empty passwords. Use columns that are required fields in your data collection process.
Test with a small batch first — Generate a few encrypted PDFs and verify they open correctly with the expected passwords. Check across different PDF readers (Adobe Acrobat, Preview, Chrome) to confirm compatibility.
Don’t include the password in the email body — If you’re sending encrypted PDFs via email, do not include the password in the same message. The recipient should already know their password from the template pattern.
Combine with email delivery for automation — Encrypting and emailing in one step is more secure than downloading and forwarding manually. The fewer manual steps, the lower the risk of sending the wrong document to the wrong person.
Document your password template — If multiple team members use the same template, document the pattern so new team members can communicate it to recipients consistently.

Get Started

Protect your merged documents with per-recipient encryption in minutes. Upload a PDF template, connect your spreadsheet, define a password template, and generate — every PDF is automatically encrypted with a unique password.

Try Mergram free and generate your first password-protected mail merge today.