sRGB vs Adobe RGB for Client Photo Delivery: Which to Send

A print looks dull on the client's phone. The gallery hero feels flat in their inbox. Both trace back to the same export setting most photographers leave on autopilot: the color space dropdown. Pick the wrong one and a properly edited file ships looking grayer than it should, on hardware you do not control.

sRGB or Adobe RGB? The short answer is: deliver sRGB. The longer one matters because the short one gets photographers in trouble every time a client questions the result. This article explains the actual gamut math, where Adobe RGB breaks in normal delivery, and the few cases where shipping Adobe RGB is the right call.

What sRGB and Adobe RGB Actually Are

sRGB came out of HP and Microsoft in 1996 and was ratified as IEC 61966-2-1 in 1999, designed for monitors, printers, and the World Wide Web. It became the assumed color space for any image without an embedded ICC profile. Adobe published Adobe RGB (1998) two years later. The goal was practical: encompass most of the colors a CMYK printer could reproduce, but express them in RGB primaries the editing software already understood.

The gamut gap is real. The standard sRGB space covers roughly 35 percent of the CIE 1931 visible color space, while Adobe RGB covers roughly 50 percent. That works out to about 40 percent more color volume in the wider space. The extra room sits where you would expect it: richer cyan-green midtones, deeper dark greens in foliage, and orange-magenta highlights that show up in dramatic skies.

Both numbers describe what the file can encode. They say nothing about what the screen showing the file can actually display, or whether the program reading the file knows which color space it is in. That second question is where every problem begins.

---

Where Adobe RGB Breaks Outside Your Edit

A color-managed program reads the embedded ICC profile and converts on the fly to the display's profile. A non-color-managed one does not. It assumes the file is sRGB and renders the numbers as if they were sRGB numbers. When those numbers actually came from Adobe RGB, the colors that should be saturated greens and reds compress toward gray, and the whole image looks dull and flat.

If you take an image with either an Adobe RGB or ProPhoto RGB colour profile and display it in a web browser, the colours may look washed out or dull.

That is the whole mechanism. The image is not wrong, it is just being read wrong. Browsers, default phone gallery apps, and the web previews inside email clients are the worst offenders. The photographer only finds out about the problem when a client asks why the colors look different from the proof on the editing screen.

There is a second, less obvious problem with Adobe RGB JPEGs. The math is unkind. Cambridge in Colour estimates that an 8-bit JPEG saved in Adobe RGB is only using about 70 percent of its bit depth on the colors actually present in a typical photo. The rest of the range is spent describing colors that are not in the image at all. In smooth tonal areas like a clear sky or a softbox-lit cheek, that wasted range shows up as visible banding.

Social platforms add another layer of unpredictability. Facebook, Instagram, and most third-party gallery hosts re-encode uploaded images to their own internal color profile, and they do not always honor the source profile faithfully. Whatever color advantage Adobe RGB had on disk vanishes the moment the file passes through that pipeline. The same holds for many client email clients, default Mac and Windows preview apps, and most consumer print kiosks.

---

When Adobe RGB Earns Its Place

Adobe RGB is not a mistake. It is a tool with a narrow set of correct uses. The first is fine-art inkjet printing on a calibrated workflow, where the printer's gamut actually exceeds sRGB in some tonal regions. Cambridge in Colour notes high-end inkjet systems can reach colors outside both sRGB and Adobe RGB at certain luminances, so shipping the wider file gives the printer profile something real to work with.

The opposite is true for consumer print labs. Cambridge in Colour points out that Fuji Frontier machines, the printers behind most school portrait, wedding album, and drugstore print services, use almost none of Adobe RGB's extra range. The only meaningful benefit Adobe RGB carries through a Frontier is in yellow highlights. Everything else collapses back to sRGB territory anyway. So if your album lab runs Frontiers, sending Adobe RGB is harmless at best and risky at worst.

The second legitimate use is the master file, not the deliverable. Editing in 16-bit Adobe RGB or 16-bit ProPhoto inside Lightroom or Capture One is fine. The wider gamut plus the extra bit depth give you room to push tones, recover highlights, and chase color you may need years from now when monitor technology has moved on. Convert to sRGB at the moment of export. The master stays wide forever; the deliverable matches the destination.

The third use is the explicit ask. A pro lab on a color-managed workflow may request Adobe RGB JPEGs and supply a custom printer profile. Ship what they request, in writing, with the profile embedded. If the audience is on the Apple side and you know they are on recent iPhones, iPads, or Macs with Display P3 panels, P3 is a cleaner wide-gamut choice than Adobe RGB for that route. Treat any wider color space the way you would treat any non-default export: only when the destination has been confirmed to read it.

---

What to Actually Deliver to Clients

For client galleries, web download links, social posts, kiosk prints, and anything you do not personally control: sRGB JPEG with the ICC profile embedded. Shotkit's photographer-facing guide reduces the rule to one line.

Every image online uses sRGB and it's ideal for the vast majority of cases.

Embed the profile even though sRGB is the default assumption. The few extra kilobytes guarantee that any color-managed program on the receiving end gets the colors right, and they cost nothing if the program ignores them.

The simplest way to make this stick is to bake the rule into your export presets and stop thinking about it on every job.

• ✓ Default delivery preset: JPEG, sRGB, color profile embedded. Use this for client galleries, web downloads, social uploads, and any consumer print path.
• ✓ Pro-lab preset: JPEG, color space matching the lab's named profile (Adobe RGB or a custom ICC), color profile embedded, full resolution. Use only after written confirmation from the lab.
• ✓ Master copy: 16-bit TIFF or PSD in Adobe RGB or ProPhoto for archival and reprocessing. Never delivered to a client.

Test your delivery flow once, then trust it. Export the same image twice: once as Adobe RGB, once as sRGB, same quality, same dimensions. Upload both to your gallery host. Open them on a phone that is not yours and on a friend's laptop. The sRGB version should look right. The Adobe RGB version may look flat, may look identical, or may look subtly different depending on whether the host re-converted on its end. If you defaulted to sRGB, the answer does not matter. If you defaulted to Adobe RGB, the wrong answer is your problem.

The dropdown is a one-time decision per delivery preset, not a per-job mystery. Default to sRGB. Reserve Adobe RGB for the small set of jobs where a named, color-managed destination has confirmed it. The Adobe RGB file is not better, it is just wider, and width is only useful when the rest of the chain knows what to do with it.