There’s a spreadsheet on my second monitor right now. It has columns for action name, date built, task type, average time saved per use, and total cumulative hours saved. I update it obsessively. The current total sits at just over 2,400 hours. That number is the reason I still evangelize automation to every photographer and retoucher I consult with, even when their eyes glaze over the moment I say the word “scripting.”

The point isn’t the number. The point is what it represents: years of small decisions compounding into something real. And the tools that got me there weren’t always the ones with the biggest marketing budgets.

Why “Just Use Actions” Is Incomplete Advice

Photoshop actions are the foundation, not the whole structure. An action records and replays a sequence of steps, but it has no awareness of context. It doesn’t know if the file it’s processing is 300 DPI or 72 DPI, RGB or CMYK, or whether the layer it’s trying to affect has been renamed by a careless junior retoucher. When an action hits a state it doesn’t recognize, it either fails silently or throws a modal error that stops your entire batch cold.

This is the part nobody explains in the YouTube tutorials. The action itself is maybe 30 percent of the solution. The other 70 percent is the infrastructure around it: how files enter the system, what condition they’re in when they arrive, and where they go after the action runs. Get that infrastructure right and the action becomes nearly bulletproof.

The Tools That Actually Earn Their Place

For batch processing, Adobe Bridge with its Image Processor script is still the most underrated free tool in the Adobe ecosystem. It’s not glamorous, but it handles folder-level batch exports with format conversion, resizing, and action application in a single pass. For e-commerce work, where a client sends 200 raw product images and needs them delivered as web-optimized JPEGs at 1200 x 1200 pixels with a consistent white balance pass, Image Processor plus a well-built action set handles it cleanly. I’ve run batches of 300 files in under 25 minutes on a mid-tier MacBook Pro.

For anything more conditional, Photoshop’s own scripting support via JavaScript is where the real leverage is. A script can check file dimensions before applying a resize, conditionally skip layers that don’t exist, and write a log file when something goes wrong. The learning curve is real, about two to three weekends of focused work if you’re new to it, but the payoff is permanent. I’ve been running a crop-and-composite script for ad agency deliverables for four years without modifying it once.

On the third-party side, Keyboard Maestro (Mac, $36 one-time) is something I recommend to nearly every retoucher I work with. It’s not a Photoshop tool specifically, but it handles the layer above Photoshop: moving files between folders, renaming batches with date-stamped prefixes, triggering Photoshop scripts from a single hotkey, and sending a notification to your phone when a long batch finishes. It removes the manual handling that eats 15 minutes out of every hour without feeling like work.

The Cautionary Tale of Over-Automation

A few years back I built what I thought was an elegant end-to-end system for a high-volume e-commerce client. Intake folder, auto-action triggered by a Hazel rule, output to three differently sized export folders, automatic upload to their FTP via a shell script. It worked beautifully for six weeks. Then their product photography team switched cameras, the new raw files had a slightly different default color profile, and the entire pipeline started delivering images with a subtle but consistent green cast. It took three days to identify the source because every step of the process was invisible.

The lesson: automated systems need visible checkpoints. Now every pipeline I build includes a “sample check” folder where one file out of every 20 gets routed for human review before the batch continues. It adds maybe 10 minutes to a large job. It has saved client relationships twice.

File Naming and Folder Structure as a Workflow Tool

This sounds boring. It is boring. It is also the thing that separates a system that runs for years from one that collapses under a new hire or a new client. I use a strict naming convention for every project: ClientCode-ProjectID-YYYYMMDD-SequenceNumber-Version. An example looks like this: ACME-0042-20240315-0001-v2.psd. Every file in a project is findable by any of those five variables. Combined with color-coded folder labels in macOS (yes, I color-code my Finder folders, I have no apologies), I can locate any asset from any client going back eight years in under 30 seconds.

For retouchers working with Photoshop actions on client files, I’d push you toward a similar convention specifically because actions can generate output files automatically. If your output file naming is inconsistent, you’ll spend more time sorting deliverables than you saved by automating the processing.

Matching the Tool to the Job Size

Not every job needs a full automated pipeline. For a 10-image editorial shoot, a single action with a function key shortcut is almost certainly enough. For 50 to 100 product images with consistent parameters, Image Processor plus an action handles it. Beyond 100 files with any variation in input conditions, you want scripting or a Keyboard Maestro-driven system with checkpoints built in.

The mistake I see most often is people applying enterprise-level automation thinking to small jobs and simple action thinking to large jobs. The tool mismatch wastes more time than just doing the work manually.

The single most important shift in how I think about workflow tools is this: the goal isn’t to automate tasks, it’s to automate decisions. If your system still requires you to make the same judgment call 200 times, you haven’t finished building it yet.