Lossy or lossless: which compression should I use for web images?

Use lossy (JPG, WebP, AVIF) for photographs — the human eye barely notices the difference at quality 80–85, and file sizes are 5–20× smaller. Use lossless (PNG, WebP-lossless) for screenshots, UI mockups, logos and anything with sharp edges or text — lossy creates ugly artifacts around boundaries.

Does conversion preserve EXIF metadata (camera, GPS, date)?

It depends on the tool: ImageMagick and FFmpeg copy EXIF by default, while cwebp drops it unless you pass -metadata all . KaijuConverter strips metadata server-side after conversion to protect your privacy — if you need to keep camera or GPS data, use a desktop tool you control.

Lossy or lossless: which compression should I use for web images?

Use lossy (JPG, WebP, AVIF) for photographs — the human eye barely notices the difference at quality 80–85, and file sizes are 5–20× smaller. Use lossless (PNG, WebP-lossless) for screenshots, UI mockups, logos and anything with sharp edges or text — lossy creates ugly artifacts around boundaries.

Does conversion preserve EXIF metadata (camera, GPS, date)?

It depends on the tool: ImageMagick and FFmpeg copy EXIF by default, while cwebp drops it unless you pass -metadata all . KaijuConverter strips metadata server-side after conversion to protect your privacy — if you need to keep camera or GPS data, use a desktop tool you control.

Guide

WebP Image Format Guide

PC By Pablo Cirre • Updated May 7, 2026

WebP Image Format: Modern Web Imaging with Superior Compression

What is WebP?

WebP is a modern image format developed by Google, designed specifically for web usage. It uses the VP8 and VP9 video codecs to encode images with significantly better compression than traditional JPEG and PNG formats. Introduced in 2010 and continuously refined, WebP represents a major advancement in image optimization for web performance.

The format is based on the RIFF (Resource Interchange File Format) container, similar to WAV audio files. WebP images are structured with a RIFF header followed by chunks containing image data, metadata, and optional animation frames. The codec employs spatial prediction, entropy coding, and transform-based compression to achieve superior efficiency.

Compression Technology: VP8/VP9 Codec

WebP leverages the same video compression principles used in VP8 and VP9 codecs, adapted for still image encoding. This results in compression ratios typically 25-35% better than JPEG at equivalent quality levels, and 25-35% better than PNG for images with transparency.

Lossy Compression: The lossy mode divides images into 4×4 and 16×16 macroblocks, applies discrete cosine transforms (DCT), and uses entropy coding to minimize file size. Psychovisual weighting ensures compression artifacts appear less visible to human perception.

Lossless Compression: The lossless variant uses Huffman coding and cache-based color prediction. It can achieve 20-30% smaller files than PNG, particularly for photographs with subtle color gradations. It's also superior for images with large areas of solid color.

Color Support and Transparency

WebP supports both RGB and RGBA color spaces (8-bit per channel). The RGBA variant includes a full alpha channel for pixel-level transparency, eliminating the need for separate mask images or PNG fallbacks.

The format also supports ICC color profiles, allowing accurate color reproduction across devices. For advanced scenarios, WebP can encode extended color spaces, though browser support for these features remains limited.

Animation Support: WebP vs GIF

WebP natively supports animated sequences through the ANIM chunk, similar to APNG. Animated WebP files are 25-35% smaller than equivalent animated GIFs while supporting 24-bit color instead of GIF's 256-color palette limitation.

Each frame in an animated WebP can have its own duration and disposal method (none, background, previous), enabling sophisticated animation control. The format also supports blending modes for smooth transitions between frames.

Metadata and EXIF

WebP preserves EXIF metadata, IPTC information, and XMP data embedded in EXIF and XMP chunks. This makes WebP suitable for professional photography workflows where metadata preservation is critical.

Browser Support: The Compatibility Picture

Excellent Support:

Google Chrome/Chromium (version 23+, 2012)
Microsoft Edge (all versions based on Chromium)
Opera (version 12.1+)
Samsung Internet
Firefox (version 65+, 2019)

