Compress
Build an image workflow you can save and reuse
Most image work is the same handful of decisions made again and again: this size, that format, under that many kilobytes, without the camera and location data. This page lets you write that sequence down once. Add the steps you want, put them in the order you want them, and the page tells you what the job will do before it does any of it - including whether any step would send your image anywhere, which none of the steps offered here do. Then run it on an image and the finished file is measured rather than assumed: the format is read back from the bytes, and the size and dimensions come from the file you actually get. Workflows are saved in this browser, on this device, and never uploaded.
How to build an image workflow you can save and reuse
- Add the steps you want, or start from one of the presets.
- Put them in the order they should run, and turn off any you want to keep but not use.
- Read what the page says the job will do, including anything it refuses.
- Drop in an image, run it, and download the result.
Supported formats
This tool accepts JPG, PNG, WebP, GIF, BMP and AVIF files. Everything is decoded by your own browser, so the formats available depend on what your browser can open - which for HEIC in particular varies between Safari and other browsers.
Frequently asked questions
Why does a preset only have one step?
Because one step is what it needs. Saying “at most 1600 pixels wide, under 200 KB, as WebP, without metadata” is a single requirement, and the constraint solver takes the whole of it at once: it crops to shape, resizes, picks the quality, encodes, and then measures the finished file to check it actually fits. Writing that as four separate steps would not be more powerful. It would be four decisions made independently instead of one search that can trade them off against each other - and the page would refuse it anyway, because a job that contains both a resize and a size requirement is asking two things to own the same decision.
Can I put the steps in any order?
You can reorder them freely, and some orders are refused with an explanation rather than quietly accepted. Background removal is the clearest case: doing pixel work before it would mean encoding your image an extra time purely to send a cropped copy, so the page says so instead of doing it. The order you see is the order that runs.
Does anything here upload my image?
No step offered on this page sends your image anywhere - every one of them runs in your browser. A workflow imported from a file could in principle contain the background-removal step, which does use an external service; if it does, the page refuses to run it until you have gone through the disclosure on that tool's own page, where the provider, what it keeps and what it may train on are all set out. Workflows themselves are stored in this browser and are never uploaded.
What happens if the image cannot meet what I asked for?
You are told, with the number it actually reached. The solver stops at a quality floor rather than grinding an image into mush to hit a byte count, and the result is still there to download because it is usually still useful. A tool that reported that as a plain success would be lying to you, and one that reported it as a failure would be throwing away your work.
Where are my saved workflows kept?
In this browser, on this device, in its local database. There is no account, and a workflow is never sent to a server, which also means we cannot recover one for you - clearing your browser data removes them. Use the export button to keep a copy as a file; the file is plain JSON containing only the steps and their settings, with no image data and no keys in it.
Related tools
Looking for something else? Browse all ImageUtility tools.