Do several things at once
Put operations in a row, drop in as many files as you like, and take the results away as one archive. Nothing is uploaded: the whole recipe runs in this tab.
Drop files here
Or paste them, or pick them from this device. Nothing is uploaded: the work happens in this tab.
Files in this tab
Nothing is loaded yet.
Steps
What it is called in the list, and what the archive is named.
No steps yet. Choose an operation below and add it.
It goes on the end, and reads what the step before it produces.
This check is deliberately coarse: an operation says what it can produce, not what these settings will make it produce, and how many files reach a step is not known until the run. So a recipe accepted here can still fail at a particular file — which is reported against that file, by name, rather than ending the run.
Run the recipe
Add at least one operation.
Saved recipes
A saved recipe is kept in this browser only. It holds the operations and the settings you typed, but never a password, never a document, and never any other file. Delete any of them here, or all of them at once.
The exported file is what `pagecraft recipe` reads, so it is the complete recipe — pictures and passwords included — wherever you chose to put it.
Nothing saved in this browser yet.
What this does
A recipe is an ordered list of operations and the settings to run them with. It is applied to every file you have loaded, and how the files are shared out is decided by the operations themselves: one that takes a single file is applied to each of them in turn, and one that takes several is given all of them at once. So thirty scans through compress, watermark and page numbers come back as thirty files, while compress followed by merge comes back as one. It is the same rule, and the same code, as `pagecraft recipe` on the command line — which is why a recipe exported from here runs there unchanged.
What it will not do
Every tool here says what it cannot do, in its own words, before you rely on it.
- A file that fails takes only itself out of the run. The rest finish, and the account of the run names the file, the step and what went wrong — except at a step holding every file at once, which cannot carry on around a file it could not read, and ends the run.
- Whether one step can follow another is checked before the run, and the check is deliberately coarse. An operation declares what it can produce, not what these settings will make it produce, so a recipe can be accepted here and still fail at a particular file.
- A saved recipe is kept in this browser and holds no file. A step that draws with a picture — a logo, a signature — asks for that file again when the recipe is reopened. Export it instead and the picture travels inside the exported file.