Limited/No Support:

Safari on macOS and iOS (no native support as of 2026; requires Safari 16+ for HEIC alternative)
Internet Explorer (no support)
Older Firefox versions (< 65)
Legacy mobile browsers

For web deployment, developers use the <picture> element with WebP as primary and JPEG/PNG as fallback:

<picture>
  <source srcset="image.webp" type="image/webp">
  <img src="image.jpg" alt="Description">
</picture>

Alternatively, JavaScript feature detection or server-side content negotiation (Accept header) can serve WebP to capable browsers while maintaining compatibility.

Advantages Over JPEG and PNG

vs JPEG:

25-35% smaller file size at equivalent quality
Native transparency support (no color key limitations)
Better color accuracy and wider gamut potential
Animation capability without GIF limitations
Lossless option for quality-critical images

vs PNG:

25-35% smaller for lossless images
Equivalent quality but superior compression efficiency
Faster rendering on some devices due to simpler decompression

General Advantages:

Reduced bandwidth consumption and faster page loads
Better mobile device performance (lower data usage)
Suitable for both lossy and lossless scenarios
Professional metadata support
Superior animated image format compared to GIF

Disadvantages and Limitations

Browser Compatibility: The lack of Safari support remains a significant limitation for iOS/macOS users, requiring fallback strategies.

Encoding Time: WebP encoding, especially in lossless mode, is slower than JPEG compression, increasing build time for large image collections.

Software Support: Fewer native editing tools support WebP directly. Most workflows require export from JPEG/PNG or conversion post-production.

Adoption Inertia: Despite technical superiority, many older websites and legacy systems continue using JPEG/PNG due to compatibility guarantees and long-established workflows.

Use Cases

Modern Web Development:

Product images on e-commerce sites (25-35% bandwidth savings)
Responsive image galleries requiring multiple resolutions
Social media image uploads (platform transcoding may re-encode)
Progressive web apps with offline image caching

Animated Content:

Animated UI elements and transitions
Social media clips and short-form video replacements
Loading animations and progress indicators

Professional Workflows:

Archival with metadata preservation via EXIF
Professional photography storage with lossless variant
Digital asset management systems

Performance-Critical Applications:

Mobile apps with strict bandwidth budgets
Global CDN-delivered content
Low-bandwidth regions with slow connectivity

Comparison Table

Feature	WebP	JPEG	PNG	GIF
File Size (lossy)	70-75% of JPEG	100% baseline	110-150%	200%+
File Size (lossless)	70-80% of PNG	N/A	100%	150%+
Transparency	Full alpha	No	Yes	1-bit
Animation	Yes	No	No (APNG)	Yes
Color Depth	24-bit + alpha	24-bit	24-bit + alpha	8-bit
Browser Support	95%+ (excl. Safari)	99.9%	99.9%	99.9%
Metadata	EXIF, XMP	EXIF, XMP	Limited	No
Encoding Speed	Moderate	Fast	Fast	Fast

Conclusion

WebP represents a significant step forward in web image optimization, offering superior compression, animation support, and transparency in a single format. For web developers and content creators, WebP should be the primary format choice when Safari compatibility isn't critical. For broader audiences, the <picture> element provides seamless fallback, allowing you to leverage WebP's benefits while maintaining universal compatibility.

The format's maturity (now over 15 years in development) and widespread browser support make WebP a practical choice for modern web development, particularly in performance-sensitive environments like mobile commerce and progressive web applications.

Related conversions

Most teams that read this guide convert images in one of these directions:

Related conversions

Put what you just learned into practice — convert your files now in seconds, free and without registration.

Convert →

Convert →

Convert →

Convert →

Convert →

Convert →

Frequently Asked Questions

Not yet—Safari still doesn't support AVIF. Use AVIF with WebP fallback via the <picture> element if your users are primarily on Chrome/Edge/Android. For general web development with significant iOS/macOS traffic, WebP remains more practical. AVIF is ideal for: professional photography with HDR, projects targeting modern browsers only, and sites willing to maintain responsive fallback chains. Plan to transition gradually as Safari support becomes available.

