I used to spend 20 minutes on every portrait just getting the file ready to edit. Open the raw, run the sharpening, convert to 16-bit, set up my layers, name them. Every single time. Same steps, same order, same mild frustration. I knew there was a better way. I just kept putting it off because learning actions felt like one more thing to figure out.

Then I ran a batch of 200 headshots for a corporate client with a two-day turnaround, and I figured it out fast.

What Photoshop Actions Are Actually Doing

An action is a recorded sequence of commands stored in the Actions panel. When you play it back, Photoshop executes those commands exactly as you recorded them, in the same order, with the same settings. That sounds simple, and it is. But understanding what gets recorded and what doesn’t is what separates an action that works every time from one that breaks on the third file.

Photoshop records most menu commands, tool settings, and dialog box inputs. It does not record freehand brush strokes in any reliable, repeatable way. It also records things you didn’t mean to record, like the specific pixel dimensions you happened to have open when you resized the canvas. This is the part that bites people. If you record an action on a 3000x2000px image and then run it on a 5000x4000px file, any step that references absolute pixel values will produce the wrong result. The fix is to use percentage-based transforms and to build in “stop” points where you want to intervene manually before the action continues.

Recording Your First Useful Action (Not a Toy One)

Open the Actions panel (Window > Actions). Click the folder icon at the bottom to create a new set. Name it something specific. I organize mine by project type, not by tool, which keeps things findable when you have more than a dozen saved.

Click the new action button (the page icon), name it, and hit Record. Now do the actual work. For a basic retouching prep action, I record these steps in order: flatten the image, convert to 16-bit (Image > Mode > 16 Bits/Channel), duplicate the background layer and name it “Retouch Base,” add a Curves adjustment layer set to neutral, and add a blank layer above everything named “Dodging.” Hit Stop.

That sequence takes about 45 seconds to record and saves me two to three minutes per file. On 200 headshots, that’s over six hours back in my day. The math is not subtle.

Where Actions Break and How to Fix Them

The most common failure point is a dialog box that appears during playback and waits for input, or worse, one that doesn’t appear and just uses whatever value was in place when you recorded. To force a dialog to open every time, click the small toggle box to the left of that step in the Actions panel. A dialog icon will appear, meaning Photoshop will pause and let you input values before continuing.

The second most common problem is path dependency. If your action saves a file to a specific folder that doesn’t exist on another machine or drive, it fails silently or throws an error. I always record Save As steps with “as a copy” checked and no hard-coded path, then handle the output destination separately at the batch processing stage.

Batch processing lives under File > Automate > Batch. Set your source folder, choose your action, set the destination, and decide how you want the files named. For client work, I use the naming convention: document name plus a two-digit serial number plus the file extension. It keeps everything sortable and avoids the nightmare of “final_FINAL_v3_USE THIS ONE.psd.”

The Action Set I Use Most (And Why It Has a Weird Name)

I keep a set called “Noir Prep” that I use for almost every retouching job regardless of style. The name is a holdover from my agency days when I was editing a lot of black-and-white fashion work. The set has seven actions: one for file setup, one that applies a high-pass sharpening layer at 1.5px radius blended in Soft Light at 60% opacity, one that builds a standard dodge and burn structure with two Curves layers masked to solid black, one for a basic color balance check using a threshold layer trick to find true black and white points, one that stamps visible and converts to Smart Object, one that resizes for web output at 2048px on the long edge at 72ppi, and one that runs a final Save As.

I’ve been refining those seven actions for about five years. They’re not dramatic. They’re not flashy. But they mean I spend my time actually retouching instead of clicking through setup menus.

I built that whole system during a week when I had no client work. My nephew was visiting, the same one who sat across from me years ago and asked me to show him how layers worked, and I spent two evenings just documenting and organizing every action I had floating around. He watched, asked questions, and somewhere in explaining why I’d built the dodge and burn action the way I had, I realized I’d been doing it slightly wrong for months. An outside question fixed a bad habit I didn’t know I had.

Making Batch Processing Reliable Across Different Files

For batch jobs to run cleanly, your source files need to be consistent enough for the action to run without hitting an unexpected state. Before I run any batch, I do a five-file test. I pick five files from different parts of the set, ones with different color profiles, different dimensions, different exposures. I run the action on each manually and watch what happens. If all five run clean, I batch the rest. If one breaks, I find out why before I’m 80 files deep into a corrupted export folder.

Also: log your errors. In the Batch dialog, under Errors, choose “Log Errors to File” and save the log somewhere obvious. It won’t stop the batch, but it will tell you exactly which files had problems and why. Reviewing that log takes five minutes and has saved me hours of manual cleanup.

The single most important habit in building actions is to record them on a generic, representative file rather than a real client file. What you do on the file you record on is what the action will try to do on every file you run it on. Start generic, and your actions will generalize.