There’s a specific kind of misery that comes from doing the same Photoshop task 200 times in a row. I know this because I lived it, about nine years ago, when a client handed me a folder of 200 product images that all needed the same crop, resize, and export sequence. I did the first thirty by hand before something in my brain snapped. I spent the rest of that day learning how to script the whole thing. I’ve never manually repeated a task like that since.

That afternoon changed how I think about tools. Not “what software looks cool” but “what actually removes friction from the work.” Here’s what’s in my stack right now, why each piece is there, and what it’s actually doing behind the scenes.

Why Most Photographers Underestimate the Cost of Manual Repetition

The problem isn’t that repetitive tasks take time. It’s that they consume the wrong kind of attention. Creative decision-making and mechanical execution run on different cognitive resources, and when you’re doing both simultaneously, you’re degrading both. A retoucher who spends four hours doing manual color grading on 80 e-commerce images isn’t just losing four hours. They’re arriving at image 60 with a tired eye and a slower hand.

From a purely technical standpoint, every manual step is also a consistency risk. Humans drift. An action or script doesn’t. When I run a Photoshop action across a 300-image batch, image 300 gets the exact same curve adjustment as image 1, to the decimal point. That’s not a luxury for high-volume work. It’s the baseline expectation from ad agencies and e-commerce clients, who will notice when the white balance shifts between product shots in a carousel.

The Core Layer: Photoshop Actions Built Around Decision Points

I keep my action sets organized by client type, not by task. E-commerce gets one folder. Advertising composites get another. Editorial retouching gets a third. Each folder contains actions built around the decisions that don’t change, and leaves room for the ones that do.

A basic product shot action in my e-commerce folder does this: converts to sRGB, runs a Levels adjustment to clip shadows at 10 and highlights at 245, applies a 0.3-pixel Smart Sharpen at 120% with reduced noise set to 10%, and exports a flattened JPEG at 85 quality to a pre-named output folder. That sequence takes about four seconds per image when batched. The same sequence done manually, conservatively, takes about 90 seconds. On a 500-image job, that’s the difference between finishing at 3pm and finishing at midnight.

I track this obsessively. I have a spreadsheet that logs estimated time saved per action set. My total is currently sitting above 2,400 hours. Some people find that neurotic. I find it clarifying because it shows exactly where my tooling investments have paid off.

Where Bridge and Lightroom Actually Fit (and Where They Don’t)

Adobe Bridge is underused by almost everyone I talk to. For batch renaming alone, it’s worth keeping in your dock. I use it to rename delivery folders using the sequence: ClientName-JobCode-YYYY-MM-DD-001 through the end of the batch, which keeps my archive searchable without touching a single filename manually.

Lightroom’s Sync Settings function handles the early-stage color work on raw files before anything touches Photoshop. I’ll grade one hero image, sync those settings to the rest of the selects, then export to a watch folder that triggers a Photoshop droplet. That handoff between Lightroom and Photoshop, when it’s built correctly, means I’m not touching individual images again until final review.

The important caveat: Lightroom sync is not a replacement for careful masking in Photoshop. It’s a first pass. Anyone who tells you a preset can handle product photography straight out of Lightroom hasn’t delivered work to a client who knows what they’re looking at.

Third-Party Tools Worth the Annual Fee

Two tools outside the Adobe ecosystem earn their keep every month for me.

Luminar Neo for sky replacement on location work. I’m not using it for its AI retouching, which I find inconsistent, but the sky replacement mask quality at the $99/year tier is faster than what I can produce manually in a similar timeframe for most standard shots. On a job with 15 hero lifestyle images, it saves me roughly 40 minutes.

FastRawViewer at $19.99 (one-time) is the first thing I open when a memory card comes in. It reads raw histograms directly from the file without rendering, which means I can cull 800 frames in about 20 minutes and only pass the genuine selects to Lightroom. Ingesting 800 files into Lightroom to cull them there is slow and punishes your catalog. FastRawViewer keeps the catalog clean.

I’ve tried the free culling tools. They’re slower and the histogram accuracy on compressed raws is unreliable. The $20 is not worth debating.

Building a System That Doesn’t Break When You’re Busy

The thing about workflow tools is that they only save you time if they’re already set up when the job lands. I built most of my current action sets during slower weeks, not because I had nothing else to do, but because that’s the only time you can think clearly about the logic of a sequence before deadline pressure makes you cut corners.

My rule: after every new job type, I spend 30 minutes asking whether any part of it could be automated for next time. Not everything can be. Retouching a beauty shot for a cosmetics campaign involves judgment calls that no action can make. But the export sequence? The sharpening pass? The file naming? Those can always be handed off to a script.

The most valuable thing I’ve built isn’t any single action. It’s the habit of treating my own time as the scarcest resource in the room, and building tools accordingly.