Speed at volume does not come from working faster. It comes from removing decisions, and there are four places where they hide.
The short answer: speed at volume comes from removing decisions, not from working faster. Decide your rejection criteria before you open the folder, group frames by lighting condition rather than by sequence, edit one reference frame per group to completion, then sync. Handle retouching as a separate batch at the end.
Photographers trying to speed up post-production usually try to work faster. That has a hard ceiling and it makes the work worse.
The gains are in the decisions. Every frame where you pause to think costs several seconds, and several seconds across 1,400 frames is an hour. A high-volume workflow is one that has already made most of the decisions before you open the folder.
Where the decisions hide
1. Culling — decide the rules first
Most culling time is hesitation over near-duplicates. The fix is to decide your rejection criteria before you start, then apply them without arguing.
A workable set: reject anything out of focus on the subject, anything with a closed eye where you have an alternative, anything where someone is walking through the frame, and all but the best of any burst. Do that pass fast and without second-guessing.
Then a second pass on what survives, choosing rather than rejecting.
Two fast passes beat one slow one, because the first pass is mechanical and the second is creative, and mixing them is what makes both slow.
2. Grouping — process by lighting, not by sequence
Sort the set into lighting conditions before touching a slider. Frames within a group share a problem; frames across groups do not.
Correct the group, then adjust the outliers. This is the single largest time saving available and almost nobody does it, because folders are naturally in chronological order and chronological order is not useful.
3. Presets — as starting points, never as finishes
A preset gets you 80% of the way on frames it suits. It gets you 40% of the way on frames it does not, and undoing that costs more than starting clean.
Build presets per lighting condition rather than per look: one for window light, one for overcast, one for your flash setup. Then a look on top.
And build them from your own edited work rather than buying them, so they match what you actually deliver.
4. Retouching — separate it completely
The frames needing real pixel work should be identified during culling and set aside. Do not discover them one at a time while processing.
Process the whole set first, then handle the retouching frames as a batch. Context switching between "adjust the set" and "work on this frame" is expensive, and it is why a 90-frame delivery takes an evening rather than two hours.
The system, end to end
- Import and back up. Two copies before anything else. Every time.
- Fast reject pass. Mechanical, criteria decided in advance.
- Selection pass. Creative, on what survives.
- Group by lighting.
- Edit one reference frame per group to completion.
- Sync each group to its reference.
- Walk the set for outliers, in grid view.
- Set aside the frames needing retouching.
- Retouch that set — yourself or outsourced.
- Final grid-view consistency check.
- Export once, from one place.
The order is the point. Every step is cheaper because the previous one narrowed what it has to handle.
Hardware, honestly
Fast local storage matters more than almost anything else. Previews, catalogue operations and exports are all disk-bound, and an SSD for the working set is the single cheapest speed improvement available.
RAM matters for pixel editing. A better processor matters for export and denoise. A calibrated monitor does not make you faster but it stops you doing work twice.
Do not buy a new machine to fix a workflow problem. Fix the workflow first and then find out whether the machine was the issue.
Where to stop optimising
There is a floor. Once you have removed the decisions, a frame takes as long as it takes, and past that point the only levers are: shoot fewer frames, deliver fewer frames, charge more, or hand some of it to someone else.
That is not a failure of your system. It is the system working, and telling you the honest answer.
The outsourcing threshold
For most photographers it arrives when the retouching block — step 9 — becomes larger than everything else combined. That happens naturally as your work gets better, because better work means clients wanting more from individual frames.
At that point per-image retouching is a capacity decision rather than a skill one. You keep steps 1 through 8, which are the ones that carry your judgement, and hand over the one that is purely hours.
What to fix first
Run the system for one job and note where it still hurts.
If the reject pass is slow, your criteria are not decided in advance and you are re-litigating each frame. Write them down.
If the processing pass is slow, you are working in file order rather than in lighting groups, and you are correcting the same thing many times.
If the retouching block is the largest number, the workflow is working and the constraint has moved to capacity. That is the honest end of what a system can do for you, and it is the point where the remaining levers are commercial rather than technical: shoot fewer frames, deliver fewer, charge more, or hand the pixel work over.
Knowing which of those you are choosing is more valuable than another round of optimisation.
Common questions
Where does the time actually go? Into decisions, not into operations. Every frame where you pause to think costs several seconds, and several seconds across 1,400 frames is an hour. A fast workflow is one that has already made most of the decisions before the folder is opened.
Are presets worth building? Yes, if you build them per lighting condition rather than per look — one for window light, one for overcast, one for your flash setup — and build them from your own delivered work rather than buying them.
Should I edit in the order the frames were shot? No. Chronological order is natural and unhelpful. Group by lighting condition so that frames sharing a problem are corrected together.
Will a faster computer fix this? Fast local storage genuinely helps, because previews, catalogue operations and exports are disk-bound. Beyond that, fix the workflow first — a new machine rarely fixes a process problem, and you will find out which you had.
Is there a floor? Yes. Once the decisions are removed, a frame takes as long as it takes. Past that the only levers are shooting fewer frames, delivering fewer, charging more, or handing some of it over. That is the system working, not failing.
Related reading: Photo Culling vs Photo Editing and How to Make an Entire Photo Gallery Look Consistent.
BeEdits Editorial Team
Post-production studio
A photography post-production company: high-end retouching, creative editing and scalable production support for photographers, studios and brands.