If every batch of photos gets the same treatment, build it once. Chain steps like resize, crop, watermark and WebP conversion, watch the result on your first image, then run the pipeline on the whole set and download a ZIP. Workflows can be saved, exported and shared.
Processing locally on your device
Overview
A workflow is an ordered list of steps, and each step works on the output of the one before it. The builder offers resize (long edge, width, height, fit inside a box or a percentage, with an option never to enlarge), crop or pad to an aspect ratio with a chosen anchor, rotate and flip, brightness, contrast and saturation, grayscale, a border or padding in pixels or as a percentage of the short side, and a text watermark with position, size, opacity and color. Output steps set the format (JPG, PNG, WebP or AVIF where your browser can encode it, or keep the original), the quality for lossy formats, and a rename pattern using {name}, {n}, {w}, {h} and {date}.
Order matters for the pixel steps. Cropping to 1:1 and then resizing to 1080 px gives an exact 1080 × 1080 square, while doing it the other way round gives a smaller square. Watermarking after resizing keeps the text at the same size on every output, because the mark is sized relative to the image width. Format, quality and rename apply when each file is saved, wherever they sit in the list. Every step can be switched off without deleting it, so you can compare versions quickly.
Everything runs locally with the Canvas API. Each image is decoded with its EXIF orientation applied, processed step by step, and encoded by the browser. Large reductions are done in halving passes for cleaner downscaling. Re-encoding through Canvas drops EXIF, GPS and other embedded metadata, so any workflow with a pixel step also strips metadata. The Strip metadata step makes that explicit and forces a re-encode even when nothing else changes. A workflow that only renames files keeps the original bytes untouched.
The preview runs the full pipeline on your first image (or any image you click) and shows a before/after slider with the output size, dimensions and file name, so a wrong setting shows up before you process hundreds of files. Batches run two images at a time with a progress bar and a stop button. Workflows are saved in your browser’s local storage and can be exported as a small JSON file to back up or share with someone who runs it on their own files.
| Preset | Steps | Typical use |
|---|---|---|
| Web-ready 1600px WebP | Strip metadata → long edge 1600 px → WebP 80% → “-web” suffix | Blogs, CMS uploads, fast pages |
| Instagram 1080 square | Crop 1:1 → width 1080 px → JPG 90% → “-ig” suffix | Instagram feed posts |
| Thumbnail 300px | Long edge 300 px → JPG 75% → “-thumb” suffix | Galleries, listings, previews |
| Watermarked proofs 2048px | Strip metadata → long edge 2048 px → tiled “PROOF” watermark → JPG 82% | Client selection proofs |
Load a preset such as “Web-ready 1600px WebP”, or add steps one by one.
Open each step to adjust its settings, and drag or use the arrows to reorder.
Drop your images. The first one is previewed with a before/after slider.
Click Run to process the whole batch and watch the progress bar.
Download all results as a ZIP, then save or export the workflow for next time.
Use cases
Save a store-ready recipe that strips metadata, crops to 1:1, resizes to 2000 px and converts to WebP at quality 80, then run it whenever a new shoot arrives.
Turn a full-resolution shoot into 2048 px JPEG proofs with a tiled “PROOF” watermark in one pass, so clients can choose images without receiving usable originals.
Use the Instagram preset to center-crop a set of holiday photos to 1080 × 1080 and add a “-ig” suffix, ready to post from your phone.
Export a workflow as JSON and send it to colleagues. Everyone gets identical sizes, watermark placement and compression without copying settings by hand.
Pro tips
Answers to common questions about the workflow builder.
For pixel steps, yes. Each step works on the previous result, so crop-then-resize and resize-then-crop produce different sizes, and a watermark added before a resize shrinks with the image. Format, quality and rename apply at save time wherever they appear.
In your browser’s local storage on this device. Nothing is sent anywhere. Use Export JSON to back a workflow up or move it to another browser, and Import JSON to load it again.
Any workflow that changes pixels or the format re-encodes the image through Canvas, which drops EXIF (camera, GPS, dates) and similar data. Add the Strip metadata step to guarantee it even when no other step changes the image.
Saving AVIF requires an encoder in the browser, and not every browser includes one. The format picker disables formats your browser can’t write. WebP is the most widely supported modern choice.
No. This builder chains image steps only. Use the dedicated video and audio tools for media files.
There’s no fixed limit. Images are processed two at a time, and results are kept in memory until you download them, so hundreds of typical photos work fine on a modern laptop.
No. ToolEnhancer processes files on your own device inside the browser. They are never sent to, stored on or seen by our servers.
Yes. The workflow builder is free to use with no sign-up, no watermarks and no daily limits.