PDF Atelier logo: a sheet of paper with a penPDF Atelier
Sign in

Batch PDF

Do the same PDF job once, then apply it to every file in the queue

Batch PDF is the main professional upgrade: select many PDFs, configure an operation once and run it across the queue. Typical jobs include compressing a folder, applying the same watermark, removing metadata or password-protecting a client handover set.

  1. 1. Choose
  2. 2. Prepare
  3. 3. Process
  4. 4. Review & export
Choose PDFsDrop files here or browse. Files stay on this device — nothing is uploaded to run this tool.

Batch PDF runs locally in this browser tab.

The queue must be resilient. One malformed or password-protected file should not make the other 49 jobs disappear. Each item needs status, error details, retry and a predictable output name, followed by Download all as ZIP when processing finishes.

Questions about Batch PDF

What can I do with Batch PDF?
Batch mode should support operations that can be applied predictably across independent files, such as compression, watermarking, metadata removal, page numbering and password protection. More complex editor interactions should only be added when they can be parameterized safely.
What happens if one PDF fails during a batch?
The batch should continue. Failed files remain in the queue with a clear reason and a Retry action, while successful outputs stay available. Users should never have to restart a 100-file job because one input was malformed.
Can I use different settings for individual files?
The default batch model applies one configuration to the whole queue for speed and consistency. Advanced users can override a setting for an individual file before running, but the UI should make exceptions visually obvious.
How are output filenames handled?
PDF Atelier should preserve the original base filename and append an operation-specific suffix only when needed, for example `contract-compressed.pdf`. It must never silently overwrite a source file. ZIP downloads should maintain deterministic names and order.
Can Batch PDF handle password-protected files?
Yes when the user supplies the required password for each file. Passwords should live only in the active local session and never be saved inside a workflow. Files that cannot be opened should fail individually without blocking the queue.
Will processing many PDFs upload them to a server?
For batch operations implemented locally, each file is processed on the device. That increases privacy but also makes memory management important. The engine should process files sequentially or with a conservative concurrency limit instead of loading every large PDF into memory at once.
Is Batch PDF included in the free plan?
The Free plan can demonstrate a small batch allowance, while the 48-hour Atelier Pass and Plus plans unlock larger queues and professional batch limits. Exact limits should remain configuration-driven so pricing can evolve without changing page copy everywhere.

Related tasks