If you shoot weddings, you already know the pattern. One wedding day can turn into thousands of captures, several cards, multiple backup folders, and a post-production process that stretches across days or weeks. Couples usually review JPEG previews or an online gallery first. Then they send a list of picks, favorites, or must-edit images.
That is where a surprisingly tedious task begins: going back to the original folders and pulling the corresponding RAW files for each selected frame.
Why this part of wedding post-production feels so slow
Wedding photographers usually do not complain that editing exists. They complain that the workflow surrounding it is fragmented. Culling, proof delivery, client selections, and final retouching often happen in different places, at different times, and with different file formats.
By the time the couple sends back favorites, you may be working from:
- JPEG previews exported for the gallery,
- a list of filenames copied from proofs,
- screenshots from an online gallery,
- or a spreadsheet of selected image numbers.
The source files, meanwhile, are still sitting as CR2, CR3, NEF, ARW, or DNG files in your original shoot folders. When you have to match those by hand, the work is tedious, easy to mess up, and hard to batch cleanly.
The usual manual process
For many photographers, the default workflow still looks like this:
- Review the couple's list of selected JPEGs.
- Search for each matching basename inside the original RAW folders.
- Copy those RAW files into a separate edit folder.
- Repeat until the selected set is complete.
Lightroom can help if everything is already inside one well-maintained catalog, but not every wedding photographer wants to live inside a large catalog workflow for this step. If the job is spread across folders, drives, or exported proof sets, the process still ends up feeling manual.
A faster workflow after client culling
The most efficient version is much simpler: treat the client's selected JPEG list as the input, treat your original RAWs as the source pool, and match them automatically by filename.
In practice, that means:
- Gather the selected filenames from JPEG files, pasted text, or screenshots.
- Point to the wedding's RAW files.
- Match by basename.
- Export only the corresponding RAW files for final edit.
If your JPEG proofs keep the same base filename as the original captures, this removes most of the repetitive searching. Instead of going one photo at a time, you can move from client picks to final RAWs in one pass.
Why this matters for delivery speed
Faster matching is not just a nice convenience. It affects turnaround time. When the proof-to-edit handoff is messy, your final gallery delivery slows down too. That is one reason wedding post-production can feel like it drags on for weeks, even when the actual creative editing is not the only issue.
Reducing the admin friction matters because it helps with all three things wedding photographers care about most:
- Time: fewer hours wasted digging through folders.
- Accuracy: less chance of missing or mis-pulling a file.
- Energy: less post-production burnout after long wedding days.
Where RAW Matcher fits
RAW Matcher is built for this exact handoff. Instead of replacing your whole editing system, it focuses on the moment after client selections arrive. You can bring in JPEG picks as files, pasted text, or screenshot-derived filenames, choose the RAW pool, and pull the matching RAWs without doing the one-by-one hunt manually.
That makes it a good fit for wedding photographers who want something lighter than a full catalog-heavy workflow, especially when the real goal is simple: get from client picks to the correct RAW files as fast as possible.