You edited a product photo until the colours looked perfect on your screen. The blue was vivid, the red was rich, the whole thing popped. Then you uploaded it to your store, opened the listing on your phone, and the same photo looked dull, flat and slightly washed out. Nothing you did in the edit was wrong. What went wrong was the colour space your image was saved in, and whether the colour profile travelled with it.
This is one of the most common and least understood reasons product photos look worse online than they did during editing. It has nothing to do with lighting or white balance. It is purely about how colour numbers get interpreted by browsers, apps and marketplaces. Get it right once and every image you export afterwards will look consistent everywhere. Get it wrong and you will chase a problem that keeps coming back.
What a colour space actually is
Every digital image stores colour as numbers: red, green and blue values for each pixel. But a number on its own is meaningless. "255 for red" only becomes a specific shade of red once you know which colour space those numbers belong to. A colour space is the rulebook that says exactly which hue and how saturated each number represents.
Three colour spaces matter for e-commerce sellers:
- sRGB — the world's default. Nearly every web browser, marketplace, phone and consumer screen assumes images are sRGB. It is the smallest of the common gamuts, but it is universal.
- Adobe RGB — a wider gamut that can describe more saturated greens and cyans. Designed for print workflows, not the web.
- Display P3 — a wide gamut used by modern Apple screens (recent iPhones, iPads and MacBooks) and some Android phones.
The trap is that a wider gamut sounds better. Sellers assume Adobe RGB must produce richer photos because it holds more colours. Online, the opposite happens.
Why wide-gamut photos look dull online
Here is the failure in plain terms. Suppose you edit and export in Adobe RGB, but the colour profile is not embedded in the file, or the platform strips it. The browser receives a set of colour numbers and, having no other instruction, assumes they are sRGB. But those numbers were written for the wider Adobe RGB rulebook. Reading Adobe RGB numbers as if they were sRGB shrinks and desaturates everything. Vivid reds become muddy, saturated blues go grey, and the whole image looks flat.
The reverse mistake is subtler but just as real. Even with the profile embedded, not every browser, app or social platform reliably renders wide gamuts. Some display the image as sRGB anyway. So a single product photo can look one way on a colour-managed desktop browser and another way in a marketplace app, an email client or a social feed. As one photography guide puts it, when an Adobe RGB image is uploaded to a website "it gets converted to sRGB, which can wash out the colours and make things look dull."
For a seller, that inconsistency is the enemy. A shopper who sees a dull, faded photo assumes the product itself is dull and faded. Colour that does not match the real item also drives returns, because the buyer feels misled when the parcel arrives.
The fix: sRGB everywhere, profile embedded
The reliable rule for anything that will be viewed on a screen is short: export in sRGB, and embed the colour profile. Because browsers and consumer devices are built around sRGB, an sRGB image displays the same across screens, websites, apps and marketplaces. It is the one choice that guarantees consistency.
Embedding the profile is the half that sellers most often miss. Without an embedded profile, the viewing device simply assumes sRGB by default. If your file genuinely is sRGB, that assumption is harmless. But if it is not, the colours break. Embedding the profile removes the guessing. The cost is trivial — an embedded profile adds only around 0.5 to 4KB per file — for an enormous gain in reliability.
Where to set it in common tools
- Adobe Lightroom Classic — in the Export dialog, set Colour Space to sRGB and tick "Include Colour Profile". Leave it on for every web export.
- Adobe Photoshop — use "Export As" or "Save for Web", choose sRGB, and tick "Embed Colour Profile". If you edit in a wider space, use Edit > Convert to Profile > sRGB before exporting rather than just Assign Profile.
- Capture One — in the Process Recipe, set the ICC profile to sRGB and enable "Include colour profile".
- Phone editing apps — most already export sRGB by default, which is one reason phone photos rarely suffer this problem. The issue almost always starts in desktop editing with wide-gamut defaults.
A quick comparison
| Colour space | Gamut size | Best for | Risk online |
|---|---|---|---|
| sRGB | Smallest | Web, marketplaces, social, email | None — the safe default |
| Adobe RGB | Wider | Professional print labs | High — washes out if uploaded without conversion |
| Display P3 | Wide | Apple-heavy audiences, optional secondary export | Medium — inconsistent app support |
For the overwhelming majority of e-commerce sellers, the answer is simply sRGB. Reserve Adobe RGB for files you are physically sending to a print lab, and treat Display P3 as an optional extra only if you know your audience is heavily on Apple devices — never as your only export.
Why 2026 makes this matter more, not less
It would be reasonable to assume screen technology has converged and this problem has faded. The reverse is true. Display fragmentation is worse now: recent iPhones and MacBooks render in wide-gamut Display P3, most Windows laptops show sRGB or less, and some Android phones ship HDR panels that stretch colour well beyond sRGB. A single product listing lands on all of them at once. Without a managed, consistent export, your photo looks different on every device a shopper might use — and you have no control over which one they are holding.
sRGB is the common denominator that every one of those devices understands correctly. It is not the most exciting colour space, but it is the one that behaves predictably, and predictability is what protects your conversion rate.
How resizing fits in
Colour profiles interact with your resizing and compression step, because that is often where the profile silently gets dropped. Many quick online compressors and bulk resizers strip metadata — including the ICC profile — to shave a few kilobytes. The file gets smaller, the profile disappears, and your carefully sRGB-tagged image is now an untagged file that some platforms will misread. If you have ever resized a batch and noticed the colours shifted, this is usually why.
When you prepare images for multiple marketplaces, use a tool that resizes to each marketplace's dimensions while preserving the sRGB colour profile rather than discarding it. PixelPrep is built for this exact e-commerce workflow — batch-resizing product photos to the right sizes for Shopify, Lazada, Shopee, Amazon, Qoo10 and Carousell without mangling the colour along the way. Getting the colour space right in your editor is step one; keeping it intact through resizing is step two, and both matter.
Your colour-consistency checklist
- Edit in whatever space you like, but convert to sRGB before you export for the web (Convert to Profile, not just Assign).
- Always embed the colour profile on export — the option is on by default in most tools, but confirm it.
- Keep Adobe RGB for print only. Never upload an Adobe RGB file straight to a store or marketplace.
- When resizing or compressing, use a tool that preserves the ICC profile rather than stripping metadata.
- Spot-check on a phone. View your live listing on a mobile device, since that is how most shoppers will see it.
- If colours look dull only after upload, suspect the colour space first — before you re-shoot or re-edit anything.
Accurate, consistent colour is not just about looking professional. It is about a shopper trusting that the product they receive will match the photo they clicked. Fix your colour space once, bake it into your export and resize routine, and that trust looks after itself on every screen your customers use.