A few years back I released a preset pack on a Tuesday afternoon, mostly as an experiment. I named every preset after a Fleetwood Mac song, spent an entire weekend dialing in the curves, and figured maybe a few hundred people would grab it. By Friday it had 50,000 downloads. My inbox was chaos. ISO, my cat, was completely unbothered.

What surprised me wasn’t the download count. It was the emails I got afterward. People asking why the preset looked nothing like the preview on their own photos. Why the skin tones went orange. Why the shadows crushed completely in their beach shots but looked perfect in the moody forest image from the thumbnail. They weren’t doing anything wrong. They just didn’t understand what a preset is actually doing to their file, and nobody had bothered to explain it.

Presets Are Instructions, Not Filters

This is the part most tutorials skip. A Lightroom preset is not a static filter baked on top of your image the way an Instagram filter works. It’s a set of instructions, stored in an .xmp or .lrtemplate file, that tells Lightroom how to move sliders on whatever raw file you feed it.

When you apply a preset, Lightroom reads those instructions and adjusts your Exposure, Tone Curve, HSL values, Color Grading wheels, and anything else the preset creator touched. The result depends entirely on what your raw file looks like before the preset runs. A preset that drops Exposure by 0.7 stops looks great on a shot that came in at +0.3. On a photo you already exposed conservatively at -0.5, you’re now two stops dark and wondering why everything looks like a noir film.

The raw file is the variable. The preset is the equation. Same equation, different variable, different result. That’s not a bug in the preset. That’s just math.

The Baseline Problem Nobody Talks About

Most preset creators, myself included, build their presets off a specific starting point. Usually a neutral raw file with exposure close to 0, highlights and shadows untouched, white balance set to Auto or Kelvin somewhere in the 5000-5500K range. If your file doesn’t match that baseline, the preset is working against you from the first slider.

Here’s a quick fix that will change how every preset you own performs. Before you apply anything, reset your file to default (hit the Reset button in the Develop module, or press Ctrl+Shift+R). Then bring your Exposure to roughly 0.00, pull your Highlights down to around -20, and push Shadows up to +15. Don’t touch the Tone Curve yet. Now apply the preset.

That 30-second adjustment creates a consistent starting surface. The preset was designed for something close to that. You’re meeting it halfway. Skin tones stay accurate, shadows hold detail, and the color grade the creator intended actually reads the way it was meant to.

How to Audit a Preset You Didn’t Build

When you download a preset from somewhere else, open the Tone Curve panel and the Color Grading panel immediately after applying it. These two areas tell you almost everything about a preset’s intent and its risk factors.

A Tone Curve with a steep S-curve and lifted blacks means the preset was built for flat, log-style raw files. Use it on a standard JPEG-style raw and your contrast will be overwhelming. A Color Grading panel with heavy orange pushed into the midtones and teal in the shadows is the “cinematic film look” preset you’ve seen a thousand times. It works on outdoor golden-hour portraits. It will wreck indoor tungsten-lit shots because you’re adding orange on top of orange.

None of this means the preset is bad. It means every preset is a starting point, not a destination. Dial the overall effect back using the Amount slider that appears when you right-click a preset in the panel, or manually reduce the Saturation in Color Grading by 10-15 points until the grade sits underneath the photo rather than on top of it.

Building Your Own Takes Less Time Than You Think

I name all my presets after songs because it helps me remember what they’re for. “Gold Dust Woman” is warm, slightly overexposed, low contrast. “The Chain” is cooler, punchy, high clarity. Weird system, but when I’m moving fast through a 400-shot wedding gallery, I can picture the sound of the song and land on the right preset without reading every label.

If you’ve never built a preset from scratch, start with one specific use case. Not “a preset for all my photos.” Pick one: sunrise portraits, cloudy street photography, indoor available light. Shoot ten frames in that condition, edit one until it looks exactly right, then save it as a preset using Develop, New Preset, and check only the boxes that you actually adjusted. Don’t save everything. Saving your Lens Corrections into a portrait preset means every time you apply it on a different lens, the corrections will override. Save Color, Tone Curve, and Detail. Leave geometry and lens corrections unchecked.

Your first preset will take maybe 45 minutes to build properly. Your second will take 20. By your fifth, you’ll have a small library that actually matches how you shoot, not how someone else shoots.

When the Preset Isn’t the Problem

I’ve spent time with photographers who swear presets don’t work for them, and nine times out of ten the real issue is their export settings or their monitor calibration, not the preset itself. A preset can look perfect in Lightroom and land completely flat after export because the export color space is wrong. Make sure you’re exporting in sRGB for anything going online, and if you’re on a wide-gamut monitor without calibration, what looks muted to you might look perfectly saturated to 90% of the people viewing your work.

Presets are one of the most powerful tools in Lightroom when you understand what they’re actually changing. Think of them as a conversation with the raw file, not a command.