Wedding culling guide

How to Cull Wedding Photos: A Three-Pass Workflow

Cull a wedding in three passes with PickSnap: mark keepers, compare similar frames, then rate the heroes. PickSnap is free and local on Apple Silicon Macs and Windows x64, supports RAW, and exports copies with optional XMP. Photos are not uploaded and originals remain untouched. The timeboxes below are suggestions, not measured performance.

Published by PickSnap.

PickSnap is our product. This guide separates our workflow suggestions from facts in the linked official documentation. It is not a speed benchmark or an independent product ranking.

Short answer: three steps

  1. Make a keep, reject or pending decision without editing.
  2. Compare competing frames within each moment.
  3. Rate standout keepers and check the story before export.

Separating these decisions gives each pass one job. The aim is fewer repeated decisions, not a promised completion time. Use the keyboard cheat sheet beside your first session.

Before you start

Back up the shoot, choose a working folder, and note the promised coverage and any client priorities. Divide your review into meaningful scenes such as preparation, ceremony and reception. Multi-camera clocks and missing metadata can make automatic time groups imperfect; review the group boundaries.

Suggested timeboxes for one manageable scene: start with 10 minutes for first decisions, 10 minutes for comparisons and 5 minutes for the hero pass. These are practice prompts, not a benchmark, a whole-wedding estimate or a reason to rush an unresolved moment. Adjust them after timing your own sample.

Where to make a wedding cull — sources checked 2026-10-29
WorkflowDocumented capabilityWhen to consider it
PickSnapLocal folder culling, adjustable burst groups and manual A/B comparison. Product facts.A free first pass before importing keeper copies into an editor.
Lightroom ClassicAssisted Culling evaluates focus, eyes and technical rejects; also available at import.You already work in Lightroom and want to review suggestions there.
Capture OneCull view opens the selected collection without requiring rendered previews.Your photos are already in Capture One and keeping one workflow is simpler.

Pass 1: P/X/U with Auto Advance

In Quick Cull, P or K keeps a frame, X rejects it and U parks it as pending. Turn on Auto Advance for a continuous pass; turn it off when you need to linger. Z undoes a decision. Reject marks leave the original files in place.

Look for whether the photograph contributes to the story. Mark a unique but uncertain moment pending instead of rejecting it solely because it is less technically clean than a nearby frame. Do not spend this pass fine-tuning every star rating.

Pass 2: bursts and A/B

Review PickSnap's burst groups, which use capture time, camera identity and parent folder. Adjust the interval, split a group that spans two moments, or merge a sequence that belongs together. Grouping is an aid to browsing, not a verdict on the best expression.

Press C on a reference, move to a candidate and press B to open comparison. In comparison, B switches A/B and the arrow keys change the candidate. Use Fit for composition, then 100% or 200% detail when focus is the deciding factor. Compare expressions and context as well as sharpness.

Pass 3: hero 1–5 / S

In Hero Selects, use 1–5 to rate and S for a five-star favorite. Give the ratings a consistent meaning for this job. For example, reserve five stars for potential album or preview choices; that is your editorial convention, not a universal scale.

Review pending frames explicitly and check that essential moments, people and transitions are represented. Avoid replacing a meaningful photograph just to make every image meet the same technical score.

Export + XMP to your editor

  1. Export the selected photos as copies to a new destination.
  2. Leave XMP off if a keeper folder is sufficient. Enable it when you want rating/rotation sidecars.
  3. Import a small sample into the receiving editor and check stars before processing the full set. Pick/reject flags and JPEG-to-RAW transfer are not guaranteed.

See culling before Lightroom and the XMP guide for the handoff details.

Stop rules and delivery counts

Stop the cull when pending decisions have been reviewed, key coverage is present, near-duplicates have an intentional role, and the export has passed a spot check. If you are repeatedly reversing choices without a new reason, take a break and return to the delivery brief.

There is no universal number of wedding photos to deliver. Coverage, contract, events and the couple's expectations set the scope. Do not delete valuable coverage to fit a number from a generic article. This guide supplies no invented average or photos-per-hour target.

If reviewing a large set is still your bottleneck, compare a manual pass with the Aftershoot alternative workflow. Include time spent checking suggestions and recovering missed moments in your own comparison.

Frequently asked questions

How long should culling a wedding take?

There is no verified universal time for a wedding cull. Shoot size, burst density, camera files and your decisions all affect it. Time a representative scene and plan breaks. The suggested 10/10/5-minute scene timeboxes in this guide are practice prompts, not performance claims.

How many photos should I deliver?

Use the agreed coverage and delivery brief, not a universal quota. Keep the moments and people needed to tell the event clearly, review duplicates deliberately, and agree expectations with the client.

Should I use AI for weddings?

Use suggestions if they reduce your total review work on a representative shoot. Review uncertain faces, unique moments and rejected frames yourself. A manual pass is also valid; neither a model score nor this guide determines the emotional value of a photograph.

Continue your culling workflow

Explore PickSnap, the 2026 photo culling software guide, and our Photo Mechanic alternative comparison. For the complete product limits, see features and specifications.

Last verified: . Official documentation was checked on this date; editor behavior can vary by version and file format.