How to batch edit images
A batch recipe applies one visible sequence of compatible operations to every selected image. Arrange geometry changes before the final conversion and compression, review warnings before processing, and keep the source files so the recipe can be adjusted and run again.
Steps
- 1Choose the source set
Add the images once and review their formats, dimensions and any source-dependent warnings before defining the recipe.
- 2Arrange the operations
Put resizing and rotation before the final format and compression choices. Place a watermark where its final size and position can be judged accurately.
- 3Inspect the outputs
Review dimensions, format, transparency and visual quality for representative results before downloading individual files or the grouped archive.
Key decisions
Why does operation order matter?
Conversion can remove transparency, resizing changes watermark scale, and repeated lossy encoding can add damage. A visible recipe avoids accidental extra generations.
What does a saved recipe contain?
A recipe stores operation settings rather than the source pixels. A local image used as a watermark must be supplied again when the recipe depends on it.
Before you download
Know the limits
- A shared recipe cannot replace per-image review when the content itself determines the edit.
- Large decoded dimensions and several canvas operations can require substantial browser memory, so unsafe work is rejected during preflight.
Verify the copy
Common questions
Can I change the recipe after a warning?
Yes. Preflight warnings appear before execution so the operation order or output settings can be corrected without changing the source files.
Are my source images stored in an exported recipe?
No. The portable recipe represents settings. Source images and local watermark assets remain separate.