sRGB, Adobe RGB or Display P3? Choosing a color space for export

A color space decides how the numbers in your JPEG turn into actual colors. Pick the wrong one and a vivid photo can look dull or oddly oversaturated on someone else's screen.

Two people can open the same JPEG and see noticeably different colors. Some of that comes from screens that are calibrated differently, but a surprising amount comes from color spaces: the file says one thing, the viewer's software assumes another, and the result is a sunset that looks washed out or a face that looks sunburned. Understanding color spaces takes about ten minutes and will save you from that kind of mismatch for good.

What a color space actually is

A digital image stores each pixel as three numbers, red, green and blue. On their own those numbers are meaningless. "Red 255" only becomes a specific, measurable red once you know which color space the file uses. The color space defines three things:

• The primaries: exactly which red, green and blue the maximum values correspond to.
• The white point: what neutral white looks like (the common spaces here all use D65, roughly daylight).
• The tone response: how numbers map to brightness, often called gamma or transfer function.

The range of colors a space can describe is called its gamut. A wider gamut can describe more saturated colors, especially deep greens, cyans and some reds and oranges.

The three spaces you will meet

sRGB

sRGB is the lowest common denominator, and that is its strength. Browsers, operating systems, phones, social platforms and image viewers all assume sRGB when they are not told otherwise. A file in sRGB looks close to right almost everywhere, even in software that ignores embedded profiles.

Adobe RGB

Adobe RGB covers more of the colors that good inkjet printers can reproduce, particularly saturated cyan-greens. Many cameras offer it as a setting for in-camera JPEGs. Its weakness is compatibility: when an Adobe RGB file is displayed as if it were sRGB, the same numbers produce less saturated colors, so the image looks flat and muddy.

Display P3

Display P3 is the space used by many modern displays, starting with Apple devices. It is roughly a quarter larger than sRGB and is common on phones that can show richer reds and greens. Phone cameras often save their own photos in P3. Like Adobe RGB, it depends on color-managed software to look right.

Why the camera setting does not matter for RAW

Your camera menu probably has an sRGB / Adobe RGB option. For RAW shooters, that setting only affects the in-camera JPEG and the small preview embedded inside the RAW file. The RAW data itself is sensor data with no color space applied yet. The color space is chosen later, when the RAW is developed and exported.

That is one more advantage of shooting RAW, covered in the RAW vs JPEG guide: you can export the same photo in sRGB for Instagram and, with a full editor, in a wider space for a print lab, without having committed to either in the field.

Color management in one paragraph

A color-managed application reads the profile embedded in an image, reads the profile of your display, and converts between them so colors appear as intended. Modern browsers and operating systems are generally color managed for images with embedded profiles. Untagged images, images in some older apps, and images that pass through processing pipelines that strip profiles are where problems appear. When the profile is lost, the software falls back to assuming sRGB. If the file actually was sRGB, nothing goes wrong. That asymmetry is the whole argument for sRGB on the web.

So which should you use?

For the web, social media, messaging and email: sRGB

Platforms frequently recompress uploads and may convert or strip profiles along the way. Exporting in sRGB means the worst case is "looks as intended." Wide-gamut exports can gain a little saturation on capable screens when everything goes right, and look worse on everything else when it does not. For most photos the gain is small, because most real-world colors fit comfortably inside sRGB.

For prints: ask the lab

Many consumer print labs request sRGB and convert it themselves. Some professional labs accept Adobe RGB or their own printer profiles and can reproduce slightly richer colors on suitable paper. Use what the lab asks for. If it says nothing, sRGB is the safe default.

For further editing: work wide, deliver narrow

If you are handing a file to a retoucher or a designer, a 16-bit TIFF in a wide space keeps the most information for later. The final delivery for screens should still be converted to sRGB at the end.

Where RAWSnap fits

RAWSnap develops RAW files directly to sRGB and exports 8-bit JPEGs. There is no color-space choice, by design: the tool is built for photos that will be shared on screens, where sRGB is the right answer. If you need Adobe RGB output for a specific print workflow or 16-bit files for retouching, use a full RAW editor; the editor comparison lists free and paid options.

Spotting a color-space problem

• Image looks dull and desaturated, especially greens and reds on one device or app but fine elsewhere: likely a wide-gamut file shown as sRGB. Re-export in sRGB.
• Image looks oversaturated or skin looks orange: an sRGB image is being stretched to a wide-gamut display by unmanaged software. This is a viewer problem; the file itself is fine.
• Colors change after uploading: the platform converted or stripped the profile. Uploading sRGB minimizes the shift.
• Everything looks too warm or too cool everywhere: that is not a color-space issue but white balance. See the white balance guide.

Your screen matters too

Even a perfectly tagged sRGB file can look different on two screens. Phone displays often ship with "vivid" color modes, and laptop screens vary in brightness and color accuracy. If color consistency matters to you, a few habits help:

1. Edit at a moderate screen brightness. Very bright screens make photos look brighter than they will print.
2. Check your phone's display mode; a "natural" or "standard" mode is closer to what others see.
3. For print work, consider a hardware calibrator for your monitor.
4. Look at an important export on a second device before sending it out.

Wide gamut is not the same as HDR

Display P3 is sometimes confused with HDR photos. They are different ideas. Gamut is about how saturated colors can be; HDR is about how bright highlights can be compared with the rest of the image. A standard JPEG in sRGB or P3 is still a standard dynamic range image. HDR photo formats exist, but they are a separate topic and are not something a typical JPEG export produces.

FAQ

Should I set my camera to Adobe RGB if I shoot RAW?

It does not change the RAW data, only the in-camera JPEG and preview. You choose the color space when you develop the RAW, so either setting is fine for RAW shooters.

Is sRGB "worse" than Adobe RGB?

It has a smaller gamut, but most everyday colors fit within it, and it is the most compatible space. For screens it is usually the best practical choice.

Why does my photo look washed out on Instagram?

A common cause is uploading a wide-gamut file (Adobe RGB or sometimes P3) that is then treated as sRGB. Export in sRGB before uploading.

Which color space does RAWSnap export?

sRGB, 8-bit JPEG. It is designed for sharing on screens. For wide-gamut or 16-bit output, use a full RAW editor.

Do I need to embed a color profile?

For sRGB it is good practice but not critical, since untagged images are assumed to be sRGB. For any wider space, the profile must be embedded or the colors will be wrong.