I used to name all my presets after songs. Still do, actually. There’s something satisfying about dropping a preset called “Harvest Moon” onto a golden-hour portrait and watching the tones shift exactly the way you imagined. But here’s the thing nobody told me when I first started building presets: the name is the least important part. What matters is understanding what the preset is actually writing to your file, because if you don’t know that, you’re just guessing. And guessing in Lightroom is a slow, expensive habit.

Presets Are Just Saved Instructions, Not Permanent Edits

This is the foundational thing. A Lightroom preset is an XMP file, a small text-based document that stores a list of slider values and settings. When you click a preset, Lightroom reads that file and applies those values to your raw image non-destructively. Your original raw file, the CR3 or ARW or NEF sitting on your hard drive, never changes. Not one pixel. The preset is just telling Lightroom’s develop module what numbers to use.

The practical upside to this is enormous. You can stack presets, partially apply them using the Amount slider at the top of the Presets panel (that slider appeared in Lightroom Classic 7.3 and most people still haven’t found it), and undo everything instantly. The downside is that because nothing is “locked in,” a lot of photographers treat presets like Instagram filters and just click around until something looks okay. That’s not editing. That’s decorating.

Why the Same Preset Looks Different on Every Photo

One summer I put out a free preset pack, mostly warm film-inspired looks I’d been refining for about two years. It ended up getting downloaded around 50,000 times, which was genuinely surprising. But the emails that followed were predictable: “Why does this look nothing like your sample photos?”

The answer is exposure. Specifically, the relationship between your base exposure at capture and what the preset was calibrated against. If I build a preset using a photo exposed at -0.3 EV with a specific white balance, that preset is baked around those values. Drop it on an overexposed JPEG with a warm auto white balance and the result will look completely different, sometimes unusably so.

This is also why presets behave differently across camera brands. A Fujifilm X-T5 raw file has a different base tone curve response than a Sony A7 IV file, even when shot under identical conditions. Color science varies by manufacturer. A preset that looked like a clean, desaturated film stock on my Canon might look greenish and muddy on a Nikon.

The fix is calibration. Before you judge any preset, bring your exposure to a neutral starting point. Roughly 0 EV, histogram not clipping on either end, white balance set to something accurate. Apply the preset from that baseline. Then adjust. Think of it as zeroing a scale before you weigh something.

How to Read a Preset Before You Apply It

Before I apply any preset to a client gallery, I check four panels in order: Basic, Tone Curve, HSL, and Color Grading. That takes about ten seconds and tells me almost everything.

In the Basic panel, I’m looking at where the preset leaves the Highlights and Shadows sliders. A lot of cinematic presets crush Shadows to around -60 or -70 and pull Highlights to -40 or lower. That can look beautiful in the preview and wreck a backlit portrait where you needed shadow detail.

The Tone Curve tells me whether the preset uses a flat S-curve (which lifts the blacks and gives that faded film look), an aggressive S-curve (contrast-heavy), or a point curve with specific node placements. Flat S-curves typically set the black point around 20-30 in the Output column. That matters because it limits how dark your shadows can ever get, regardless of what your Blacks slider says.

HSL shows me which hues the preset targets. A lot of popular “moody” presets desaturate oranges and yellows, which looks cohesive in landscape work and removes all warmth from skin tones in portraits. Not a flaw, just a choice you need to know about before you deliver a wedding gallery.

Color Grading (the upgraded version of the old Split Toning panel, available since Lightroom Classic 10.0) shows me the midtone, shadow, and highlight hue bias. Most film presets push shadows toward teal or green and highlights toward warm yellow or orange. The Luminance sliders inside Color Grading are often set to 0 by preset creators and left there. Adjusting those, especially in shadows, can dramatically change how a preset behaves in darker tones without touching anything else.

Building Your Own Presets Around How You Actually Shoot

The most efficient thing I ever did was stop downloading other people’s presets and start building from my own starting-point edits. Not because outside presets are bad, but because mine are calibrated to my cameras, my typical lighting conditions, and the way I expose.

My workflow now: I pick three to five “anchor” edits from recent shoots, images I’m genuinely happy with. I strip them back to just the adjustments that are consistent across all five, usually a specific Tone Curve shape, a Texture value around +15, Dehaze at -5 to avoid that processed look, and a Color Grading shadow shift toward teal at about 15-20 hue with 10-15 saturation. I save that as a base preset. Everything else gets layered on top.

A base preset built this way takes about four to six hours to dial in properly. After that, it saves me somewhere between 20 and 40 minutes per session, not because it replaces editing, but because it eliminates the first ten decisions every time.

Presets aren’t shortcuts around knowing how to edit. They’re accelerators for people who already do. Get that order wrong and you’ll spend more time fixing preset damage than you would have spent editing from scratch.