If you sell on more than one marketplace, you already know the problem. Shopify wants one thing, Amazon wants another, and Shopee and Lazada each have their own ideas about pixels, file size and framing. Resizing every photo by hand for every channel turns a 50-SKU launch into a weekend of repetitive work. Worse, when you rush it, you end up with blurry zoom, products cropped at the edges or uploads that bounce back with an error.

The fix is a batch workflow. You keep one high-quality master image per shot and generate every marketplace version from it automatically. This guide walks through how to set that up, which sizes to target and the mistakes that quietly lower image quality along the way.

Why batch resizing beats one-at-a-time editing

Editing images one by one feels manageable when you have ten products. It stops being manageable at a hundred. A batch approach gives you three advantages:

Consistent images also matter to shoppers. A search results page where your products sit at the same size and position looks more trustworthy than one where each thumbnail is framed differently.

Step 1: Start with a proper master file

Every batch workflow depends on the quality of the source. Resizing can make an image smaller cleanly, but it cannot invent detail that was never captured. Before you think about marketplace sizes, make sure each master image meets this baseline:

Store masters in their own folder and never overwrite them. All marketplace versions are outputs, and outputs can always be regenerated.

Step 2: Know your target sizes

Marketplace requirements change, and published figures vary between sources, so always confirm the current numbers in each seller centre before a big upload. As a working reference for 2026, these are the targets most sellers use:

MarketplaceRecommended sizeAspect ratioFile size limitNotes
Amazon2,000 x 2,000 px1:1 (most categories)10 MB1,000 px on the longest side is needed for zoom; main image on pure white
Shopify2,048 x 2,048 px1:1 (theme dependent)20 MBShopify serves resized versions from its CDN automatically
Shopee1,024 x 1,024 px1:1Around 2 MBKeep files light; very large uploads may be rejected
Lazada800 x 800 px or larger1:1Around 3 MBProduct should fill most of the frame on the main image
TikTok Shop1,000 x 1,000 px or larger1:1 (3:4 also used)Around 5 MBWhite or clean background preferred for the main image
Qoo10 / Carousell1,000 x 1,000 px1:1Keep under 2 to 3 MBSquare crops display most reliably in feeds

Notice the pattern. Almost every marketplace prefers a square image. That is good news for batch processing, because one square master crop can serve nearly every channel with only the pixel size and compression changing.

Step 3: Decide how to handle non-square images

Many products are tall or wide: bottles, skateboards, dresses, cables. When you convert them to a 1:1 square, you have two options.

Pad to square (recommended for main images)

Add white space to the short sides so the whole product stays visible. This is the safest choice for main images, because nothing gets cut off and the white background stays compliant. The trade-off is that tall products can look small in the frame, so keep the padding even and avoid leaving more empty space than necessary.

Crop to square (use with care)

Cropping fills the frame but removes part of the image. It works for lifestyle shots and texture close-ups, but on a main image it risks cutting off part of the product, which some marketplaces treat as a policy problem. If you crop in a batch, check the results, as automatic centre crops do not know where your product actually is.

Step 4: Set compression per marketplace

Pixel dimensions are only half the job. File size is the other half, and it is where most batch uploads fail on Southeast Asian marketplaces with tighter limits.

Step 5: Run the batch

You have several ways to do the actual processing, depending on your volume and technical comfort:

  1. Desktop editors with actions or presets. Photoshop actions or Lightroom export presets can resize a folder in one go. They are powerful but require a licence and some setup for each marketplace.
  2. Command-line tools. Free tools such as ImageMagick can resize and compress thousands of files from a script. They are fast and flexible, but you need to be comfortable writing commands.
  3. Browser-based batch resizers. Tools built for e-commerce let you upload a folder, pick the marketplaces you sell on and download every version ready to list. PixelPrep works this way, with presets for Shopify, Amazon, Shopee, Lazada, Qoo10 and Carousell, so you do not need to look up dimensions each time.

Whichever method you choose, output each marketplace into its own folder, for example /amazon, /shopee and /shopify, and keep the original file names. Consistent names make it much easier to match images to SKUs when you upload.

Step 6: Quality-check before you upload

A quick review takes five minutes and prevents a week of suppressed or ugly listings. Open a sample of the output from each folder and check:

If images look soft after resizing, a light output sharpening step after the resize usually restores crispness. Apply it to the resized version, not to the master.

Common batch resizing mistakes

Your batch resizing checklist

  1. Shoot or source masters at 2,000 pixels or larger, in sRGB, on a clean white background.
  2. Keep masters in a separate folder and never overwrite them.
  3. Confirm current image specs in each seller centre before a large upload.
  4. Pad tall or wide products to square for main images; crop only where safe.
  5. Export JPEGs at quality 80 to 90, with metadata stripped and headroom under each file limit.
  6. Output each marketplace to its own folder with consistent file names.
  7. Spot-check framing, background colour, sharpness and file size before uploading.

Set this workflow up once and every future product launch gets faster. Instead of resizing the same photo five times, you prepare one strong master and let the batch handle the rest, whether that is a script, an editor preset or a dedicated tool like PixelPrep.