Batch image prep for cross-platform sellers
Resize, crop, compress and export product photos for Amazon, Etsy and Shopify — all in your browser.
Or . JPG, PNG, WebP, GIF, BMP or AVIF — up to 20 images, 20 MB each.
Nothing leaves your device. Files are decoded and re-encoded in this browser tab.
Each selected marketplace supplies its own output size — Amazon uses 1600 × 1600 px. Switch to a custom size to override them all.
Fills the frame and trims the overflow — the usual choice for product grids.
Settings apply to every image in the batch once you upload.
Most resizers make you repeat the same job per platform. This one keeps a single batch in memory and derives each platform version from it, so the crop, the quality setting and the filename rules stay consistent across every output.
A single batch becomes Amazon 1600 × 1600 JPEG, Etsy 2000 × 2000 JPEG and Shopify 2048 × 2048 WebP, each in its own folder.
Lock a ratio, pick a focal anchor, zoom in. The crop runs first so the output dimensions stay exactly what the platform expects.
Every rendered file is measured. You see the byte count and the percentage change against the original before you download.
Prefix, per-image SKU, zero-padded sequence, custom separator. Collisions get a -2 suffix instead of silently overwriting.
Up to three images render in parallel Web Workers. Each file is decoded once and reused for every platform variant.
No signup wall, no branding burned into your photo, no server-side copy of your catalogue sitting somewhere.
Every number below was read from the platform's own documentation on 2026-11-03. Where a platform publishes no limit, the preset says so instead of inventing one.
Square, white-background JPEG at 1600 px. That is above the 1000 px zoom threshold Amazon describes and well inside the 500–10000 px range.
Square 2000 px JPEG. Etsy recommends at least 2000 px on both sides for listing photos, and it does not support transparency.
Square 2048 px WebP. Shopify says square product images around 2048 × 2048 display best, and WebP keeps the file light while preserving transparency.
Your images are processed locally in your browser. We do not upload or store your product photos on our servers.
File → createImageBitmap → OffscreenCanvas → convertToBlob → ZIP. All four steps happen in your tab. The worker receives a reference to the local file, not a network request.
The page loads HTML, CSS and JavaScript. That is it. No image bytes are posted anywhere, there is no analytics script reading canvas data, and no third-party image API is called.
Object URLs are revoked, decoded bitmaps are closed and nothing is persisted. Clear All does the same thing on demand, mid-session.
No. The files are read with the browser File API, decoded with createImageBitmap, drawn onto a canvas and re-encoded in a Web Worker on your own machine. There is no upload endpoint in this application. The privacy page lists exactly what the network tab should show while you work.
This build allows 20 images per batch at 20 MB each. The planned Free tier is 5 per batch and Pro is 50; the pricing page explains the current state of that switch.
No, and no tool can promise that. The checks cover measurable things: pixel dimensions, format, file size, transparency. Amazon also requires the product to fill at least 85% of the frame, a pure white background for the main image, and no watermarks or added text — those need your eyes, which is why they are marked Manual in the checklist.
Only where it had transparency. Transparent areas are flattened onto white; existing opaque backgrounds are preserved exactly as photographed. This tool does not remove or replace photo backgrounds — no cut-outs, no background swap.
Etsy accepts .jpg, .gif, .png, .svg and .heic. WebP is not on that list, and Etsy also renders transparent PNG areas as black. The Etsy preset therefore flattens onto white and encodes JPEG.
No. Every export is a decode-and-re-encode through the Canvas API. PNG to PNG stays visually lossless, but JPEG and WebP are lossy by design and the quality slider controls that trade-off. We do not claim lossless conversion anywhere.
They disappear. Nothing is written to IndexedDB, localStorage or the Cache API. The Clear All button releases every object URL immediately so the decoded pixels can be garbage collected.