Removing an embedded profile saves metadata bytes, but it can also remove information a color-managed application needs to reproduce intended color.
An ICC profile tells software what RGB values mean
The same numeric RGB triplet is not a complete description of appearance without a color-space interpretation. PNG can embed an ICC profile in the iCCP chunk so color-aware software can map samples appropriately.
PNG defines color-information precedence
The current PNG specification defines an order among color-space signaling chunks. cICP has the highest listed priority, followed by iCCP, sRGB, then the older cHRM/gAMA combination. This prevents software from treating contradictory signals as equally authoritative.
Stripping can be harmless—or not
If the image is already correctly converted to sRGB and tagged appropriately, removing a redundant large profile may be reasonable in a controlled workflow. If you simply delete the only description of a non-sRGB image, the same sample values may be interpreted differently.
Why brand colors expose mistakes
Flat logos and UI colors make small shifts easier to notice because viewers compare them against known brand values and neighboring CSS colors. A profile mistake can make a 'correct' exported asset look mismatched on the page.
Optimization needs a color policy
Decide whether your delivery pipeline converts assets to a known web color space, preserves source profiles, or handles wide-gamut material intentionally. Then configure optimization around that policy rather than letting random tools strip metadata.
Test on a color-managed path
Compare before and after files in color-aware software and on the actual target platform. A smaller byte count is not a win if the optimized file no longer represents the intended color.
Sources and technical basis
Primary technical reference: W3C Portable Network Graphics (PNG) Specification, Third Edition (2025). Web-delivery sections also use MDN guidance for responsive images where relevant.
