The Difference Between Shooting RAW and Working RAW

I see it constantly when photographers share their screens during consultations. They’re shooting RAW, which is great. But then they’re sitting on folders of unprocessed CR3 or ARW files, sometimes from shoots three months ago, with no consistent naming structure, no processing presets, and no clear path from ingestion to delivery. They think shooting RAW makes them serious photographers. What actually makes you serious is knowing what to do with those files before the client’s first follow-up email lands.

RAW processing isn’t a style choice. It’s a technical responsibility. And if you don’t have a documented workflow behind it, you’re one hard drive failure or corrupted card away from losing work you can’t reconstruct.

What a RAW File Actually Is (and Why That Matters for Processing)

A RAW file is sensor data. That’s it. It has not been processed, sharpened, white-balanced, or compressed by your camera’s internal JPEG engine. When you open a CR3 from a Canon R5 or a NEF from a Nikon Z6 II, you are looking at a container full of uninterpreted light data, and your RAW processor, whether that’s Lightroom Classic, Capture One, or something else, is rendering an interpretation of that data in real time.

This matters because every adjustment you make in the develop module is non-destructive. You are writing instructions, not pixels. The actual sensor data never changes. That’s the core mechanical advantage of the RAW format, and it’s also why your processing settings need to be deliberate and repeatable. If you’re eyeballing white balance on every single frame without a reference or a preset, you’re not using RAW correctly. You’re just working harder for the same result you’d get from a JPEG.

A full-resolution RAW from a 45-megapixel camera typically runs between 45MB and 90MB per file. A 500-shot commercial shoot can land you 35GB before you’ve touched a single slider. That volume demands a system, not a vibe.

The Ingestion and Processing Framework I Actually Use

The moment a card comes out of a camera, it goes into my card reader and straight into Lightroom Classic using a tethered import with auto-backup enabled. I import to a primary working drive (a Samsung T7 Shield, around $90 for the 2TB version) with a simultaneous copy going to a second drive during import. That’s not backup paranoia. That’s the minimum floor.

My folder naming structure is fixed: YYYY-MM-DD_ClientName_JobType. No exceptions. This makes finding a specific shoot from 18 months ago a 10-second search instead of a 10-minute dig.

For processing, I work in Lightroom Classic with a base preset applied at import. That preset handles my lens correction (on), chromatic aberration removal (on), and a calibration shift I’ve dialed in for my primary body over years of testing. It does not set exposure or white balance, because those vary by job. What it does is eliminate 40% of the repetitive click-work before I’ve made a single conscious decision.

From there, my processing order is always the same: white balance first, then exposure, then highlights and shadows, then color grading, then sharpening. Sharpening always last. If you sharpen before you’ve corrected exposure and color, you’re sharpening a mistake.

For a 500-image commercial shoot, my initial cull and base processing runs about 90 minutes. Delivery-ready selects, usually around 80 to 120 images, take another two hours including export. Total RAW processing time: under four hours. If you’re spending more than that on a standard shoot, the problem is probably your workflow, not your eye.

When the System Actually Saved Me

My twins are 11 now and have grown up around hard drives and editing stations like other kids grow up around kitchen tables. A few years back, one of them managed to drag and drop an entire folder of client proofs, about 340 processed files, into the system trash and empty it. Gone from the working drive in about four seconds.

I had those files restored from the backup drive and back in Lightroom in under two minutes. The client never knew. More importantly, I didn’t spend the next six hours in a cold sweat trying to reprocess work I’d already done. The backup wasn’t heroic. It was just the system working the way a system is supposed to work.

That’s what a real workflow gives you: the ability to absorb a disaster without it becoming a catastrophe.

Export Settings That Protect Your Deliverables

Export decisions are part of RAW processing, not separate from it. For commercial deliverables, I export full-resolution TIFFs at 16-bit when the client needs layered flexibility, and high-quality JPEGs at sRGB when they don’t. JPEG compression at quality 90 in Lightroom gives you a file that’s visually indistinguishable from 100 at about 60% of the file size. For web deliverables, I export at 2048px on the long edge, sRGB, quality 80. That keeps files under 1MB while holding plenty of detail for screen display.

Every export gets a standardized file name with the client code and a sequential number baked in. This matters because clients reuse images, sometimes years later, and being able to match a delivered file back to a RAW original in your archive is a professional skill that most photographers overlook until they need it.

Your RAW files are the original negatives. Treat your export naming like a paper trail, because one day a client will come back asking for a specific shot from a job you did in 2021 and you will either find it in 30 seconds or spend an afternoon paying for the fact that you didn’t have a system.

The single most important thing you can do for your RAW workflow isn’t buying better software. It’s deciding exactly what you’re going to do with every file, in what order, and making that decision once, so you never have to make it again under deadline pressure.