A few years ago I released a preset pack on a Tuesday afternoon, mostly as an experiment. By Friday it had 50,000 downloads. I hadn’t charged a cent for it. The emails I got back were mostly some version of the same sentence: “I applied the preset and it looks nothing like your example photo.” That told me everything I needed to know about how people misunderstand what presets actually are.

They’re not filters. They’re not Instagram overlays. And they are absolutely not a substitute for understanding light.

What a Preset Is Actually Doing to Your File

When you apply a Lightroom preset, you’re applying a saved collection of slider values across panels like Basic, HSL, Tone Curve, Color Grading, and Detail. That’s it. The file sitting on your hard drive doesn’t change at all. Lightroom writes instructions into an XMP sidecar file (or into its catalog), and those instructions tell the software how to render the raw data when it displays or exports your image.

This is why the same preset can look completely different on two photos. A preset that sets Exposure to +0.85 and Shadows to +40 is going to behave wildly differently on a shot taken at f/1.8 in golden hour versus one taken at f/8 under a blown-out midday sky. The preset isn’t broken. The light was different.

Raw files are not photographs yet. They’re data waiting to be interpreted. Presets are interpretation instructions, and context matters enormously.

The Anatomy of a Preset That Actually Works

The presets I build are organized around what I call a hierarchy of influence: global tone first, then color relationships, then stylistic finish. If you flip that order, you’re decorating a house before you’ve laid the foundation.

Here’s what that looks like in practice. The Basic panel handles your global tone: Exposure, Contrast, Highlights, Shadows, Whites, Blacks. Get these in a reasonable range before anything else touches the file. I typically aim for Whites around +15 to +25 and Blacks pulled to somewhere between -10 and -20 to give the histogram a little room to breathe on both ends. Contrast I almost always leave at 0 in the preset and handle manually with the Tone Curve, because the Contrast slider is blunt and the Tone Curve is a scalpel.

From there, color temperature and tint get set to zero in most of my presets, deliberately. I want the color science to respond to each image’s actual white balance, not a fixed value I chose on a different day with a different camera. HSL adjustments are the exception: I’ll often push Luminance on yellows down by 15 to 20 points in portrait presets to keep skin tones from going chalky.

Color Grading is where the personality lives. Midtone hue and saturation do the heavy lifting. A slight push toward teal in the shadows (hue around 195, saturation at 8 to 12) paired with warm highlights (hue near 40, saturation at 10) is the engine behind most of the “filmic” looks you see all over editorial photography right now.

Why Most Preset Packs Fail the People Who Buy Them

The problem with most commercial preset packs isn’t quality. It’s context mismatch. A preset designed on Sony sensor files at 400 ISO is going to behave differently on Canon files at 3200 ISO, and most preset sellers don’t tell you that. The color science between camera manufacturers is genuinely different. Sony tends to render skin with a slight magenta push. Canon leans warmer. Fuji’s Film Simulations bake color into the raw file itself, which means color-grading presets applied on top can create strange, unpredictable interactions.

Before you buy any preset pack, find out what camera and what lighting condition the creator shot their examples under. If that information isn’t published anywhere, that tells you something.

The presets I gave away for free, the ones that hit 50,000 downloads, were built on a mix of Canon R5 and Nikon Z6 files in mixed natural light, and I documented that in the download readme. The people who had trouble were almost always shooting Fuji or working with heavily artificial light. Not a failure of the preset, just a mismatch in expectation.

A Workflow That Makes Presets Actually Useful

I apply presets as a starting point, never an endpoint. My actual workflow looks like this:

Apply the preset. Then immediately check three things: the histogram for clipping, the skin tones in the HSL panel, and the Color Grading wheels to see if the split-tone is working with or against the image’s natural color temperature. That whole check takes about 45 seconds.

From there I’ll make exposure corrections in the Basic panel before I touch anything stylistic. Usually that’s a Highlights pull somewhere between -20 and -50 and a slight Shadows lift. Then I look at the image again and ask whether the preset’s color signature is actually serving this specific photo or fighting it.

The preset I named after a Joni Mitchell record works on maybe 60% of the photos I try it on. The other 40% need a different starting point. I name my presets after songs because it reminds me they’re moods, not formulas.

How to Build Your Own Instead of Buying Someone Else’s

The fastest way to understand presets is to build one. Spend an hour with a single well-exposed raw file and work through each panel deliberately: tone, then color, then detail, then effects. When you land on something you like, save it as a preset and apply it to ten completely different images. Note where it works and where it falls apart. That failure data is more educational than any tutorial, including this one.

A preset that only works on 3 out of 10 images isn’t a failed preset. It’s a specialized one. Know what it’s for.

The photographers who use presets best are the ones who understand that what they’re really building is a library of moods they can deploy quickly, not a single magic setting that works on everything.