How to Cull Photos Captured Across Multiple Memory Cards in One Shoot

Card swaps are an import problem, not a culling problem

A full wedding day routinely fills more than one card, whether from a planned swap between getting-ready and ceremony or an unplanned one when a card fills faster than expected. None of that changes how the take should be culled once it is on your drive; a merged 3,000-frame take from four cards culls exactly like a 3,000-frame take from one. What card swaps do change is the import step before culling starts, where the real risks live: forgetting which cards have already been copied, re-importing one by accident, or starting to cull before confirming every card actually transferred in full.

A concrete example

Say a wedding day fills three cards: one for prep and ceremony, a second for portraits and formals, a third for the reception after a card swap during dinner. If the photographer copies all three onto the laptop but loses track of which one she already copied earlier in the day, re-plugging the ceremony card a second time either duplicates thousands of frames into the working folder or, worse, overwrites a partially organized folder mid-cull. A simple running list, ticked off as each card is copied and verified, prevents the entire problem for the cost of thirty seconds per card.

Step-by-step: importing and culling a multi-card shoot

1. Copy each card into its own subfolder as you offload it, rather than dumping everything into one folder as cards come in, following the same pattern as how to organize wedding photos after the shoot.
2. Track which cards have been copied as you go, a written list or labeled cards works fine, so a card never gets imported twice by accident.
3. Verify each card's copy before setting the card aside, comparing file counts and spot-opening a few frames, the same check described in how to back up wedding photos before culling.
4. Merge the verified card folders into one wedding job folder once every card is confirmed copied, keeping the per-card subfolders as your record of what came from where if you want that history.
5. Cull the merged take as a single project from that point forward; the fact that it came from several cards has no further bearing on the process.

Limitations

None of this catches a card that failed to copy silently, which is why spot-checking matters more than trusting a file count alone; a corrupted transfer can sometimes report a plausible count while missing actual image data. If two cards were used in different bodies rather than sequentially in one, you may also be dealing with clock drift between cameras on top of the card-merge itself, which is worth checking before you rely on chronological order across the merged set. Card swaps also do not by themselves cause duplicate photos, sequential cards from one body do not overlap in content, so treat this as an import-discipline problem, not a duplicate-detection problem.

How Cull AI Studio handles a multi-card take

Once the cards are safely merged into one organized folder, Cull AI Studio scans and sorts the whole take together, locally, into KEEP, REJECT, and REVIEW, with no distinction made between frames that came from the first card of the day and frames that came from the last. RAW+JPEG pairs are detected and always kept together regardless of which card they originated from, and burst and duplicate grouping works across the full merged timeline, so a moment shot right at a card swap is still grouped and compared correctly. If two different camera bodies were involved rather than one body across several cards, culling photos from two camera bodies with conflicting file names covers that added wrinkle.