Why Exported AVIF Files Look Different on Windows vs macOS in 2026

You export an image from Lightroom, Affinity Photo, or Squoosh. It looks great on your Mac — rich shadows, punchy colors, exactly what you intended. You send it to a colleague on Windows and they say it looks flat, washed out, or like the saturation is turned down. You open it on their machine and they're right. Same file, same bytes — completely different result.

This isn't a bug in your export settings or a problem with the file itself. It's a fundamental difference in how Windows and macOS handle color management for AVIF files specifically — and in 2026, despite AVIF being widely supported, the gap is still very real. Here's what's actually happening and how to work around it.

↑ Same AVIF file. Left: Windows 11 rendering. Right: macOS Sequoia. The difference comes from how each OS reads the embedded color profile.

The Short Answer: Color Profiles and Decode Frameworks

AVIF files can contain embedded ICC color profiles — small chunks of data that tell the viewing software exactly what color space the image uses. The most common are sRGB (the standard web color space) and Display P3 (a wider gamut used by most modern iPhone cameras and Apple displays). When everything works correctly, the software reads the ICC profile, converts the colors appropriately for your display, and the image looks as the photographer intended.

The problem is that "reading the ICC profile correctly" requires your operating system's image decoding framework to actually honor it — and in 2026, Windows and macOS still use completely different frameworks that behave very differently with AVIF specifically.

macOS uses ImageIO, Apple's own image decoding framework, which has had full color management for AVIF since macOS Ventura. It reads the ICC profile, understands Display P3, and passes the correctly color-managed image to whatever app is displaying it. On a P3-capable display — which includes every Mac sold since 2017 — you get the full gamut.

Windows uses WIC (Windows Imaging Component) and in some cases DirectX-based decoders depending on the application. WIC's AVIF support was added via a codec update in 2022, but its ICC profile handling for AVIF has been inconsistent. In many apps, it silently falls back to treating the image as sRGB regardless of what the embedded profile says, or it maps wide-gamut colors into sRGB range using a tone-mapping approach that compresses saturation. The image looks duller not because it is — it's because the colors have been squashed into a narrower box.

↑ How the same AVIF file travels through two different decode pipelines. The ICC profile is where the paths diverge.

It Gets More Complicated: Browsers Add Another Layer

Even within the same operating system, different browsers handle AVIF color differently because each browser ships its own image decoder rather than always deferring to the OS framework. Chrome on Windows uses its own AVIF decoding path that doesn't always pass color management through to the OS display pipeline correctly. Firefox has its own decoder with its own set of quirks. Edge, being Chromium-based, mostly follows Chrome's behavior.

On macOS, Safari uses ImageIO directly, which is why Safari typically shows the most accurate AVIF colors on Mac — it's essentially the same pipeline as Preview or Photos. Chrome on Mac is better than Chrome on Windows because macOS's color management infrastructure handles the conversion even when Chrome's own decoder doesn't do it perfectly. The OS fills in the gap. Windows doesn't do that consistently.

Which Apps Get It Right in 2026

The consistency problem isn't equally bad everywhere. Applications that manage their own color engines — like Photoshop — tend to handle AVIF correctly on both platforms because they don't rely on the OS decoder alone. The places where you're most likely to see the problem are system image viewers (Windows Photos in particular) and browsers on Windows.

↑ AVIF color accuracy by app and OS in 2026. "PARTIAL" means ICC is read but wide-gamut colors are compressed. "POOR" means ICC is ignored entirely.

How to Fix It — Practical Steps for Exporters

You can't control what OS or browser your audience is using, but you can make export choices that minimize the difference. Here's what actually works:

• 01
  Embed sRGB ICC profile on export, not Display P3 If your image is going on the web — a blog, a portfolio, a product page — export with an sRGB ICC profile embedded. Convert to sRGB before exporting rather than letting the decoder do it. sRGB is the one color space that every decoder on every OS handles correctly. You lose a small amount of color range, but what you gain is consistency: the image looks the same everywhere.
• 02
  Always embed the ICC profile — never strip it Some exporters (particularly CLI tools and automated pipelines) strip ICC metadata to reduce file size. With JPEG this is often fine because sRGB is the assumed default. With AVIF it's risky — if there's no ICC profile embedded and the colors were captured in P3, the decoder has to guess, and it will guess wrong on Windows. Keep the profile in the file.
• 03
  Test on Windows before publishing If you only have a Mac, use Chrome with DevTools color emulation, or spin up a Windows 11 virtual machine (available free from Microsoft for development purposes). Open your AVIF in Windows Photos and in Chrome on Windows specifically — those are the two worst-case scenarios. If it looks good there, it'll look good everywhere.
• 04
  For professional work: keep AVIF for display, JPEG for delivery If you're sending images to clients or collaborators who will view them in various software, consider delivering JPEG or PNG alongside your AVIF. JPEG color management is far more mature and consistent across platforms. Use AVIF for your website where you control the context — it gives you smaller file sizes and better quality — but default to JPEG for anything being sent to people whose viewing environment you don't control.

Will This Get Fixed?

Slowly, yes. Microsoft has been improving WIC's AVIF handling with each Windows update, and the Chromium team has ongoing work to improve AVIF color management on Windows. The core problem — that Windows doesn't have a centralized, OS-level color management framework as mature as Apple's ColorSync — is structural and won't disappear overnight. Apple has had decades of investment in color accuracy because their professional user base (photographers, designers, video editors) demands it. Windows has been catching up, but the gap is still visible in 2026.

The practical upshot: if your workflow keeps you entirely within macOS — shooting on iPhone, editing in Lightroom or Affinity, viewing in Safari or Preview — you'll rarely see the problem. The moment your files cross over to Windows users viewing them in a browser or a standard image viewer, it shows up. Exporting in sRGB and embedding the ICC profile is the fastest, most reliable workaround until the platform support matures further.