It's a common, disorienting experience: an image looks perfect on the device it was edited on, then looks noticeably different — washed out, oversaturated, slightly off — once viewed somewhere else. Color profiles are usually the reason, and they're one of the more overlooked technical details in everyday image work. This is a genuinely common and often invisible source of confusion, and understanding the underlying cause clears up a surprising number of otherwise mysterious color complaints. A quick mental note of this saves real confusion later on.
What a color profile actually is
A color profile defines the specific range of colors (the "gamut") a device or file is working with, and how numeric color values should be interpreted to produce a consistent, accurate result. Without an agreed color profile, the same stored numeric color value could be displayed as subtly different actual colors on different screens, since there's no shared reference for what that number is supposed to mean visually.
Why sRGB is the web standard
sRGB is a color profile developed specifically to represent a range of colors most conventional displays can reproduce reasonably consistently, which made it the practical standard for web images decades ago, and it remains the default assumption most browsers and websites still work with today. Images not explicitly tagged with a color profile are generally assumed to be sRGB by default, which is why exporting web images specifically in sRGB avoids a whole category of color-shift problems.
Why the same file can look different on different screens
Even with a correctly tagged sRGB image, physical differences between screens — brightness, calibration, panel technology, ambient lighting in the room — can still produce some visible variation in how identical color values actually appear. This is a separate, additional layer of variation beyond the color profile issue, and it's part of why professional photo and print work often involves specifically calibrated reference monitors, to remove as much of this display-to-display inconsistency as possible.
A common, specific mistake: exporting in Adobe RGB for the web
Adobe RGB is a wider-gamut color profile commonly used in professional photography and print work, capable of representing a broader range of colors than sRGB. Exporting a web image in Adobe RGB instead of sRGB is a common, specific mistake that causes colors — reds and greens especially — to look noticeably washed out or shifted once displayed in a browser, since most browsers and monitors are calibrated around the narrower sRGB assumption rather than Adobe RGB's wider one.
A quick way to check an image's embedded color profile
Most professional image editing software displays an image's embedded color profile in its file information or document properties panel, making it straightforward to confirm whether a specific file is tagged sRGB, Adobe RGB, or something else before publishing it somewhere the wrong profile could cause a visible color shift. For web use specifically, explicitly converting to sRGB during export, rather than assuming the working file is already in that profile, is a reliable habit that avoids this category of problem entirely.
Try the image tool yourself — free, instant, no upload to any server.
Open the toolFrequently asked questions
What color profile should I use for images going on a website?
sRGB is the standard, safest choice for web images, since it's the profile most browsers and displays assume by default, avoiding the washed-out or color-shifted look that can happen with wider-gamut profiles like Adobe RGB.
Why does my photo look different in my editing software than it does once uploaded?
This is commonly a color profile mismatch — if the image was edited or exported in a wider-gamut profile like Adobe RGB but displayed somewhere assuming sRGB, colors (particularly reds and greens) can shift noticeably from how they appeared during editing.
Can two correctly profiled images still look slightly different on different screens?
Yes. Beyond the color profile itself, physical differences between individual screens — brightness, calibration, panel type — introduce additional variation that a color profile alone doesn't fully eliminate. For most everyday purposes, simply defaulting to sRGB throughout an entire image workflow, from capture through final export, sidesteps the majority of color-profile-related surprises without needing to think carefully about the distinction on every single image.
