Building Editing Presets That Still Feel Custom Per Trip

Presets get a bad reputation among photographers who worry they flatten everything into the same look. Used the wrong way, they do exactly that. Used the way I actually rely on them, they save real editing time without making every trip look interchangeable.

Editing is roughly half of the total time I spend on any project, and presets are one of the only tools that meaningfully cuts that time down without cutting corners on quality. If you're building your own editing workflow around a full production process, the Adventure Travel Photographer's Playbook covers how I structure post-production alongside everything that happens before a shutter ever clicks.

The Real Problem With Most Preset Workflows

The complaint that presets make everything look the same is usually true, but it's not really a complaint about presets themselves, it's a complaint about how most people use them. Applying one preset uniformly across every image from every location, regardless of the light, the environment, or the story of that specific trip, is what produces the flat, interchangeable look people rightly criticize.

A preset applied without any per-image adjustment treats editing as a single mechanical step instead of the second half of a creative process. That's the actual failure mode, not the existence of a starting point. The tool isn't the problem. Using it as a finish line instead of a starting line is.

Once I started treating presets purely as a first pass rather than a final result, the entire criticism stopped applying to my own workflow, because the presets were never meant to be the last decision made on an image.

Why I Build a Base Preset Instead of Buying One

I don't use a single purchased, generic preset pack across everything. I've built my own base preset over years, refined specifically around how I want color, contrast, and skin tones to render across a wide range of light conditions, since that base is meant to be a starting point for every kind of trip I shoot, not a finished look tuned for one specific environment.

A generic preset built by someone else reflects their eye, not mine, and applying it universally means every project starts from someone else's baseline instead of my own. Building my own base took real time upfront, but it means the starting point for every edit already reflects the visual identity I want the finished work to carry, before any trip-specific adjustment happens on top of it.

This base preset isn't static either. I revisit and refine it periodically as my own eye and style shift, rather than treating it as something built once and left untouched indefinitely.

Layering Trip-Specific Adjustments on Top of the Base

The base preset gets applied first, as a starting point, and then every trip gets its own layer of adjustment on top of it, built around the specific light, color palette, and mood of that location. A desert trip and a tropical trip both start from the same base, but they end up looking meaningfully different because of what happens in that second layer.

This second layer is where the actual creative decisions live. Does this trip's story call for warmer tones that emphasize the heat and dust of a desert shoot, or cooler, saturated greens that match the humidity of a tropical one. That decision doesn't come from the base preset, it comes from thinking specifically about what this particular trip is trying to communicate visually.

Building this second layer as its own preset, saved specifically for that trip or that type of environment, means I'm not reinventing trip-specific adjustments from scratch every time, while still keeping the door open to make each trip feel distinct.

Why I Still Adjust Individual Images by Hand

Even with a base preset and a trip-specific layer applied, individual images still get hand adjustment before final delivery. Presets, no matter how well built, can't account for every specific lighting situation within a single shoot, a backlit moment that needs different treatment than the rest of the gallery, a shadow detail that needs pulling in a way the batch settings didn't anticipate.

This final hand-adjustment pass is usually quick, since the preset layers have already done most of the heavy lifting, but it's the step that keeps individual standout images from looking like they were run through an assembly line. It's also where I catch outliers, images that technically match the preset settings but don't actually look right, and correct them individually rather than letting a systemic setting override what the specific image actually needs.

Skipping this step is exactly how a preset-based workflow starts to feel mechanical. Keeping it in is what keeps the efficiency of presets without losing the judgment that makes an edit actually good.

How Presets Actually Speed Up Delivery Without Cutting Quality

My rule of thumb has long been that a day of shooting produces roughly two days of editing. Presets don't eliminate that ratio, but they meaningfully shrink the portion of it spent on repetitive baseline work, freeing up more of that time for the judgment calls that actually improve an image rather than just get it to a consistent starting point.

