All notable changes to PDF Batch Suite are documented here.
Renamed from PDF Power Tools to PDF Batch Suite and repositioned around secure
batch document preparation. Three new operations.
- rotate – turn every page 90°, 180° or 270° (negative angles rotate counter-clockwise)
- pageNumbers – stamp page numbers or Bates numbers onto every page
(
{n} / {total} / {filename} tokens, zero-padding, 9 positions, font control)
- sanitize – strip embedded JavaScript, file attachments, XMP metadata and the
document information dictionary before a PDF leaves your organisation
- Actor name is now
pdf-batch-suite; store title PDF Batch Suite
- README rewritten around "the PDFs you assemble and send" and an explicit
"not a PDF-to-text scraper" scope note
- Input, dataset and roadmap updated for the nine operations
First public release.
- merge – combine all input files into one PDF (list order or sorted)
- split – break a PDF into parts by page numbers or every N pages (ZIP output)
- watermark – stamp a diagonal text watermark on every page
- compress – reduce file size while keeping the PDF readable
- protect – add a password / 40-, 128- or 256-bit encryption
- decrypt – remove a known password
- Batch input:
https:// URLs, kvs://STORE_ID/KEY references, bare key-value store keys, or data: URIs
- Batch isolation – one bad file never aborts the run; you get a failed row instead
- Pay-per-event pricing:
actor-start + file-processed (successful outputs only)
- Self-contained PDF engine; nothing is added to the output and no file leaves the Actor
- Dataset + key-value store output schema for API / AI-agent consumption
- First operation of a run waits ~30–45 s for the embedded PDF engine (JVM) to boot
compress returns the original file when the source is already optimised
- OCR and text extraction are intentionally out of scope