Why I Batch Edit in Passes Instead of Photo by Photo
Early in my career I edited the way a lot of photographers start out editing: open the first image, finish it completely, move to the next one, repeat until the whole set is done. It feels methodical, and for a small set it's manageable.
It falls apart fast once the volume of a real assignment kicks in, especially with the rule of thumb I've settled into, that one day of shooting produces roughly two days of editing. the Adventure Travel Photographer's Playbook covers how I structure the full editing workflow, from culling through final delivery.
Why Photo-by-Photo Editing Never Actually Worked for Me
Early in my career I edited the way a lot of photographers start out editing: open the first image, finish it completely, move to the next one, repeat until the whole set is done. It feels methodical and thorough, and for a small set of images it's manageable. It falls apart fast once the volume of a real assignment kicks in, especially with the rule of thumb I've settled into, that one day of shooting produces roughly two days of editing.
The core problem with photo-by-photo editing is that it forces a huge number of small creative decisions in isolation, without the context of the full set around them. I'd finish an early image, feel good about it, then get twenty photos deeper into the same set and realize the earlier edit didn't actually match the tone the rest of the set was establishing. That meant going back, which meant the process wasn't actually linear at all, just disguised as linear.
Once I switched to editing in passes instead, working across the whole set at each stage rather than finishing one image before starting the next, both my speed and my consistency improved in ways that photo-by-photo editing never delivered no matter how disciplined I tried to be about it.
What Batch Passes Actually Look Like in My Workflow
My process now runs in distinct stages across the entire set: a first pass for culling, a second pass for base exposure and color correction applied broadly, a third pass for more specific creative grading, and a final pass for the handful of hero images that get individual, detailed attention. Each pass has one job, and I don't let myself blend jobs together within a single pass.
This structure means I'm making the same type of decision repeatedly across many images before moving to a different type of decision, which keeps my eye calibrated to one specific judgment at a time rather than constantly switching between technical correction and creative grading and hero-image polish within the same five minutes.
The AI-assisted first pass I now use handles a meaningful chunk of the earlier, more mechanical stages of this process, which means my own batch passes increasingly start further along than they used to, closer to the creative grading and hero-image stages where my attention actually matters most.
Why Culling First, Separately, Changes Everything Downstream
Culling as its own dedicated pass, before any real editing starts, is probably the single biggest efficiency gain in this whole approach. Trying to cull and edit simultaneously means making a keep-or-reject decision on an image while also half-invested in the specific edit I've already started applying to it, which biases the decision and slows it down at the same time.
A clean cull pass, judged purely on composition, moment, and technical soundness without any editing applied yet, produces a tighter, more honest final selection than culling while editing does. It also means every minute spent editing afterward is spent on an image that's already earned its place in the set, rather than wasted polishing something that gets cut later anyway.
This separation sounds obvious written out, but it's genuinely easy to blur in practice, especially under deadline pressure when the instinct is to just start working on whatever image is open rather than stepping back to make the harder, less immediately productive-feeling selection decisions first.
Consistency Is Easier to See Across a Full Set
Editing in batch passes makes inconsistency visible in a way photo-by-photo editing never does. Applying the same base correction across twenty images in a row, side by side, makes an outlier obvious immediately. Editing those same twenty images one at a time, spread across an afternoon with breaks in between, makes that same outlier nearly invisible until much later, if it gets caught at all.
This matters enormously for client work, where a delivered set needs to read as one coherent body of work rather than twenty individually well-edited but visually disconnected images. Batch passes are, in a real sense, a built-in consistency check that photo-by-photo editing simply doesn't offer by design.
It's also just faster to spot and fix a systemic issue, a slightly off white balance across an entire location's worth of images, for instance, when you're looking at that whole batch together rather than discovering the same issue image by image, potentially long after the earlier corrections have already been finalized.
How This Changed My Actual Turnaround Time
The two-days-of-editing-per-day-of-shooting rule of thumb held roughly steady even after switching to batch passes, but what changed was how predictable and front-loaded that time became. Photo-by-photo editing produced unpredictable finish times, since some images took far longer than others and I never knew until I was deep into a set how long the whole thing would actually take.
Batch passes made the timeline far more predictable, since each pass has a roughly consistent per-image cost across a set of similar images, which means I can estimate a realistic delivery date with much more confidence than I ever could estimating photo-by-photo. Clients notice that reliability, even if they never see the actual workflow behind it.
It also means I can more accurately tell a client mid-project how much longer delivery will take, rather than giving a vague estimate I'm not confident in myself. That clarity has become part of how clients experience working with me, not just a private efficiency gain.
Where Individual Attention Still Matters Most
Batch passes aren't meant to flatten every image into identical treatment. Hero images, the ones actually driving a campaign or leading a story, still get individual, detailed attention beyond what the broader batch passes apply. The difference is that this individual attention now happens deliberately, as its own final stage, rather than being spread unevenly and inconsistently across the whole editing process from the start.
This distinction matters because treating every image with hero-level individual attention isn't actually more careful, it's just slower without a proportional gain in quality for images that were never going to carry that much weight in the final deliverable. Reserving that level of attention for the images that actually need it is a better use of the same total editing time.
Knowing which images deserve that extra attention is its own skill, built from understanding what a client actually needs from a set rather than treating every frame as equally important by default.
What I've Gotten Wrong Trying to Batch Too Aggressively
There's a failure mode on the other end of this too, batching so aggressively that genuinely different images get forced into the same treatment when they actually needed different handling. A set spanning wildly different lighting conditions, morning light and harsh midday sun in the same shoot, doesn't always respond well to one blanket correction applied across the whole batch.
I've learned to sub-batch by lighting condition or location within a larger set rather than treating an entire day's shoot as one uniform batch, which preserves most of the efficiency gain of batch editing while still respecting real differences in the source material that a single blanket pass would flatten inappropriately.
This took some trial and error to get right, and I still occasionally misjudge where the sub-batch lines should fall. But the fix, when I catch it, is usually quick: split the batch further and rerun that specific pass, rather than reverting to full photo-by-photo editing for the whole set.
How Batch Editing Interacts With the AI-Assisted First Pass
Bringing an AI-assisted editing platform into the workflow for a first pass has actually reinforced the batch approach rather than replacing it. The tool handles an initial cull and base correction across the full set in one motion, which is itself a batch process, and my own subsequent passes build on top of that same batch logic rather than reverting to a photo-by-photo review of its output.
This has shifted where my own batch attention goes. Instead of spending a batch pass on basic exposure and color correction, that stage is largely handled already, so my first real pass now often starts closer to creative grading, which means more of my actual editing time goes toward decisions that genuinely need my judgment.
I still review the tool's output in a batch-oriented way rather than image by image, scanning across the full set for anything that reads wrong before diving into individual corrections. That scan-first habit, itself a form of batch thinking, catches systemic issues faster than a photo-by-photo review would.
Batch Editing on the Road With Limited Time
Working out of a van with nightly review and import time built in, batch passes fit naturally into that rhythm: cull one night, base correction another, creative grading once I'm back with more reliable power and less trip fatigue. Trying to fully finish images one at a time during limited nightly windows on the road never worked nearly as well as making steady, batch-based progress across the whole set instead.
On more remote, scrappier shoots, relying on solar power in unreliable conditions, batch passes also make it easier to communicate honest expectations to clients about delayed backups or delivery, since I can point to which pass a set is currently in rather than giving a vague sense of overall progress that's hard to verify or explain.
This structure has made editing on the road feel less like catching up during scattered pockets of time and more like steady, trackable progress, even when the actual conditions I'm editing in are far from ideal.
Teaching This Approach to Anyone Helping With Editing
When I've had help on the editing side, whether a past freelance editor or now the earlier stages handled by an AI platform, explaining the batch-pass structure clearly has been essential to getting useful results. A collaborator who understands which pass they're working on, and what that pass is and isn't responsible for, produces far more consistent output than one just told to edit the set generally.
This clarity also makes it much easier to review someone else's work quickly, since I know exactly what a given pass was supposed to accomplish and can check specifically for that, rather than reviewing a finished, fully-edited image against a vague sense of whether it looks right.
It's the same team-huddle logic I apply to shoot days: define the specific goal clearly, make sure everyone understands it, then let people execute without unnecessary interference. Batch passes give editing collaboration the same kind of clear structure a shoot day already has.
Tracking Progress Across a Set Instead of Just Finishing Images
Batch passes changed how I track progress on a project too. Instead of measuring progress by how many finished images exist, which photo-by-photo editing naturally encourages, I measure it by which pass the whole set is currently in. A set that's fully through the cull and base correction pass but not yet graded is meaningfully further along than a scattered handful of fully finished individual images, even though the second scenario can feel more tangible in the moment.
This tracking method has made it much easier to give clients accurate status updates mid-project, since I can say clearly that a set is through two of four passes rather than trying to estimate a vague percentage of individually finished images. It also makes it easier for me to plan my own week, since I know roughly how long each pass takes across a set of a given size.
It's a small mental shift, but it's made the whole editing process feel less like an open-ended slog and more like a series of discrete, trackable stages, each with a clear start and finish, which has done as much for my own motivation through a long editing week as it's done for actual efficiency.
Why This Approach Scales Better as Volume Grows
Photo-by-photo editing might be manageable at a small scale, a handful of images from a quick session, but it scales terribly as volume grows, since the inconsistency and unpredictability problems compound with every additional image added to a set. Batch passes, by contrast, scale almost linearly, since each additional image just adds a predictable increment to each pass rather than introducing new inconsistency risk.
This has mattered more as my own business has grown and the average project size has grown with it. Early in my career, with smaller sets and less volume, the inefficiencies of photo-by-photo editing were annoying but survivable. At current volume, they simply wouldn't be, and I don't think I could sustain the current pace of work without having made this shift years ago.
For anyone whose volume is currently small enough that this problem doesn't feel urgent yet, I'd still recommend building the batch habit early, since it's a much easier shift to make before years of photo-by-photo muscle memory are already built in and harder to unlearn.
What I'd Tell Someone Still Editing One Photo at a Time
If you're still editing photo by photo, I'd say try running a real side-by-side test on your next project: edit half a set the old way and half in batch passes, then compare the total time spent and the consistency of the final result. That comparison convinced me more than any advice I'd read ever could have.
I'd also say start with just separating the cull from the edit, even if you're not ready to fully restructure your whole workflow into distinct passes yet. That single change alone captures a meaningful share of the benefit, and it's a much smaller habit shift than rebuilding your entire process at once.
Mostly, I'd say trust that batch thinking isn't a shortcut that sacrifices quality for speed. In my experience it's produced more consistent, more coherent final sets than photo-by-photo editing ever did, precisely because it forces decisions to be made with the full context of the set in view rather than one image at a time in isolation.
Reflection Questions
- Have you ever caught an inconsistency in a delivered set that a photo-by-photo edit let slip through unnoticed?
- What would change about your timeline predictability if you separated culling from editing entirely?
- Where in your current workflow are you giving every image the same level of individual attention, whether it needs it or not?
- Could you run a real side-by-side test comparing batch passes against your current photo-by-photo approach on your next project?
If you're rethinking your own editing workflow, the Adventure Photographer's Playbook covers how I structure batch passes, culling, and final delivery across a full shoot.
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.