Without a preset system, every image starts from a completely blank slate, which means re-deciding basic color and contrast choices hundreds of times across a single gallery. With a well-built system, those baseline decisions are made once, upfront, and applied consistently, leaving the remaining time for the parts of editing that actually require a trained eye rather than repeated technical adjustment.

This is also where recent AI-assisted editing tools have changed my process meaningfully, handling an initial cull and base pass that lets me start my own refinement further along than I used to, which stacks on top of the time savings presets already provide.

Keeping a Trip From Looking Like a Copy of the Last One

The real risk with a mature preset system isn't that any single trip looks bad, it's that trips start to blur together over time, since the underlying base preset is doing so much of the visual heavy lifting across every project. I actively watch for this by periodically reviewing galleries from different trips side by side, checking whether they're actually distinct or quietly converging toward sameness.

When I notice convergence, that's usually a sign I leaned too heavily on the base preset and skipped the trip-specific layer that should have made this particular project look and feel different from the last one. Catching that pattern requires deliberately stepping back and comparing work across projects, not just judging each gallery in isolation.

This periodic check is part of why I don't treat the base preset as something to blindly trust. It's a tool that requires ongoing supervision, not a system that runs itself once it's built.

What I Do Differently for Client Work vs. Personal Projects

Client work and personal projects get slightly different treatment within the same overall system. Client deliverables lean more heavily on the base preset and a consistent trip-specific layer, since brands often want a recognizable, dependable visual consistency across a campaign rather than dramatic experimentation on every individual frame.

Personal projects get more room to deviate from the base entirely, since there's no client expectation of consistency to protect and more freedom to push an edit somewhere the base preset was never designed to go. That flexibility is part of why I still shoot and edit personal work alongside client projects, it keeps the editing muscle from atrophying into pure repetition of the same system every single time.

Keeping these two modes distinct also protects the base preset itself from drifting too far in either direction, since client consistency and personal experimentation pull in different directions and both deserve their own space.

Building a System That Can Evolve Without Starting Over

My visual style today isn't identical to what it was several years ago, and the preset system has had to evolve alongside it rather than staying frozen at whatever version I built first. I periodically revisit the base preset itself, adjusting it to reflect where my eye has actually moved, rather than continuing to edit through an outdated lens just because the system was already built and working.

This evolution has to be deliberate rather than accidental. An unreviewed preset system tends to calcify, since it's easy to keep using what already works without questioning whether it's still actually representing the best version of the current style. I schedule a periodic review specifically to prevent that kind of quiet stagnation.

The goal was never a static, finished system. It's a living one that captures real efficiency gains while staying flexible enough to keep growing alongside the actual work.

What I'd Tell a Photographer Worried Presets Will Flatten Their Work

If the concern is that presets make everything look the same, the fix isn't avoiding presets entirely, it's building a system with enough layers, a base, a trip-specific pass, and individual hand adjustment, that the preset is doing foundational work rather than making every final creative decision. Used that way, presets are a genuine efficiency tool rather than a threat to a distinct visual style.

The photographers whose work actually does look interchangeable usually skipped the layering entirely, applying one setting uniformly and calling it done. That's a workflow problem, not evidence that presets themselves are incompatible with a distinct, evolving style.

How I Organize Preset Files So They Stay Useful, Not Cluttered

A preset system only stays useful if it doesn't quietly turn into an unmanageable pile of one-off variations saved during a rushed project and never cleaned up afterward. I keep a strict, small set of named presets, the base, a handful of trip-type variations, snow, desert, tropical, low light, rather than letting every individual trip spawn its own permanent, rarely reused preset that clutters the library over time.

When a trip-specific adjustment turns out to be genuinely reusable across similar future locations, it gets folded into one of those named categories rather than kept as a one-off. When it's truly unique to a single project, I let it live only within that project's edit rather than saving it permanently. This discipline keeps the preset library small enough that I can actually remember what each one does, instead of scrolling through dozens of vaguely named options trying to guess which one fits a new trip.

