Batch Resize and Rename Photos
Inspect a downloadable three-file ZIP, then build a repeatable product-code naming and export routine without changing your originals.
Choose a stable product code
Use one product code per batch so an exported filename tells you which item it belongs to. For example, MUG-042-001.jpg combines a stable product code with the image sequence. Keep the originals in another folder; the export folder should contain copies that can be recreated.
The downloadable archive below contains three real image files and the exact names generated by this site's filename function. Extract the ZIP and inspect it before adapting the scheme to your own catalog. A filename organizes files; it does not establish storefront image order or guarantee search rankings.
Inspect a finished ZIP
This reference archive contains three real JPG exports named using the site's filename function. It demonstrates names and archive contents; it is not a captured marketplace upload.
Download the verified three-file ZIP (269,019 B). Extract it and confirm the names, dimensions and file types before using the workflow on your own images.
Image sources and reproduction
Photographs: Coffee Cup, The Metropolitan Museum of Art; Coffee cup and coffee bean, mcfoodie. Both are CC0. They are third-party test material, not photographs taken by this project. Pattern, text, transparency and noise fixtures are generated tests.
Measured 2026-10-20 with sharp 0.35.4, libvips 8.18.6, Node 24.13.1. Download all dimensions, byte counts and SHA-256 hashes. Reproduction script.
Prove one export first
Begin with a landscape image, a portrait image and a detail image. Keep the output settings the same. Open the saved results outside the browser to check dimensions, framing and important details. One representative test is cheaper to repair than an incorrectly cropped full batch.
In any editor, set an export folder, retain the original extension only if it matches the actual encoded type, and record the resize rule. If you use Image Prep, every file receives the same prefix and settings. Prefix characters outside A–Z letters, digits, hyphens and underscores become hyphens; an empty prefix becomes product.
- Choose the product code, destination ratio, dimensions and accepted file type.
- Prepare a small representative set and open a saved copy.
- Check that the number of exported files equals the expected successful inputs.
- Inspect the names and actual file types before uploading.
- Arrange the primary image and remaining order inside the marketplace.
Understand ordering and gaps
Image Prep assigns numbers in the order displayed after selection. Operating-system file pickers can return a different order from the one you expected, and this tool does not offer drag-to-reorder. Use the visible list as the export-order reference.
If input 2 fails, the successful files can be numbered 001 and 003. The gap preserves the connection to the failed input. Review the errors, then remove or replace the failed file and prepare again if continuous numbering is required. Never assume that a ZIP containing some successful files means the entire batch succeeded.
Close and reuse the batch
ZIP collects the exports in one archive; it does not necessarily make already compressed images substantially smaller. Extract it and open representative files. A webpage can request a download but cannot prove that you saved and extracted it successfully.
Saved settings belong to this device's browser profile. They include the filename prefix, so replace the previous product code before a new batch. They do not save photos in a cloud library, sync to another device or substitute for a backup. Clear the batch when finished, and use Forget saved settings to remove the optional stored recipe.
How this guide was made
Written from the documented sources and downloadable examples on this page. Reference-encoder results explain the file decisions; the final browser output and destination preview still need checking.
Reference: MDN: localStorage persistence and browser restrictions