Image workflow builder
Chain tools into one workflow and run it on a whole batch of images, decoded and saved once, on your device.
- Processed locally
- Batch many images
- 125 chainable tools
- Saved once, no re-encoding between steps
Start from a template
10 ready-made workflows1Images
Drop images here
or choose files · paste with Ctrl/⌘ V
JPG, PNG, WebP, HEIC, AVIF, GIF, TIFF, SVG, RAW, PSD and more. Whole folders work too.
2Steps
Add at least one step.
How to build an image workflow
- 1
Pick a template such as Web-ready or Email-ready, or add steps yourself from the list of chainable tools.
- 2
Open a step to adjust its options. Drag steps or use the arrows to change the order.
- 3
Drop your images or a whole folder. Use Preview on one image to check the result before running the batch.
- 4
Run the workflow, compare before and after, then download each file or everything as one ZIP.
Why one pipeline instead of one tool after another
Encoded once
Running tools one at a time means every step decodes the previous step's file and encodes a new one. With lossy formats such as JPG and WebP, every extra encode throws away a little more detail.
The workflow builder merges all steps into one pipeline before anything runs: the image is decoded once, resize, crop, filters and watermarks are applied in order to the same pixels, and the result is encoded a single time with the output settings of your steps.
10 templates to start from
Templates cover common jobs: Web-ready, Share privately, Email-ready, Instagram post, Product photos, Print at 300 DPI, Thumbnails, Archive copy, Lossless clean-up, Portfolio watermark. Load one, change any setting, and save it under your own name.
Limitations
- Very large batches need memory: images are processed a few at a time, but every finished file is kept in memory until you download it.
- Steps that work on still images (for example Auto Trim) make animated GIF or WebP input keep only its first frame. The builder warns you when that applies.
- Camera metadata survives re-encoding only when a JPG is saved as a JPG with Keep EXIF turned on.
Frequently asked questions
What is an image workflow?
A list of tools that run one after another on every image you add, for example resize, convert to WebP and remove metadata. You set it up once and get the finished files in one go, instead of downloading and re-uploading between tools.
Does chaining tools lower the quality?
No more than the last step would on its own. The steps are combined into a single pipeline, so each image is decoded once, every step works on the same pixels in order, and the file is encoded once at the end. A workflow made only of Remove Metadata and Change DPI edits JPG, PNG and WebP files byte by byte without re-encoding at all.
Two steps both set an output format. Which one is used?
The last one. Output settings follow the order of the steps: later steps override earlier ones, and the builder tells you when a format is replaced. Compression settings from Compress, Compress to Size or Smart Optimizer still apply to the final format.
What happens to metadata?
If any step removes metadata, it is removed. Steps that re-encode the image write a fresh file, so camera details and GPS are not carried over unless you turn on Keep EXIF in a Convert or Compress step and the image stays a JPG. Removing only the location is exact only in a lossless workflow; mixed with other steps, all camera metadata is removed.
Why are some tools missing from the step list?
Only tools that turn one image into one image can be chained. Tools you use by hand (crop, redact, the editor), tools that combine several images (collage, images to PDF) and local AI tools work on their own pages. Extract Frames creates several files per image, so it can only be the last step.
Are my workflows saved, and can I share them?
Press Save to keep a workflow in this browser's local storage, where you can rename or delete it. The address bar always holds a link that recreates the steps and their settings, so you can bookmark it or send it to someone. The link never contains your images, and logo images used in a watermark step are not included.
Is anything uploaded?
No. Every step runs in your browser, on as many background threads as your device can handle, and the upload counter at the bottom of the workbench stays at 0 B. Large batches are limited only by your device's memory.