I once handed a client a USB drive full of JPEGs processed straight out of camera. This was early in my commercial work, after years at a newspaper where speed was the only thing that mattered. The photos were technically fine. The client came back two months later needing a reprint at a different crop ratio, and I had nothing to give her. The original exposures were gone. What I’d delivered was the end product, not a living file. That mistake cost me a reshoot, a half-day of my time, and a client who never booked again.

That’s what shooting RAW actually protects you against. Not just bad exposures. Futures you can’t predict yet.

What’s Actually Inside a RAW File (and Why It’s Not the Same as a JPEG)

A RAW file is sensor data. It hasn’t been processed, sharpened, color-corrected, or compressed by your camera’s onboard computer. A JPEG, by contrast, is a finished interpretation made by firmware that doesn’t know your client’s brand colors or the fact that their CEO was squinting slightly and needs that highlight opened up.

When you shoot RAW, you’re preserving the full dynamic range your sensor captured. On a modern mirrorless body, that’s often 13 to 15 stops of latitude. A JPEG bakes that down into 8 bits per channel, which means you’re throwing away real information before you’ve even opened the file on your computer. If you underexpose by two stops in JPEG, the shadows may be unrecoverable. In RAW, with a file from something like a Sony A7R V or a Nikon Z8, you can pull two to three stops of underexposure back cleanly with almost no visible noise degradation. That’s not a marketing claim. That’s physics.

Building a Processing Workflow That Doesn’t Eat Your Day

Here’s what my import workflow looks like in Lightroom Classic, which is still, despite everything Adobe has done to annoy me, the most practical tool for volume commercial work.

On import, I apply a custom develop preset built around my most common shooting conditions: a flat tone curve, +10 texture, -15 clarity, lens correction enabled, and chromatic aberration removal checked. That preset doesn’t make the photos done. It makes them all start from the same honest baseline instead of whatever the camera manufacturer decided looked punchy that day.

I rename files on import using a custom template: YYYYMMDD-ClientCode-####. So a job for a restaurant client shot on March 3rd, 2025 becomes 20250303-TACO-0001.RAF. This sounds fussy until you’re searching for a file two years later and you find it in 30 seconds instead of 30 minutes.

From that baseline, a 400-image commercial shoot typically needs selective editing on maybe 80 to 100 selects. I cull first using the Lightroom compare view, flag keepers with P, rejects with X, and auto-reject on the first pass. Total culling time for 400 images: 25 to 35 minutes. Then I edit the selects to delivery standard, sync similar setups across the board, and export to a client folder at full resolution as 16-bit TIFFs for licensing deliverables, and compressed JPEGs at 90 quality for web proofing. Export time with a modern machine: under 8 minutes for 100 files.

The File Size Math You Need to Account For

A single RAW file from a 45-megapixel camera runs roughly 85 to 110 MB. A 600-image shoot generates 50 to 65 GB of RAW data before you’ve made a single edit. Exported TIFFs will add another 30 to 40 GB for your selects. You need to budget for this.

My working storage is a Synology NAS running two 8 TB drives in RAID 1. After delivery, project files move to cold storage on a 14 TB external drive, duplicated to a second drive kept off-site. Yes, I have three copies. I test them every month. This is not overkill. It’s just what the job requires when clients license images for five years and call you asking for the original RAW file in year four.

When the Twins Tried to Teach Me About Redundancy

A few years ago, my kids were in my office doing homework while I took a call. When I came back, a folder of proofed client selects had been moved to the Trash and emptied. My daughter had been trying to delete her own school project and grabbed the wrong folder.

The whole thing was restored in 90 seconds from my local backup. I didn’t lose a single file and delivered to the client on time. I’m not telling this story to brag. I’m telling it because for years I ran my business without proper redundancy because nothing bad had happened yet. The day it almost did happen, the only reason it didn’t blow up my client relationship was because I had finally gotten serious about the infrastructure behind my workflow.

Your RAW processing pipeline is only as good as the system keeping those files alive.

What Separates Archival Quality From Folder Chaos

The last piece most photographers skip is catalog architecture. In Lightroom Classic, I keep one catalog per year, backed up to a separate drive every Sunday night using an automated task. Each catalog entry links to the physical file location on the NAS. If I need to locate, reprocess, or re-export anything from a shoot in 2019, I open the 2019 catalog and it’s there, with the edit history intact.

RAW files with Lightroom develop settings are non-destructive by design. The original sensor data never changes. That means a client can come back in 2027 needing a different crop, a different color grade, or a version without their old logo in the background, and you can deliver it without a reshoot.

The whole point of a RAW workflow isn’t image quality for its own sake. It’s that you’re building a business that can honor commitments to clients long after the shutter clicked.