Introduction

Modern Image Formats Explained

View contents

Modern Image Formats: WebP and AVIF Explained

Introduction

If you’re still serving images only in JPEG and PNG formats, you’re likely sending 25-50% more data than necessary. Modern image formats—specifically WebP and AVIF—offer significantly better compression without sacrificing visual quality.

The UXR SEO Analyzer checks whether your website serves images in modern formats because this directly affects page load speed, Core Web Vitals scores, and ultimately SEO rankings.

What Are Modern Image Formats?

Modern image formats use advanced compression algorithms derived from video codecs to achieve smaller file sizes while maintaining image quality.

WebP

WebP is an image format developed by Google that provides both lossy and lossless compression. It uses predictive coding from the VP8 video codec for lossy compression and a combination of Huffman encoding and LZ77 for lossless compression.

Key specifications:

  • MIME type: image/webp
  • File extension: .webp
  • Maximum dimensions: 16,383 × 16,383 pixels
  • Compression: 25-35% smaller than JPEG at equivalent quality
  • Browser support: 97%+ of browsers globally

AVIF

AVIF (AV1 Image File Format) is newer than WebP and offers even better compression. It uses the AV1 video codec and can achieve approximately 50% smaller file sizes compared to JPEG.

Key specifications:

  • MIME type: image/avif
  • File extension: .avif
  • Maximum dimensions: 2,147,483,647 × 2,147,483,647 pixels
  • Compression: ~50% smaller than JPEG at equivalent quality
  • Browser support: 85%+ of browsers globally

Why Modern Formats Matter for SEO

1. Faster Page Load Times

Images often account for 40-60% of a webpage’s total size. Using modern formats can significantly reduce this:

File Size Comparison (same image, similar quality):
┌─────────────────────────────────────────────────┐
│ Format     │ File Size │ Savings vs JPEG        │
├────────────┼───────────┼────────────────────────┤
│ JPEG       │ 500 KB    │ Baseline               │
│ WebP       │ 325 KB    │ 35% smaller            │
│ AVIF       │ 250 KB    │ 50% smaller            │
└─────────────────────────────────────────────────┘

2. Better Core Web Vitals

Since LCP (Largest Contentful Paint) often measures image loading time, smaller files directly improve this critical metric:

Metric Impact of Modern Formats
LCP Faster loading for hero images
CLS No impact (depends on dimensions)
INP Faster image decode times

3. Mobile User Experience

Mobile users on slower connections benefit most from smaller file sizes. A 50% reduction in image size can mean the difference between a 2-second and 4-second load time.

Format Comparison

Feature WebP AVIF JPEG PNG
Compression Excellent Superior Good Lossless
Lossy support Yes Yes Yes No
Lossless support Yes Yes No Yes
Transparency Yes Yes No Yes
Animation Yes Yes No No
HDR support Limited Full No No
Browser support 97%+ 85%+ 100% 100%

When to Use Each Format

Use WebP When:

  • You need broad browser compatibility
  • Encoding speed matters (faster than AVIF)
  • You want a good balance of compression and compatibility
  • Your target audience includes users on older browsers

Use AVIF When:

  • Maximum compression is the priority
  • You’re targeting modern browsers
  • You need HDR or wide color gamut support
  • You have time for slower encoding (AVIF encoding is more CPU-intensive)

Fallback Strategy

Since not all browsers support modern formats, use the <picture> element to provide fallbacks:

<picture>
  <source srcset="hero.avif" type="image/avif">
  <source srcset="hero.webp" type="image/webp">
  <img src="hero.jpg" alt="Hero image description"
       width="1200" height="600">
</picture>

This tells the browser to try AVIF first, then WebP, and finally fall back to JPEG if neither is supported.

How UXR SEO Analyzer Checks This

The analyzer examines your images and flags when:

  • Images are served only in JPEG/PNG when WebP/AVIF would reduce file sizes
  • No fallback is provided for browsers that don’t support modern formats
  • Large images (>100KB) that could benefit from modern format conversion

Common Mistakes to Avoid

1. Not Providing Fallbacks

Some older browsers and tools don’t support WebP or AVIF. Always include a fallback image.

2. Using Modern Formats for Small Images

For very small images (< 5KB), the overhead of format negotiation may not be worth it. The compression savings are minimal.

3. Ignoring Encoding Quality Settings

Modern formats have quality settings just like JPEG. Over-compressing creates visible artifacts; under-compressing wastes the format’s potential.

4. Forgetting Server Configuration

Your server needs to serve the correct MIME types:

  • WebP: image/webp
  • AVIF: image/avif

Quick Implementation Checklist

  • [ ] Convert existing JPEG/PNG images to WebP and AVIF
  • [ ] Set up <picture> elements with fallbacks
  • [ ] Configure server MIME types correctly
  • [ ] Test in multiple browsers
  • [ ] Verify file sizes are actually smaller
  • [ ] Monitor LCP improvements in Core Web Vitals

Next Steps

For detailed implementation guidance including conversion tools, quality settings, and server configuration, read our comprehensive WebP and AVIF Implementation Guide.



References

  1. MDN Web Docs - Image file type and format guide
  2. web.dev - Optimize your images
  3. Chrome Developers - Serve images in modern formats
  4. Cloudinary - AVIF vs WebP: Key Differences

Related articles

Related version

Detailed guide

Webp Avif Implementation Guide

This comprehensive guide walks you through implementing WebP and AVIF image formats on your website

Category hub

Hub

Images Seo Hub

Images are critical to user engagement—but they can also be your website's biggest performance bottleneck

In the same category

Detailed guide

Image Optimization Explained

Images are often the largest resources on a webpage, accounting for 40-60% of total page weight on most websites

Introduction

Responsive Images Explained

When you serve a 2000px wide image to a mobile phone with a 400px viewport, you're wasting bandwidth and slowing down page load