Save a PDF Workflow and Run It Again
A saved workflow is the order you run tools in and the settings you use. It records no document, so re-running one always asks you for a file.
Written against the Sep 12, 2026 release·what has changed since
Some document jobs are a single step. Most of the tedious ones are not. Turning a phone scan into something you can send usually means rotating it upright, recognising the text so it can be searched, compressing it to fit an upload limit, and numbering the pages. Doing that once is fine. Doing it every week, and trying to remember which compression mode you used last time, is the part worth automating.
A workflow is a recipe, not a file
A saved workflow records two things: which tools you ran, in what order, and the settings you ran each of them with. It records nothing about the document you happened to be working on. Not its name, not its contents, not a pointer to it.
That is why re-running a workflow always asks you for a file. It is not an oversight to be fixed later. A record that cannot name a document cannot leak one, and on a site whose whole promise is that documents stay in your browser, that boundary is the design rather than a limitation of it.
Workflows worth saving
- 1
The scan cleanup
Rotate upright, recognise text, compress. Useful for anything that arrived as a photograph of paper.
- 2
The submission packet
Merge the parts in order, number the pages, then flatten so nobody can edit the fields you filled in.
- 3
The archive copy
Compress losslessly, then protect with a password before it goes anywhere shared.
Order matters more than people expect
Two orderings that look interchangeable are not. Numbering before merging numbers each part separately, so the finished document restarts at one partway through. Flattening before filling bakes an empty form. Compressing to raster before recognising text gives the recognition a worse image to work from.
Where to build one
The tools hub lists everything a workflow can be made of, and the power tools guide walks through chaining them by hand first. Once a tool has done what you wanted, Save this as a workflow appears under the result; run the next tool and add it to the same workflow, and the order you worked in is the order that is kept. Your account page lists them afterwards, and opening a step takes you back to that tool with its settings waiting.
The short version
- A workflow stores tool order and settings, never a document.
- Re-running one always asks for a file, by design.
- Order changes the result: number after merging, flatten after filling.
- Protecting and splitting end a chain.
Merge PDF files
Combine PDF pages in the exact order you choose.
Was this article helpful?
Your answer stays in this browser. Nothing is sent to us. See how it works.
Keep reading
Reviewed and maintained by
Novus Stream Solutions Editorial Team
The Novus Stream Solutions Editorial Team maintains Novus PDF Studio's product documentation, tutorials and PDF explainers. The team checks product claims against the current browser-local implementation and tests, prefers primary specifications and vendor documentation, and corrects material errors openly. The byline identifies the responsible organization; it does not imply a named expert or professional adviser.
Privacy note: every tool mentioned in this article runs entirely in your browser. Nothing is uploaded or queued on a server. A PDF stays in the tab unless you explicitly use Save on this device, which stores that session in this browser without storing passwords. More on the how it works page.