Workflows
The job you do every week, done in one run. Chain the tools together (merge, then shrink, then stamp), save the chain under your own name, and run it on the next folder that lands. Ready-made chains live on the preset gallery.
For the same few jobs in the same order, every week: build the chain once, then run files through it.
Take a starter chain or build your own
Drop files on the tray
Run the chain
Four ready-made chains. Read what each one does, then add it with its button; it lands in your saved chains below, ready to run.
Drop the files on the tray, or click to pick them
PDFs and images, as the chain needs · they stay on this device
Take a starter chain or build one, then drop files.
A chain is the tools, run in sequence in this page: merge deals PDFs into one file, compress works a file toward its target, split takes a page range, stamp writes a line of text onto every page, compress image works a photo toward its target. Each step hands its output to the next, and the run log prints every step's work per file, including the files a step could not use and passed through.
Two whole tools are not chain steps yet: background removal and reading a scan (OCR) cannot be added to a chain today, so a chain like cut out a photo, then shrink the cutout, cannot be built here yet. Both still work on their own pages. Chains run steps in order, on the files as they are; this page does not read your documents, so a chain cannot branch on what a file says. A chain lives only in this browser: it is not synced, shared or backed up, and a different browser starts empty. The steps are the five listed; steps that would need a server (sending, requesting, certifying) do not exist here.
A short list of jobs that run in order, each step's output feeding the next: merge these invoices into one file, then shrink it to 500 KB, in one run. On the leading PDF suite, chained jobs like this are a paid-plan feature. Here they are part of the workbench.
In this browser's own storage, on this device, like your job notes and settings. A chain holds its steps and settings only, never files. Clear the browser's site data and the chains go with it; nothing about them exists anywhere else.
It passes the file through unchanged and writes what happened in the run log: compress a photo with the PDF step and the photo simply continues to the next step. Nothing is silently dropped, and a step that fails stops the chain with the reason shown; your originals are never touched.
Nowhere. Every step runs in this page, in your browser, with the same engines as the single tools. Watch the network panel while it works if you want to check.