Build an image workflow, then watch it run

A batch workflow you build once and reuse forever

Every other online batch editor makes you redo the setup on every visit: pick a size, pick a format, run, download, and start from zero next week. Here the sequence itself is the product. Resize to 1600 px, convert to WebP, remove the background: arrange the steps once, name the workflow, and it is waiting in this browser the next time you land on the page. You can keep several recipes side by side, one per client or per platform, and switch between them from the toolbar.

A workflow also travels. Export writes it as a small JSON file; Import loads it on another machine or hands it to a colleague. The images themselves never travel anywhere: every step runs inside your browser, and the only thing that ever crossed the network was this page.

The order of the steps changes the result

A pipeline is honest about one thing most tools hide: each step feeds the next, so the order matters. Convert to JPG before removing a background and the transparency you were about to create has nowhere to live. Put two lossy conversions in a row and the second one recompresses the artifacts of the first. Cutflow inspects the sequence as you build it and flags these combinations in plain words, without blocking you: sometimes a white background after a cutout is exactly what you wanted.

While a batch runs you can watch it move: the current image travels along the connector between steps, and every finished step keeps a small trace with its real dimensions, weight and duration. If the final files look wrong, the trace tells you which step did it.

How to batch resize, convert and remove backgrounds at once

1. Pick a starting point. Start from an empty flow or one of the ready-made recipes, like "Shrink for the web". Every step can be moved, retuned or removed later.
2. Tune the steps. Select a card to edit its settings: target size for a resize, format and quality for a conversion. Add steps with the plus button between cards.
3. Drop up to 50 images. The batch starts on its own. Each image completes the whole sequence before the next one begins, so memory stays flat even on a big batch.
4. Inspect and download. Open any image to compare every intermediate step, then download files one by one or the whole batch as a single ZIP.

Frequently asked questions

Are my images uploaded to a server?

No. Files are read straight off your disk and processed by your own browser. Nothing is sent, stored or queued anywhere. Close the tab and nothing remains.

Is my workflow still there next time?

Yes. Workflows are saved in this browser and reappear on your next visit. They stay on your machine: to move one to another computer, export it as JSON and import it there.

Why is the first background removal slow?

Background removal runs on an AI model that your browser downloads once, the first time a workflow needs it. After that it is cached and later batches start immediately. Workflows without a background removal step never download it.

Does chaining steps degrade quality?

Only lossy encodes cost quality, and only when they happen. A resize followed by one WebP or JPG conversion encodes once, exactly like doing it by hand. The tool warns you when a sequence would encode lossily twice, so the quality you lose is always a decision, not an accident.

Why does background removal always produce a PNG?

Because transparency needs a format that can store it, and JPG cannot. If you want a flat white background instead, add a JPG conversion step after the cutout: the warning you will see is the tool checking that this is intentional.

Do I need a workflow for a single operation?

No. If all your images need is one size, the bulk image resizer is quicker to set up. Same for a one-off background removal or a simple JPG to WebP conversion. The workflow builder earns its keep when the same two or three operations repeat, in order, week after week.