Repeat a monthly job

1. Write the rules once, then keep them

Build the job the first time as you normally would: the sizes, the formats, the filenames. Then save it. A saved set lives in this browser; an exported recipe is a small .resizly.json file you can keep next to the photos, send to a colleague or check into a project. It holds rules only: no photo, no filename, nothing about what you processed. The fields are listed on the recipe format page.

For a colleague who just needs the same settings once, Copy as a link puts the recipe in the address itself, after the #. Browsers never send that part of an address to a server, so the rules travel inside the link and nowhere else. Opening it shows what the link holds and waits for a click before anything changes.

2. Keep the record of each run

Every archive carries a _resizly folder: a CSV and a JSON manifest listing each source with its path and size, and each file written with its pixel size and bytes, plus the recipe that made them. Keep the manifest from this month's run.

_resizly/manifest.csv
_resizly/manifest.json   sources (path, bytes), outputs (path, size, bytes)
_resizly/recipe.json     the rules that ran

3. Next time, run only what changed

Next month, drop the folder again, load the recipe, and drop last month's manifest.json beside the queue. The workspace compares the two and marks each picture as new, changed (same path, different size) or unchanged. Leave “only changed” on and the run writes the new and changed pictures, so a folder of 400 with 12 new photos is a 12-picture job.

• Keep the folder layout stable between months: the comparison goes by path inside the drop.
• Put {date} in a filename template, or rely on the dated archive name, so two months of output never overwrite each other.
• If a run stops part-way, the page offers to resume when the same folder and rules come back.

For the arithmetic of how large a folder a browser can take in one go, see two hundred files in a browser; for building the rules themselves, the recipes page opens with a three-output set already written.