AVIF vs WebP vs JPG in 2026: Which Format Should You Actually Use?

Every few years a new image format arrives and the conversation gets confusing. WebP was supposed to replace JPG. AVIF is supposed to replace WebP. JPG has been declared dead repeatedly for 15 years and still dominates 60% of images on the web. So what should you actually use in 2026?

Here is the short version, then the long version with the reasoning, then specific recommendations for different use cases.

The short answer

If your decision is already made by the table above, you can stop reading. The rest of this article explains why these recommendations are correct and what the real performance numbers look like.

What each format actually is

JPG (JPEG) — born 1992, still dominant

JPG (technically JPEG) uses Discrete Cosine Transform compression, which discards visual information the human eye is least likely to notice. It has been the default image format on the web since the mid-1990s. Every operating system, image viewer, email client, design tool, and printing service handles JPG natively. There is no app made in the last 30 years that cannot open a JPG file.

What JPG does well: universal compatibility, predictable behavior, fast encoding and decoding on any hardware, no licensing concerns, and excellent photographic compression at high quality settings.

What JPG does badly: no transparency support, blocky artifacts at low quality settings, larger files than modern formats, no animation support.

WebP — Google's first attempt, finalized 2010

WebP was developed by Google in 2010, based on the VP8 video codec. It uses predictive coding (analyzing surrounding pixels to predict each pixel's value) rather than JPG's block-based DCT, which gives it better compression efficiency on most images. It supports both lossy and lossless compression, transparency (alpha channel), and animation.

What WebP does well: 25-35% smaller files than JPG at the same visual quality, supports transparency (unlike JPG), supports animation (replaces some GIF use cases), 97%+ browser support in 2026.

What WebP does badly: still not universally supported in desktop apps (Microsoft Office, older Photoshop versions, many photo viewers), no print driver support, slightly slower to encode than JPG.

AVIF — the new contender, finalized 2019

AVIF (AV1 Image File Format) was developed by the Alliance for Open Media — the same group behind the AV1 video codec used by Netflix and YouTube. It is essentially "take the AV1 video codec, encode a single frame, save it as an image." Because AV1 is one of the most sophisticated video codecs ever made, AVIF inherits that compression efficiency.

What AVIF does well: 50% smaller files than JPG and 20% smaller than WebP at the same visual quality, supports transparency, supports HDR and wide color gamut, supports animation, 95%+ browser support in 2026.

What AVIF does badly: slow to encode (5-10x slower than JPG), still inconsistent support in desktop apps even in 2026 (Photoshop added support in 23.2, but many other apps still cannot open AVIF), no print driver support.

Real file size comparison: what these formats actually produce

Here are real-world numbers from converting the same source image to all three formats at equivalent visual quality (no perceptible difference between them):

The pattern is consistent across image types: AVIF is roughly half the size of JPG, WebP sits in between at roughly two-thirds the size of JPG. The savings are larger for photographic content with smooth gradients and smaller for images with hard edges and limited color palettes (logos, screenshots).

Browser support in 2026 (you can stop worrying)

Global browser support in 2026: JPG is 100%, WebP is 97%+, AVIF is 95%+. The 3-5% of users on browsers that do not support AVIF are mostly on Internet Explorer (officially dead), very old versions of Android browsers, or specific embedded browsers. For any general-purpose website, AVIF support is now mainstream.

Why the format wars do not matter for desktop apps

Browser support is essentially solved. Desktop application support is still messy in 2026:

• Microsoft Word, PowerPoint, Excel: support WebP in 365 subscription versions, AVIF support is recent and inconsistent. JPG always works.
• Adobe Photoshop: WebP supported since CC 2018, AVIF supported since 23.2 (January 2022). Older Photoshop versions cannot open WebP or AVIF.
• Windows Photo Viewer: requires HEIF Image Extensions installed from Microsoft Store, even then AVIF support is unreliable. JPG always works.
• macOS Preview: WebP since macOS Sonoma (2023), AVIF since macOS Ventura (2022). JPG always works.
• Email clients (Outlook, Apple Mail, Gmail web): mostly cannot display AVIF inline. WebP inconsistent. JPG always displays.
• Print software: almost none support WebP or AVIF. Convert to JPG before printing.

Rule of thumb for 2026: AVIF and WebP are excellent for web delivery. JPG is still the safe choice for anything that will be opened in a desktop application, attached to an email, or sent to a recipient whose software you do not control.

When to use which format

Use AVIF when:

• You control the image delivery pipeline (your own website, your own CDN)
• You can serve AVIF with a WebP or JPG fallback using the HTML picture element
• Bandwidth and page load speed are critical (e-commerce, content sites, image-heavy applications)
• Your audience uses modern browsers (general consumer audience is fine; specifically-old-browser audiences are not)

Use WebP when:

• You want better compression than JPG without AVIF's encoding cost
• You need transparency support (replaces PNG for logos and icons)
• You need broader app compatibility than AVIF (more desktop tools support WebP)
• You are using a CDN or image service that does not support AVIF yet

Use JPG when:

• Sharing with people whose software you do not control (email, document attachments)
• Uploading to forms, marketplaces, or platforms with strict format requirements
• Printing photographs
• Archiving photos for long-term preservation (JPG will absolutely be readable in 2050; the others are bets)
• You need fast encoding (mobile devices, real-time generation)

Practical workflows

For website owners optimizing for speed

Convert all images to AVIF with WebP and JPG fallbacks. Use the HTML picture element to let browsers pick the best format they support:

Most static site generators (Next.js, Astro, Hugo, 11ty) have built-in image optimization that handles this automatically. For WordPress, plugins like ShortPixel or Imagify do the same. For Cloudflare customers, the Polish feature converts and serves AVIF automatically with no code changes.

Expected impact: 40-60% reduction in image bandwidth, 1-3 second improvement in Largest Contentful Paint, measurable Core Web Vitals score improvement.

For users who received an AVIF and need to open it

If you right-clicked an image on a modern website and saved it, you probably got an AVIF file. To open it in a desktop application:

For photographers maintaining a photo archive

Stick with JPG (or RAW + JPG sidecars) for the master archive. AVIF compression is impressive but it is a young format — there is no guarantee that AVIF files will be readable in 30 years. JPG is the format you can trust for long-term preservation. Use AVIF or WebP for derivative web copies, not for the originals.

For social media managers

Upload as JPG. Every social platform re-compresses uploaded images on their own servers — your AVIF or WebP source file is converted to whatever the platform internally uses (usually JPG) before being shown to viewers. Uploading AVIF gains you nothing, and may even cause upload errors on platforms that do not accept it.

The exception: profile pictures and banner images that are stored once and displayed many times. Some platforms now accept WebP for these. But for posts, JPG is fine.

What is coming next

AVIF will continue gaining adoption through 2026-2028. JPG will not die — it never has, and the long-term archive use case keeps it permanently relevant. The interesting development to watch is JPEG XL (JXL), which was finalized in 2022 but lost a Chrome support fight in 2023. If JPEG XL ever gets revived in mainstream browsers, it has technical advantages over AVIF for some use cases. Until then, AVIF is the format to bet on for new web infrastructure.

The format wars matter less than they used to. Browsers have become flexible — you can serve multiple formats and let each user's browser pick the one it supports. Tools have become better — you can convert between any of these formats in seconds. The question is not really "which format is best" but "which format is best for this specific use case" — and the table at the top of this article gives you that answer.