Last year I timed myself doing a standard skin retouch pass on a portrait. Frequency separation, a curves adjustment, a sharpening layer, and my usual export setup. Eleven minutes. Not bad. Then I multiplied that by the 40 portraits in the batch I was working through. That’s over seven hours of the same eleven steps, in the same order, every single time.
I already had an action for most of it. I just hadn’t wired it up properly. After one afternoon of fixing that, the same batch took 22 minutes total.
That’s what Photoshop actions actually are when you use them correctly. Not a party trick. Not a “nice to have.” A multiplier on every hour you put into this work.
What an Action Actually Does (and Why Most People Underuse Them)
An action is a recorded sequence of Photoshop commands saved to the Actions panel. When you play it back, Photoshop executes every step in order, exactly as you recorded it. That sounds simple because it is. The power is in what you chain together and how you trigger it.
Most people record one action, use it twice, and forget about it. The problem is they treat actions like macros instead of building blocks. A single action that flattens, sharpens, and exports is useful. But an action that calls other actions, pauses for your input at specific steps, and then hands off to a batch process? That’s a completely different category of tool.
Under the hood, actions store commands as a sequential list tied to specific panel states. Some commands are fully reproducible regardless of the document. Others, like certain filter settings, are document-dependent. Knowing which is which saves you from broken playback later.
Recording Your First Useful Action (With the Settings That Actually Matter)
Open the Actions panel: Window > Actions. Create a new set first. I name mine by workflow type, not by date or project. “Retouching,” “Export,” “Compositing” are three of mine. Inside that set, click the new action icon, name it something specific like “Frequency Separation 8-bit” and hit Record.
Now work slowly and deliberately. Every click is being logged. For a frequency separation setup, you would:
- Duplicate the base layer twice. Name the bottom “Color,” the top “Texture.”
- Select the Color layer and run Filter > Blur > Gaussian Blur at 4.0 pixels for standard portrait work at 300dpi. Adjust for different resolutions.
- Select the Texture layer. Go to Image > Apply Image. Set Layer to “Color,” Blending to Subtract, Scale to 2, Offset to 128. For 16-bit files, change Blending to Add, Scale to 2, Offset to 0.
- Set the Texture layer blend mode to Linear Light.
Hit Stop. You just recorded a four-step setup that used to take two minutes every time. Across a 40-image batch, that’s 80 minutes returned to you.
The key detail most tutorials skip: if you want the action to pause and wait for your input at any step, like before you apply a filter so you can adjust the radius per image, go to the Actions panel menu and enable “Toggle Dialog On/Off” for that specific command. The checkbox icon next to the step controls this.
Building a Batch Process That Runs While You Sleep
The real automation lives in File > Automate > Batch. This is where you point Photoshop at a folder, assign an action, and let it run.
Set your Source to a folder of raw files. Choose your action set and the specific action. Under Destination, I use “Save and Close” for most export batches or “Folder” when I want to preserve originals. Check “Override Action ‘Save As’ Commands” if your action includes an export step, otherwise Photoshop will attempt to save twice and you will get errors.
File naming matters here. Use the token system: Document Name + underscore + 2-Digit Serial Number gives you “Portrait_01.jpg” automatically. For client work I add the date token in front so I can sort by batch instantly.
One place people get burned: layer-dependent actions. If your action expects a specific layer to be active and the source files don’t match that structure, the batch fails mid-run. Build actions that start from a flattened or merged state when possible, or use a “Flatten Image” command as the first step.
The Organization System That Saves You From Your Own Library
I have over 400 custom actions. I know how that sounds. But none of them are hard to find because every action set is named with a clear category prefix and a specificity level. “Export > Web 1200px sRGB,” “Retouch > Dodge Burn Setup,” “Color > Split Tone Warm.”
Two things that make this work. First, assign keyboard shortcuts to your highest-frequency actions. Function keys F2 through F12 are available through Edit > Keyboard Shortcuts > Tools. I keep F5 for my export action and F6 for my sharpening sequence. Second, export your action sets regularly as .ATN files and back them up offsite. Losing a well-built action library is the kind of thing that ruins a Tuesday.
The Actions panel also supports color coding per action. I use red for destructive actions, yellow for anything that flattens layers, and green for safe-to-run-anytime setups. It takes ten seconds per action and has saved me from running the wrong process on the wrong file more times than I want to admit.
When Actions Break and How to Debug Them Fast
Actions fail for three common reasons: resolution mismatch, color mode mismatch, or a missing layer. Before running a batch, check that all source files are in the same color mode, RGB vs CMYK will break filter commands silently. Check that your action’s recorded resolution assumptions match the source files if you have any pixel-specific operations like Gaussian Blur or canvas size changes.
To debug, open one source file and play the action in single-step mode by holding Ctrl (Windows) or Cmd (Mac) while clicking Play. Photoshop will pause after each command and show you exactly where it stops. Fix the recording from that step forward instead of re-recording the whole thing.
The single most valuable habit I’ve built in 15 years of doing this: every time I catch myself doing the same thing three times in a row, I stop and record an action. Three repetitions is the threshold. That discipline compounds faster than any individual technique you’ll ever learn.
Comments
Leave a Comment