I built my first Photoshop action at 26 after spending an entire day doing the same crop-and-resize operation 200 times on catalog images for a mid-size retailer. By 4pm I was making mistakes. By 6pm I wanted to quit the industry entirely. By 9pm, after teaching myself the Actions panel over a lukewarm dinner, I had automated the whole sequence in about 40 minutes. I haven’t manually repeated a task since.

That was 15 years ago. I now run a post-production consultancy out of Chicago, and actions are still the first thing I audit when I take on a new client. What I find, almost every time, is the same category of mistake. Not in the concept of using actions, but in how they’re built.

Why Actions Break Differently Than You’d Expect

Photoshop actions are essentially keystroke and command recordings played back in sequence. The panel captures what you do, in what order, with what settings, and stores it as a series of steps that can be triggered with a single click or run across a folder in Batch mode. Simple enough.

The problem is that actions record context, not intent. When you record a step that moves a layer 40 pixels to the right, the action doesn’t know you wanted to center something. It just knows you moved a layer 40 pixels. Run that action on a document with different dimensions and you’ve now got a layer in the wrong place, with no error, no warning, and potentially no way to notice until you’re looking at 300 finished files.

This is the core technical issue most tutorials skip. Modal controls, conditional stops, and document-relative positioning exist specifically to solve this problem, and most self-taught action builders never learn they exist.

The Setting That Saves Batch Jobs From Falling Apart

Inside any recorded action step, you’ll see a small toggle column to the left of each step, next to the checkmark visibility toggle. That second column controls whether a dialog box opens during playback. By default, it’s off, meaning the action blasts through with recorded settings. Turn it on for critical steps like curves adjustments, transform operations, or any filter with parameters, and the action pauses, opens the dialog, and waits for your input.

For client work, I use a hybrid approach. Steps that should always be identical (file naming structure, baseline sharpening at Amount: 80, Radius: 1.0, Threshold: 0 for screen-optimized deliverables) get recorded with modal controls off. Steps where the target value might shift slightly based on the image, like a selective color correction on product backgrounds, get modal controls on so I can make a quick judgment call without breaking the automation structure.

This is the difference between an action that handles 20 images and an action that handles 500.

Building for Batch Without Losing Your Mind

The Batch command lives under File > Automate > Batch, and it has settings that most people leave at their defaults, which is a mistake. The “Override Action ‘Open’ Commands” checkbox matters if your action includes an Open step. If it doesn’t, leave it unchecked or Photoshop will try to open the source file twice. The “Suppress File Open Options Dialogs” and “Suppress Color Profile Warnings” checkboxes are worth enabling for any folder of images you’ve already pre-qualified, because every stopped dialog adds friction and compounds across a large folder.

For destination, I always use “Folder” rather than “Save and Close,” and I specify a subfolder with a naming convention that includes the document name plus a two-digit serial number. This keeps the original files untouched and makes the output folder sortable by sequence, which matters when a client asks why image 47 looks different from image 48.

One afternoon a few years back, I processed 500 product shots for an e-commerce client using a batch system I’d built over a weekend specifically for their color profile requirements (sRGB IEC61966-2.1, 72ppi, JPG at quality 10, max 2000px on the long edge). Start to finish, the whole folder took about 90 minutes of machine time and maybe 20 minutes of my actual attention. That’s the kind of leverage that changes what you can charge and what you can take on.

Where Action Sets Fall Apart in Real Studios

I track the hours my actions have saved me in a spreadsheet. Right now I’m over 2,400 hours across 15 years, which sounds absurd until you realize that’s roughly one full year of 40-hour weeks. I’m not sharing that number to brag. I’m sharing it because it represents a failure mode that took me years to understand.

The failure is treating actions as personal tools instead of studio infrastructure. When an action lives only on your machine, in your panel, with no documentation and no portable .atn file exported to a shared drive, you’ve created a single point of failure. I had a freelancer once who built genuinely brilliant retouching sequences, and when she moved on, those workflows went with her. We spent two weeks rebuilding something that should have been a documented, exportable asset.

Now, every action set I build gets exported immediately as an .atn file, labeled with the date and client code, stored in a folder structure that my team can access, and accompanied by a plain-text note explaining what the action assumes about the incoming file (color mode, layer structure, resolution). That last part is what separates a tool from a system.

The Single Setting Most Photographers Forget to Record

Color mode awareness. Actions recorded in RGB will not behave correctly when played back on a CMYK document, and vice versa. Steps involving blending modes, certain filters, and adjustment layer types are all color mode-dependent. If you’re building actions for a studio that delivers both screen and print files, you either need separate action sets for each, or you need a conditional Mode Check step at the start of your action using the Image > Mode menu path.

Build the action for the file, not for the ideal file. The ones that hold up over years are the ones that assume nothing.