There has never been a more confusing time to choose an image format. JPEG has been the safe answer for thirty years. WebP has been pushed by Google for fifteen and is now near-universal. AVIF is the new compression king on paper, but its encoding is slow and the tooling is still catching up. Then there's JPEG XL, HEIF, and a handful of others that occasionally surface in the conversation.
This guide cuts through that noise with the simplest possible question: in 2026, given a real image and a real use case, which format should you pick? The answer is shorter than the format wars suggest.
The quick verdict
If you don't read the rest of this article, here's the summary that covers 90% of cases:
- Building a website in 2026? Use AVIF as primary, WebP as fallback, JPEG as last resort.
- Sending an image by email or chat? JPEG. Universal compatibility wins.
- Saving a screenshot or graphic with sharp edges? PNG (or WebP lossless), not any of the three above.
- Archiving photos for the long term? JPEG — it will still be readable in 50 years; AVIF probably will be too, but JPEG is the safer bet.
- Replacing GIFs with animation? AVIF or WebP. Either is dramatically smaller.
JPEG: still the lingua franca
JPEG (technically JFIF, but no one calls it that) launched in 1992 and has been the default photographic image format ever since. It's a lossy format optimised for natural images: photographs of the real world, with smooth gradients and continuous tones. For graphics with sharp edges or solid colours, JPEG produces visible artifacts and is the wrong choice.
Strengths:
- Universal support — every device, every browser, every OS, since the 1990s.
- Mature tooling. Every camera, every phone, every print shop speaks JPEG natively.
- Predictable quality settings. 'Quality 75' has the same meaning across every JPEG encoder.
- Modern encoders (mozjpeg) compress 10–15% smaller than 1990s encoders at identical quality.
Weaknesses:
- Larger files than WebP (~25% bigger) and AVIF (~50% bigger) at equivalent quality.
- No alpha transparency. (You need PNG, WebP, or AVIF for that.)
- Visible artifacts on text, line art, and high-contrast edges.
- Generational loss: every re-save degrades quality slightly.
WebP: the safe modern default
Google introduced WebP in 2010 and has been pushing it relentlessly ever since. By 2026, browser support is effectively universal — Chrome, Firefox, Safari, and Edge all encode and decode it natively, and the long tail of holdouts is below 3% globally. WebP supports both lossy compression (similar engine to JPEG, ~25% smaller files at equivalent quality) and lossless compression (alternative to PNG, often smaller too).
Strengths:
- 25–35% smaller than JPEG at equivalent visual quality.
- Supports alpha transparency (the PNG strength) and animation (the GIF replacement) in one format.
- Fast encoding — only marginally slower than JPEG.
- Excellent tool support: every modern image editor, every CDN, every CMS handles WebP without complaint.
Weaknesses:
- Still 25–30% larger than AVIF.
- Email clients and some legacy desktop apps don't render it (use JPEG for email).
- Older systems (pre-2018) may not display it.
AVIF: best compression, slowest encoding
AVIF is the image format derived from the AV1 video codec. It launched in 2019, hit broad browser support in 2022, and by 2026 covers about 94% of global users. On compression, it's the clear winner: at the same visual quality, AVIF files are typically 30% smaller than WebP and 50% smaller than JPEG. It supports lossy and lossless modes, alpha transparency, animation, HDR, and 10/12-bit colour depth.
Strengths:
- Smallest files of any widely-supported format. Often dramatically smaller — a 1MB JPEG can become a 400KB AVIF with no visible quality loss.
- HDR support and 10/12-bit colour for high-quality photography.
- Animation support that crushes GIF (90%+ smaller).
- Lossless mode that often beats lossless WebP and PNG.
Weaknesses:
- Encoding is slow — often 5–20× slower than JPEG or WebP. A noticeable wait when batch processing.
- Decoding is also slower (though not user-noticeable).
- Browser support is broad but not universal (~94% in 2026).
- Tool support is improving but still spotty in older image editors and CMSs.
Side-by-side: file size and quality
Concrete numbers from a representative test photo (2400×1600 landscape photograph, lots of detail and gradients):
- JPEG quality 90: 1100 KB
- JPEG quality 75: 480 KB
- WebP quality 75: 360 KB (~25% smaller than JPEG 75)
- AVIF quality 60 (visually equivalent to JPEG 75): 220 KB (~55% smaller than JPEG 75)
Numbers vary by image — high-detail photos benefit most from AVIF; flat illustrations or simple photos see less dramatic gains. But the relative ordering (AVIF smallest, WebP middle, JPEG largest) holds across virtually all natural images.
Recommendations by use case
For a website
Serve AVIF as the primary format with WebP as fallback (most CDNs and frameworks handle this with a single configuration). The HTML <picture> element handles the negotiation gracefully. If you can only pick one, WebP — broader support, faster generation, only marginally bigger files.
For email and messaging
JPEG. Email clients lag the web by a decade in format support. WebP support in Gmail is OK; in older Outlook installations it's a coin flip. JPEG just works.
For archival and long-term storage
Counterintuitive answer: JPEG (or RAW for the originals). Format longevity matters here, and JPEG has thirty years of universal compatibility. AVIF will probably still be readable in 50 years, but 'probably' isn't what you want for irreplaceable photos. Keep originals in JPEG for compatibility, generate AVIF on demand for serving.
For animation (replacing GIF)
AVIF or animated WebP. Both produce files 80–95% smaller than the equivalent GIF, with smoother motion and more colours. Don't use GIF for new content unless your distribution channel literally requires it.
The bottom line
WebP is the boring, correct answer for most modern web work. AVIF is the right answer if you can spend the encoding time and want every last kilobyte saved. JPEG is the right answer when compatibility outweighs efficiency, which is more often than the format-war discourse suggests. Pick based on where the file is going, not which format scored highest in the latest benchmark.