The first time I handed over a card to be ingested on a deadline at the newspaper, I watched the photo editor pull the RAW files into Photoshop, make about four adjustments, and have a print-ready image in under three minutes. I’d spent forty-five minutes on a similar image the night before. That moment taught me something I’ve never forgotten: a RAW file is not a finished product. It’s a liability until you have a system for handling it.

Fifteen years later, running my own commercial operation out of San Francisco, I still think most photographers treat RAW processing like it’s a creative act when it’s really an engineering problem. Get the engineering right first. Then be creative.

What’s Actually Sitting in That RAW File

A RAW file is not an image. That sounds like a semantic argument, but it matters practically. What you’re looking at in Lightroom or Capture One is a rendered preview, built by the software using the metadata your camera attached at capture. The actual file is sensor data, unmolested, waiting to be interpreted. That’s the whole value proposition. You haven’t committed to a white balance, a tone curve, or a noise reduction approach. Every one of those decisions is still on the table.

This is also why RAW files are large. A 45-megapixel Sony A7R V produces RAW files in the range of 55 to 120 megabytes each, depending on compression settings. Shoot 500 frames on a commercial day and you’re looking at somewhere between 27 and 60 gigabytes before you’ve done anything. That number matters for storage planning, backup time, and delivery speed. If you don’t have a number in your head before you show up to a shoot, you’re guessing, and guessing is how professionals become amateurs.

The Ingestion Step Most Photographers Skip

Before I touch a single slider, every card gets copied twice. Once to my primary working drive, a Samsung T7 Shield, and once to a dedicated backup drive, a G-Drive Slim I keep in a separate bag. That bag stays in my car. The working drive comes inside with me. This isn’t paranoia. This is the minimum responsible behavior for someone who gets paid to deliver files.

I use Photo Mechanic for ingestion, not Lightroom. Photo Mechanic reads cards faster because it uses the embedded JPEG previews rather than rendering from the RAW data. On a 500-image card, this cuts my culling time from around 40 minutes in Lightroom down to about 12. At my billing rate, that difference is real money. After culling, I import only the selects into Lightroom for processing. Lightroom never touches the full card dump.

At ingest, I also apply a metadata template automatically. Client name, shoot date, copyright line, my contact information. Every single file, before I’ve looked at a single image. This is not optional if you’re running a business.

Building a Processing Baseline That Doesn’t Start From Zero

I keep a folder of Lightroom develop presets organized by lighting condition, not by look. One for overcast daylight. One for mixed tungsten and window light. One for strobe in a white studio. Each preset sets my starting white balance, a calibrated tone curve, lens corrections, and noise reduction appropriate to the ISO range I shoot in that environment. Nothing about color grading, nothing about creative interpretation. Just a clean technical baseline.

When I open a gallery of selects, I sync that baseline preset across everything in the shoot before I look at a single image closely. Then I do a second pass where I make exposure corrections by group, selecting all the images shot in the same lighting setup and adjusting them together. Ninety percent of my gallery is done at this point. I’m making individual adjustments on maybe one image in ten.

For noise reduction, I use Lightroom’s AI Denoise on anything shot above ISO 3200. One click, let it run. The quality difference versus the old luminance sliders is significant enough that there’s no argument. For color accuracy on product work, I shoot an X-Rite ColorChecker at the start of every setup and use the Lightroom plugin to build a custom profile from it. This is a ten-minute setup that saves two hours of arguing with a client about whether the fabric is “warm white” or “cream.”

The Time I Had to Prove the Backup System Worked

A few years ago, my twins, who were seven at the time, got curious about my desktop while I was on a call. They dragged a folder of client proofs to the trash and emptied it. We’re talking a folder with 340 processed JPEGs ready to send for review. I came back to an empty folder and two kids who looked like they’d swallowed something.

I had those files restored from my backup drive in ninety seconds. Literally. I keep a mirrored backup of my active projects folder that updates every fifteen minutes using ChronoSync, which costs $49.99 and is worth ten times that. The clients never knew. The twins are now very clear on what the external drives are for.

The point is not that I’m organized. The point is that backup is part of processing. It is not separate from it. If your processing workflow ends when you export your files, you don’t have a workflow. You have a habit.

Exporting for Delivery Without Guessing What the Client Needs

I have three Lightroom export presets: full-resolution TIFF for print or retouching handoff, sRGB JPEG at 3000 pixels on the long edge for web and social, and a 1500-pixel JPEG at 72 DPI for internal review and proofing. The review files are watermarked automatically using a Lightroom watermark preset I set up once in 2019 and have not touched since.

Every client gets a delivery spec sheet on booking that tells them exactly which format they’ll receive and why. This takes one thing off my plate during the delivery conversation and signals that I’ve thought about this before they asked.

The RAW originals stay on my archive drives for a minimum of five years, organized by year and client. I test those drives monthly. Not quarterly. Monthly.

Your camera captured something real. The workflow is how you honor that, and how you make sure you can prove it when someone asks.