Blog

Prepare product photos for a catalogue, one batch at a time

To prepare product photos for a catalogue of two hundred items without losing a week, stop deciding photo by photo and decide once per batch. This guide sets the three numbers that matter (longest side, format and target weight), the three sizes every product needs, a file naming rule that survives the next shoot, and a five-minute quality check. It ends with the exact steps in Airpic.

Decide once, apply to everything: longest side, format and target weight

A catalogue where every photo has its own size looks messy even when each photo is fine on its own. One shirt is 3,024 pixels wide because it came straight from the phone, the next is 800 because the supplier sent it that way, and a third is a 9 MB PNG because someone exported it from a layout file. On the listing page the eye reads those differences as carelessness: products sit at slightly different scales, some load instantly and some draw line by line.

The fix is to write down three decisions before you open a single file, and then never revisit them for that batch:

  • Longest side in pixels. Pick one figure per size you publish (more on the three sizes below). Use the longest side, not the width, so portrait and landscape shots end up with the same visual weight.
  • Output format. WebP is the safe default for a shop today; AVIF is smaller still if your platform serves it; JPEG if your shop software or a marketplace only accepts JPEG. PNG only for images that genuinely need transparency, because a photo saved as PNG is several times heavier than the same photo as JPEG.
  • Target weight. A ceiling in kilobytes per size, for example under 150 KB for the product page image. You will check against this number at the end.

Format is the decision that moves the needle most. In an Airpic study on 2026-10-19, we looked at 296 Spanish online shops and 9,620 homepage images: converting their JPEG and PNG files to AVIF would cut the total image weight by 58 %, and converting them to WebP by 55 %. That is more than half of every page's image payload, gained without touching the photography.

Write the three numbers on a sticky note or at the top of your spreadsheet. The point is that photo 140, processed on a Thursday evening, gets exactly the same treatment as photo 1, processed on Monday morning. When someone asks you to optimise images for an online store, this note is most of the job.

Product image size for a catalogue: three versions per product

Most shops need each product in three sizes, and each one has a different job:

  1. Thumbnail for the listing grid, 400-600 px on the longest side. A category page may show 24 to 48 products at once. On a phone each tile is roughly 170-200 CSS pixels wide, which on a high-density screen means about 400-600 real pixels. Anything larger is downloaded and thrown away. Aim for 30-60 KB.
  2. Product page image, 1,200-1,600 px. This is the main photo next to the price. 1,200 px covers a full-width phone and most desktop layouts; 1,600 px gives headroom for large screens. Aim for 100-200 KB.
  3. Zoom version, 2,000-2,500 px. Loaded only when the shopper taps or hovers to inspect stitching, texture or a label. Marketplaces have their own rules here: Amazon, for instance, enables zoom only when the longest side is at least 1,000 px, and more gives a better zoom. Aim for 300-500 KB.

Why not upload only the big one and let the browser shrink it? Because the browser shrinks the picture, not the download. A 2,500 px zoom image used as a thumbnail costs the visitor the full file, multiplied by every tile on the grid. Forty products at 400 KB each is 16 MB for a single category page on mobile data, against under 2 MB with proper thumbnails. Browser downscaling is also not the best resampling available, so fine patterns such as knitwear or striped fabric can shimmer (moiré) in a way a properly reduced file does not.

One honest warning about the zoom size: it only works if the original is big enough. If a supplier sends you 700 px photos, exporting them at 2,500 px gives you a larger file with no more detail. In that case upscale the image by ×2 or ×4 first, and check the result at 100 % before you call it a zoom image. An AI upscaler can rebuild edges and texture convincingly, but it cannot read a washing label that was a grey smudge in the original.

File names and order: a convention that survives the second batch

IMG_4821.jpg tells nobody anything, including search engines. Google reads the file name as one of the signals for what an image shows, and image search sends real traffic to shops that sell visual products. A descriptive name also saves you time: when a customer complains about the wrong colour on the navy linen shirt, you find the file in seconds.

A convention that works for most catalogues:

  • Lowercase, words separated by hyphens, no spaces or accents: linen-shirt-navy-front-1200.webp. Spaces become %20 in URLs and accents break on some servers.
  • Order from general to specific: product, variant (colour, size if it changes the look), angle, size. Sorting the folder alphabetically then groups every view of the same product together.
  • Fixed angle words: decide on front, back, side, detail and lifestyle, and never write rear one day and back the next.
  • Two-digit numbers when there are several shots of the same angle: detail-01, detail-02. Without the zero, detail-10 sorts before detail-2.
  • Optional SKU prefix if your shop software matches images to products by reference: LS204-linen-shirt-navy-front-1200.webp.

The second batch is where conventions die. Three months later a new person shoots the spring collection and invents their own scheme. Put the rule in a one-line text file inside the photo folder (for example naming.txt with a sample name) so the convention travels with the photos rather than living in your head.

Do not keyword-stuff the name. cheap-linen-shirt-best-linen-shirt-buy-linen.jpg helps no one. Describe the image, then write a matching alt text in your shop for the same photo.

The quick quality check: three photos at 100 %

You cannot inspect two hundred photos one by one, and you do not need to. Processing with the same settings produces the same faults, so a sample tells you about the whole batch. After each batch, open three files: the one with the most fine detail (a knit, a print, a wood grain), the one with the largest flat area (a white mug, a plain sofa against a light wall) and one chosen at random.

