How to Cull Photos From Two Camera Bodies With Conflicting File Names

Why the same file name shows up on two cards

Most cameras number files from a counter that either resets when you format a card or simply starts over on a second body of the same model, so two shooters, or one shooter switching bodies mid-day similar to swapping memory cards mid-shoot, routinely end up with files like IMG_4821.CR3 or DSC_0002.ARW on both cards at once. The names collide because the counters are independent, not because anything is wrong with either camera. The actual risk is not that a culling tool gets confused by the coincidence; it is that a photographer copies both cards into one shared folder and one file silently overwrites the other, with no error and no warning, before culling even starts.

A concrete example

Say a second shooter's body resets its counter on a fresh format the morning of a wedding, and so does the lead's backup body after a mid-day battery swap. Both cameras produce a run of files named DSC_0001 through roughly DSC_0600 during the reception. If both cards get dragged straight into a single folder called Reception Photos, every file name that exists on both cards collides, and depending on copy order, one shooter's frame silently replaces the other's on disk. Nothing about culling causes this; it happens at the copy step, before any cull begins.

Step-by-step: importing two bodies without losing anything

1. Give every card its own destination folder at import, never a folder shared with another card, as described in how to organize wedding photos after the shoot, for example Originals/Camera-A and Originals/Camera-B inside the wedding's job folder.
2. Copy one card at a time and verify the count before starting the next, comparing the number of files copied against what the card reports.
3. Decide whether to rename, and do it only inside each camera's own folder if you want a permanent record of which body shot which frame, for example a batch prefix like A_ or B_ added to that folder's files only.
4. Only merge after both folders are safely separated on disk, either by pointing your culling tool at the parent folder that contains both subfolders, or by copying into one merged folder now that renaming or subfolder paths make every file name unique.
5. Cull the combined take as a single project once the import is settled; from this point the fact that two bodies were involved does not change your process.

Limitations

Keeping filenames separate does not fix a second, related problem: if the two bodies' internal clocks disagree, chronological sorting and burst grouping can still interleave the day incorrectly, a separate step covered in culling workflow for second shooter files. Filenames also carry no record of which camera shot which frame unless you add that yourself at import; if a client or your own workflow ever needs to know provenance later, a shooter prefix added while the cards are still separate is the only reliable way to preserve it.

How Cull AI Studio handles conflicting file names

Cull AI Studio scans the folder or folders you point it at and treats every file on its own terms, matching RAW+JPEG pairs by what sits in the folder rather than by trying to infer which camera produced a shot from its name. Because it works at the folder and file level, not by parsing filenames for camera identity, two bodies that both numbered a frame IMG_0001 cause it no confusion once each card has landed in its own folder instead of being copied on top of each other. Every RAW+JPEG pair is detected and moves together into KEEP, REJECT, or REVIEW as one unit, and originals are never edited or deleted, so a naming collision you catch after the fact is never destructive to correct.