A few years back, I released a preset pack on a Tuesday night mostly because I couldn’t sleep. I’d spent the better part of a weekend building it, named every preset after a Wilco song, and figured maybe a hundred people would download it. By Friday it had 50,000 downloads. By the following Monday, my inbox was a disaster of people saying the presets “didn’t work” on their photos.

That week taught me more about Lightroom presets than the previous three years of using them. The problem wasn’t the presets. The problem was that people were treating them like Instagram filters, one tap and done, instead of what they actually are: a starting point built around specific assumptions about light, color temperature, and exposure.

What a Preset Is Actually Doing to Your File

When you apply a Lightroom preset, you’re not applying a visual effect on top of your image. You’re pushing specific slider values into your develop module settings. That’s it. A preset that looks incredible on a golden-hour portrait shot at ISO 400 with a warm white balance can look completely broken on a flat, overcast street photo shot at ISO 3200. The preset didn’t fail. It just wasn’t designed for that image.

Under the hood, most presets are touching a combination of the following: white balance (temperature and tint), the tone curve, HSL sliders (hue, saturation, and luminance per color channel), color grading in the shadows and highlights, and sometimes lens corrections or grain. A good preset is usually doing something intentional with three or four of those. A bad preset is cranking everything to 11 and hoping you don’t notice.

The Baseline Problem Nobody Talks About

Here’s what most preset tutorials skip: your exposure has to be close before the preset can do its job. I’m talking within about half a stop. If your image is underexposed by 1.5 stops, a preset built around a correctly exposed file is going to push your shadows into gray mud and your highlights nowhere near where they need to be.

Before applying any preset, I get my exposure to baseline first. That means exposure slider, black clipping check (hold Alt or Option while dragging the Blacks slider until clipping just disappears), and a quick white balance adjustment. Takes maybe 45 seconds. After that, the preset is working with a photo that’s in the ballpark, and the results are dramatically more predictable.

The other thing nobody mentions is that camera profiles matter. If you’re shooting Fuji and your preset was built on Sony files with a Camera Standard profile, the starting color science is different. Check the Camera Calibration panel (or the Profile section in newer Lightroom versions) and match the profile to what the preset creator used. They should tell you. If they don’t, that’s a red flag.

How to Build a Preset That Actually Travels Across Photos

The presets I’ve built that hold up across different images share one thing: they do less than you’d think. My most-used preset, the one I named “Jesus Etc.” after the Wilco track, only touches the tone curve, adds a slight teal shift to the shadows via color grading, pulls the orange luminance down about 15 points, and adds 12 units of grain at a size of 25 and roughness of 50. That’s it. Five decisions. It works on 80% of my natural light portraits because it’s not fighting the image, it’s nudging it.

If you’re building your own presets, save everything in XMP format, not as a catalog preset, so they’re portable. Keep your preset file sizes under 5KB. If a preset file is larger than that, someone probably embedded a LUT or something unusual, which works fine but removes the ability to tweak individual sliders intuitively.

When to Use Presets in Batch and When Not To

Batch applying presets is one of Lightroom’s best features and one of its most abused ones. If you shot a full event, a wedding ceremony, a concert, or any situation with consistent lighting throughout a scene, batch applying makes real sense. Select all the images from that lighting setup in the grid view, apply the preset to the first image, sync your settings to the rest, and then do a quick pass through for individual exposure corrections. On a 400-photo wedding gallery, this workflow cuts my culling-to-delivery time from around 6 hours to closer to 90 minutes.

Where batch applying breaks down is when your lighting changed every few frames. Indoors to outdoors, flash to ambient, midday to golden hour. In those cases, group your images by lighting condition first, establish one edit per group, then sync within each group. Ten minutes of sorting saves hours of individual corrections.

The One Thing That Makes a Preset Actually Yours

Presets someone else made are a shortcut, not a style. I’ve bought preset packs from photographers I admire and used exactly zero of the presets as-is. What I do use them for is studying the decisions. I’ll apply a preset, open the HSL panel, and just read what they did. Why did they pull the aqua hue toward blue? What made them push magenta luminance down by 30? That’s the education.

If you want a consistent editing style, which is the whole point of building a preset library, your presets need to reflect how you see, not how someone else does. Start with someone else’s work, understand why each slider moved where it did, rebuild it with your own instincts, and name it after something that means something to you. Mine are named after songs because that’s what’s playing when I make them.

The single most important thing I can tell you about presets is this: a preset is a hypothesis about an image, and your job after applying it is to test whether that hypothesis is correct. The photographers who get the most out of presets are the ones who understand them well enough to know exactly which sliders to correct when the hypothesis is wrong.