The File That Contains Everything (And Does Nothing on Its Own)

I shot newspaper assignments for seven years before I went commercial. In that world, you had maybe four minutes from the moment you handed your card to the photo desk to the moment your image hit the wire. There was no time to fix a bad exposure in post, no time to second-guess your white balance, and absolutely no time to dig through 800 frames hoping something was usable. That pressure built habits I still use today, but it also taught me the one truth that most photographers learn too slowly: a raw file is not a finished image. It is a liability that you agreed to deal with later.

That “later” is where most workflows quietly fall apart.

What a RAW File Actually Is (And Why It Demands More From You)

A raw file is sensor data. Your camera has not made any decisions about sharpening, white balance, tone curves, or color rendering. None. The file you are looking at in your camera’s LCD is a JPEG preview baked on top of the raw data for display purposes only. When you open that file in Lightroom or Capture One, you are starting from scratch every single time.

This matters because it means every processing decision is yours. That is the power and the problem. Shoot in JPEG and the camera handles 30 or 40 micro-decisions for you at the cost of losing data you can never recover. Shoot raw and you keep every stop of dynamic range, every color depth bit, every recovery option. A raw file from a Sony A7R V holds around 14 stops of dynamic range. A JPEG from the same camera throws away roughly 2 to 4 of those stops permanently at capture.

The file size difference is significant too. A compressed raw from that camera runs about 60 to 80 MB. An uncompressed raw is closer to 120 MB. A JPEG from the same shot might be 15 to 20 MB. Multiply that across a 1,200 frame commercial shoot and you are talking about storage decisions that have real dollar costs.

Building a Processing Workflow That Actually Ships Work

Here is how I run my raw processing pipeline, specifically in Capture One Pro 23, which I switched to from Lightroom in 2020 after a subscription price change made me recalculate the math.

When cards come off the camera, they go into a tethered ingest through a dedicated card reader (I use the Lexar Professional USB-C Multi-Card), not the USB port on my laptop. Simultaneously, a copy goes to a dedicated SSD on my desk and a second copy goes to a 4TB Sandisk Extreme portable drive. That happens before I look at a single frame.

Inside Capture One, I have a base style preset I built over about two years of calibrating against my most common deliverables. It is not aggressive. It sets sharpening to around 90 with a radius of 0.8, noise reduction at 30 luminance for ISO values under 3200, and a very slight S-curve lift in the blacks to about 5. White balance stays as-shot until I do a global pass. That one preset saves me four to six decisions per image before I even start culling.

I cull first, process second. This is not obvious to everyone. I go through the full take in Capture One’s browser at 1x magnification, rating with a three-star system: one star means maybe, two means yes, three means hero. I never process a one-star. After culling, I apply my base style to all two-stars in a batch, then spend individual time on three-stars. On a 1,200 frame shoot, this typically gets me to 40 to 60 processed finals in about three hours.

Why Your Color Space Decision at Export Matters More Than You Think

Processed does not mean exported. These are different steps and collapsing them creates problems.

I export client-facing JPEGs in sRGB at 300 DPI for print and 72 DPI at 2,000 pixels on the long edge for digital review. I export in AdobeRGB only when the client has confirmed they are printing to a wide-gamut device and their print vendor has confirmed their workflow supports it. Sending an AdobeRGB file to someone who opens it in an unmanaged browser is how your beautifully processed portrait turns into a desaturated, muddy mess that you have to explain to a client who does not understand color profiles. Do not do it.

The raw masters stay on my system indefinitely, in their original folder structure: year, month, client name, shoot name. I do not delete raw files. Storage is cheap. Reshoots are not.

The Time I Understood What Backup Actually Means

My twins are eight now. A few years ago, they found their way into my office while I was on a call and managed to drag an entire folder of client proof selects into the trash and empty it. We are talking about a final delivery folder for a corporate headshot day. Sixty-four processed JPEGs, ready to go.

I had them back in 90 seconds. Because that folder, like everything on my system, syncs automatically to Backblaze, which runs in the background at $9 a month and maintains 30-day version history. I did not panic. I did not apologize to the client. I sent the delivery link on schedule.

That is what backup actually means. Not “I have an external drive somewhere.” A system you have tested under pressure, that you know will hold.

The Processing Decision That Defines Your Business

Raw processing is not a creative luxury. It is the step where you either have control over your work or you are just hoping the defaults hold. Every minute you spend building a real workflow pays you back across every shoot for the rest of your career.

Set up your ingest, build your base preset, cull before you process, and never conflate raw files with finished deliverables. Your clients are paying for the final image. Make sure you know exactly how you get there.