Why do presets look different on every photo?
· 8 min read
This guide explains what a Lightroom preset actually stores, and why the same preset produces a different result on two photos of the same person. It then gives four documented causes to check, and where skin tone sits in the mechanism.
Short answer
Why do presets look different on every photo?
Because Lightroom develop settings are absolute. A preset overwrites the settings it includes with stored numbers, so applying the same fixed Exposure value to two frames shot a stop apart does not correct the difference between them. The exception is a preset saved with Auto Settings, which re-analyses each photo.
What a preset actually saves
One clause in Adobe's description of a preset explains the whole problem: "Presets you create are based on the current settings of the selected photo" (Adobe). A preset is a snapshot of one photo's finished slider positions. It carries no record of how that photo was exposed, what light it was shot in, or what to do when it meets a different one.
The load-bearing word is absolute, and Adobe's own staff says it plainly. Rikk Flohr of Adobe Photography Customer Advocacy, answering a request open on Adobe's ideas board since March 2011, wrote in February 2023: "Relative Presets have never been released. To date, the only place to perform a relative adjustment to a range of images is the Quick Develop Panel" (Adobe community). Photography educator Tim Grey states the same thing from outside Adobe: "the adjustments saved in presets in Lightroom are absolute adjustments rather than relative adjustments" (Tim Grey).
So a preset that looks unreliable is doing the identical thing to every photo. Two photos that started in different places end up in different places, because the preset moved both of them to the same numbers.
Adobe has built per-photo adaptation three times, and never to skin tone
Adobe has engineered per-image adaptation into presets on three separate occasions, each as its own named feature.
Auto Settings is the first. Grey describes it in one sentence containing both halves of the mechanism: "The Auto Settings option will cause each image to be analyzed and adjusted with the Auto adjustment individually, while other adjustments saved with the preset will be applied with the same settings for all photos to which the preset is applied" (Tim Grey). If the preset you bought has Auto Settings ticked, you are getting different exposure, contrast, highlights, shadows, whites and blacks on every frame by design.
ISO adaptive presets are the second, shipped in Lightroom Classic 9.3 and Camera Raw 12.3 in June 2020, interpolating between two stored values (Greg Benz). Julieanne Kost, Principal Digital Imaging Evangelist at Adobe, says they "allow a single preset to apply different edit settings to different photos depending on their ISO settings," and specifies they only work as intended across images "taken with the same camera" (Julieanne Kost).
Adaptive presets are the third, from 2023. Rob Sylvan, who answers Lightroom questions on the KelbyOne Help Desk and has written several Lightroom books, describes them as using Lightroom's AI masking tools to "automatically detect either a person, sky, or subject respectively, then create a mask for it, and then apply the included settings to that mask" (Lightroom Killer Tips). The mask is regenerated per photo, which is why hovering over one can take a moment.
Now look at what each of the three adapts to: the image histogram, a number in the EXIF, and the outline of a person. A preset can be taught to respond to how bright the frame is, how noisy the sensor was, and where the face sits in the composition. None of the three responds to the tone of the face itself, and that boundary is drawn by Adobe's own feature list.
Four documented causes to check first
Each of these has Adobe documentation behind it. Work through them before you conclude the problem is your subject.
One. White balance, if your preset was authored on a raw file and you are applying it to a JPEG. This is the single slider where Adobe documents a different unit per file type: raw files let you "adjust the color temperature as if you were changing a setting in a camera during capture", while "when working with JPEG, TIFF, and PSD files, you work in a scale of -100 to 100 rather than the Kelvin scale" (Adobe). Scott Kelby puts the same point in a sentence: with a JPEG "you're adjusting a white balance already embedded in your file, so you're not adjusting Kelvin numbers" (Lightroom Killer Tips). The two sliders are measured in different units, so the same stored number does not mean the same thing on both. That is one reason a pack can look right on a seller's raw sample and land differently on a phone JPEG. If white balance is where your preset goes wrong, setting it deliberately is the fix rather than scaling the preset.
Two. Auto Settings inside the preset, per the section above. Open the preset and look for it before you blame your photos.
Three. A camera profile the photo cannot use. Adobe ships a warning string for this, quoted by a user in Adobe's own community: "This preset includes a profile that was made for a different camera which cannot be applied to this photo" (Adobe community). Adobe documents the general case and the preference that reveals it: "There are some presets which are partially compatible with the selected photo as not all of the settings of the preset can be applied to the photo", and Show Partially Compatible Develop Presets in Preferences makes them visible (Adobe). It is not a mistake on your part.
Four. Process version. Adobe defines it as "the Camera Raw technology that Lightroom Classic uses to adjust and render photos in the Develop module", and warns that updating it "may incur significant visual changes to your photos" (Adobe). Grey explains why an old preset can misbehave: the sliders themselves differ between versions, so process version 1 had "Exposure, Recovery, Fill Light, Blacks, Brightness, and Contrast" where the current version has "Exposure, Contrast, Highlights, Shadows, Whites, and Blacks" (Tim Grey). A preset file can carry a process version instruction, which Adobe Community Expert Johan Elzenga confirmed on Adobe's bug board in 2018 (Adobe community). That thread's version numbers are from 2018 and are not current guidance; the mechanism is the point.
The Amount slider, and what it cannot do
Lightroom Classic has something close to a strength control: "Adjust the intensity of the applied preset using the Preset Amount slider" (Adobe). Two limits are worth knowing before you reach for it.
It is unavailable on some presets, because the author has to enable Support Amount Slider when creating one, and "if you are unable to select the Support Amount Slider option, that indicates the selected settings don't support the Amount slider" (Adobe). Users do run into the greyed-out version (Adobe community). It also scales the whole preset proportionally, so if a preset is too warm but correctly contrasted on your photo, dialling Amount down reduces both. It cannot fix a preset that is wrong in one direction and right in another.
What this means for skin tones
This section is the article's own explanation. Nobody has published it as a finding. No Adobe page discusses how a preset behaves across skin tones, and no named authority says absolute presets fail worse on deeper skin. The mechanism below does not establish it either, so it is worth being exact about what it shows.
Start with Adobe's definition of the tone curve. "The horizontal axis represents the original tone values (input values), with black on the left and progressively lighter values toward the right" (Adobe). The curve is a function of the tones already in the photo. It has no idea what is in the picture.
Two things follow from that. How far the curve moves a tone decides how much brighter or darker that tone becomes. The steepness of the curve at that point sets how much separation survives between tones near it. Both vary along the curve, so one stored curve can change two photos by different amounts depending on where their tones sit.
Skin itself varies a great deal before a camera is involved. A team led by UCSF measured skin pigmentation on 789 people with a spectrophotometer held against the skin and found "a wide ITA range of -75.8 to 61.9", from a sample they describe as coming from "a predominantly lightly-pigmented geography" (Lipnick et al.). ITA is an angle calculated from how light and how yellow the reflected light is, so a higher number means lighter skin. That paper is a February 2025 preprint and has not been peer reviewed.
What the mechanism does not tell you is where any particular face sits. That depends on exposure and lighting as much as on the subject, and a face covers a spread of values across the range. So the claim this supports is narrow: if two photos place a face in different parts of the range, a fixed curve can change them by different amounts. Which of the two comes off worse is not something the mechanism decides. The orange and grey cast article takes up the same question for colour.
The deflationary reading is correct too: dark skin tones "have some extra considerations but aren't necessarily more difficult to edit, as they follow the same rules and suggestions as light skin" (The Drawhorns).
What is worth knowing is that the preset comes last. Google retuned capture on the Pixel because, in the words of its image equity lead, "stray light had a tendency to disproportionately wash out darker skin tones" (Google). Ava Berkofsky, ASC, director of photography on HBO's Insecure, made a related point about setting exposure on a camera: "If you've got black skin, [dialing it] up to 50 or 70 is just going to make the rest of the image look weird" (Mic). Both are about the camera, before any Lightroom setting is applied. If capture has already placed two frames at different brightness, fixed numbers land differently on each.
What to do after the preset lands
This is the order to work in.
- Rule out the four documented causes above before touching a slider.
- Set exposure per frame. A preset carrying a fixed Exposure value cannot do this for you, because it wrote a number rather than an adjustment. A preset with Auto Settings ticked does it for you, which is worth checking before you redo it by hand.
- Set white balance once for each lighting situation, then copy it to every frame shot in that light.
- Judge the result on the person, then decide whether the preset's look still needs scaling.
Check the four documented causes first, set exposure and white balance yourself, then judge whether the preset's look still fits.
Questions people ask
- Does turning the Amount slider down fix a preset that looks wrong?
- Sometimes, and not always. The Amount slider scales the entire preset proportionally, so it reduces the parts that were right along with the parts that were wrong. Adobe also documents that the slider is unavailable unless the preset's author enabled support for it, so it may be greyed out entirely on a purchased pack.
- Why does the same preset look right on my camera files and wrong on phone photos?
- White balance units are one documented cause. Adobe puts raw files on the Kelvin scale and JPEG, TIFF and PSD files on a scale of minus 100 to plus 100. The two sliders use different units, so a temperature value a preset stored from a raw file does not mean the same thing on a JPEG.
- Is my preset broken if part of it does not apply?
- No, and Adobe documents this behaviour. A preset can be partially compatible when a setting it carries cannot apply to your photo, such as a camera-specific profile. Lightroom Classic hides partially compatible presets by default, and you can reveal them by turning on Show Partially Compatible Develop Presets in Preferences.
- Are deeper skin tones harder to edit with presets?
- No published source says so, and the techniques do not change. The mechanism does not settle it either: a preset stores a fixed tone curve whose effect depends on the tones a photo starts with, and where a face sits in that range depends on exposure and lighting as much as on the subject.