View each at 100 %, not fitted to the screen, and look at three things:

  1. Edges. Where the product meets the background, look for a halo, a jagged outline or a coloured fringe. If you removed the background, check hair, fur, fringes and transparent parts such as glass or packaging film.
  2. Flat areas. Smooth gradients and plain backgrounds are where compression shows first: blocky squares, banding in a gradient or a faint mosquito pattern around text on a label. If you see it on the white mug, quality is set too low for the whole batch.
  3. Weight. Check the file size against the ceiling on your note. Far under the target usually means you could raise quality; over it means quality or longest side is too high.

If one of the three is wrong, assume the batch is wrong, fix the setting and reprocess everything. Fixing just that photo by hand is how catalogues end up inconsistent again.

A common piece of advice that goes wrong here: setting only a target size in KB for a mixed batch. A plain product on white compresses easily, so it reaches 150 KB at a high quality; a patterned rug needs far more data, so the same 150 KB forces quality down until it looks smeared. For a batch that mixes simple and busy products, fix the longest side and a quality value instead, and use the KB target as a ceiling you check, not as the setting that drives the export. A target in KB works best when the products in the batch look alike, such as forty plain T-shirts shot on the same background.

Batch edit product photos in Airpic: compress, then remove the background where needed

Here is the exact process with the three numbers from your note. In our tests on 2026-09-19, a 1.2 MB JPEG product photo went down to 208 KB (83 % smaller) at quality 72, in 2 seconds, so the compression step is not where the batch spends its time.

If the product page needs a clean background, do that step first, on the full-size original, because cutting out an already compressed image gives the background remover less detail around the edges:

  1. Open remove the background from a photo and drop in the original. JPG, PNG, WebP, TIFF, HEIC and AVIF are accepted, and the phone's orientation is applied automatically.
  2. Choose the background your channel asks for: white for most marketplaces, transparent if your theme places the product on its own colour, or a hex value to match your brand (for example #f4f2ea). Edges are calculated at full resolution, so hair and fine outlines keep their detail without a halo.
  3. Look at the preview, zoom in on the edges, and download the result. This becomes your new master file.

Then produce the three sizes in the image compressor, which is free to process and to download, with no credits used:

  1. Drop in the master (the cut-out version, or the original if the photo needs no background change).
  2. Format: pick the one on your note. WebP for most shops, AVIF if your platform serves it, JPEG if a marketplace requires it. If you cut out with a transparent background, choose WebP or PNG; JPEG has no transparency and would fill it.
  3. Longest side: type 1,600 for the product page version. The tool resizes before encoding, so the file weight drops on two counts.
  4. Quality: start around 75-80 for WebP or around 72 for JPEG. Or, for a batch of similar products, set a target size in KB (for example 150) and let the tool find the quality.
  5. Remove metadata: tick it. It strips camera model, date and GPS location from every file, which you do not want to publish from a warehouse or your home, while keeping the ICC colour profile so colours stay as shot.
  6. Check the result: the tool shows the new weight next to the original and a before and after comparison. Zoom in on an edge and a flat area.
  7. Repeat with the other two numbers: longest side 2,500 for zoom and 500 for the thumbnail, same format and quality. Name each file with your convention as you save it.

Keep the same settings for the whole batch and only change them after the three-photo check tells you to. If some supplier photos are too small for the zoom size, run those through the upscaler before this step, and if a product shot has a stray tag or a stain on the backdrop, remove the object from the photo before compressing. For more on format choices, see the guide to compressing images for the web without losing quality.

FAQ

What size should product photos be for an online shop?

Use three versions: 400-600 px on the longest side for listing thumbnails, 1,200-1,600 px for the main product page image, and 2,000-2,500 px for zoom. Keep thumbnails around 30-60 KB and product page images around 100-200 KB.

How do I batch edit product photos so they all look the same?

Decide the longest side, the output format and a target weight once, write them down, and apply exactly the same settings to every photo in the batch. Then check three photos at 100 %; if one is wrong, change the setting and reprocess the whole batch.

Is WebP or JPG better for product images?

WebP is usually smaller at the same visual quality, and AVIF smaller still. In an Airpic study of 296 online shops, converting JPEG and PNG images to WebP would cut total image weight by 55 % and to AVIF by 58 %. Use JPEG only where a marketplace or your shop software requires it.

Should I remove the background before or after compressing?

Before. Remove the background on the full-size original, save that as your master file, and compress it into the three sizes afterwards. Cutting out an image that is already compressed leaves less detail around hair and fine edges.

We measured it

  • A 1.2 MB JPEG photo went down to 208 KB (83% smaller) at quality 72, in 2 seconds. (19-09-2026)
  • Across 296 Spanish online shops (9,620 homepage images), converting their JPEG and PNG files to AVIF would cut total image weight by 58%; to WebP, by 55%. (19-10-2026)

Measured on airpic.app with the GPU already running. If nobody has used it for a while, the first job takes 40 to 90 seconds longer to start.

Compress your catalogue photos now

Keep reading

Product photos for Amazon and Etsy that pass review

Product photos for Amazon and Etsy that pass review: white background main image, consistent framing, secondary shots and a workflow for a batch of twenty.

Product photos with a phone, a window and two sheets of card

Shoot product photos at home with a phone, a window and two sheets of card, then cut the background out on the original file. Settings, framing and formats.