Why I Stopped Trusting My Own Hands for Repetitive Work

A few years into running my own post-production consultancy, I had a client send over 500 product shots on a Thursday afternoon. White background, consistent lighting, but every image needed a clipping path, a levels adjustment, an output sharpen, and an export at three different pixel dimensions for web, print, and Amazon listings. Five hundred images. Three exports each. That’s 1,500 output files.

I built a batch system over the weekend before that job arrived, mostly out of necessity and a mild panic response. By Monday morning, the whole thing ran while I made coffee. I’ve tracked the hours my actions have saved me in a spreadsheet since around 2016, and that single batch system accounts for somewhere over 200 hours of recovered time on its own.

The point isn’t to brag about efficiency. The point is that most photographers are still doing things manually that a properly configured tool could handle invisibly, and the cost isn’t just time. It’s consistency, accuracy, and the mental overhead of repeating the same decisions 400 times in a row.

What’s Actually Happening When a Batch Process Runs

Photoshop’s Actions panel records a literal script of your mouse events, dialog inputs, and menu selections. When you play that action on a folder via File > Automate > Batch, Photoshop opens each file, runs the recorded sequence, and either saves in place or exports to a destination folder, depending on how you’ve configured the Save step.

The part most people get wrong is the “Override Action ‘Save As’ Commands” checkbox in the Batch dialog. If your action contains a Save As step and you don’t check that box, every file will try to save to the exact path you recorded during the action, not the destination folder you just specified. That one checkbox causes more broken batch jobs than anything else I see.

File naming is the other variable worth controlling tightly. The Batch dialog lets you build a filename string from components: document name, serial number, date, file extension. For product work, I typically use Document Name + two-digit serial number + underscore + custom text for the size variant. Something like bag_hero_01_2000px.jpg. This makes sorting by variant trivial in Bridge or the client’s asset management system.

The Tools Worth Paying For (and One You’re Probably Overlooking)

For anything beyond Photoshop’s native batch system, I rely on three tools with real regularity.

Photoshop Droplets are underused. A Droplet is a standalone application you export directly from the Batch dialog. You drag a folder onto the Droplet icon on your desktop and it runs your action without you opening Photoshop manually. I have Droplets for web output sharpening, background neutralization, and my standard e-commerce export sequence. They live in a folder color-coded yellow on my second monitor.

Adobe Bridge’s Image Processor (Tools > Photoshop > Image Processor) is faster than the Batch dialog for pure export tasks because it skips the action overhead entirely. If all you need is a JPEG at 85 quality and a max dimension of 2,000 pixels on the long edge, Image Processor does it in roughly 60 percent of the time Batch takes on the same folder. For a 300-image product catalog, that difference is about 18 minutes on my current machine (M2 MacBook Pro, 32GB RAM).

Keyboard Maestro ($36, Mac only) sits outside Photoshop entirely but integrates cleanly with it. I use it to trigger Droplets via hotkey, rename output folders automatically based on the date, and move finished exports into the correct client folder in my project hierarchy. It’s not a Photoshop tool, but it closes the gaps between Photoshop and everything else.

Building an Action That Doesn’t Break Six Months From Now

The biggest mistake I made early on was recording actions against specific layer names. If your action selects a layer called “Background copy” and that name doesn’t exist in the next file you run it on, the action either throws an error or does nothing, silently. Silent failures in a 400-image batch are genuinely painful to discover.

Record against layer position instead of name where possible: use “make layer active” from the Layers panel rather than targeting by name. For any step where you’re not sure, wrap the action in a conditional using the “If/Then” scripting support in Photoshop’s Script Events Manager. It takes about 20 minutes to learn the basics and saves hours of troubleshooting.

I also keep a “version date” in every action name itself, like Ecom_Export_v2024-03. When a client updates their spec sheet, I duplicate and modify the action, keep the old one, and know exactly which version was running during which project period. This sounds obsessive. It has saved a client relationship at least twice.

The Real Cost of a Broken Workflow

I learned to write basic Photoshop scripts after spending an entire workday doing the same crop-and-resize on 200 files by hand. Not because I didn’t know batch processing existed, but because I was certain the task had enough variation that I needed manual control over each one. It didn’t. I made the same crop. Two hundred times. Eight hours.

The scripting took a weekend to learn at a basic level. The time I’ve recovered since then is logged in a spreadsheet. It’s well past 2,400 hours across all my actions and automations combined.

The tools in this space are not glamorous. Nobody posts a Droplet to Instagram. But the photographers and retouchers who run efficient studios all have something in common: they made the boring infrastructure decisions early, and now those decisions run quietly in the background while they do the work that actually requires their judgment.

The single most valuable thing you can do this week is record one action for a task you repeat more than three times a day, and test it on a batch of ten files before you trust it with hundreds. Everything else follows from that habit.