iformat.io Logo iformat.io
iformat.io Logo iformat.io

The Wedding Photographer's Workflow: Batch-Converting a Full RAW Shoot

Aug 25, 2026
7 min read

You get home from a 12-hour wedding day with four 128 GB cards full of RAW files. That's somewhere between 2,000 and 4,000 photos totalling 60–120 GB. The couple wants a sneak peek on social media tonight, a highlight gallery within a week, and the full edited set within four to six weeks. Every day you spend processing is a day you're not shooting, not marketing, and not invoicing.

This workflow is built around speed without sacrificing quality. It's the process that works for a solo shooter or small studio handling 20–40 weddings per year. The tools change — Lightroom vs Capture One, Photo Mechanic vs FastRawViewer — but the steps and timing are consistent.

Step 1: Ingest and backup (day of, evening)

Before you do anything else, get the files off the cards and backed up. Cards are fragile and singular — if one fails before you've copied the data, those photos are gone. No RAID, no cloud sync, nothing can recover them. The 3-2-1 rule applies: 3 copies, 2 different media types, 1 offsite.

Practical implementation: copy all cards to your working drive (internal SSD for speed) using a dedicated card reader — not the camera's USB connection, which is slower. Simultaneously copy to a backup drive (external HDD or NAS). A USB 3.2 reader transfers a 128 GB card in about 8–10 minutes. Four cards = ~40 minutes of transfer time.

Once both copies verify (check file counts match — Quick Tip: ls | wc -l on each folder), start your offsite backup — Backblaze, Google Drive, or rsync to a remote server. This runs overnight. Do not format the cards until you've confirmed at least two successful copies. Keep the cards in a separate case from your camera bag as a physical backup until the offsite copy completes.

Step 2: Culling (day 1)

Culling is where you separate the keepers from the rejects. Of 3,000 RAW files, you might deliver 600–900 final images. Fast culling is the biggest time-saver in the entire workflow — if you spend 5 seconds per photo, that's still 4+ hours for 3,000 photos. Speed matters.

Photo Mechanic Plus is the industry standard for culling. It loads embedded JPG previews from RAW files (not the full RAW data) which means you're flipping through photos at full speed — no waiting for rendering. Colour-tag or star-rate your keepers. Most photographers use a two-pass approach:

First pass: go through everything quickly. Yes/no only. This should take 1–2 hours for 3,000 photos. Don't evaluate quality at this stage — just flag whether the moment is worth keeping. Blurry group shot? No. Sharp group shot with everyone looking at the camera? Yes. Move fast.

Second pass: go through the "yes" pile. Rate on quality: sharp focus, good expression, good composition, good light. This narrows 1,200 first-pass keepers down to 600–900 final selects. Another 30–60 minutes.

If you don't have Photo Mechanic, Lightroom's Library module works but it's slower because it generates its own previews from the RAW data rather than using the embedded JPG previews. FastRawViewer is another fast culling option that shows actual RAW data (useful for checking true exposure).

Step 3: The sneak peek (day of or day 1)

Couples expect a handful of photos on Instagram or in a private text within 24 hours. This is non-negotiable for client satisfaction in 2026 — social media moved the timeline expectation from "weeks" to "hours." Pick 10–15 strong images from the culling pass — ceremony moment, first look, one detail shot, one portrait, one reception candid.

