A slow gallery, a blurry logo, a 40 MB email: most image problems in E-commerce Products trace back to one early decision — the file format. Choosing deliberately takes five minutes and pays back on every single asset.
Formats worth considering
| Format | Compression | Transparency | Animation | Support (2026) |
|---|---|---|---|---|
| WebP | Lossy and lossless | Yes | Yes | over 96% of browsers in use in 2026 (caniuse) |
| AVIF | Lossy and lossless | Yes | Yes | over 93% of browsers in 2026, including Chrome, Firefox, Safari and Edge |
| JPEG | Lossy | No | No | every browser and device made in the last 25 years |
| PNG | Lossless | Yes | No | every browser since the early 2000s |
| SVG | Vector | Yes | Yes | all modern browsers |
Five formats cover effectively every E-commerce Products scenario. What separates them is below.
Start with WebP
25-34% smaller than an equivalent JPEG, per Google's published study, with support across over 96% of browsers in use in 2026 (caniuse). For most E-commerce Products work that combination — smaller files, near-universal support, transparency and animation included — makes WebP the sensible starting point. The WebP converter turns existing JPEG/PNG libraries into WebP in batches.
AVIF for the heavy lifting
AVIF goes further: roughly half the size of a comparable JPEG, and about 20% under WebP. Encoding is slower and very old browsers miss it (over 93% of browsers in 2026, including Chrome, Firefox, Safari and Edge), so the classic pattern is AVIF first with a fallback. Try one hero image through the AVIF converter and compare.
Where the classics still win
JPEG remains the file that opens absolutely everywhere — email clients, ancient CMS installs, kiosk software. PNG keeps its role wherever E-commerce Products needs sharp edges, text or transparency: a 1080p screenshot is typically 150-400 KB; a 12-megapixel photo can exceed 15 MB.
SVG for everything vector
Logos, icons and diagrams belong in SVG: icons usually weigh 1-10 KB, less than a single photo thumbnail, and they stay crisp at any resolution. Exporting a logo as a 2,000-pixel PNG when an 8 KB SVG exists is the most common self-inflicted wound in E-commerce Products.
A working strategy for E-commerce Products
Photographs go modern (WebP or AVIF) with a JPEG fallback where compatibility is unknown. Graphics and UI go PNG or SVG. Everything gets resized to its real display dimensions before upload — serving a 4000-pixel image in an 800-pixel slot is pure waste — and below-the-fold images get loading="lazy".
The quality dial matters more than the tool: JPEG at 80-85% is visually identical to 100% for most photos and roughly half the size.
E-commerce Products: quick decisions
Photos and hero images: WebP, or AVIF where you control the stack. Logos, icons, diagrams: SVG, with PNG as the raster fallback. Screenshots and UI captures: PNG.
Email attachments and downloads: JPEG, because it opens on whatever the recipient has. Short animations: animated WebP over GIF — same clip, a fraction of the megabytes. Print handoffs: TIFF or high-resolution PNG, never a web-compressed file.
Tape this list next to the upload button: every E-commerce Products decision above repeats weekly, and deciding once beats re-debating it per file.
The metadata question nobody asks
Every photo from a camera or phone carries hidden baggage: capture date, device model, exposure settings and — on phones — often GPS coordinates. Conversion is one of the moments where that baggage can be kept or dropped.
For files headed to the public web, dropped metadata is a privacy feature: nobody needs your home coordinates embedded in a product photo.
The practical rule: treat the original as the metadata archive and the converted copy as the public version. That division of labour answers most privacy and copyright questions before they come up.
Prove it with numbers
Run the page through PageSpeed Insights before touching anything and note two numbers: total image weight and Largest Contentful Paint. Those are your baseline.
Convert the images, redeploy, run the same test. On image-heavy pages the LCP shift is usually visible on the first re-test — that delta, not a blog's promise, is what justifies rolling the change across the whole site.
If the numbers barely move, your bottleneck is elsewhere — scripts or server response — and you just saved yourself from optimizing the wrong thing.
Image SEO beyond the format
Filenames describe the subject in plain words with hyphens — search engines read them, and so do you in six months. Alt text describes the image for screen readers and image search in one natural sentence, not a keyword pile.
Dimensions in the HTML (width and height attributes) stop layout shift, the CLS half of Core Web Vitals. Large previews need one meta line — max-image-preview:large — for Google Discover to show your images at full size.
None of these depend on the format, and all of them compound with it: a light, well-described, properly-sized image is the complete package for E-commerce Products.
What this means for page speed
Images are usually the heaviest asset class on a page, so format choice flows straight into Largest Contentful Paint — the Core Web Vitals metric Google weighs for ranking. Lighter images, earlier paint, better scores: the chain is that direct.
The compounding is what surprises people: 200 KB saved per image across a forty-image page is eight megabytes a visitor never downloads.
Measure before and after with PageSpeed Insights — the image-weight line item makes the improvement concrete instead of theoretical.
Common mistakes in E-commerce Products
Serving originals. Uploading camera files straight from the device puts multi-megabyte images behind every thumbnail. Resize to display dimensions first; the format choice comes second.
One format for everything. Photos, screenshots and logos compress on different curves — forcing them all into one format guarantees at least one of them is badly served.
Never measuring. PageSpeed Insights and Lighthouse both show exactly how many kilobytes your images cost. Run the test once before and once after converting, and the improvement stops being theoretical.
Where the rules bend per platform
WordPress converts uploads to WebP on modern versions but keeps the original — uploading lighter files still pays. Shopify and most e-commerce platforms recompress aggressively; feed them the highest-quality source and let the CDN do the dirty work.
Social platforms recompress everything on upload, so chasing the perfect encode for them is wasted effort — correct dimensions matter far more there.
Frequently Asked Questions
Is JPEG obsolete in 2026?
No — it is the universal fallback. Anything that must open in unknown environments (email attachments, downloads, legacy systems) still travels safest as JPEG, even when your primary delivery is WebP or AVIF.
Should logos be PNG or SVG?
SVG whenever the logo exists as vector art — a few kilobytes, infinitely sharp. PNG is the fallback for raster-only logos or platforms that reject SVG uploads.
Do I need different formats for retina screens?
Not different formats — different sizes. Serve 2× dimensions for high-density screens via srcset, and let the format (ideally WebP/AVIF) keep the bytes in check.
Are GIFs still acceptable for E-commerce Products?
Only out of habit. GIF caps at 256 colors and balloons in size: a 5-second animation easily reaches 5-10 MB; the same clip as animated WebP is a fraction of that Animated WebP delivers the same clip dramatically lighter, and every current browser plays it.
How many formats should one E-commerce Products project use?
Usually three: a modern format for delivery, a universal fallback, and SVG for vector assets. More than that and the upload rules stop being memorable, which is when mistakes creep back in.
Is it worth re-converting an old image library?
Run the arithmetic on one folder first: convert a sample, multiply the saving by the library size. Libraries behind high-traffic pages almost always justify it; archives nobody serves can stay as they are.
Start small: convert one page's images this week, measure the load time before and after, and let the result decide how far you roll it out.
Written by Giovanni Picaro, a web developer who has been building image tools and optimizing sites since 2019. Sources: MDN image format reference and Google web.dev. Last reviewed: 2026.