Listing optimization
How to compress product photos without losing quality
· 4 min read
Resize a product photo to the pixel dimensions it actually displays at, then export it as WebP or AVIF, which typically run 25 to 50 percent smaller than JPEG at the same visual quality. Aim for roughly 100 to 300KB per image depending on its role on the page. Google's Largest Contentful Paint benchmark treats a page as slow past 2.5 seconds, and an oversized hero photo is often the single asset responsible for missing it.
Do this in RorlAIProduct: Clean studio backdrop for anything boxed or bottled.Why file size is a conversion problem, not just a loading one
Largest Contentful Paint measures how long it takes the biggest visible element on a page to finish rendering, and Google's own thresholds call anything under 2.5 seconds good, 2.5 to 4 seconds needing improvement, and anything past 4 seconds poor. On a product page, the largest visible element is almost always the hero photo. That means one oversized image file can single-handedly decide whether your product page passes or fails the benchmark, regardless of how fast everything else on the page loads.
This is not an abstract scoring exercise. A slow-loading hero photo is the first thing a shopper experiences on your listing, before they have read a single word of the description or seen the price.
A realistic size budget
| Image role | Reasonable target |
|---|---|
| Primary hero photo, zoomable | 150 to 300KB |
| Secondary gallery or thumbnail image | 60 to 120KB |
| Mobile hero, above the fold | under roughly 150 to 200KB |
These are working targets gathered from current image-optimization guidance, not a single platform's official spec, and they will vary a little by the complexity of the image itself. A plain product on a white background compresses further than a busy scene before quality loss becomes visible, so treat the table as a ceiling rather than a rule to hit exactly.
The order of operations that actually saves bytes
- 1Resize before you compressA camera or a generation tool commonly exports at 3000 to 4000 pixels wide. If the photo displays in a 1200 pixel slot on your page, resize it to roughly that width first. Compressing an oversized image still ships an oversized image, just a slightly smaller one.
- 2Export as WebP where your platform supports itWebP commonly runs 25 to 35 percent smaller than a JPEG at matched visual quality, and AVIF can go further still. Most current ecommerce platforms and browsers support WebP; check whether yours serves it automatically or needs the file uploaded in that format directly.
- 3Set JPEG quality around 70 to 85 when WebP isn't an optionDefault export settings from editing software are often needlessly high. A quality setting in this range is visually indistinguishable from the original for most product photos and meaningfully smaller than a 100 percent export.
- 4Strip embedded metadataCamera settings, color profiles beyond what the page needs, and GPS data some phones embed add file weight a shopper never sees. Most compression tools strip this by default; confirm yours does.
The distinction that matters most:
- Lossless compression keeps every pixel exactly as captured and barely shrinks a photograph. It suits graphics with flat color and sharp edges, not photography
- Lossy compression discards data that is hard for a human eye to notice and is where the real savings live for a photo
- A modern encoder set correctly lands well below the point where a shopper notices the difference, long before it reaches the point where you would
Where a generated or edited photo fits
A photo produced by any editing or generation tool still needs the same resize and compression pass as a photo straight off a camera. These tools commonly export at full resolution by default, and a full-resolution export carries the same weight problem whether the pixels came from a sensor or a model. Treat it as a raw file waiting for the same budget, not as a finished asset.
Common questions
- Will compressing my product photos make them look worse?
- Not at a reasonable setting. Lossy compression in the ranges described here is tuned to discard detail a human eye does not register, so a correctly compressed photo looks identical at normal viewing size while loading in a fraction of the time.
- Should I use WebP or stick with JPEG?
- Use WebP if your store platform supports it, since it is typically 25 to 35 percent smaller than JPEG at matched quality. Fall back to a well tuned JPEG only if your platform or theme does not serve WebP automatically.
- Do I need separate image sizes for mobile and desktop?
- Ideally yes. A mobile shopper is viewing the photo in a much smaller space than a desktop shopper, so serving a smaller file on mobile saves real loading time without any visible quality loss on that screen.
- Does image file size actually affect sales, or just a speed score?
- Page speed and conversion are tied together closely enough that most ecommerce platforms now treat it as a ranking and conversion factor, not just a lab benchmark. A hero image that single-handedly pushes a page past the 2.5 second Largest Contentful Paint threshold is a real, measurable slowdown a shopper experiences, not an abstract score.