I’ve been shooting professionally for nearly two decades, and I can tell you with absolute certainty: your shooting technique matters, but your processing workflow determines whether you’re running a sustainable business or constantly putting out fires.

Raw processing isn’t just about making images look better. It’s about protecting yourself legally, maintaining consistency across jobs, and creating an efficient pipeline that doesn’t hemorrhage time and money.

Why Raw Isn’t Optional

Let me be direct: if you’re delivering JPEGs straight from your camera, you’re leaving money on the table and creating liability.

Raw files give you latitude. When a client’s skin tone is slightly off, or the white balance needs adjustment, you have the data to fix it without destroying image quality. JPEGs compress that data away—permanently. You get one shot, and if the in-camera settings weren’t perfect, you’ve failed your client.

Beyond that, raw files are your insurance policy. I’ve had clients request re-exports in different color spaces, ask for black-and-white conversions months later, or request edits for different platforms. With raw files, I deliver. With JPEGs, I’m starting from scratch or explaining why I can’t.

From a business standpoint, raw processing also justifies your pricing. Clients don’t see the work—they see the final image. But you know the difference between a five-minute JPEG cleanup and a thirty-minute raw edit that transforms a mediocre shot into a sellable image.

Building a Processing Workflow That Scales

Here’s where most photographers sabotage themselves: they treat each image as a standalone project.

I use a tiered approach:

First pass: Culling and flagging. I import everything into Lightroom, set library flags, and mark my selects. This happens before any adjustment. I’m ruthless here—deleted images don’t require processing time.

Second pass: Global adjustments. I create a develop preset for the shoot based on lighting conditions. White balance, exposure, vibrance, shadow/highlight recovery—these go on everything that made the cut. Most of my shots get 80% of the way to done in ten minutes using one preset.

Third pass: Individual refinement. Now I handle specific images. Skin tone corrections, dodging and burning, clarity adjustments. This is where artistry happens, but only for images that deserve the time.

Export and backup. I export to PSD and JPG simultaneously—the PSD stays in my archive for future adjustments, the JPG goes to the client. Both get backed up to two separate locations immediately.

The Non-Negotiable Settings

After years of correcting my own mistakes and redoing work for clients, I’ve learned what matters:

  • Color space: Export in sRGB for web and print unless the client specifically requests Adobe RGB. Most displays can’t handle it anyway, and you’ll frustrate clients with unexpectedly dark images.
  • Metadata: Strip EXIF data you don’t need, but keep copyright and licensing information embedded. This protects you legally.
  • File naming: Use consistent naming—Date_Client_ImageNumber. Future you will thank present you when you’re searching archives three years later.
  • Resolution: 300 DPI for print, 72 DPI for web. Don’t overthink it.

The Real Cost of Skipping Steps

I once tried to streamline by skipping the global preset phase and adjusting each image individually. Saved maybe two minutes per image. But consistency suffered, my color grading varied wildly between shots, and I spent double the time fixing problems.

The workflow I’ve described takes longer upfront but saves time and headaches throughout the client delivery process and future revisions.

Raw processing done right isn’t about perfectionism—it’s about building systems that work.