Setting up Assisted Culling, and when to overrule it

Adobe's Assisted Culling works best when you treat it as a lens rather than a verdict. Turn everything on at full strength and it will feel like half the shoot has been hidden from you. This is the setup, control by control, with every menu path taken from Adobe's own help pages, and then the more useful half: the frames where a working photographer should overrule it.

Where the feature is, in both versions of Lightroom

In Lightroom Classic you switch it on under Catalog Settings > Metadata > Assisted Culling. Adobe's help page for the feature gives a second route as well: select the drop-down beside the Identity Plate and turn on Auto Analysis. Then pick a folder or a collection in the Library module and let the analysis run. The panel appears on the right hand side.

In cloud Lightroom it is simpler and worded differently. Adobe's page for Lightroom says to open an album and select Assisted Culling > Cull. The two versions do not use identical labels, which trips people up when they follow a tutorial for the wrong app. Classic says Subject Focus and Eye Focus. Cloud Lightroom says Subject Sharpness and Eyes Sharpness. Same idea, different words on screen.

Two things worth knowing before you build a season around it. Adobe labels Assisted Culling early access, and in its own walkthrough of the feature it states that "the current feature set is optimized for portraits and headshots". That single sentence should shape how much you lean on it, and it is why the setup below is organized by scene. This article is about the panel itself. If you want the whole culling pass in Lightroom Classic, the flag keys, the filter bar and Compare view, that is our full Lightroom Classic tutorial.

The panel, control by control

There are four parts to it, and they do different jobs. Select decides what gets promoted. Reject decides what gets pushed out. View is just a filter on what you are looking at. Organize Result is the one that writes to your files.

The Reject section is the part I would trust on any job in any genre. A misfire is a misfire and a photograph of a receipt is a photograph of a receipt. The Select section is where judgment starts.

Running it at import, and the checkbox to think twice about

Classic can also run the analysis as the files come in. Adobe's page on culling at import gives the steps: in the Library module select Import, choose a folder from the Source menu, then select Assisted Culling. The same Select and Reject controls appear, along with Auto Stack and an Assisted Culling Info button.

Two extra checkboxes live there. Import Auto Stacks to Collections is harmless and useful if you already work in collections. Don't Import Rejected Images is the one to think about. It does what it says: the frames the analysis rejected never enter your catalog. The files themselves are untouched on the card or the drive, so nothing is lost, but they are also not in front of you, and a frame you never see is a frame you cannot argue with.

My rule is simple. For a headshot day or a set of product frames, that checkbox saves time and costs nothing. For a wedding, a documentary job, or anything where the best photograph of the night might be technically imperfect, leave it off and do the rejecting inside the catalog where you can look. There is a wider list of the frames a machine reliably gets wrong in what AI culling misses.

Set it by scene, not by job

The fastest route to poor results is one strict setting applied to an entire wedding. A bright family formal, a dark dance floor and a windy portrait session produce completely different kinds of failure. For formals, open eyes and sharpness are a fair first gate. For a reception, those same settings will push out intentional blur, partial faces and dramatic light that belong in the gallery.

So split the job before you filter it. Make collections, or use a temporary flag, to divide the day into scenes. On a 3,000 frame wedding I would build groups for details, preparation, ceremony, formals, portraits, reception and exit. It takes a few minutes and it stops a formal portrait standard from flattening the dance floor.

Then set the panel differently for each one. Formals and prep get the strict version. Ceremony gets Eyes Open off, because half the frames are of people looking down. Reception gets Subject Focus loosened and the eye rejection switched off entirely. If a scene is not about faces at all, details, rings, the venue, the cake, run the Reject section over it and ignore the Select section, since face scoring has nothing useful to say about a table setting. That boundary is drawn properly in the limits of Assisted Culling.

A setup that works for family formals

Group photographs are where this feature genuinely shines, because the delivery standard is unusually clear: eyes open, faces recognizable, focus reliable. Set Eyes Open on, leave both focus sliders near the default, turn on all three reject reasons, and start by filtering for the frames where eyes are open. Then do the human part.

