
Culling is rarely slow because photographers are slow. It's slow because of a handful of habits: each one small, each one multiplying your time by a little, all of them stacking. Here are the nine I see most, grouped by where they bite, with the fix for each.
You get home, import the cards, and start sorting while the adrenaline is still up. The problem: you're not judging photos, you're reliving moments. Every frame carries the memory of taking it, so every photo looks worth keeping and every reject feels like betrayal. Back up the same day, always, but cull after a night's sleep. With a day of distance you see what's actually on the screen, and the cull runs faster and more ruthlessly.
Research on decision fatigue suggests that the quality of our choices degrades as we stack more of them, and a cull is thousands of choices in a row. Late-night culling is where the two failure modes live: keeping everything because deciding feels hard, or nuking frames you'd have loved at 10 AM. If you're too tired to shoot well, you're too tired to judge what you shot. Schedule the cull like a session, in daylight, with a hard stop.
Timing mistakes cost you hours per week; decision mistakes cost you seconds per frame, which is worse, because a wedding hands you thousands of frames. Shave two seconds off the average decision and you've bought back more time than any app can. These four are where those seconds hide.
Zooming to 100% to check eyelash sharpness on a frame you haven't even decided you like is backwards. Judge at fit-to-screen first: moment, expression, composition. Zoom only to break ties between frames that already earned it. If you check focus on everything, you've multiplied your per-frame time several-fold for information that mostly doesn't change the decision.
The five-star scale forces a five-way judgment on every single frame, is this a 3 or a 4?, when the only question that matters on a first pass is in or out. Binary flags are faster because comparative, yes/no calls are cognitively cheaper than absolute grades. Stars have a job, but it comes later; the full argument is in stars vs flags.
Re-reviewing your rejects "just to be sure" means culling the same shoot twice. Trust the pass you made; if a frame didn't earn a flag the first time, it almost never earns one the second. One pass, forward only, no scrolling back. (If you genuinely can't let go, do a single fast review of picks, never of rejects.)
Ten frames of the same hug, all kept, because deleting nine feels like losing something. That's loss aversion doing the deciding. The psychology is unpacked in why picking photos is so hard. The cost is triple: storage now, the same decision again at editing, and a weaker gallery if the dupes survive to delivery. Pick the best frame of the burst and let the rest go; the near-duplicate playbook has tiebreakers for when they truly look identical.
Blinks, test frames, misfires, and hopeless exposures might be a big slice of any card, and they need zero deliberation. Sweep them out in a fast first pass so your real attention lands only on photos actually worth keeping. Skipping this means paying full decision-price on frames a glance could have killed.
Culling a wedding chronologically frame-by-frame means constantly re-loading context: ceremony, portraits, reception, back again. Group by scene and decide within groups: "best three of these forty" is a dramatically easier question than "is this frame good, in the abstract?" It's the backbone of the two-hour wedding cull.
The meta-mistake that protects all the others. If you don't know your cull took three hours, you can't notice that flags cut it to two, or that an AI first pass cut it further. Time one cull, count the frames, and you have a baseline. The math is laid out in how long culling actually takes.
| Mistake | The fix |
|---|---|
| Culling on shoot day | Back up today, cull tomorrow |
| Culling at 1 AM | Schedule it like a session, hard stop |
| Pixel-peeping | Fit-to-screen first; zoom only for ties |
| Rating 1 to 5 | Binary pick/reject with auto-advance |
| Second-guessing | One pass, forward only |
| Keeping near-dupes | One frame per burst, tiebreakers ready |
| No reject pass | Fast sweep for obvious kills first |
| No scene grouping | Decide within groups, not across the whole shoot |
| Never measuring | Time one cull; get your baseline |
None of these fixes cost money. Together they routinely halve a cull, and if you later hand the first pass to software, the habits still compound, because AI tools accelerate a clean system far more than they rescue a messy one. For the full craft, start at the complete culling guide.
Back up the same day, cull later. Fresh from a shoot you're emotionally attached to frames because you remember taking them, not because they're good. A day of distance makes you judge the image on screen instead of the moment in your head, and the cull goes faster because of it.
It costs you three times: storage, a second decision later (you'll face the same duplicates again at editing), and a diluted gallery if they slip through to the client. Research on loss aversion helps explain why deleting feels risky, but in practice the "just in case" frame almost never gets used. Pick one per burst and move on.
Usually a stack of these mistakes: zooming to 100% on every frame, rating on a 1 to 5 scale instead of binary keep/reject, no rejects-first pass, and re-reviewing decisions you already made. Each one multiplies your seconds-per-frame, fix them and the same shoot culls in a fraction of the time.
No, every fix in this article works with the software you already own. AI culling tools help most with the first-pass mistakes (obvious rejects, duplicate grouping), but flags-over-stars, scene grouping, and not culling at 1 AM are free habit changes.
Kepla for Mac clears the obvious misses from a card, names the reason on every frame it sets aside, and leaves the choosing to you. Nothing is ever deleted, moved or renamed. Free through the private preview · the first hundred photographers keep it at $99 a year.