The File Format Isn’t the Problem. Your Workflow Is.

I spent years shooting for a daily newspaper. Deadlines were not suggestions. You delivered clean, print-ready images by a hard stop, or someone else did. There was no room for “I’m still processing” or “my catalog is being weird.” That environment shaped everything about how I approach files to this day, and nothing exposed weak workflows faster than RAW.

RAW is not a magic format. It’s a promise. A promise that you captured enough data to make good decisions in post, and that you have the system in place to actually redeem that promise without burning three hours on a single gallery. Too many photographers treat RAW as the destination when it’s really just the starting line.

What’s Actually Inside a RAW File, and Why It Changes Everything

A JPEG bakes in your camera’s processing decisions at the moment of capture. White balance, contrast, sharpening, tone curves. all of that gets cooked in and compressed down. You get a smaller file and faster preview, but you lose the latitude to change your mind.

A RAW file, whether that’s a Canon CR3, a Nikon NEF, or a Sony ARW, stores the unprocessed sensor data. Your camera’s picture profile doesn’t apply. White balance is metadata, not pixels. Highlight recovery can pull back a stop or more. Shadow lifting is cleaner, with far less noise than doing the same work on a JPEG. A Sony A7R V, for example, produces a roughly 60MB RAW file compared to a 15MB JPEG from the same frame. That size difference represents real recoverable information.

The processing is deferred, which is where your workflow either earns its keep or collapses under volume.

Building the Processing Pipeline Before You Open a Single File

The mistake most photographers make is treating RAW processing as an editing task. It isn’t. It’s a production task, and it needs to be systematized before your first cull, not figured out during it.

Here’s what my baseline looks like in Lightroom Classic. I shoot in a custom camera profile that I’ve matched to a DCP profile in Lightroom, so my starting point isn’t the flat, desaturated default that most people fight against. I built that profile once, saved it as my import preset, and I haven’t thought about it since.

On import, every file gets: lens correction enabled, chromatic aberration correction enabled, noise reduction set to 20 luminance as a floor, and my export sharpening preset applied at the develop stage. None of this is creative. It’s maintenance. Getting files to a clean, neutral starting point takes zero additional time because it happens automatically.

From there, I batch-apply my base exposure corrections using the Sync function for any group of images shot in consistent light. I’m not painting every frame by hand. I’m correcting by group, then only touching the outliers. A 500-image commercial shoot takes me roughly 90 minutes of processing time using this method. I’ve watched photographers spend that long on 50 images because they’re doing it one frame at a time.

The Settings That Actually Matter for a Commercial Deliverable

Clients don’t care how you got there. They care what they receive. So let’s talk about export settings that hold up professionally.

For web and social delivery, I export JPEGs at sRGB, quality setting 85, with the long edge at 2048 pixels. That’s the sweet spot for file size and visual quality on screens. Files come out between 400KB and 900KB, fast to upload and still sharp on a Retina display.

For print or high-resolution licensing, I export full-resolution TIFFs in AdobeRGB at 16-bit, with no downsampling. Those files run 80MB to 150MB depending on the camera, and they go to the client on a shareable folder via a service like Pixieset or Dropbox Business, not Gmail.

Metadata matters too. Every exported file leaves my machine with my copyright embedded, my contact email, and a usage description in the IPTC fields. That’s not paranoia. That’s a paper trail when a brand uses your image without licensing it.

What Happened When My Twins Discovered the Delete Key

My kids were about eight when they got curious about my work computer one afternoon. They found a folder labeled “CLIENT PROOFS, DO NOT TOUCH” which is, evidently, the most inviting label you can give a file to an eight-year-old. By the time I walked back in, around 240 processed JPEGs were in the trash and the trash had been emptied.

I had those files restored from my backup NAS in under two minutes. Not because I’m a tech wizard, but because my system was already in place. Every processed export goes automatically to a local NAS drive and mirrors to Backblaze B2 within six hours. The NAS is a Synology DS423+ running a RAID 1 array, and the offsite cloud backup costs me $9 a month.

The point isn’t the specific hardware. The point is that my processing workflow includes the backup step as part of the workflow, not an afterthought I remember to do occasionally.

The Part Nobody Tells You About RAW Processing at Scale

RAW processing only saves you time if your catalog stays organized. I use a folder structure of Year, then Month, then Client Name and Shoot Date. Every import goes into the right folder before I touch a single slider. Lightroom’s catalog grows, and if you don’t maintain it, it becomes a liability.

Once a quarter, I do a catalog audit. I verify that my backup drives still sync, that my folder structure hasn’t drifted, and that my import preset still reflects how I’m actually shooting. It takes 45 minutes. It has saved me from several disasters that I caught early enough to fix quietly.

Your RAW workflow is a business system, not just a technical preference. Build it once, test it under pressure before a client does, and it will hold.