The Friday Afternoon That Changed How I Work

A few years back, I took on a rush job for an e-commerce client: 500 product images, all needing background removal, a levels adjustment, a sharpen pass, and export to three different sizes for web, print, and mobile. Deadline was Monday morning. It was Friday at noon.

I could have done what I used to do: open each file, run through the steps manually, save, close, repeat. I know exactly how long that takes because I tracked it obsessively before I built my first real batch system. About 4 minutes per image when you include file management. That’s 33 hours of work I did not have.

Instead, I spent 90 minutes on Friday building a batch workflow in Photoshop. By 5:00 PM, all 500 images were processed, sorted into folders by output size, and ready for delivery. I spent the evening with my family.

That story is not me bragging. It’s me telling you what batch automation actually looks like when it’s built correctly, not just recorded once and hoped for the best.

What Photoshop Is Actually Doing When You Run a Batch

Most people think of Actions as a simple macro recorder. You hit record, click around, hit stop, and replay. That’s the surface. What’s happening underneath is that Photoshop is writing a sequential instruction set that operates independently of the specific file you recorded on.

The catch is that Actions are stateful. They remember things like exact pixel coordinates, specific layer names, and hardcoded color values. If your recording session had a canvas that was 3000 x 2000 pixels and your batch folder contains 4000 x 3000 files, steps that reference absolute pixel positions will break. This is why so many people record an Action, run it on 200 files, and come back to find half the outputs corrupted or skipped.

The fix is building Actions that use relative, not absolute, references wherever possible. Use “Fit Image” instead of “Image Size” with locked pixel values. Use “Select All” before a crop operation rather than drawing a selection at coordinates. Use percentage-based canvas operations. These habits separate an Action that works once from one that works every time.

Building a Batch That Holds Up: The Actual Steps

Here is the workflow structure I use for e-commerce product batches. This is not theoretical.

Start by creating a master Action set, not a single Action. I typically build three chained Actions: one for raw corrections (levels, curves, noise reduction), one for output prep (sharpening, color profile conversion to sRGB), and one for export. Running them in sequence via File > Automate > Batch gives you checkpoints where you can interrupt if something goes wrong, instead of one monolithic Action that fails silently 300 files in.

For the Batch dialog settings: set Source to Folder, check “Override Action Open Commands” if your Action includes an Open step, and set Destination to Folder with a subfolder naming convention. I use a date prefix plus a descriptor, something like 20240912_web or 20240912_print. “Override Action Save As Commands” should also be checked if you’ve built a Save step into the Action. If it’s unchecked, Photoshop will try to save back to the original file location, which is not what you want.

For file naming inside the Batch dialog, I use Document Name plus a two-digit serial number plus the extension. This keeps files sortable and prevents the naming collisions that happen when batches are interrupted and restarted.

On export size: I run three separate batch passes rather than building a multi-export Action. Each pass writes to its own folder. Web gets 1200px on the long edge at 72 PPI, JPEG quality 8. Print gets 3000px at 300 PPI, JPEG quality 11. Mobile gets 800px at 72 PPI, JPEG quality 7. Separating these passes means if the print export fails halfway through, you are not reprocessing everything.

The Time I Ignored My Own System and Paid For It

About two years into running my consultancy, I took a shortcut I knew better than to take. A client needed 120 fashion images retouched with a fairly complex skin smoothing step. I was busy, so I recorded a quick single-pass Action instead of breaking it into the modular structure I described above.

The Action worked fine on the first 40 images. Then I hit a file that had an extra layer the photographer had left in, a notes layer with feedback text. The Action tried to apply a Curves adjustment to that layer, failed, and because I had “Continue” selected in the error handling, Photoshop quietly kept going for the next 80 files, applying every subsequent step to the wrong layer.

I delivered the job, the client caught it, and I spent a Sunday reprocessing everything correctly. That mistake cost me about 6 hours and a fair amount of client trust. The lesson is not that batch automation is fragile. The lesson is that your Action needs to explicitly target the correct layer by name or position before any adjustment step, and your error handling should be set to “Stop For Errors” on any batch where the output matters.

Droplets Are the Part Most People Skip

Once your Action set is tested and stable, convert it to a Droplet. File > Automate > Create Droplet outputs a small executable that you can park on your desktop or share with a team member. Drag a folder onto the Droplet and the whole batch runs without you opening the Batch dialog at all.

The less obvious benefit of Droplets is documentation. A Droplet encodes exactly which Action set, which source and destination settings, and which file naming convention you used. When a client comes back six months later and needs 200 more images processed to match the original batch, you are not trying to remember your settings. You drag the folder. You get consistent results.

The single most valuable thing I can tell you about Photoshop batch automation is this: the time you spend building a reliable, modular Action set is not setup time, it is every future hour of that task back in your pocket.