I named my first serious preset pack after Fleetwood Mac songs. “Gold Dust Woman” was a warm, hazy film look with crushed shadows. “The Chain” was high contrast, almost brutal in the highlights. The naming was partly for fun, but it also forced me to think about each preset as having a mood rather than just a collection of slider positions. That reframe changed how I built presets, how I applied them, and honestly how I thought about editing entirely.

Most people use presets like Instagram filters. One click, done, move on. And that’s fine if you’re posting casual shots, but if you’re trying to build a consistent body of work or cut your editing time in half without sacrificing quality, you need to understand what a preset is actually doing to your file.

What’s Really Happening When You Apply a Preset

A Lightroom preset is a saved collection of develop module instructions. That’s it. It’s a .xmp file (or .lrtemplate in older versions) that stores slider values, tone curve points, HSL adjustments, and camera calibration settings. When you apply it, Lightroom reads those instructions and overwrites your current develop settings with the preset’s values.

The critical word there is overwrites. If you shoot a RAW file at 6400 ISO in low light and apply a preset designed for a clean, sunny exposure, the preset doesn’t know that. It will apply whatever white balance, exposure offset, and shadow recovery it was built with, regardless of what your image actually needs. This is why preset results look inconsistent across a shoot. It’s not a bad preset. It’s a mismatch between the preset’s assumptions and your file’s baseline.

The fix is simpler than most people think: normalize your exposure before you apply anything.

The Two-Step Baseline Method That Changes Everything

Before I touch a single preset, I do two things. First, I set white balance to something neutral, either “As Shot” if I trust my in-camera setting, or a manual Kelvin value. For most of my Nashville outdoor work, I land around 5500K to 6000K in golden hour. Second, I pull my exposure slider so the histogram is roughly centered, with nothing clipping hard on either end. We’re talking maybe 30 seconds per image.

Now when I drop a preset on top of that normalized file, it’s working with a consistent starting point. The tonal relationships the preset was designed for actually exist in my image. I’ve easily cut my per-image correction time from around 4-5 minutes down to 90 seconds on a typical portrait session using this method alone.

Some photographers skip this because it adds a step before the “fun part.” That’s a false economy. You’ll spend three times as long fighting the preset afterward.

When Presets Should Only Go Halfway

Here’s something most preset tutorials don’t tell you: the Amount slider at the top of the Presets panel, the one that lets you blend between 0% and 100%, is genuinely useful and chronically underused. I almost never apply a preset at full strength on the first pass.

My default is 70-75%. This gives me the tonal direction and mood of the preset without locking in the color cast or the shadow depth until I’ve seen how it reads on that specific image. Then I fine-tune from there. It’s like turning down a song on vinyl slightly before you decide if it’s the right track for the moment. You’re auditioning, not committing.

This also applies to skin tones. Most warm, film-emulation presets push orange into the skin quite aggressively. At 100%, that looks great on some complexions and terrible on others. At 65-70%, you get the warmth without the muddy skin. Small numbers, real difference.

The Preset Pack I Gave Away for Free (and What I Learned)

A few years ago I spent an entire weekend building a preset pack I called “Side A” because each preset was named after the first track on a classic album. When I finished, I decided to just give it away through my site rather than charge the standard $20-30 that comparable packs were selling for at the time. I figured maybe a few thousand people would download it.

It got 50,000 downloads.

What I learned from the feedback wasn’t what I expected. The most common complaint wasn’t about the presets themselves. It was that people didn’t know how to make them look good on their own photos. They were applying them to unprocessed RAW files with wildly different exposures and color temps and then wondering why “Side A” looked nothing like my demo images. That feedback is the reason I’ve been writing about baseline normalization and workflow structure ever since.

The presets were fine. The missing context was everything.

Building Presets That Actually Travel Across Your Work

If you’re creating your own presets rather than buying them, there are three things worth locking in and one thing worth leaving out. Lock in your tone curve (this carries your contrast signature more than any other single setting), your HSL panel adjustments for your signature colors, and your camera calibration settings. These give a preset its personality.

Leave exposure compensation out of saved presets unless you’re building something very specific. An exposure offset of even plus-0.3 stops will throw off the preset’s behavior across different scenes. Let exposure stay neutral and adjust it per image during the normalization step. Your presets will apply more cleanly, more consistently, and you’ll spend less time undoing the preset’s assumptions instead of working with them.

The single most important thing I can tell you about Lightroom presets is this: a preset is a starting point that assumes a certain kind of image, so give it the image it’s expecting, and it will almost always deliver what it promised.