Last spring I landed a product photography gig for a small Austin-based skincare brand. Forty-seven product shots, all needing the same treatment: resize to 2000x2000px, sharpen, color-correct to match their brand palette, export as sRGB JPEG at 85% quality. Simple enough. I sat down at my usual corner table at Epoch Coffee, ordered an oat latte, and started editing. Manually. One. At. A. Time.

Four hours later I had gotten through eleven images, my coffee was cold, and I had developed a genuine, personal grievance against the number 47. There had to be a better way. There was. I had just been too stubborn to learn it.

What Batch Processing Actually Does (And Why It’s Not Magic)

Batch processing in Photoshop is the process of applying a recorded Action to a folder full of files automatically, without you clicking through each one yourself. That’s really it. No AI, no mystery. Photoshop reads your Action like a script, opens each file, runs the steps in order, saves the output, and moves on.

The reason people avoid it is that it sounds more technical than it is. “Actions” and “batch automation” feel like developer territory, not designer territory. But the underlying mechanic is just a macro recorder. If you can edit one photo, you can batch process a thousand.

The catch is that batch processing only works well when your inputs are consistent. If you’re working with files of wildly different dimensions, color profiles, or exposure levels, the same Action will produce wildly different results. Garbage in, garbage out. This is why batch processing rewards you most on repetitive, structured work: e-commerce product shots, social media resizing, client deliverable exports.

Recording an Action Worth Using

Open the Actions panel (Window > Actions) and create a new Action set, then a new Action inside it. Name it something specific, not “Action 1.” I use names like “Client-Resize-2000px-sRGB” so that six months later I know exactly what it does without opening it.

Hit Record, then perform every edit step you want repeated. For a typical e-commerce workflow that looks like: Image > Mode > Convert to Profile (sRGB IEC61966-2.1), Image > Image Size (2000px on the long edge, Bicubic Sharper for downscaling), Filter > Sharpen > Unsharp Mask (Amount 85%, Radius 1.0px, Threshold 3), then File > Export > Export As (JPEG, quality 85). Stop recording.

A few things that will save you pain later: do not record the Save step as a regular Save. Use Export As or Save As and point it to a dedicated output folder. Batch processing with a plain Save will overwrite your originals if you’re not careful, and I have absolutely watched a fellow freelancer do exactly that on a rush deadline.

Running the Batch

Go to File > Automate > Batch. Select your Action set and the specific Action. Under Source, choose Folder and point it at your raw files. Under Destination, choose Folder again and point it somewhere different. Check “Override Action ‘Save As’ Commands” if your Action includes an export step. This tells Photoshop to ignore the hardcoded file path you recorded and use the destination folder instead.

Hit OK and go do something else. Seriously. Make another coffee. For my 47-product-shot job, Photoshop processed the entire folder in about 14 minutes on my M1 MacBook Air. Those same 47 files had already cost me four hours of manual work before I wised up. The math does not flatter me.

The Droplet Shortcut Nobody Talks About

If you run the same batch workflow more than a few times, turn your Action into a Droplet. Go to File > Automate > Create Droplet. Choose your Action, set your destination folder, save the Droplet as a small executable file on your desktop. From then on, you drag a folder of images onto that icon and it runs the whole batch automatically, no menus required.

I have a Droplet on my desktop called “web-export.exe” that resizes and exports images for client websites. It has probably saved me six or seven hours a month for the past two years. That is not a number I made up to sound impressive. I actually sat down and calculated it after a client asked why my turnaround time was faster than other designers they’d worked with. The Droplet was most of the answer.

When Batch Processing Breaks Down

Batch processing assumes every file needs identical treatment. When that assumption is wrong, the results will show it.

I learned this on a portrait retouching job. I recorded an Action that included a Curves adjustment I’d dialed in for one particular image, then ran it across 30 portraits shot under mixed lighting. Half of them came out looking like they’d been color-graded by someone who hated faces. The problem wasn’t the batch process itself. The problem was that I’d baked a correction meant for one specific image into a universal workflow.

The fix is to keep your Actions as non-destructive and universal as possible. Resize, sharpen, profile conversions, file format exports: these are safe to batch. Exposure corrections, color grading, anything that was tuned to a specific image: these need to stay manual, or at least need to be revisited per-image using Conditional Actions (which is a whole other conversation).

The single most valuable thing about batch processing is not the time it saves on any one job. It is the discipline it forces you to develop around consistent shooting and file preparation, because the more consistent your inputs are, the harder your automations can work for you.