Why does dark skin look different on Instagram than it did in Lightroom?

October 15, 2026 · 8 min read

what actually changes when a file leaves Lightroom and arrives in a feed, and why

Lightroom converts the file, clipping any colour sRGB cannot hold. Export wider and the feed may read the numbers against sRGB instead. Soft proof to sRGB first and see whether the face falls outside it at all.

What changes depends on your export setting

A colour in an image file is three numbers. On their own they mean nothing. They become a colour only when something decides which colour space to read them in, and that decision is what changes between your Lightroom window and the feed.

The web settles the decision by rule, and the rule has two branches. The specification that governs colour on the web says that "colors specified in HTML, and untagged images must be treated as being in the sRGB color space ([SRGB]) unless otherwise specified" (W3C, CSS Color Module Level 4, section 3.5). The verb is doing the work. Treated means the file's numbers are left alone and held up against a smaller set of colours, so a deep saturated red from a wide space comes out as a duller red.

That branch fires when a file arrives carrying no profile. When a file does carry one, the same specification takes the other branch and requires the colours to be converted, and says a viewer "must not" simply treat the file's numbers as the screen's own (W3C, section 3.4). Which branch your photograph takes depends on whether its profile survives the trip, and you cannot see that from your desk. What export decides is whether it matters: a file converted to sRGB reads the same on both branches, and a wider file depends on the tag surviving.

So if you took the common advice and exported sRGB, the numbers did move. Lightroom converted them on the way out, and anything the smaller space could not hold was clipped there and then. Jao vdL describes a photographer's file in exactly that state: "the export already clipped it to sRGB and dulled the colors as a result" (Adobe Community, 2023). That loss happens on your own machine, before anything reaches a feed, which is the half of this problem you can actually see coming.

The specification also measures the difference. By volume of colour that can be expressed, sRGB holds 0.820 million cubic Lab units and Display P3 holds 1.233 million, so P3 carries roughly half again as much colour (W3C). Both spaces hold the same neutrals, so the extra volume is all chroma: the colours a wider space adds are the vivid ones at the edges. In a portrait the edge you care about is the warm one, where skin, lips and warm light sit, and the next section is about how little of that we could find measured.

The question is twenty years old, and one part of it has since been settled. Jeffrey Friedl, who writes some of the Lightroom export plugins photographers use, wrote in 2006 about a second marker, the Exif tag that names a file's colour space: "[a]dvanced image-processing software like Photoshop understands these tags, but I don't know of any browser that does" (Jeffrey Friedl, Digital-Image Color Spaces). That tag is a different marker from the profile, or equivalent tag, the two branches above turn on, and the specification now requires a viewer to convert whenever a profile is present. What is left of the old problem is the untagged case, and the clipping you do to your own file at export.

Scott Kelby puts the practical half of it in one line: Lightroom's editing space is wide, and "[m]any Web browsers out there use the more limited (color wise) sRGB as their default color space" (Scott Kelby, Lightroom Killer Tips, 19 April 2021). His fix is to export in sRGB rather than leave a wider space in the file.

The part about skin tones we could not find measured

It is reasonable to expect the shift to show up on deep skin first. Sked's help page says wider colour spaces show more vibrant colours, "especially reds, oranges and purples", and that an upload with saturated reds "won't display quite the same way" (Sked Social Help Center). Deep skin sits among the first two, and a face is usually the subject. That chain is reasoning. We could not find anyone who has turned it into a measurement.

We looked for the measurement. Adobe's own help pages would not load for us, so that corner is a blind spot. Within what we could open: no study and no named authority we could open reports how far real deep-skin tones sit outside the sRGB gamut, or whether they sit outside it at all in a typical exposure.

