PDF Bulk Password
Password-protect PDFs in bulk without touching the originals.
Overview
PDF Bulk Password is a lightweight command-line utility for applying password protection to multiple PDF documents in a single operation. Apply one common password to every PDF in a folder or assign individual passwords using a simple CSV password list.
Protected copies are created with AES-256 encryption and written to a separate Protected subfolder. Source PDFs are treated only as inputs and are never modified, overwritten, or deleted.
Key capabilities
Bulk PDF processing
- Processes all PDF files in a specified folder in one operation.
- Handles errors per file so a problem with one document does not stop the remaining work.
- Provides detailed
--helpcontent covering usage, examples, password-list formatting, output behavior, security considerations, and exit codes.
Two password modes
- Use
--passwordto apply the same password to every PDF in the folder. - Use
--password-fileto assign a different password to each PDF from a CSV list.
Simple CSV password lists
Password lists use two columns. PDF filenames are specified without the .pdf extension.
filename,password
Drawing-001,ExamplePassword1
Drawing-002,ExamplePassword2
Drawing-003,ExamplePassword3
AES-256 encryption
Protected PDF copies are created using AES-256 encryption.
Non-destructive output
- Original PDF files are preserved without modification or deletion.
- Protected copies are automatically placed in a separate
Protectedsubfolder. - If a corresponding protected PDF already exists, the utility reports the conflict instead of overwriting the file.
PDF Files\
Drawing-001.pdf
Drawing-002.pdf
Protected\
Drawing-001.pdf
Drawing-002.pdf
Password-safe results and logging
- Passwords are never displayed in processing results.
- Passwords are never written to result logs.
- Use
--log-resultsto write processing results and summary information to a timestamped log file.
Safety by design
PDF Bulk Password deliberately leaves original PDF documents untouched. Protected copies are created separately so they can be verified before any independent decision is made about retaining or deleting the source documents.
--password may be visible through command-line history or process inspection. For workflows where that matters, use the --password-file approach and protect the CSV file appropriately.