Not yet—Safari still doesn't support AVIF. usar AVIF com WebP fallback via the <picture> element if your users are primarily on Chrome/Edge/Android. para general web development com significant iOS/macOS traffic, WebP remains more practical. AVIF is ideal for: profissional photography com HDR, projects targeting moderno browsers only, e sites willing to maintain responsive fallback chains. Plan to transition gradually as Safari support becomes disponível.

Not yet—Safari still doesn't support AVIF. verwenden AVIF mit WebP fallback via the <picture> element if your users are primarily on Chrome/Edge/Android. für general web development mit significant iOS/macOS traffic, WebP remains more practical. AVIF is ideal for: professionell photography mit HDR, projects targeting modern browsers only, und sites willing to maintain responsive fallback chains. Plan to transition gradually as Safari support becomes verfügbar.

Not yet—Safari still doesn't support AVIF. usar AVIF con WebP fallback via the <picture> element if your users are primarily on Chrome/Edge/Android. para general web development con significant iOS/macOS traffic, WebP remains more practical. AVIF is ideal for: profesional photography con HDR, projects targeting moderno browsers only, y sites willing to maintain responsive fallback chains. Plan to transition gradually as Safari support becomes disponible.

Use <strong>lossy</strong> (JPG, WebP, AVIF) for photographs — the human eye barely notices the difference at quality 80–85, and file sizes are 5–20× smaller. Use <strong>lossless</strong> (PNG, WebP-lossless) for screenshots, UI mockups, logos and anything with sharp edges or text — lossy creates ugly artifacts around boundaries.

