Product Image Optimizer
Compress product photography to a target file size so listings load fast and marketplace zoom still works — without shipping a 6 MB JPEG to every visitor.
Drag and drop images
or click to browse files
How it works
A compact workflow from input to download.
Add your product photo
Drop in the studio or phone shot you plan to list. JPG, PNG, WebP, and HEIC all work.
Set a file-size budget
200 KB suits most listing images. Raise it for hero shots that need zoom detail, lower it for thumbnails and variant swatches.
Download and upload to your store
The compressed file keeps its pixel dimensions, so marketplace zoom requirements are still met.
Tool details
Practical capabilities and safeguards built into this workflow.
Budget per image, not per guess
Set the kilobyte ceiling your page-speed budget allows and the tool iterates on quality until the file fits it.
Speed affects conversion
Product images are usually the heaviest asset on a listing page, and image weight is the most common cause of a poor LCP score.
Dimensions preserved
Compression reduces bytes, not pixels, so a 2000×2000 image stays 2000×2000 and still satisfies zoom thresholds.
Unreleased products stay private
Nothing is uploaded. Product shots for an unannounced launch never leave your browser.
Consistent catalogue weight
Compressing every image to the same budget keeps page weight predictable as your catalogue grows.
No signup or watermark
No account, no per-day export cap, and nothing stamped onto commercial product photography.
Frequently asked questions
What are Amazon's product image requirements?
What image size should I use for Shopify?
How small should product images be?
Does image compression hurt SEO or conversion?
Should I use WebP for product images?
Do I need to resize as well as compress?
Are my product photos uploaded anywhere?
Product Image Optimization for Marketplaces and Storefronts
Product images have to satisfy two audiences at once. Buyers want to zoom in far enough to judge fabric, finish, and scale, which argues for large, detailed files. Browsers and ranking systems want pages that render quickly, which argues for small ones. The resolution is not to pick a side but to serve high pixel dimensions at a disciplined file size — compressing bytes aggressively while leaving the pixel grid intact.
Platform requirements worth knowing
Amazon requires a pure white background on the main image, the product occupying at least 85% of the frame, and a long edge of 1600 pixels or more to enable zoom. Shopify recommends 2048×2048 square images and generates smaller variants from your upload. eBay requires at least 500 pixels on the long edge but recommends 1600 for its zoom feature. Etsy suggests 2000 pixels wide. In every case the platform minimum is a floor, not a target — uploading at the recommended size and compressing well beats uploading a raw camera file.
Why image weight decides your Core Web Vitals
On a typical product page the main image is the Largest Contentful Paint element, which means LCP is effectively a measurement of how fast that one file arrives and decodes. Google treats an LCP under 2.5 seconds at the 75th percentile as good. A 4 MB hero image on a mobile connection makes that threshold unreachable no matter how well the rest of the page is built. Getting hero images under a few hundred kilobytes is usually the single highest-leverage performance change an online store can make.
Choosing a format for each surface
For your own storefront, WebP is the default worth reaching for: roughly 25 to 35% smaller than JPEG at matched quality, with near-universal browser support. Keep JPEG for marketplace uploads, where WebP is often rejected. Reserve PNG for images that genuinely need transparency, such as a product overlaid on a coloured background — a PNG photograph can be five to ten times the size of the equivalent JPEG for no visible benefit.
A workflow that scales across a catalogue
Settle on one set of dimensions per image role — hero, gallery, thumbnail, swatch — and one file-size budget for each. Resize to the role's dimensions first, then compress to its budget. Applying the same two numbers to every product keeps page weight predictable as the catalogue grows and stops one badly exported photo from dragging down a category page. Start with the image resizer for dimensions, then compress here.
Related tools
Continue the workflow with adjacent tools.