Colour Spaces: The Invisible Force Shaping Every Image You Capture
- Sophie Poualion

- 1 hour ago
- 8 min read
By a photographer & videographer who learned this the hard way
There’s a moment most photographers know well. You’ve spent an hour editing a portrait in Lightroom, the skin tones are warm and perfect, the shadows have that rich, inky depth, and then you export it and open it on your phone. Suddenly it looks flat. Washed out. Wrong. You haven’t touched a single slider, but somehow the image has changed.
Welcome to the world of colour spaces. It’s one of the most misunderstood corners of digital imaging, and getting it wrong costs you in ways that aren’t always obvious until it’s too late.
What Is a Colour Space, Exactly?
Think of colour as a vast, three-dimensional territory, every possible hue, saturation, and brightness that exists. The human eye can perceive an enormous chunk of this territory. Cameras, screens, and printers, however, can only handle a defined portion of it.
A colour space is essentially a map of that portion. It defines a specific, bounded range of colours, called a gamut, and assigns precise numerical values to every colour within it. When your camera writes a pixel with a value of R:220 G:45 B:60, the colour space is the codebook that tells every downstream device what that number actually means as a real-world colour.
Without a shared codebook, those numbers are ambiguous. The same value means different things in different colour spaces, and that’s exactly where problems start.
The Key Players
sRGB is the oldest and most universal standard, created in 1996 by HP and Microsoft. It covers roughly 35% of all visible colours. It was designed for monitors and the web, and it remains the lingua franca of screens, social media, and most consumer devices. When in doubt, sRGB is the safe choice.
Adobe RGB (1998) covers about 50% of visible colours, with a significantly wider reach into cyans and greens. It was designed for professional print workflows where offset presses could reproduce colours that sRGB couldn’t. If you’re printing large format work or delivering to a commercial printer, Adobe RGB is worth knowing.
Display P3 is the colour space of the modern era. Originally developed for digital cinema, it covers about 25% more colours than sRGB and has been adopted by Apple across its entire lineup, iPhones, iPads, Macs. It’s becoming the new standard for high-quality screen display.
Rec. 709 is the video equivalent of sRGB, the standard colour space for HD video. If you’re delivering broadcast content or YouTube videos, this is your baseline.
Rec. 2020 is the wide-gamut standard for 4K UHD and HDR video. Very few consumer displays can fully render it yet, but it’s the target space for future-proof video production.
ProPhoto RGB is an enormous colour space used internally by Lightroom and other applications during processing. It’s so wide that it contains colours the human eye can’t see. You’d never deliver an image in ProPhoto, but it’s useful as an internal editing space to prevent rounding errors.
Log formats (S-Log, Log-C, V-Log, C-Log) deserve a special mention. These aren’t colour spaces in the strict sense, they’re gamma curves that compress a camera’s wide dynamic range into a manageable signal. Log footage looks flat and desaturated straight out of camera, but it preserves highlight and shadow information that would otherwise be lost. Log footage always needs to be transformed into a proper colour space (like Rec. 709 or Rec. 2100 for HDR) before delivery.
How Colour Spaces Work in Practice
Modern cameras and phones don’t just capture light, they encode it. Every image file carries metadata (or in the case of video, a defined standard) that declares: “these pixel values should be interpreted according to this colour space.”
When software that understands colour management reads that file, it uses the colour space information to display the image correctly on whatever screen you’re using. A well-managed workflow looks like this:
Capture → Tag → Edit → Convert → Deliver
Each stage needs to speak the same language, or at least translate accurately between languages. When the chain breaks, when one piece of software ignores the tag, or a device assumes a different colour space — colours shift.
Choosing the Right Colour Space
For Photography
Shooting for web and social media? Shoot and deliver in sRGB. Every platform (Instagram, Facebook, X, your website) assumes sRGB. Upload an Adobe RGB image without converting it, and it will look dull and undersaturated on most screens, because the platform will strip or ignore your colour profile.
Shooting for print? Adobe RGB gives you more headroom in the greens and cyans that commercial printing can reproduce. Deliver as Adobe RGB to your lab, but confirm they accept it first.
Shooting RAW? Your colour space choice in-camera has minimal effect on the RAW file itself. RAW files contain the raw sensor data; the colour space tag is just a hint for the embedded JPEG preview. When you open the RAW in Lightroom or Capture One, you’re working in that application’s internal colour space anyway. Choose your output colour space at export time.
Shooting JPEG? Here it matters immediately. The camera bakes the colour space into the file at capture. Choose sRGB for general use; Adobe RGB only if you have a specific print workflow that calls for it.
For Video
Delivering HD for web, broadcast, or YouTube? Rec. 709 is your standard. Colour grade in Rec. 709 and deliver in Rec. 709.
Shooting for future-proofing or HDR delivery? Consider shooting in a Log format and delivering in Rec. 2020/PQ or Rec. 2020/HLG for HDR. This is a more complex workflow requiring proper HDR monitoring.
Shooting in a hybrid photo/video role? Understand that your camera may have separate colour space settings for stills and video, check both.
Compatibility: Where Things Go Wrong
This is where the real-world pain lives. Colour space mismatches between hardware and software are common, and the symptoms range from subtle to catastrophic.
Camera vs. Software
The Adobe RGB trap in Lightroom: If you shoot JPEGs in Adobe RGB but your Lightroom colour management isn’t configured correctly, or you export to sRGB without converting, the image gets re-interpreted with the wrong codebook. Greens and cyans that looked vivid in-camera become muddy on delivery.
iPhone and Display P3: Since the iPhone 7, Apple phones capture photos in Display P3. This is great, it gives you richer, more saturated colours. But if you open that photo in software that doesn’t understand P3 (older versions of Photoshop, or any application that assumes sRGB), it will display incorrectly. The colours will look oversaturated and “hot,” particularly in reds and oranges.
Log video in an SDR timeline: Import S-Log3 footage into a Premiere Pro or DaVinci Resolve timeline that’s set up for Rec. 709 with no colour management enabled, and your footage will look flat and greenish. You need either a LUT applied, or a proper colour-managed workflow, to bring it back to a normal-looking image.
Software-Specific Issues
Adobe Lightroom works internally in a wide-gamut space (based on ProPhoto RGB with a linear light response, called “Melissa RGB”). This is largely invisible to users, but it means your export settings matter enormously. Always check your export colour space: choose sRGB for web, Adobe RGB for print (when your lab requests it).
Adobe Photoshop has full colour management and will warn you with a “profile mismatch” dialogue when you open a file whose colour space differs from your working space. Pay attention to these warning, they’re telling you something important. Choosing “don’t convert” versus “convert to working space” will produce different results.
DaVinci Resolve has one of the most powerful colour management systems available, called DaVinci YRGB Colour Managed or the newer Resolve Colour Managed (RCM). When properly configured, it can automatically transform between colour spaces, converting Log footage to Rec. 709, for instance. But when it’s not configured, and you’re working in a manual workflow, you can easily end up with footage in the wrong space. A common mistake: forgetting to set the correct input colour space for a camera’s Log format, resulting in a grade that looks right on your monitor but delivers incorrectly.