Teaching This System to an Editor I Work With

Since shifting to an AI-assisted first pass on culling and base editing, I've had to make my own preset logic explicit enough to actually hand off, rather than relying on instinct that lives only in my own head. Writing down which base preset applies in which lighting conditions, and how the trip-specific layer should be chosen, has been necessary to get a genuinely useful first pass back rather than one I have to substantially rebuild.

This process of externalizing the logic turned out to be useful beyond just enabling that handoff. It forced me to notice inconsistencies in my own past decision-making, cases where I'd applied a trip-specific layer somewhat arbitrarily rather than for a clear reason. Cleaning that up made the whole system more consistent, which benefited my own hands-on editing too, not just the parts I've started delegating.

Why I Still Shoot Raw and Build Presets Around Raw Flexibility

My whole preset system depends on shooting raw rather than compressed formats, since a preset's real value comes from how much room it has to work with in adjusting highlights, shadows, and color before an image starts to break down. A preset applied to a file with less dynamic range to draw on simply can't do as much, regardless of how well the preset itself was built.

This is worth stating plainly because it's easy to focus entirely on the editing side of a preset system and forget that the capture decisions upstream determine how much the editing system can actually accomplish. A well-built preset applied to a poorly exposed or compressed file is still limited by that file's real constraints. Getting the capture right in the field is still doing at least half the work that a strong final edit depends on.

What I Watch For When a Preset Starts Feeling Like a Crutch

There's a specific warning sign I watch for in my own editing habits: reaching for the base preset reflexively, without actually looking at the image first, purely out of routine rather than a genuine judgment that it's the right starting point for that specific frame. When I notice that happening, it's usually a signal I'm moving too fast through a batch and skipping the actual seeing that good editing depends on.

The fix isn't abandoning the preset system, it's slowing down enough to genuinely evaluate each image before applying anything, even if the eventual choice is still the same base preset I'd have reached for automatically. That small pause, actually looking before applying, keeps the system serving my judgment instead of quietly replacing it, which is the exact failure mode that gives presets their reputation for flattening work in the first place.

I've found the easiest time to catch this drift is right at the start of a new editing session, before fatigue sets in and the temptation to move on autopilot grows stronger. A quick, deliberate first pass through a new gallery, genuinely looking rather than clicking through on habit, sets the tone for the rest of the session and makes it much easier to notice later, deeper into the batch, if the judgment has started slipping into pure routine.

This kind of self-monitoring is easy to let slide when deadlines are tight and the volume of images from a trip is genuinely large, which is exactly when the temptation to lean fully on automation is strongest. I've had to build the habit of checking in with myself specifically during those high-pressure stretches, since that's when a preset system quietly sliding from a tool into a crutch is most likely to happen without me noticing until well after the edit is finished and delivered.

Reflection Questions

  1. Does your current editing workflow have a base layer, a trip-specific layer, and individual hand adjustment, or just one uniform pass?
  2. When was the last time you compared galleries from different trips side by side to check for unintentional sameness?
  3. Have you revisited your base editing style recently, or is it frozen from whenever you first built it?
  4. How do you currently balance consistency for client work against experimentation on personal projects?

If you're refining your own post-production workflow as part of a growing business, the Adventure Photographer's Playbook covers how I structure editing systems that scale without losing what makes each project distinct.

Dalton Johnson is a professional adventure and editorial photographer with over a decade of experience creating images on all seven continents. His client work includes Patagonia, GoPro, Arc'teryx, Four Seasons, Nike, Rivian, Big Agnes, Ford Bronco, and 160+ other brands. He runs Dalton Johnson Media as a full-service studio, from pre-production through post and distribution.

Previous
Previous

Organizing a Shoot's Files So Nothing Gets Lost Before Delivery

Next
Next

Naming Your Business: Why It Matters More Than You Think