WebP vs AVIF vs JPG: which format to choose in 2026?

The stakes: why image weight matters

On the modern web, images account for an average of 50-65% of a page's total weight (source: HTTP Archive 2025). That's more than HTML, CSS, and JavaScript combined. Reducing image weight mechanically speeds up the entire page.

Since Google's Page Experience update in 2021, loading speed has been an official ranking factor. Core Web Vitals — LCP, INP, and CLS — measure how fast and stable your site feels, and the LCP (Largest Contentful Paint) is almost always determined by the main image of your page. A hero image that drops from 800 KB to 300 KB often gains 1-2 seconds of LCP, which can make the difference between a Google "Good" and "Needs Improvement" score.

The stakes are not just aesthetic. Choosing the right image format in 2026 also means optimizing your SEO, your mobile conversion rate, and your CDN bill. Let's see in detail what WebP and AVIF are worth against the old JPG.

JPG — the universal but aging standard

JPG (or JPEG, Joint Photographic Experts Group) dates from 1992. It's the most widespread digital image format in the world: all browsers, all operating systems, all editing software, and all online services read it without the slightest installation. This absolute compatibility remains its main asset in 2026.

JPG uses lossy compression optimized for photography: it analyzes areas where the human eye is poorly sensitive (subtle hue variations, micro-details in shadows) and removes information there to reduce weight. Export quality ranges from 1 (very compressed, visible artifacts) to 100 (maximum quality, little weight savings). In practice, quality 75-85 offers the best compromise for the web.

JPG's limitations: it doesn't support transparency (alpha channel), it's not ideal for vector graphics or visuals with few colors (logos, screenshots), and its aging compression is less efficient than modern formats. At equivalent quality, a JPG weighs 30-50% more than a WebP.

WebP — the modern alternative by Google

WebP was launched by Google in 2010, but its widespread adoption took a decade. It offers significantly more efficient compression than JPG (on average 25-35% less weight at equivalent visual quality), supports transparency like PNG, and can also compress animations like GIF. It's therefore a hybrid format that can replace JPG, PNG, and GIF depending on context.

WebP compatibility is now excellent in 2026: all modern browsers (Chrome, Firefox, Edge, Safari, Opera) support it natively, which represents about 97% of global users according to caniuse.com. The remaining 3% are essentially old browsers (Internet Explorer 11, old Safari versions on iOS 13 and earlier) that nobody targets in 2026.

In practice, converting all of a site's JPGs to WebP is probably the most rentable SEO optimization you can do in 2026. The average gain on LCP is 30-40% for pages whose hero image weighed over 500 KB. Our PixFlow tool (pixflow.tech/en/convert-jpg-to-webp) does batch conversion in seconds.

AVIF — the ultra-efficient newcomer

AVIF (AV1 Image File Format) is even more recent, based on the AV1 video codec developed by the Alliance for Open Media (Google, Netflix, Mozilla, Amazon, Apple). It offers even better compression than WebP: on average 50% less weight compared to JPG at equivalent visual quality, twice as efficient as WebP.

AVIF compatibility in 2026 is solid: Chrome (since 2020), Firefox (2021), Safari (iOS 16+ and macOS 13+), Edge — about 94% of global users. Non-supported users are essentially older Safari versions on iOS 15 and earlier, and some in-app browsers of social networks that are behind.

The trade-off with AVIF concerns encoding speed. Converting a JPG to AVIF takes more compute time than converting it to WebP (on average 5-10 times longer depending on target quality). For a site with hundreds of images, this can represent several hours of batch processing. But once encoded, the final file is smaller than any other format, which pays off long-term.

Numerical comparison on a typical image

Let's take a classic 4000 × 2667 pixel photo (typical resolution of a 12-megapixel digital camera), exported in three formats at quality 80:

— JPG: 1,240 KB on average, no transparency, readable everywhere. — WebP: 720 KB (–42% vs JPG), with transparency possible, supported by 97% of browsers. — AVIF: 480 KB (–61% vs JPG, –33% vs WebP), with transparency and HDR possible, supported by 94% of browsers.

The visual difference on screen is invisible to the human eye in most cases — all three renders are strictly identical for a standard photo. The gain is solely on weight and therefore on loading speed.

On Google PageSpeed score, going from a JPG hero image at 1,240 KB to an AVIF at 480 KB typically gains 1-2 points (out of 100) and 0.8-1.2 seconds of LCP on mobile 4G connection. Very significant for SEO ranking.

What format strategy to adopt in 2026

The best strategy in 2026 is to serve your images in the most modern format supported by each browser, via the HTML <picture> tag:

<picture> <source srcset="hero.avif" type="image/avif"> <source srcset="hero.webp" type="image/webp"> <img src="hero.jpg" alt="..." loading="lazy"> </picture>

This tag tells the browser: "Serve AVIF if you can, otherwise WebP, otherwise JPG as fallback". The browser automatically chooses the first format it can decode, and the user always gets the most optimal version for their context.

In practice, you gain about 60% global weight reduction on recent Chrome/Firefox/Edge users (who'll take AVIF), 40% on Safari iOS 16+ (AVIF), and 30% on all others (who'll take WebP). Only very old users receive the JPG fallback, and they've become a minority.

Our PixFlow tool offers JPG→WebP conversion (pixflow.tech/en/convert-jpg-to-webp) and JPG→AVIF (pixflow.tech/en/convert-jpg-to-avif). For graphics with transparency (logos, icons), we offer PNG→WebP and PNG→AVIF that fully preserve the alpha channel.

What about HEIC then?

You may have heard of HEIC, the default image format on iPhone since iOS 11. It's technically a close cousin of AVIF (both derive from HEVC/H.265 codec for HEIC, and AV1 for AVIF). HEIC offers compression similar to AVIF but with much lower web compatibility — it's not supported by Chrome or Firefox.

For this reason, HEIC is NOT suitable for the web. If your photos are in HEIC from your iPhone and you want to publish them online, convert them first to JPG, WebP, or AVIF (according to your strategy). Our PixFlow tool does HEIC→JPG (pixflow.tech/en/convert-heic-to-jpg) and HEIC→PNG (pixflow.tech/en/convert-heic-to-png) in seconds.

HEIC remains excellent for local iPhone storage (space savings), but for web publication, it must be converted to a web-suitable format — AVIF if possible, WebP as standard, JPG as fallback.