The queue runs on your machine. Nothing leaves it.

Build a resize recipe you can run again

Grid, listing and zoom outputs are already stacked. Inspect their dimensions, formats and names, then save the rules in this browser before giving them a real folder.

1The queue

A folder, a selection or a paste. Sub-folders are kept.

files queued

Drop a folder. Or 200 files.One file is faster at resizepicture.com.Sub-folders are kept, so a folder name can go in a filename.

/a paste works too

2The rules

Ordered, and every rule a file matches writes a file. That is how one photo becomes three.

Responsive set320 640 960 1280 1920 / 1x / webp q78

Save these rules as

3What will be written

Every file, named and measured, before anything runs.

If two outputs share a nameInside the ZIP

Drop a folder and this fills in: one row per file that will be written, with its name, its size and an estimate of its bytes, plus every collision and every dropped width. Nothing runs until it is on screen.

4The run

Nothing to run yet.

That is the ledger, mid-run. One line per file as it is written, newest at the bottom, and the real byte count rather than the estimate.

The opening recipe

Grid     480 × 480 cover    WebP q78   {parent}/grid.webp
Listing  960 × 960 contain  WebP q82   {parent}/listing.webp
Zoom     max-width 1800     WebP q86   {parent}/zoom.webp

Every source that matches all three rules writes three outputs. The plan expands that before the run, so a hundred inputs become three hundred named rows and filename collisions are visible while changing a rule still costs nothing.

What a saved recipe contains

Matchers, dimensions, fit and crop anchors.
Format, quality, pixel ratio and whether enlargement is allowed.
The filename template, archive layout and collision policy.

It contains no source name, pixel dimension, thumbnail or run history. Storage is local to this browser, so the portable version of a recipe is still its readable rule list. Use {parent} when each source folder represents one product.