Plan around the storefront, not an arbitrary pixel target
Product photos may appear in a collection grid, a product detail page, a zoom view, and a mobile layout. The right output dimensions depend on your theme and the largest view shoppers can open. Before resizing a catalog, inspect the storefront and write down the image sizes it actually uses. A single small export may look fine in a grid but become visibly soft when a shopper zooms in.
Also check your commerce platform's current image requirements and your theme's responsive behavior. Platform limits and recommended sizes can change, and a theme may generate additional thumbnails after upload.
Prepare a reversible batch
- Export or copy the source images to a separate working folder. Keep an untouched backup.
- Choose a small sample covering common cases: square product photos, portrait items, wide banners, transparent products, and images with embedded text or fine detail.
- Decide whether you need resizing, format conversion, compression, or all three. Avoid changing dimensions and quality blindly in one large operation.
- Set a maximum dimension based on the largest real display size, and preserve aspect ratio so products do not become stretched.
- Test the sample in the theme before processing the full catalog.
Choose settings by image type
Photographs often tolerate lossy compression well, but reflective surfaces, fabric texture, hair, and small labels can reveal artifacts. Inspect these areas at the display size customers use. Graphics with sharp edges, text, or transparency may need different settings or a lossless format. Do not flatten transparency unless the design calls for a background.
Color profiles can also affect how a product looks across applications. Check a few converted examples in the storefront, not only in a desktop image viewer. If color accuracy is important, make color handling part of the sample review.
Keep file naming and product mapping intact
A bulk workflow should not detach files from their products. Preserve stable names or maintain a mapping between original and converted files. Check that variants, gallery order, and product identifiers remain associated after upload. If the platform creates its own image sizes, confirm that replacing a source does not leave stale thumbnails or broken references.
Process in manageable batches and save a record of the input folder, output settings, date, and any skipped files. If a batch fails or quality is unacceptable, this makes it possible to isolate and redo the affected group instead of repeating the entire catalog.
Verify before publishing the full catalog
- Compare file size and visual quality for the sample images.
- Check desktop and mobile layouts, including the largest product view.
- Confirm that thumbnails, variants, and gallery order still work.
- Inspect the actual image requests in the browser to see what format and dimensions are delivered.
- Clear relevant page or CDN caches after changing the image delivery setup.
- Keep originals and verify your restoration process before a large replacement.
Use local or cloud processing deliberately
Some browser-based tools process selected files locally, while cloud services upload images for processing. Check the tool's current mode and privacy information, especially when product images are confidential or not yet released. Consider device memory and batch size as well: processing a very large catalog in one browser session may be less reliable than splitting it into smaller groups.
ImageTight's bulk compressor can be used to resize or convert selected image files. Test with a representative sample first, then review the output and your store's behavior before replacing a live catalog.
Make optimization repeatable
Once the first batch works, turn the settings into a short team checklist for new product uploads. That checklist should state target display dimensions, accepted formats, quality review steps, file naming rules, and who keeps the originals. Consistent inputs help a catalog look coherent and reduce rework without sacrificing product detail.
Frequently Asked Questions
What dimensions should product images use?
Use the largest dimensions your storefront actually displays, including zoom or high-density screens, and check your platform and theme documentation. There is no one pixel size that fits every store.
Should every product image be converted to WebP?
Not automatically. Check the platform's delivery support, image content, transparency needs, and output quality. Test representative files and verify the format served to visitors.
Can I overwrite the originals after resizing?
Keep a separate backup until the full catalog, product mapping, and restoration process have been verified. A reversible workflow protects against quality or upload problems.