Last month I took on a product photography job that seemed simple enough: retouch 340 product images for an e-commerce client. Same edits on every single one. Resize to 2000x2000px, sharpen, adjust white balance, export as sRGB JPEG at 85% quality. Clean, repetitive, boring work.

My first instinct was to just… start doing them. One by one. I got through about 40 images in two hours before I wanted to throw my laptop into a lake. There had to be a better way, and there was. Batch processing finished the remaining 300 images in about 11 minutes while I refilled my coffee.

If you’re still manually applying the same edits to multiple files, this is the article that’s going to save your sanity.

Why Photoshop Can’t Just Read Your Mind (But Kind of Can)

Here’s what’s actually happening when you batch process in Photoshop. You record a sequence of steps as an “Action,” which is basically a macro. Photoshop logs every command you execute, down to the specific values, blend modes, and menu selections. When you point that Action at a folder full of files, Photoshop opens each one, runs through the recorded steps at machine speed, saves the result, closes the file, and moves on to the next.

The key thing to understand is that Actions are literal. They don’t interpret, they execute. If you recorded an action that crops to 500x500px from the top-left corner, it will do that to every file, regardless of whether the subject is centered or in the bottom-right. That’s not a flaw, that’s just physics. Knowing this upfront saves you from some genuinely painful mistakes.

Recording Your First Action Without Messing It Up

Open the Actions panel (Window > Actions) and hit the “Create New Action” button at the bottom. It looks like a dog-eared page icon. Name it something useful, like “Product Export 2000px,” not “Action 1.” Click Record, and then work through your edit steps exactly as you want them applied to every file.

For that client job, my recorded steps were: Image > Image Size (2000x2000px, Bicubic Sharper for downsampling), Filter > Sharpen > Unsharp Mask (Amount 85%, Radius 1.0px, Threshold 3), Edit > Convert to Profile (sRGB IEC61966-2.1), then File > Export > Export As, with JPEG quality set to 85. When I was done, I hit the Stop button (the square icon in the Actions panel). Total recording time: about 90 seconds.

One critical tip: before you record, make sure the file you’re working on is representative of your actual batch. If your source files are 16-bit TIFFs and your test file was an 8-bit JPEG, some steps may behave differently or fail outright when run across the batch.

Running the Batch Without Babysitting It

Go to File > Automate > Batch. This is the control room. Set your Action set and the specific Action you recorded. Under Source, choose Folder and point it at your folder of originals. Under Destination, choose Folder again and point it somewhere else, like a subfolder called “Exported.” Do not set the destination to the same folder as your originals unless you enjoy chaos.

Check “Override Action ‘Save As’ Commands” if your Action includes a save step, which it should. This tells Photoshop to use the destination folder you just set rather than saving back to wherever the file originally lived. If you skip this checkbox, Photoshop will ignore your destination folder entirely and save files wherever it feels like. Ask me how I know.

For the naming convention, I use “Document Name” plus a sequence number. That way “product_001.jpg” stays named sensibly instead of becoming “Copy of Copy of final_FINAL_v3.jpg.”

The Time I Learned This Lesson Slightly Too Late

A few years back, before I really committed to learning Actions, I was editing a batch of 80 headshots for a corporate client. Same basic adjustments on each one: exposure, skin tone correction, background cleanup. I did every single one manually over a full afternoon. I think I charged something like $120 for the job.

A friend who does commercial photography watched me finish and just stared at me. She pulled up her setup and showed me an Action she’d built that handled 70% of those corrections automatically, including a frequency separation step she’d recorded months earlier and reused on every skin retouch job. She would have knocked that out in under an hour. I spent four. That’s not a workflow problem, that’s a billing problem.

I rebuilt that Action from scratch the next week and it’s paid for itself more times than I can count.

When Batch Processing Will Let You Down

Batch processing is not magic. It doesn’t handle edge cases, it doesn’t make creative decisions, and it absolutely will not rescue a badly shot photo. If your source images have wildly inconsistent exposure, you’ll get 340 images that are all consistently mediocre instead of just inconsistently bad.

It also struggles with anything that requires spatial awareness. Cropping to a specific subject, removing a background, selecting a face: these still need a human eye, at least until AI tools improve enough to be reliably trustworthy (jury’s still out on that one). Use batch processing for the mechanical, repeatable stuff and save your brain for the decisions that actually require judgment.

The real skill isn’t recording the Action. It’s knowing which part of your workflow is actually repetitive enough to automate, and doing it before you’ve already wasted three hours doing it by hand.