“What quality should I use?” is the wrong first question. The right first question is: where on the page does this image render, and how big does it need to actually be? Settings only make sense once you know that. This guide breaks down concrete targets by image role, the lossy-vs-lossless decision most sellers get wrong, the math behind why certain numbers work, and real benchmarks from a side-by-side test.
By the end you’ll have a settings sheet you can hand to a photographer, a virtual assistant, or your future self — so every image that enters your store is compressed correctly the first time.
Lossy vs. lossless WebP: pick based on content, not habit
WebP supports two very different compression modes, and mixing them up wastes bandwidth in both directions.
- Lossy WebP behaves like JPEG — it discards information to shrink file size, controlled by a quality percentage. Use it for photography: product shots, lifestyle images, banners.
- Lossless WebP behaves like PNG — pixel-perfect, larger files, no artifacts. Use it for logos, line art, and screenshots with sharp edges and flat color, where lossy compression introduces visible fuzz around edges.
Running a logo through lossy compression to save a few kilobytes usually isn’t worth the visible softness on hard edges. Running a product photo through lossless mode wastes 3–5x the file size for a quality difference no shopper will register. The decision is content-driven, not preference-driven.
Recommended settings by image role
Here’s a settings sheet of common starting points for typical Shopify and WooCommerce themes. They hold up for most stores, but they are starting points — adjust by ±5% based on your own photography style and theme dimensions.
| Image role | Mode | Quality | Max width | Target file size |
|---|---|---|---|---|
| Hero / homepage banner | Lossy | 85–90% | 2560px | 200–400 KB |
| Product page main image | Lossy | 80–85% | 1600–2048px | 120–250 KB |
| Collection / catalog grid thumbnail | Lossy | 70–75% | 800–1200px | 40–90 KB |
| Zoom / lightbox detail image | Lossy | 85–92% | 2400–3000px | 300–500 KB |
| Logo, icon, flat graphic | Lossless | n/a | Match display size | 5–30 KB |
| Blog / editorial imagery | Lossy | 75–80% | 1200–1600px | 80–180 KB |
| Category / collection banner | Lossy | 80–85% | 1920px | 150–300 KB |
These are starting points, not laws — run a handful of your own catalog images through the WebP compressor at these settings and confirm they hold up on your actual product photography style before batching the full catalog.

An illustrative benchmark: the same photo at every quality level
To show how quality tends to map to file size, the table below uses a single representative product photo (a leather handbag on a white background, originally 4000px wide, 4.2 MB JPEG) run through WebP conversion at each quality band, resized to 2048px. These are illustrative figures — actual sizes vary by image content and encoder:
| Quality | File size | Reduction vs source | Visible quality |
|---|---|---|---|
| 100% (lossy) | 1.1 MB | −74% | Indistinguishable from source |
| 90% | 380 KB | −91% | Indistinguishable at 100% zoom |
| 85% | 260 KB | −94% | Indistinguishable at 100% zoom |
| 80% | 195 KB | −95% | Barely perceptible softness in stitching |
| 75% | 150 KB | −96% | Slight softness, fine for product pages |
| 70% | 120 KB | −97% | Visible softness, fine for thumbnails |
| 60% | 85 KB | −98% | Noticeable artifacts, decorative only |
| 50% | 62 KB | −99% | Clear blocking artifacts |
Notice the diminishing returns: dropping from 100% to 85% saves 840 KB, but dropping from 85% to 70% only saves another 140 KB while crossing into visible quality loss. The curve flattens right around 80–85%, which is why that band is the recommended default — you capture nearly all the size savings before quality becomes a tradeoff.
Why resolution targets matter as much as quality
Serving a 4000px image inside a 600px container wastes bandwidth regardless of how well it’s compressed — the browser downloads all 4000px of data just to scale it down visually. Match your maximum export width to the largest size that image slot will ever render at on your theme, including at 2x for retina displays if your theme requests it.
Shopify and WooCommerce both have predictable image slot sizes. If you don’t know your theme’s exact dimensions, the platform presets in the compressor use safe, commonly-correct defaults for product, collection, and hero images on both platforms.
Shopify image slot reference
Shopify generates multiple sized variants of every uploaded image and serves the appropriate one based on the device. The source image you upload should be large enough to cover the largest variant your theme requests. Common reference points:
- Product images: upload at 2048px wide. Shopify’s largest product variant is typically 2048px.
- Collection grid: 800–1200px is plenty for thumbnails; Shopify downscales automatically.
- Slideshow / hero: 2560px covers full-width banners on large desktops without over-serving mobile.
- Blog featured images: 1200–1600px wide.
WooCommerce image slot reference
WooCommerce generates named image sizes on upload (defined inWooCommerce → Settings → Products). The defaults are a useful starting point, but many themes override them:
- woocommerce_single (single product page): default 800px, often raised to 1600px by themes for zoom.
- woocommerce_thumbnail (catalog/shop grid): default 300px, commonly 600–800px on modern themes.
- woocommerce_gallery_thumbnail (gallery strip): default 100px.
- Full-width hero/slider: theme-dependent, typically 1920–2000px.
Check your theme’s actual registered sizes before exporting — uploading images larger than your largest registered size wastes bandwidth with no visual benefit, since WordPress will still generate downscaled variants from it.
Chroma subsampling and why you shouldn’t worry about it
Advanced encoders let you tune chroma subsampling (how aggressively color detail is reduced relative to brightness detail). The human eye is more sensitive to brightness than color, so most encoders default to 4:2:0 subsampling — keeping full brightness resolution but halving color resolution in both dimensions. For product photography on the web, the default subsampling used by browser-based WebP encoders is already tuned for photographic content and rarely needs manual intervention — it’s a rabbit hole that saves single-digit kilobytes for a lot of added complexity. Spend your time on quality and resolution instead; that’s where the real savings live.
The one exception: product photography where exact color matching matters (cosmetics, paint, fabric swatches for interior design). If shoppers rely on the photo to judge a precise color, avoid pushing quality below 82% and consider exporting at full 4:4:4 chroma if your encoder supports it. The file size cost is modest and color fidelity is the whole point of the image.
Lossless WebP vs PNG: when the swap pays off
For logos and flat graphics, lossless WebP is almost always a strict win over PNG. A typical store logo saved as a 400px-wide PNG might be 18 KB; the same as lossless WebP is typically 12–14 KB — a 20–30% reduction with identical visual output. Across a site with a logo in the header, footer, email templates, and structured data, those savings add up.
The caveat is fallback support: very old browsers (Internet Explorer, early Safari versions before 14) don’t support WebP at all. If your analytics show meaningful traffic from those browsers, keep a PNG fallback for logos. For all modern browsers — which is effectively all traffic in 2024 and beyond — lossless WebP is safe.
A quick sanity check before you commit
- Pick one representative image per role above (hero, product, thumbnail, logo).
- Compress each at the recommended setting using the matching platform preset.
- Compare output size against your current live image — you should see 40–70% reduction on photography.
- Zoom into detail-heavy areas at 100% to confirm no visible artifacting.
- Load the compressed images on an actual mid-range phone over a throttled connection to confirm the page feels faster.
- Lock in the settings and batch the rest of your catalog through the same presets.
Once you’ve settled on your numbers, the fastest way to apply them across a whole catalog is a proper batch workflow — covered in our guide on batch WebP compression workflows. And if you want to understand how these settings translate directly into Core Web Vitals scores, read our guide on reducing image size for Core Web Vitals.