The nearest thing to an answer comes from Jao vdL, the same Community Expert who recommends Display P3 above, bounding his own advice in the same thread: "it is fairly rare for images to have large areas of color outside of sRGB. Most people would never notice and most of the web and popular apps (instagram, facebook, etc.) are still all sRGB" (Adobe Community, 2023). That is one expert's general impression, offered as a caveat and not a measurement, and it is the only answer the question has, and it carries no figure.

So the honest position is that we found no measurement, and you do not need one. You can measure your own frames in under two minutes.

The two pieces of advice are both right

Search this question and you will be told to export sRGB; a little further down you will be told to export Display P3. Neither camp is wrong, and the disagreement is informative.

The case for sRGB is predictability. It is the space the web rule assumes, so a file tagged sRGB is read the way you meant it, including on screens and in apps that do nothing clever. This is Kelby's advice and it is the safe default.

The case for Display P3 is that it stops you throwing away colour you actually captured. In the Adobe Community thread on washed-out mobile exports, Jao vdL, a Community Expert whose answer is marked correct, tells a photographer to "make sure you export to display P3 instead (the colorspace your iPhone's display is in)" (Adobe Community, 2023). When the viewing path is colour managed end to end, P3 shows colours sRGB cannot hold.

And when the path is not colour managed, P3 is the riskier choice. Sked, a scheduling tool, reports from testing its own upload route that a P3 file comes out "slightly less vibrant" and recommends sRGB (Sked Social Help Center). Sked's own explanation is narrower than a rule: "At present, Sked doesn't support files that utilise P3 colour." Take that for what it is. Sked tested its own upload route, and that says nothing about the Instagram app itself. We found no Instagram documentation on image colour that we could open.

Which means the choice depends on a viewing path you cannot see from your desk. So test it on one of your own frames.

The test: soft proof your own frame

Soft proofing shows you your file through the smaller space before you commit to it. Jao vdL demonstrates exactly this in the thread above, with out-of-gamut areas marked in red, and reports that soft proofing is not available in cloud Lightroom, so use Lightroom Classic or Photoshop.

1. Open your finished edit in Lightroom Classic and go to the Develop module. Soft proofing only

exists there. Press S (Julieanne Kost), or tick the Soft Proofing box on the toolbar below the image (Tim Grey).

1. A soft proofing section opens below the histogram (Grey).

Set its Profile to sRGB, which is the proof Jao vdL runs in the thread above.

1. Turn on the destination gamut warning with Shift and S together (Kost),

or the blank sheet of paper icon at the top right of the histogram (Grey). Areas that sRGB cannot hold turn red. The icon at the top left is a different, monitor gamut warning (Robin Whalley, Lenscraft); the one you want here is the destination warning on the right.

1. Look at the face first, then the lips, then any warm highlight on the skin or in the background.
2. If no red appears on the face, sRGB costs you nothing on this photograph. Export sRGB and stop

thinking about it.

1. If red does appear on the face, you have a real decision to make. Export sRGB and let Lightroom

perform the conversion deliberately, which protects you on uncontrolled screens, or export Display P3 and accept that some viewers will see it flatter than you do.

Then do the thing no article can do for you. Post one frame both ways a day apart, and look at both on a phone you did not edit on. Two posts a day apart is enough to compare.

Your preset, your screen, and Instagram itself

A preset writes slider values into the file. The colour space is an export setting in a different panel, so an edit can be exactly right and the export still wrong. If the colours shift from one photograph to the next while every app shows you the same thing, the cause is different (why presets look different on every photo).

Screens matter too, and not only yours. Sked notes that a desktop screen "probably doesn't support full P3, unless you're on a fancy one designed for creative professionals" (Sked Social Help Center). Your export setting cannot reach any of that.

Instagram itself is the part we cannot tell you about. Instagram Engineering has published on wide colour, and the post would not load on either of our two attempts, so we are leaving its internals alone. The web specification covers the part you control, and that is the part this article describes.

If the face itself is the thing that will not hold up after export, the exposure underneath it is the next thing to check (how to edit dark skin in harsh sun or next to a white dress).