Culling in Lightroom: the fastest workflow, and when to stop using it

Here's a secret about "Lightroom is too slow for culling": out of the box, it genuinely is, and three settings fix most of it. Lightroom Classic culls respectably once you stop making it render previews mid-cull and take your hand off the mouse. This is the full setup, the keyboard-only pass, and, because honesty beats loyalty, the point where even a perfectly tuned Lightroom is the wrong tool for the job.

Lightroom isn't slow. Your preview settings are.

When you arrow through fresh imports and hit that Loading… flash on every frame, Lightroom is rendering a preview on demand, decoding a RAW file while you sit there. Multiply a beat of delay by a wedding's typical 2,000 to 4,000 RAW frames and the renders alone eat serious time before you've made a single decision. That's the entire mystery of "why does culling take all night in Lightroom": you've been watching a progress bar in disguise.

The stakes are bigger than annoyance. In a UK survey of 300+ wedding photographers, culling consumed 11% of total working time, with editing at 55% and actual shooting at just 4%. Culling is a real line item in your working year, and preview strategy is the cheapest lever you'll ever pull on it.

Five settings before your next import

1. Import with Embedded & Sidecar previews

In the Import dialog, set Build Previews to Embedded & Sidecar. Your camera already rendered a full-size JPEG inside every RAW file; this setting tells Lightroom to show you that instead of building its own (Adobe's preview documentation covers the details). Browsing becomes near-instant because there's nothing left to render: the same trick that made Photo Mechanic famous, which we unpack in Photo Mechanic vs Lightroom.

2. Stop Lightroom from replacing those previews mid-cull

In Preferences, enable the option to prefer embedded previews and leave Standard-preview generation for after the cull. Otherwise Lightroom quietly swaps its own renders in while you work, and the stutter returns.

3. Only build 1:1 previews when you'll zoom a lot

Zooming to check focus forces a full render. If your cull is zoom-heavy, critical-focus portrait work, say, build 1:1 previews overnight and cull in the morning against instant zooms. For most event culls, the embedded JPEG plus an occasional zoom-and-wait is the better trade than hours of pre-rendering.

4. Cull from a fast local drive, and optimize the catalog occasionally

A catalog and previews on an internal SSD beat a shoot culled directly off a spinning external. Housekeeping, not magic, but it stacks.

5. Decide your system before frame one: flags, not stars

Pick/reject is a binary decision; a five-star scale is an essay question asked four thousand times. Flags for the cull, stars later for album selects. The full reasoning lives in star ratings vs flags.

The keyboard-only cull

Go to Library, hit E for Loupe view, and, the single best Lightroom culling trick, turn on caps lock. With caps lock on, every flag keystroke auto-advances to the next photo. Your hands never leave the keyboard; the photos come to you.

Run it as two passes. Pass one, rejects only: X or nothing, no comparing, no lingering, you're deleting the obvious failures from contention. Pass two, picks: work scene by scene on what survives, using N (Survey) to shrink a burst to finalists and C (Compare) to settle ties side by side. Comparison is the judgment your eye is actually good at. The two-pass method scales up to full wedding volume. That walkthrough is in how to cull 3,000 wedding photos fast, and the complete keymap (plus Bridge and Capture One equivalents) is in the keyboard-only culling guide.

What about the maybes?

Undecided frames get U: unflagged, auto-advanced past, dealt with later. The trap is letting "later" mean "after the whole shoot," when you've lost the scene's context and have to re-judge from scratch. Sweep your maybes at the end of each scene instead, while the finalists are fresh, and give yourself a hard cap: if a frame survives two viewings without earning a P, it's an X. A maybe pile that grows past a handful is usually second-guessing wearing a system's clothes.

Close the loop: from flags to output

The cull isn't finished until the flags become file actions. Open the Library filter bar, filter to picks. That's your edit set, straight into Develop. Then filter to rejects and deal with them in one batch, as an admin chore, not a fresh round of decisions: archive them out of the working catalog (or delete, if your written retention policy says so: after confirmed backups, never before). Handling rejects in bulk also sidesteps the delete-anxiety that makes photographers re-open closed decisions; the psychology of why one-by-one deleting hurts is covered in why picking photos is so hard.

What a perfectly tuned Lightroom still can't do

Optimized Lightroom removes the waiting. It does nothing about the deciding, and deciding is the real cost. Be clear-eyed about what's missing:

• No automatic scene grouping. Dedicated tools cluster bursts and near-duplicates for you; in Lightroom, you are the clustering algorithm, all night.
• No blink, blur or closed-eye detection. Every technically-doomed frame still crosses your eyes and burns a decision. On a 3,000-frame wedding, that mechanical pass is exactly the work AI culling tools exist to absorb.
• No best-of-burst suggestions. Survey view displays ten near-identical smiles beautifully; it has no opinion about which one is sharp with both sets of eyes open.
• Every frame costs attention. The keyboard flow makes each decision fast, but you still make all of them yourself: thousands per job, usually at night.

None of this is a knock on Lightroom; culling is a task it hosts, not a task it was built around. The question is volume: at what point does the residual manual grind cost more than a tool that removes it?

So measure it. Next shoot, note the clock when you open the Library and when the last reject is filtered away, most photographers have never timed a cull and are consistently surprised by the answer. That one number is your decision input for everything below: multiply it by your jobs per year, price the hours at your rate, and the "should I pay for a culling tool" debate stops being a vibe and becomes arithmetic.

When to stop culling in Lightroom

The entry price of AI-assisted culling is lower than most photographers assume: Aftershoot Select runs $10/month billed annually ($120/year), and Narrative Select's Lite tier is also $10/month billed annually: both desktop apps that process locally and hand finished flags to Lightroom, both with unlimited images. So the switch question is really: is the first-pass grind of your annual volume worth more or less than roughly a hundred-and-twenty dollars a year to you?

Picture a photographer shooting a 20-wedding year at typical volumes, tens of thousands of frames crossing their eyes annually just to find the 400 to 800 photos each wedding delivers. For that photographer, software that automates the mechanical rejection pass costs pocket change against the hours it returns; the honest debate is only which tool, which is why our culling software roundup compares them head-to-head. For a photographer shooting the occasional family session, the free fix in this article is the whole answer, and free trials (Aftershoot's 30 days, Narrative's full Ultra trial, FilterPixel's 4 free projects, all no-card) mean testing the upgrade costs nothing but curiosity when volume grows.

Our own cards on the table: Kepla is building the next step in this direction: AI culling as native apps for iPhone, iPad and Mac, where the AI proposes picks and you approve them from the couch instead of the desk, with Lightroom integration planned. It's coming soon (waitlist, free while we build), not shipped today; until it ships, the workflow above is the best free cull there is.

FAQ