This PNG shows a different version when opened in Chrome than in an image viewer

Why your art looks washed out in Chrome: the Apple vs Google color slapfight

TLDR: A PNG’s hidden color profile makes it look foggy in some browsers because they treat colors differently. Comments erupt into Apple vs Google snark: is Chrome right to honor profiles, is Safari smarter, or should everyone convert to sRGB so the painting stops playing tricks?

A gorgeous Victorian painting suddenly looks like it got dragged through a fog machine in Chrome, while desktop viewers show it “normal.” The author traced it to an embedded ICC color profile — basically a hidden color recipe — and said Chrome is doing the right thing by honoring it. That’s when the crowd lit the torches. One commenter, dcrazy, declared Safari has led the charge on wide-color displays and is “extremely suspicious” of claims that Apple’s browser would ignore profiles. Another user on Linux saw everything washed out everywhere and admitted they weren’t even sure which version was “real,” which perfectly sums up the chaos.

Then dylan604 dropped a spicy correction: “That’s not how color management works.” If a picture’s saved in a fancy wide palette like Display‑P3, you should convert it to old‑faithful sRGB before showing it, not just assume viewers will interpret it right. Cue the nostalgia: msla linked the legendary koolefant saga — the happy cow vs dead elephant browser color war from the early web — proving we’ve been fighting about color since dial‑up. For dessert, brokensegue flexed a wild tangent: you can sneak HDR (ultra‑bright color) into old JPEGs with hdr‑steganography. The vibe? Memes about “Chrome’s fog filter,” Apple vs Google shade, and a universal plea: just convert your images so the art looks the same everywhere.

Key Points

  • PNG appeared washed out in Chrome/Chromium and Firefox but looked normal in desktop viewers and Safari.
  • Metadata stripping, alpha checks, gamma adjustments, pixel rewrites, and gAMA removal did not fix the issue.
  • Inspection revealed an embedded ICC profile (~5KB), likely Display-P3, as the source of rendering differences.
  • Chrome honors ICC profiles and performs color management, while many desktop viewers assume or approximate sRGB.
  • The recommended fix is to convert image pixels to sRGB and embed an sRGB ICC profile using ImageMagick mogrify.

Hottest takes

"I am extremely suspicious of the author’s assertion that Safari is ignoring an embedded ICC profile" — dcrazy
"That’s not how color management is meant to work" — dylan604
"will see a dead flat elephant" — msla
Made with <3 by @siedrix and @shesho from CDMX. Powered by Forge&Hive.