The vague request
Two files can both be “square” and still be wrong.
A 1:1 crop does not tell me the pixel dimensions, JPEG quality, color treatment, filename, or destination. A correct-looking image in the wrong folder still creates work for the person who has to publish it.
So I describe one row for each finished use. I do not start by opening an export tool and hoping the missing decisions become obvious later.
My three-row example
Each destination gets a sentence I can test.
- Store: 1:1 crop, requested pixel edge, neutral color,
PEN-017-001.jpg, Store folder. - Website: 3:4 crop, separate pixel target, the treatment that matches the product page, Website folder.
- Social: 9:16 or the current placement, its own color adjustment and naming rule, Social folder.
These values are examples from my workflow, not official standards for every destination. I replace them when the destination's current requirement changes.
Source first
I crop each delivery from the original, not from another export.
The square version may remove the sides. The portrait version may need more height. The social version may need a different emphasis. If I make one from another, the first crop has already decided what the next one is allowed to contain.
SizeFold keeps the source as the starting point for each enabled config, so the outputs remain independent. That makes the output plan easier to reason about and easier to change.
The order I check
I verify the file that will actually leave the folder.
- Check the visible crop at the intended composition.
- Check the actual pixel dimensions, not just the aspect ratio.
- Check color, sharpening, JPEG quality, and metadata choices.
- Check the filename and destination folder.
- Open an output at its real size before trusting the whole batch.
A progress bar can tell me that a file was written. It cannot tell me whether the right product detail survived the crop or whether the file landed in the folder where it belongs.
What SizeFold covers
One config describes one delivery row.
SizeFold supports up to three enabled output configs. Each one stores its own crop ratio, dimensions, image adjustments, JPEG quality, filename rule, and destination. Every output starts from the source image.
The boundary is clear too: the first release creates JPEG outputs. If I need a fourth simultaneous specification, PNG transparency, or TIFF delivery, I use another tool or another pass.
Completion
The source moves only when the row set is complete.
For one source photograph, every enabled output must exist before the original is archived. If one row fails, incomplete products from that attempt are removed and the source remains in Input for retry.
That makes “done” mean something stronger than “some files appeared.” It means the delivery set described before the run is present.
The useful result
The next batch works like the last one.
Once the output rows are saved, put the next product photos in the same Input folder and click Run. The same crops, sizes, color settings, filenames, and destination folders are used again. Add a model name only when you want it included.