AVIF uses the AV1 codec, which employs 67+ prediction modes (vs WebP's 13) and recursive block partitioning. These advanced techniques deliver superior compression but require significantly more computational analysis. At default quality, WebP encodes in ~3-5 seconds while AVIF requires 15-60+ seconds for equivalent quality. For production pipelines with pre-encoding during builds, this is acceptable. For real-time/on-demand transcoding, slower speed becomes a practical limitation.

AVIF uses the AV1 codec, which employs 67+ prediction modes (vs WebP's 13) e recursive block partitioning. These advanced techniques deliver superior compressão mas require significantly more computational analysis. At default quality, WebP encodes in ~3-5 seconds while AVIF requires 15-60+ seconds para equivalent quality. para production pipelines com pre-encoding durante builds, this is acceptable. para real-time/on-demand transcoding, slower speed becomes a practical limitation.

AVIF uses the AV1 Codec, which employs 67+ prediction modes (vs WebP's 13) und recursive block partitioning. These advanced techniques deliver superior Komprimierung aber require significantly more computational analysis. At default quality, WebP encodes in ~3-5 seconds while AVIF requires 15-60+ seconds für equivalent quality. für production pipelines mit pre-encoding während builds, this is acceptable. für real-time/on-demand transcoding, slower speed becomes a practical limitation.

AVIF uses the AV1 codec, which employs 67+ prediction modes (vs WebP's 13) y recursive block partitioning. These advanced techniques deliver superior compresión pero require significantly more computational analysis. At default quality, WebP encodes in ~3-5 seconds while AVIF requires 15-60+ seconds para equivalent quality. para production pipelines con pre-encoding durante builds, this is acceptable. para real-time/on-demand transcoding, slower speed becomes a practical limitation.

For new projects in 2026, WebP is supported by all modern browsers (95%+ of traffic) and saves 25–35% over JPG at the same visual quality. AVIF is even more efficient (40–50% smaller) but encoding is slower and Safari support is recent. Use WebP as the default and AVIF as the progressive enhancement via <code><picture></code> with JPG fallback.

macOS 11+ supports AVIF through system frameworks, but not in Safari until macOS 14 Sonoma. For earlier macOS versions, you'll need third-party viewers (FFmpeg, ImageMagick, or dedicated AVIF viewers). On iOS, AVIF support appears in iOS 16+, but only in system applications, not Safari. Web browsers on Mac/iOS still require explicit fallback to WebP/JPEG for AVIF to be useful to most users.

MacOS 11+ suporta AVIF através de system frameworks, mas not in Safari until macOS 14 Sonoma. para earlier macOS versions, you'll need third-party viewers (FFmpeg, ImageMagick, ou dedicated AVIF viewers). no iOS, AVIF support appears in iOS 16+, mas only in system aplicativos, not Safari. Web browsers on Mac/iOS still require explicit fallback to WebP/JPEG para AVIF to be useful to most users.

MacOS 11+ unterstützt AVIF durch system frameworks, aber not in Safari until macOS 14 Sonoma. für earlier macOS versions, you'll need third-party viewers (FFmpeg, ImageMagick, oder dedicated AVIF viewers). auf iOS, AVIF support appears in iOS 16+, aber only in system Anwendungen, not Safari. Web browsers on Mac/iOS still require explicit fallback to WebP/JPEG für AVIF to be useful to most users.

MacOS 11+ soporta AVIF a través de system frameworks, pero not in Safari until macOS 14 Sonoma. para earlier macOS versions, you'll need third-party viewers (FFmpeg, ImageMagick, o dedicated AVIF viewers). en iOS, AVIF support appears in iOS 16+, pero only in system aplicaciones, not Safari. Web browsers on Mac/iOS still require explicit fallback to WebP/JPEG para AVIF to be useful to most users.

It depends on the tool: ImageMagick and FFmpeg copy EXIF by default, while cwebp drops it unless you pass <code>-metadata all</code>. KaijuConverter strips metadata server-side after conversion to protect your privacy — if you need to keep camera or GPS data, use a desktop tool you control.

AVIF lossless typically achieves 60-80% of PNG file size (meaning 20-40% smaller), though actual percentages vary by image. AVIF excels particularly on: photographic content, images with subtle color gradations, and high bit-depth content. PNG remains smaller on: images with large areas of solid color, line art with few unique colors, and simple graphics. For archival scenarios with strict quality requirements, lossless AVIF is reliable but offer slightly less compression benefit than when compressing photographs vs JPEG.

AVIF sem perdas tipicamente achieves 60-80% of PNG tamanho do arquivo (meaning 20-40% smaller), though actual percentages vary by image. AVIF excels particularly on: photographic content, images com subtle color gradations, e alta bit-depth content. PNG remains smaller on: images com large areas of solid color, line art com few unique colors, e simples graphics. para archival scenarios com strict quality requirements, sem perdas AVIF is reliable mas offer slightly less compressão benefit than when compressing photographs vs JPEG.

AVIF verlustfrei typically achieves 60-80% von PNG Dateigröße (meaning 20-40% smaller), though actual percentages vary by image. AVIF excels particularly on: photographic content, images mit subtle color gradations, und hoch bit-depth content. PNG remains smaller on: images mit large areas von solid color, line art mit few unique colors, und einfach graphics. für archival scenarios mit strict quality requirements, verlustfrei AVIF is reliable aber offer slightly less Komprimierung benefit than when compressing photographs vs JPEG.

AVIF sin pérdidas typically achieves 60-80% de PNG tamaño de archivo (meaning 20-40% smaller), though actual percentages vary by image. AVIF excels particularly on: photographic content, images con subtle color gradations, y alta bit-depth content. PNG remains smaller on: images con large areas de solid color, line art con few unique colors, y simple graphics. para archival scenarios con strict quality requirements, sin pérdidas AVIF is reliable pero offer slightly less compresión benefit than when compressing photographs vs JPEG.

Three common causes: (1) ICC color profiles dropped during conversion shift colors slightly; (2) chroma subsampling (4:2:0) reduces color accuracy in lossy JPG/WebP; (3) the new format may not support all features of the original (e.g. PNG → JPG drops transparency to white). For pixel-perfect results stick to lossless formats and preserve color profiles explicitly.