Quick-edit these in Lightroom: basic exposure, white balance, your signature colour grade applied via preset. Export at 2048px long edge, JPG quality 90, sRGB. Total time: 20–30 minutes. If time is extremely tight (you're exhausted after a 14-hour day), the image converter can extract the camera's embedded JPG previews from the RAW files — these are unedited but properly exposed and colour-corrected by the camera's built-in processing, which is good enough for a same-day social post.

The image resizer can batch-resize the exports to Instagram dimensions (1080 × 1350 for feed posts, 1080 × 1920 for stories) if needed.

Step 4: Batch editing (days 2–5)

This is the core of the workflow. The goal is consistent colour and exposure across 600–900 images without editing each one individually. Individual editing at 2 minutes per photo would take 20+ hours — that's not sustainable at volume.

Preset-based workflow: Start with a base preset that applies your signature look — colour grade, tone curve, sharpening, noise reduction, lens profile correction. Apply it to all imported photos on import. Then go through groups by scene (ceremony, portraits, reception, dance floor) and adjust exposure and white balance to match the lighting conditions for that group.

In Lightroom: select a group of similarly-lit photos, edit one, then Sync Settings to the rest. Ceremony in a dimly lit church? Edit one frame for white balance and exposure, sync to all 200 ceremony shots. Outdoor portraits in golden hour? Edit one, sync to the batch. This approach means you're making maybe 15–20 unique edits across the entire set — one per lighting condition — and syncing each to its group.

AI-assisted editing: Tools like Imagen AI and Aftershoot learn your editing style from previous weddings and apply it automatically to new imports. The AI handles crop, exposure, white balance, and colour grading based on patterns in your editing history. You review the results and tweak the ones that need it. This can cut batch editing time from 4–6 hours to 30–60 minutes, though you'll still want to review every photo manually.

Step 5: Export and delivery (week 1–2)

Export settings for the final gallery:

Full-resolution JPGs: Long edge 4500px (or full resolution), JPG quality 92, sRGB colour space, 300 DPI. These are the print-ready files the client gets. File size: 5–10 MB each. For more on export format choices, see export settings for print vs web.

Web-resolution JPGs: Long edge 2048px, JPG quality 85, sRGB, 72 DPI. These are for the online gallery (Pixieset, Pic-Time, ShootProof, CloudSpot). File size: 800 KB – 2 MB each. These load fast in the browser and look sharp on any screen.

Lightroom's export dialog handles both in one pass: create two export presets and run them simultaneously to two different output folders. Export time for 800 images at two sizes: approximately 30–60 minutes depending on your CPU.

Upload web-resolution files to your online gallery platform. Deliver full-resolution files via download link (Google Drive, Dropbox, or the gallery platform's download feature). The image compressor can reduce file sizes further if the gallery platform has upload limits.

Step 6: Album design (weeks 3–6)

If the couple purchased an album, select 80–120 images from the final set and design the layout in SmartAlbums, Fundy Designer, or your album company's built-in tool. Export spreads as TIFF or high-quality JPG at 300 DPI per the album printer's specs.

Album files are large — a 30-spread album at 300 DPI runs 3–5 GB total. If the album company has upload size limits (some cap at 50 MB per spread), the image compressor can bring individual files down.

Storage and archival

After delivery, archive the full wedding: RAW files, Lightroom catalog (or Capture One session), exported JPGs, and album design files. A typical wedding archive is 80–150 GB.

Store on two separate drives (one working, one backup) plus one offsite copy — Backblaze B2, Wasabi, or a physical drive at a different location. At current hard drive prices (~$15/TB for archival HDDs), a 150 GB wedding costs about $0.23 to store per copy.

How long to keep the archives depends on your contract and your risk tolerance. Most wedding photographers keep RAW files for 1–3 years and delivered JPGs indefinitely. Some keep everything forever — the storage cost is negligible. Put the retention period in your contract so clients know what to expect.

Frequently asked questions

How many photos do wedding photographers deliver?
Typically 50–100 photos per hour of coverage. An 8-hour wedding day yields 400–800 delivered images. A 12-hour full-day coverage yields 600–1,200. These are culled, edited, and exported — not the raw card dump of 3,000+ files.

RAW or C-RAW for weddings?
Both work. C-RAW (Canon) saves 30–40% storage with negligible quality difference in normal processing. The only scenario where full RAW helps: extreme shadow recovery in very underexposed reception dance floor shots. Full RAW is the conservative choice if storage isn't tight. See the CR3 format comparison for more detail on C-RAW quality.

What's the fastest way to get a few JPGs from RAW files?
The image converter extracts the camera's embedded JPG preview instantly — no RAW processing, no software installation. Good for same-day social media posts when you need 10 photos in 5 minutes.

Should I shoot RAW + JPG at weddings?
Some photographers do for the immediate social media turnaround. The JPGs are share-ready from the card; the RAW files are there for full editing later. The downside is double the storage per shot. With 256 GB+ cards, it's manageable. See the RAW vs JPG guide for the full trade-off analysis.

How long should the full editing process take?
For a solo shooter delivering 700 images: culling takes 2–3 hours, batch editing takes 4–6 hours (less with AI tools), export takes 30–60 minutes, gallery upload takes 30–60 minutes. Total active time: roughly 8–12 hours spread across a week. Album design adds another 3–5 hours.

Batch Convert RAW to JPG

Convert entire shoots in your browser. No software needed.

Browse All Posts