Adobe added something in the June 2026 release that helps here. Its what's new page describes a Faces panel in Assisted Culling Info that lets you review Eye Focus and Eyes Open scores for each detected face in a photo. On a group of fourteen that is the difference between knowing a frame scored badly and knowing which uncle caused it.

1. Filter the obvious blinks and focus misses out of the first view.
2. Compare what is left in order, at size, not as thumbnails.
3. Zoom to the people at the edges of the frame. They are the ones a quick scan misses.
4. Mark the strongest whole group expression, plus one safety alternative. If no single frame is right, keep two rather than force an answer.
5. Clear the filter once before you move on, to check that a misread face was not hidden from you.

An eyes open score also means less as the group grows, which is its own problem with its own arithmetic. We worked through that, and the head swap question, in culling group photos.

Auto Stack, bursts, and not flattening the story

Adobe's help page notes you can Auto Stack images based on time and visual similarity, and the June 2026 release added automatic detection of duplicate images that can be organized into stacks for review. Both are a real time saver on controlled bursts, and both can quietly flatten a sequence if you let a stack stand in for a decision.

A bride turning toward a window might give you six related frames, each with a different relationship between dress, light and expression. Use the stack to find the cluster, then open the whole cluster and look at it as a contact sheet. The question is not which file is sharpest. It is which version earns its place.

Three passes is usually enough. Set aside the frame that is genuinely unusable. Mark the cleanest representative. Then ask whether a different frame in the group says something the representative does not: a laugh, a hand moving, a wider composition, a transition that will carry a gallery spread. If it does, it is not a duplicate just because the camera barely moved.

How to overrule it cleanly

Do not argue with a filter by trying to make every exception fit its logic. Give yourself one manual override state instead. I use a single color label for frames the panel pushed aside that still deserve a look, and I go back to that label before finalizing anything. The visual separation keeps them from disappearing into the rejects while keeping the main selection small. Pick one color and keep its meaning for the whole season, as we argue in using color labels for culling.

Where to spend that override attention is predictable. Check the frames immediately before and after every selected moment, since reactions arrive late. Check any frame with a person the client cares about disproportionately: a grandparent, a child, the guest who traveled furthest. Check profile portraits, glasses glare, long hair, eyelashes and anyone deliberately looking down, because eye criteria struggle there. Adobe itself points at the sunglasses case as the reason the eyes detected checkbox can be turned off.

And lower your expectations of technical criteria in low light on purpose. In a dark reception I do not use them as a reject list at all, only as a way to decide what to review first. A soft frame can be perfect at the size a client will actually view it, and softness that is invisible in a gallery is not a defect. The cleanest photograph of a speech may be the one where the father of the bride is listening politely. The one with a focus wobble may be the one where his hand is over his mouth while his daughter watches him. No score can make that call.

Before you press the batch action, and what to do when it looks wrong

Organize Result is the only part of this panel that changes thousands of files at once. In Classic, Adobe describes those batch actions as flagging, rating, labeling and adding the Selects and Rejects to a collection or folder. In cloud Lightroom the same section offers a delete option for rejected photos, so read the screen you are actually on before clicking, especially if you move between the two.

Look at the Rejects view first, every time. It takes two minutes at thumbnail size and it is the only check that catches a setting you got wrong across a whole wedding. If the Rejects view looks right, the Selects view almost always is. Then apply. Doing it in the other order heads our list of Lightroom culling mistakes.

If the results look wrong, work through it in order. Confirm you are looking at the collection you think you are and that no attribute filter is still switched on from the last job, which is the single most common cause of photos appearing to vanish. Then test on twenty images you know well and look for a pattern: profile faces, one camera's focus behavior, dark clothing, a scene you should have split out. If it is slow rather than wrong, let previews finish before you start and cull one scene at a time. The settings that make the whole catalog quicker are in the Lightroom speed setup.

One last habit: do not assign permanent star ratings while you are still testing thresholds. Make the broad decision first, then rate in one pass. And if what you actually want back is the evening rather than the sorting, that is the gap Kepla is being built for, a first pass on the phone on the drive home with nothing ever deleted, moved or renamed. The picking app is still in development. Your booking page is live today, free while we build.

FAQ