Culling and editing: why your picks set the edit clock

Most photographers try to fix a slow edit by editing faster. The edit is usually not the problem. How many frames reach Lightroom, the shape they arrive in, and the decisions you left open are what set the clock. This is how the two halves of post-production connect, and which selection choices actually change your Tuesday night.

Editing time is set before you open Lightroom

A UK survey of more than 300 wedding photographers, reported by PetaPixel, found editing took 55 percent of working time and culling took 11 percent. Shooting took 4 percent. Those figures come from a pre-AI era, so treat them as shape rather than gospel. The shape is what matters: editing is the largest block in the week by a wide margin, and it is not close.

So that is where everyone attacks. Faster presets, a newer machine, better shortcuts, an outsourced editor. All of it helps at the margins. None of it touches the thing that sets the size of the block in the first place, which is how many frames arrive at the edit and what condition they arrive in.

Here is the claim, stated plainly. Editing time is mostly a downstream measurement of selection quality. Two photographers with the same camera, the same presets and the same skill can finish the same wedding hours apart, and most of that gap opens before either of them touches a develop slider. If the edit is the expensive room, the cull is where you decide how much furniture goes into it.

That makes selection the highest-leverage hour in your week, and it explains why it feels so disproportionately draining for something that produces no visible output. We looked at the whole week's distribution in where photographers' time actually goes.

Four ways a pick becomes an editing hour

"Cull harder" is not advice, it is a mood. The useful version is knowing exactly which selection decisions convert into editing time, because they are not all the same size and only one of them is about the raw number of photos.

Notice that only the first row is about volume. The other four are about shape. A selection of 700 frames handed over in a workable order beats a selection of 600 handed over scrambled, which is why photographers who obsess over the delivery count and ignore everything else rarely feel faster.

The multiplication nobody actually runs

Do this once and the whole argument stops being theoretical. Open a shoot you have already edited, pick twenty representative frames, and time yourself honestly on all twenty. Include the small stuff: the crop, the straighten, the spot you noticed, the second look. Divide by twenty. That number is your true per-frame edit cost and it is almost always higher than the number in your head.

Now multiply. Say your average lands at 45 seconds. A 700-image delivery is about eight and three quarter hours of editing. Push the same wedding to 900 images and you have added two and a half hours, for photos that by your own judgment were the weaker ones. That is a full evening, spent on your own second-best work, decided in the four seconds you spent flagging a frame you were unsure about.

A wedding day typically produces 2,000 to 4,000 RAW frames and 400 to 800 delivered images. The gap between the bottom and the top of that delivery range is not a stylistic preference, it is a working week, several times a season. If you want help setting the number itself rather than defending it after the fact, we went through it in how many wedding photos to deliver.

Why the order you pick in changes the edit

This is the part almost nobody is told. Editing is fast when frames that need the same correction sit next to each other, because then one correction serves twenty photos. Editing is slow when it is one photo, one decision, one photo, one decision. The difference between those two experiences is decided during selection, not during editing.

Selection sets the order the edit arrives in. If you work scene by scene, finishing the getting-ready room before you touch the ceremony, the picks come out of the cull already clustered by light. Sync a correction across the block, move on. If instead you sweep the whole day looking for your favorites, you end up with a beautiful selection in which no two consecutive frames share a white balance, and you pay a setup cost on nearly every image.

Two habits protect this. First, finish a scene before you move. Second, when a moment has six versions, judge those six against each other and pick from within the group rather than judging each one against the whole wedding. That is easier on your eye anyway, since comparison is a far more reliable human judgment than absolute rating, and it is the subject of choosing the best frame from a burst.

The payoff shows up immediately in batch editing. A grouped selection is batchable. A scattered one is not, no matter how good the individual photos are.

The maybe pile is where the money goes

Every slow post-production week I have seen has the same fingerprint: a large undecided middle. Not photos you picked, not photos you set aside, photos you postponed. A maybe feels like caution. It is actually a decision you have moved into the most expensive room in the house.

The reason it costs so much is sunk cost. Once you have spent two minutes editing a frame, you are no longer judging whether it belongs in the gallery. You are judging whether to waste the two minutes. Almost everyone keeps it. So the maybe pile does not shrink during the edit, it converts, at full price, into delivered photos you did not really want to deliver.

This also protects your judgment. Deciding is what tires you out, and quality of decision degrades as the count of decisions rises, which is why the last hour of a cull looks nothing like the first. Front-loading and finishing the decisions in one deliberate pass is cheaper than dribbling them across two evenings. There is more on that pattern in decision fatigue for photographers.

What the edit actually needs from the cull

If selection sets the edit clock, then the cull owes the edit a specific package, and it is worth naming what is in it. Three things, in order of how badly it hurts when they are missing.

A verdict you trust. One flag or label that means picked, applied consistently, with no second meaning hiding inside it. If you have to re-examine the picks before you can start, the cull did not finish, it just stopped.

The groupings, intact. The edit needs to know which frames came from the same moment and the same light, because that is what makes a batch a batch. A flat list of filenames throws that away and the editor rebuilds it by eye.

File identity that survives the trip. Whatever names or folders you settled on happen once, at ingest, and never again. Renaming after selection is how picks quietly lose their link to the files they pointed at.

Notice that none of this is about anything being taken away. Nothing needs to be thrown out for the handover to be clean, and the frames you did not pick stay exactly where they are, which is worth saying because plenty of workflows still assume tidying means losing something. The mechanics of that handoff, and the six other joints between the card and the archive, are laid out in the post-production pipeline, joint by joint. Both articles sit under our broader photography workflow guide.

How to test this on your next two shoots

Do not take the argument on trust, it is cheap to check. Run two shoots of similar size back to back and change exactly one thing.

On the first, cull the way you always do and write down three numbers: how long the cull took, how many frames you picked, and how long the edit took. On the second, work scene by scene, resolve every maybe before editing begins, and hold yourself to the lower end of your normal delivery count. Write down the same three numbers.

Almost everyone finds the second cull took slightly longer and the second edit took considerably less, and the total came down. That is the whole thesis in one experiment, measured on your own work with your own hands, which is far more persuasive than any survey. If the totals come out level, then your bottleneck genuinely is elsewhere and you have saved yourself from optimizing the wrong stage, which is also a win.

Software changes the arithmetic here rather than the logic. A tool that proposes a shortlist moves you from making thousands of decisions to reviewing a few hundred, and the shape rules still apply: a reviewed shortlist that respects scenes edits faster than one that does not. Kepla is being built around exactly that idea, with the first pass happening on an iPhone or iPad on the drive home and the same shoot picking up on the Mac later. It picks, and it never takes a file anywhere. The apps are still in development, but the booking page is live and free today while we build.

FAQ