Marketplace Image ToolkitLocal batch image prepUpload images

The full workflow

Marketplace Image Preparer

One upload, three storefronts. The same photos become Amazon JPEGs, Etsy JPEGs and Shopify WebPs, sorted into folders inside a single ZIP — with the originals untouched.

  • Outputs per image3 (or pick fewer)
  • Folder layoutexport/Amazon, /Etsy, /Shopify
  • Decodes per batchOne per image

Drop product photos here

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.

Output targets

Pick one or several. Each gets its own folder in the ZIP.

Size source

Each selected marketplace supplies its own output size — Amazon uses 1600 × 1600 px. Switch to a custom size to override them all.

Fit

Fills the frame and trims the overflow — the usual choice for product grids.

Settings apply to every image in the batch once you upload.

Export

0 source images × 3 targets = 0 files

Platform check

These are the rules that will be applied once you prepare the batch.

Amazon

Official source · checked 2026-11-03
  • Longest side at least 500 pxRequiredAmazon states product images must be 500 to 10,000 pixels on their longest side.Pending
  • Longest side at most 10,000 pxRequiredAnything larger is outside the range Amazon publishes.Pending
  • Each side above 1,000 px (zoom)RecommendedAmazon says it prefers images larger than 1,000 pixels on each side so the zoom widget has data to work with.Pending
  • JPEG, TIFF, PNG or non-animated GIFRequiredAmazon accepts JPEG, TIFF, PNG and non-animated GIF, and says it prefers JPEG. This tool exports JPEG or PNG.Pending
  • Main image on pure white (255,255,255)RequiredAmazon requires a white background for most product shots. Transparent areas are flattened onto white; existing opaque backgrounds are preserved as they are. This tool does not remove or replace photo backgrounds, so only you can confirm the photo itself was shot on white.Manual
  • Product fills 85% or more of the frameRecommendedAmazon recommends the product fill at least 85% of the frame. Cropping is a manual judgement call — check the preview.Manual
  • File size limitInfo10 MB tool warning threshold — not a verified Amazon official limit. Amazon does not publish a byte limit on the page we verified; confirm the current cap in Seller Central (G1881). (Not confirmed on an official page.)Unverified
  • Filename carries the product identifierInfoUsing the ASIN or SKU as the filename keeps bulk uploads traceable. Set a SKU in the naming panel before exporting. (Not confirmed on an official page.)Unverified

Etsy

Official source · checked 2026-11-03
  • At least 2000 × 2000 pxRecommendedEtsy recommends listing photos have a width and height of at least 2000 pixels.Pending
  • First photo at least 635 pxRecommendedEtsy says the first listing photo should be at least 635 pixels wide and tall to avoid appearing lower in search.Pending
  • JPG, PNG, GIF, SVG or HEIC onlyRequiredEtsy supports .jpg, .gif, .png, .svg and .heic. WebP is not on that list, which is why this preset exports JPEG.Pending
  • No transparent backgroundRequiredEtsy does not support transparent PNGs — transparent areas render as black. The preset flattens onto #FFFFFF.Pending
  • Keep files small (over 1 MB may stall)InfoEtsy warns that images larger than 1 MB may not finish uploading on slower connections.Pending
  • Landscape or square, consistent shapeRecommendedEtsy recommends the first photo be landscape or square, and that every photo in a listing share the same shape. Square is the default here; switch to the 4:3 crop if you want landscape.Manual
  • At least one unedited photo of the real itemRequiredEtsy requires one photo that has not been edited or altered. Resized exports are fine for the rest of the set, but do not replace your only unedited shot.Manual
  • sRGB colour profileRecommendedEtsy converts images to sRGB. Browser canvas exports are untagged sRGB, which matches.Manual

Shopify

Official source · checked 2026-11-03
  • At most 5000 × 5000 pxRequiredShopify product and collection images can be any size up to 5000 × 5000 px.Pending
  • At most 25 megapixelsRequiredShopify caps product media at 25 megapixels. For square images this coincides with the 5000 px limit; for non-square media the megapixel count can bite first.Pending
  • Smaller than 20 MBRequiredShopify product images must be under 20 MB to upload.Pending
  • PNG, JPEG, WebP and other listed formatsRequiredShopify lists PNG (preferred), JPEG, TIFF, BMP, GIF, SVG, HEIC and WebP. WebP is the default export here for size.Pending
  • 2048 × 2048 px for square imagesRecommendedShopify says a size of 2048 × 2048 px usually displays best for square product images.Pending
  • Same aspect ratio across the product setRecommendedShopify notes that collection pages show images side by side and look wrong when ratios differ. One crop ratio for the whole batch keeps them aligned.Pending

How it works

  1. Upload the batch once

    Twenty photos, twenty megabytes each, mixed JPG and PNG. Each file is decoded once and reused for every platform variant.

  2. Select the marketplaces

    Amazon, Etsy and Shopify each contribute their own dimensions, format, background rule and rule checklist. Turn off any you do not sell on.

  3. Prepare, review the tree, download

    You get a per-platform preview with measured file sizes, the exact folder structure, and one ZIP containing all of it plus a manifest.json.

What makes this different from running three tools

Three separate resizers means three uploads, three crop decisions and three chances for the set to drift apart. Here the crop, the quality level and the naming rules are defined once and applied per platform:

  • Amazon — 1600 × 1600, JPEG, flattened onto #ffffff.
  • Etsy — 2000 × 2000, JPEG, flattened onto #ffffff.
  • Shopify — 2048 × 2048, WEBP, transparency preserved.

The differences are real, not cosmetic: Etsy cannot take WebP or transparency, Amazon wants white behind the product, Shopify is happy with WebP and a kept alpha channel.

One thing the background rule does not mean: transparent areas are flattened onto the preset colour, and existing opaque backgrounds are preserved as photographed. This tool does not remove or replace photo backgrounds.

The export tree

export/
  Amazon/
    SS26-MUG-001.jpg
    SS26-MUG-002.jpg
  Etsy/
    SS26-MUG-001.jpg
    SS26-MUG-002.jpg
  Shopify/
    SS26-MUG-001.webp
    SS26-MUG-002.webp
  manifest.json

One decode, many outputs

A naive implementation decodes the file once per platform. With three platforms and twenty photos that is sixty full-resolution decodes, and each one costs memory and time. Here a job carries one file and a list of variants: the worker decodes once, renders every platform from that bitmap, closes it, and moves on. Three workers run at a time, so the tab stays usable.

Questions

Do the three outputs come from the same crop?

Yes. One crop ratio applies to the batch, so all three platform folders contain the same framing at different sizes. That consistency is the reason to use one workbench instead of three tools.

Can I use a different format for one platform?

You can force one format for everything in the Convert tab, but the presets already encode the right choice per platform. Per-platform overrides are a planned addition, not a shipped feature.

Does the Amazon output get a white background automatically?

Only where the source had transparency. Transparent areas are flattened onto white; existing opaque backgrounds are preserved as photographed. There is no background removal or background replacement in this tool.

What is in manifest.json?

A list of every file with its platform, source filename, dimensions, format and byte count, plus the preset versions and their verification dates. Useful for auditing a large export later.

What if one image fails?

The rest of the batch still completes. Failures are listed with the reason, the successful files stay in the ZIP plan, and Retry failed images re-runs only the failures.

Is anything uploaded?

No. There is no upload endpoint in the application. The manifest records processedLocally: true because that is literally how the bytes were produced.

Related tools