Final Cut Pro uses a “wide gamut” internal colour space and manages colour automatically, generally doing a good job, but hiding the complexity from the user. If you’re rounding-tripping media between Final Cut and another application, be aware that colour information may shift if the receiving app doesn’t honour the embedded profiles.
Capture One defaults to the ICC profile of your camera model, which is generally excellent. Watch out when exporting: like Lightroom, you choose your delivery colour space at export time.
Hardware Display Mismatches
A calibrated, wide-gamut monitor is a wonderful tool, but only if your software knows you have one. Open an sRGB image on a P3 monitor in an application without colour management (a basic image viewer, a web browser without proper colour profiles, a cheap video player), and the software will treat your wide-gamut monitor as if it were sRGB, stretching those sRGB values across the full P3 gamut. The result: oversaturated, garish colours.
The fix: use colour-managed applications, and ensure your operating system colour profile matches your display. On macOS, this is generally handled automatically. On Windows, it requires more attention to your display profile settings.
The “looks great on my screen, terrible on my client’s screen” problem is almost always a colour space or calibration issue. Your wide-gamut, calibrated editing monitor shows you what the file actually contains. Their uncalibrated laptop in sRGB mode shows them a flattened, different version of reality. Soft-proofing, previewing how your image will look when converted to a target colour space, is your best defence.
The Consequences of Getting It Wrong
Let’s be specific about what bad colour space management actually costs you.
Blown-out, neon social media images. You shoot in Adobe RGB or P3, export without converting, and upload. Instagram reinterprets your wide-gamut file in sRGB. Reds become orange-red. Skin tones shift. Your carefully graded image looks like it was edited by a stranger.
Dull, flat prints. The opposite problem: you’ve been shooting and editing in sRGB, your commercial print lab works in Adobe RGB, and the conversion shifts your colours in the wrong direction. You pick up your prints and wonder why the grass looks olive.
Inconsistent client deliverables. A wedding album where the cover image (printed) looks slightly different in saturation from the digital files delivered on USB. One was exported in Adobe RGB, the other in sRGB, and nobody noticed until the client did.
Banding and posterisation. Working in a narrow colour space (like sRGB) when editing and then trying to output to a wider space can reveal banding in gradients, the sky goes from smooth to stepped, because the editing space didn’t have enough colour resolution to hold a smooth gradient.
Wasted grading time. You spend four hours colour grading a project in DaVinci Resolve, deliver it, and the client plays it on a TV with auto colour enhancement. Your careful, nuanced grade is obliterated. This isn’t always a colour space issue, but understanding the target display environment, and delivering to the appropriate standard, is part of colour space literacy.
A Practical Workflow Checklist
The Bottom Line
Colour spaces are not a “set it and forget it” issue, they’re a living part of every workflow decision you make, from the camera you pick up to the export dialogue before you hit send.
The good news: once you understand the logic, that colour spaces are codebooks, that mismatches mean mistranslation, and that every link in the chain needs to speak the same language, the specific decisions become intuitive. You stop wondering why your images look different across devices and start controlling that outcome instead.
The goal isn’t to make colour management invisible. It’s to make you the one in control of it.
Questions? Colour horror stories? Drop them in the comments — I've seen most of them, and survived.

Comments