Batch image processing with workflows

Real folders are mixed: phone photos next to screenshots, large scans next to small icons. A condition lets one workflow treat them differently. A step can be told to run only when the picture is at least or at most a given width or height, when the file is over or under a given size, when it has transparency, or when it arrived in a certain format.

A step whose condition does not hold is skipped. The picture moves on unchanged and the report says which steps ran. That is how a single chain can shrink only the oversized photos and convert only the PNG files, while everything else passes through untouched.

In the editor every block opens into three parts: what came in, its settings, and what goes out. The Test step button runs the chain up to that block on your sample and shows the picture as it leaves, with its dimensions and format. You see at once whether the crop sits where you meant it.

A dry run goes through the whole chain without processing anything. It tells you which steps would run for that picture and what the result would be called. A step that is set up in a way that cannot work is named, together with the reason.

A saved workflow is a preset of the API. Send one image together with the workflow's name and the finished picture comes back in the answer. For many images, start a batch job with a list of addresses or uploaded files. It works in the background and reports each image as it finishes.

If your account has a webhook address, a signed message goes there when a job ends. A script, a shop back end or an automation tool such as n8n can carry on from that point. Saving a workflow again under the same name keeps the earlier version, and a request can ask for a version by its number.

Pictures are processed on our own server in the EU. The two steps that use a model, background removal and upscaling, run on that same server, and no picture is passed to another company.

The files you upload are not kept once the run is over. Results stay for one hour so that you can download them, and are then deleted. A run started on the page carries on if you close the tab, and a signed-in account sees it under Running now on the account page.

A workflow is one line of steps. It has no branches that split and join again, no timers, and it does not sign in to other services to fetch or publish files. Those jobs belong to a general automation tool, which can call a workflow through the API for the image part.

It also handles one picture at a time, so a step cannot merge two pictures into one. For the images of a whole website the Website Optimizer is the better fit: it finds the pictures on your pages by itself and writes a map of what to replace.