Product Photo Sizes and File Weight for Online Stores
For most stores, one square master at 2000 × 2000 pixels covers every use: crop and downscale from it to get gallery images at 1600 px, thumbnails at 500 px, and category tiles at 800 px. Export as WebP around quality 80, and keep the main gallery image under roughly 200 KB. That single habit removes most of the sizing confusion in a product catalogue.
The numbers below are a working default, not a rule handed down from above. What matters is that the set is consistent across the catalogue and that no page ships a file larger than it needs.
Why one huge image is the wrong default
A product page usually has one image the visitor actually looks at and several they might. If all of them ship at camera resolution, three things go wrong at once: the page takes longer to become usable on a phone, the layout shifts as images arrive, and the hosting bill grows. On a slow mobile connection, a 4 MB hero image is several seconds of staring at a placeholder.
The fix is not aggressive compression of everything. It is matching each slot to the pixels it actually occupies: a 500 px thumbnail slot does not benefit from a 3000 px source, because the browser decodes all of it and then throws most of it away.
A preset matrix that works
| Slot | Aspect | Long edge | Format | Budget |
|---|---|---|---|---|
| Main gallery image | 1:1 | 1600 px | WebP (JPEG fallback) | 120–200 KB |
| Zoom / lightbox view | 1:1 | 2000 px | WebP | 200–350 KB |
| Thumbnail strip | 1:1 | 400–500 px | WebP | 20–40 KB |
| Category tile | 1:1 or 4:3 | 800 px | WebP | 40–80 KB |
| Cart line item | 1:1 | 200 px | WebP | 10–20 KB |
| Email / newsletter | 1:1 | 600 px | JPEG | 40–70 KB |
| Marketplace feed | Per feed spec | 1600 px | JPEG | Follow feed limits |
Marketplace and ad feeds publish their own minimum sizes, aspect rules and byte limits, and they change them. Check the current specification for each channel before a bulk export rather than reusing last year's numbers. Feeds are also the one place where JPEG still wins, because the validator on the other end is often older than your browser.
Square first, then derive
Shooting or cropping to a square master makes a catalogue look intentional. Mixed aspect ratios produce grid rows of different heights, uneven whitespace around products, and tiles where one item appears twice the size of the next. Two practical rules:
- Keep the product centred with consistent padding — roughly 8–12% of the frame on each side — so nothing touches the edge when a tile is cropped.
- Derive every other size from the master by cropping and scaling, never by re-cropping the original differently for each slot.
If a product is naturally tall (a bottle) or wide (a sofa), keep the square canvas and let the empty space do its job. Catalogue consistency beats filling the frame.
Background, colour and sharpening
Most stores are best served by a plain white or very light grey background, exported as sRGB. sRGB matters: a file tagged with a wide-gamut profile can render dull or oversaturated in browsers that ignore the profile, and the same product photo appearing in two different colours on two pages is a returns problem, not a design problem.
Heavy drop shadows and gradient backgrounds look good in a mockup and compress badly. Soft gradients are exactly what JPEG and WebP handle least gracefully, so a subtle shadow can cost 30% more bytes for the same dimensions. A tight, soft shadow close to the product is cheaper and reads better at thumbnail size.
Sharpen once, after resizing, and lightly. Sharpening before scaling produces halos that survive the resize and then get amplified by compression. If you are producing several sizes, sharpen each size separately at export time rather than sharpening the master.
Transparency: often not what you want
Cut-out PNGs with alpha look flexible because they sit on any background. For a store grid they are usually the wrong choice: PNG is lossless and large, and the file carries a transparent region the page then composites over a colour you may change later. A flattened WebP or JPEG on a known background is smaller, consistent, and shows exactly what the customer will receive.
Keep alpha where it earns its keep — a logo, a floating product on a hero banner, a category icon — and flatten everywhere else.
The export order that avoids double work
- Start from the camera file or a high-resolution retouched master. Never overwrite it.
- Crop to the square, correct exposure and colour, clean the background.
- Resize to the target long edge in one step, not in several small steps.
- Sharpen lightly at the final size.
- Encode once, at the quality you intend to ship.
- Name the file and record the settings in a text note next to the masters.
Step 5 is where most catalogues lose quality: exporting a JPEG, then resizing it later, then exporting again produces two rounds of lossy encoding from a file that was already compressed. Do the resize and the encode in a single pass. The browser compressor is built for exactly that: set a longest edge and an output format, and it scales and encodes in one step without an intermediate file.
Naming, alt text and the small SEO details
Two things make a product image findable: a descriptive filename and honest alt text.
- Use a stable pattern such as
walnut-desk-lamp-01.webp, with the variant number for additional angles. Avoid spaces, camera defaults likeIMG_4821.jpg, and keyword stuffing. - Write alt text that describes what is visible — “walnut desk lamp with brass arm, lit, on a grey surface” — and skip it entirely for decorative images.
- Serve one size per slot. Loading a 2000 px file into a 200 px slot is the most common performance mistake in store themes.
- Keep the first image representative: it is the one used in shares, feeds and search results.
Common mistakes in product catalogues
- Uploading camera originals. A 6 MB file in a gallery slot costs the visitor time and costs you bandwidth for no visible benefit.
- Ignoring EXIF rotation. Photos shot in portrait can arrive sideways after processing if orientation metadata is dropped without being applied first. Check the output, not the source.
- Letting the theme resize. Server-side or CSS-side resizing still transfers and decodes the original. Export the right size instead.
- Different background colours per product. A grid of slightly different whites looks like a marketplace, not a brand.
- Compressing to the point of texture loss. Fabric weave and brushed metal are the first details to go; check a close crop at 100% before publishing.
FAQ
What resolution do I need for a printed catalogue?
Print needs about 300 pixels per inch at final size, so a 10 cm wide image needs roughly 1200 px. That is a different file from your web asset: keep a print master and export web copies separately rather than trying to serve one file to both.
Does compression affect product feed approval?
Feeds care about dimensions, background, and sometimes file size and format. Compression itself is fine as long as the product is still clearly visible and the background stays clean. Rejected images are usually too small, cropped, or show watermarks — not over-compressed.
How many images should each product have?
Enough to answer the questions a buyer would ask in a shop: front, back, detail, scale, and in use. Three to six well-shot images with consistent lighting beat twenty near-duplicates, and each one costs page weight.
Written by the PixelPress team. Last updated November 19, 2026.