Why Image Colors Change After Export: Profiles, Gamut and Browser Workflows

A file can contain an embedded profile describing how its RGB values relate to colors. A color-managed application uses that information together with the display's profile to render an appropriate appearance. An application that ignores or misinterprets the profile may display the same numbers differently. The monitor's brightness, white point, HDR mode, and viewing environment also affect what you see. Compare the exact same file in a second color-managed application before deciding that the export itself is wrong. A screenshot of one viewer is not a universal color measurement.

Keep a small reference set containing neutral grays, skin tones, saturated colors, and a smooth gradient. Compare the original and exported file under the same viewing conditions. If every image looks warmer on one screen, investigate that screen's settings rather than cooling all your files. If only one exported file changes while other references remain stable, inspect its profile and conversion path. The brightness correction guide is useful when exposure is the actual issue, but raising brightness or saturation does not repair an incorrect profile interpretation.

sRGB is a common interchange choice for web images and ordinary sharing. Display P3 and Adobe RGB describe different gamuts and should not be treated as interchangeable labels for better color. A wide-gamut source can contain colors outside sRGB. Converting those colors into a smaller gamut requires mapping them, so exact appearance cannot always be preserved. A wide-gamut file can work well in a properly managed pipeline, but a destination that strips profiles or assumes sRGB may alter its appearance. Choose based on the delivery chain rather than the largest advertised gamut.

For a general website, a deliberate sRGB export from a color-managed editor is often the simplest reliable baseline. Keep the wide-gamut master if it has value for later editing or specialized output. Test representative saturated products before a catalog migration; small color changes can affect whether a fabric or paint sample is represented fairly. The product image guide covers broader delivery considerations. A profile is not a promise that every customer's display will match yours, so critical physical color matching still needs an appropriate real-world reference.

Assigning a profile tells the application what existing numbers are supposed to mean. Converting to a profile recalculates numbers to preserve the intended appearance within the destination's limits. If an Adobe RGB image is merely relabeled as sRGB, the numbers remain the same but their interpretation changes, often shifting appearance. If the source profile is missing, assigning the correct one can be appropriate, but guessing introduces uncertainty. Find the original export settings or a known reference before experimenting. Keep an untouched copy so a mistaken assignment can be reversed.

Renaming the file extension is even less useful: it changes neither the pixel encoding nor a valid color conversion. Likewise, deleting all metadata is not automatically a safe color-management strategy because an embedded profile can be important to appearance. Separate privacy fields such as GPS from color interpretation. The EXIF guide explains camera metadata, but ICC profiles and other color information are not equivalent to GPS tags. A metadata viewer that shows no location fields does not establish that every kind of profile or ancillary data has been removed.

A browser converter typically decodes the input, draws it to a canvas, and encodes a new file. This is not a byte-preserving rewrite of the original container. The browser's decoding and canvas color-space behavior, supported output format, and bit depth influence the result. You should not assume it preserves an original ICC payload, an HDR gain map, wide-gamut samples, or camera editing metadata. For ordinary web delivery the result may be entirely suitable; for a color-critical master, use an editor that explicitly controls and documents those properties.

Prepare a deliberate delivery copy first, then use JPG to WebP or PNG to WebP for a web candidate where appropriate. Compare the downloaded output with that delivery source on representative colors. If the output differs materially, return to the color-managed export rather than stacking saturation corrections on the converter result. The lossless versus lossy guide explains why a lossless PNG encoder does not guarantee that every earlier color-space or bit-depth operation preserved the original samples. Pipeline boundaries matter more than file-extension slogans.

For web delivery, inspect the actual file served by the site. A CMS, optimization plugin, or CDN may re-encode the upload, so comparing only the local original and media-library preview misses the delivered derivative. Test the image in both light and dark page contexts because surrounding colors influence perception even when the file is unchanged. Check more than one representative device while keeping expectations realistic. You can control your export and delivery process, but not every reader's calibration, brightness, accessibility settings, or environmental lighting.

For print, follow the printer's requested color space, profile, and proofing process. Do not convert to an arbitrary CMYK profile merely because printing uses ink; different devices and papers need different output conditions, and some services explicitly request sRGB. The images for printing guide covers dimensions and resolution, which are separate from color management. Preserve the original and the chosen delivery export with clear names. Record the intended profile and any proofing approval so a later resize or compression pass does not silently replace the approved file with a visually different derivative.