The Day I Stopped Doing Things Twice

I was 26, working in a commercial studio in Chicago, and someone handed me a folder of 200 product images that all needed the same crop, the same canvas size, and the same sharpening pass before they went to the client. No one told me about actions. I just started doing it manually, one file at a time, and by image 47 I wanted to quit photography entirely.

I didn’t quit. I opened the Actions panel instead.

That afternoon I built my first Photoshop action, ran it as a batch across the rest of the folder, and watched Photoshop chew through 150 files in about 11 minutes. I’ve never willingly repeated a manual task in Photoshop since. I track this obsessively, the way other people track steps or calories. Right now, my spreadsheet puts my cumulative time savings from actions at just over 2,400 hours. That’s roughly 100 days of my life I got back.

If you’re not building actions yet, or if the ones you’re building keep breaking on you, here’s what you actually need to understand.

What Actions Are Really Doing Under the Hood

Most people think of Photoshop actions as a simple macro recorder, press play and it repeats what you did. That’s true at the surface level, but the reason actions break so often is that they record more context than you realize.

When you record a step like “flatten image” or “apply Gaussian Blur at 2.3px,” Photoshop stores that as a command with specific parameters. But when you record something like “move this layer to the top,” it can store the absolute pixel position, or the layer index, depending on what you moved and how. Run that action on an image with different dimensions or a different layer stack, and it fails silently or does something unexpected.

The critical technical distinction is between document-relative operations and layer-relative operations. Resizing a canvas by percentage is portable. Moving an element to pixel coordinates 340, 880 is not. Actions built without this awareness work great on the test file and nowhere else.

There’s also the issue of color mode. An action recorded in RGB will throw errors or skip steps when run on a CMYK file. If your clients include print vendors, and mine do, you need either separate action sets for each color space, or you need to build a mode-check into your workflow using a conditional action, which Photoshop has supported since CC 2014 and most people have never touched.

Building Batch-Proof Actions: The Settings That Actually Matter

When you open the Actions panel and hit record, slow down before you do anything. The decisions you make in the first 30 seconds determine whether this action runs on 10 files or 10,000 files without breaking.

First, set your ruler units to percentage before recording any move or transform. Go to Preferences, Units and Rulers, and switch from pixels to percent. Now your transformations scale with the document. This one setting change fixed probably 60% of the broken actions I’ve inherited from other photographers when taking over a client’s workflow.

Second, use Save As with a specific naming convention rather than Save. Record a Save As step that targets a subfolder called “processed” relative to the source folder, using Photoshop’s built-in filename variables in the Batch dialog, not hardcoded paths. Hardcoded paths are the fastest way to build an action that only works on your machine.

Third, when building actions for e-commerce specifically, where I do a lot of my work, I build separate actions for each output channel. One action for web JPEG at sRGB, 72ppi, quality 8. Another for print TIFF at Adobe RGB, 300ppi, uncompressed. Running them sequentially through a droplet takes about 4 seconds per file and removes every manual export decision from the equation.

Why I Build Action Sets, Not Single Actions

A single action is useful. An action set built like a modular system is transformative.

I organize every client’s workflow into a set structure: a “Prep” action that flattens, converts to the correct color profile, and checks canvas size; a “Retouch” action or set of actions that applies standardized adjustments; and an “Export” group with one action per delivery format. The Prep action always runs first, which means by the time any downstream action fires, the file is in a known state. That predictability is what lets me batch 500 files with confidence instead of nervously babysitting the process.

A few years ago I took on an e-commerce client who had a catalog of about 500 product shots that all needed background cleanup, color correction to a reference standard, and three export sizes. I spent one weekend building and testing the action system. The following Monday I processed the entire catalog in a single afternoon. The client thought I’d had a team working on it. I was alone, eating a sandwich, mostly watching a progress bar.

When Actions Fail and What to Do Instead

Actions are not the answer to every problem. I want to be honest about that.

Complex retouching decisions, anything involving content-aware tools, and anything that requires you to assess the image creatively before acting on it, these don’t belong in an action. Photoshop’s content-aware fill, for example, behaves differently on every image by design. Record it in an action and you’ll get unpredictable results at best.

For those tasks, I use actions to handle everything around the creative step, the prep before and the export after, and I leave the judgment-dependent work as a manual pause. You can build a Stop command into any action that halts playback, shows a custom message, and waits for you to resume. That way the repetitive scaffolding is still automated, and you’re only spending time on the parts that actually require your eyes.

The single most valuable thing I can tell you about Photoshop actions is this: the goal is not to automate everything, it’s to automate everything that doesn’t require a decision, so that when you do make a decision, it’s the only thing you’re doing.