There’s a specific kind of misery that comes from doing the same Photoshop crop 200 times in a single day. I know because I lived it. Early in my career, before I understood what Photoshop could actually do for me, I sat in a studio chair for eight hours resizing product images one at a time, clicking File > Export, typing a filename, clicking Save, and doing it again. By image 140, I had started making errors. By image 180, I was questioning my career. By the end, I had wasted an entire working day on something a properly configured batch process could have handled in eleven minutes.

That day is the reason I learned scripting. It is also the reason I have never manually repeated a task since.

What Batch Processing Actually Does Inside Photoshop

Most people treat Photoshop’s Batch function like a mystery box. They record an action, point the Batch dialog at a folder, click OK, and hope for the best. When something breaks, they have no idea why, because they never understood what was happening under the hood.

Here is the short version: when you run File > Automate > Batch, Photoshop opens each file in your source folder, runs your selected action against it as if you were clicking every step yourself in real time, then saves or closes the file depending on your export settings. The critical detail is that Photoshop is not preprocessing or queuing. It is executing sequentially, in memory, one file at a time. That matters for two reasons. First, any step in your action that opens a dialog box and waits for user input will stall the entire batch. Second, memory management becomes a real issue with large files if you do not set a file-close step at the end of every action.

The “Override Action ‘Open’ Commands” checkbox in the Batch dialog is one of the most misunderstood settings in Photoshop. Check it, and Photoshop ignores any Open command embedded in your action and uses the source folder instead. Leave it unchecked with an Open step in your action, and you will get a dialog prompt for every single file. I have watched freelancers sit there clicking through 300 prompts because nobody explained this to them.

The Folder Structure That Makes or Breaks Your Pipeline

Before you touch a single action, the folder setup determines whether your batch runs cleanly or creates chaos. I use a four-folder system for every client job: Source, Processing, Output, and Archive. Source is untouched originals, always. Processing is a working copy Photoshop can write into without risk. Output is where the final exports land, organized by format. Archive is a compressed backup of Source that gets copied to a second drive before I start anything.

For e-commerce clients, Output typically splits into subfolders by spec: 2000x2000 at 300dpi for print, 800x800 at 72dpi for web thumbnails, and a layered PSD folder if the client needs editable files. Naming conventions in the Batch export settings use the original filename plus a suffix, so a file called SKU_04821.jpg becomes SKU_04821_web.jpg and SKU_04821_print.jpg without any manual renaming.

Setting this up takes about 20 minutes the first time. After that it is a folder template I duplicate for every new job. Boring? Absolutely. But boring is the point.

Recording Actions That Don’t Break on New Files

The action recording step is where most batch automation falls apart. The problem is usually absolute values. If you record a crop by dragging to specific pixel coordinates on a 3000x4000 image, that crop will execute incorrectly on a 2500x3500 image. Photoshop will attempt the same pixel coordinates regardless of the new file’s dimensions.

The fix is to build actions around relative or conditional operations wherever possible. Use Image > Canvas Size with percentage-based values rather than fixed pixels when you need to add whitespace. Use Image > Image Size with “Resample” checked and Constrain Proportions on, specifying the long edge dimension rather than both width and height. For sharpening, use a Smart Sharpen step with values that work across a range of resolutions. I use Amount: 85%, Radius: 0.8px, Reduce Noise: 10% as a safe default for product photography.

One more thing: always end every action with a File > Close step that saves changes. Without it, Photoshop holds every processed file open in memory until the batch finishes, and on a 500-file job with 50MB TIFFs, that is how you crash a session halfway through.

The Afternoon That Convinced a Whole Agency

A few years ago, an ad agency came to me in a real bind. Their e-commerce client had a product launch in three days, and they had 500 lifestyle product images that needed background removal, color correction to match a brand standard, resizing to four different specs, and export to both JPEG and PNG. Their internal team had estimated four days of work.

I spent a weekend building and testing a batch system specific to that image set. Monday afternoon I ran it. By 4:30 PM, all 500 images were processed, named, and sorted into the correct output folders. The agency account manager asked me to run it again because she assumed something had gone wrong. Nothing had gone wrong. That job is currently sitting in my spreadsheet at 31.5 hours of estimated manual labor replaced by 3.5 hours of setup and execution.

The Setting Most People Never Change

Inside Edit > Preferences > Performance, there is a “History & Cache” section with a “Cache Levels” setting. The default is 4. For batch processing large files, I set this to 2. Lower cache levels reduce the memory overhead Photoshop keeps per file, which means faster processing and fewer crashes on long batch runs. It is not a dramatic change, but on a 300-file run of 80MB layered PSD files, it is the difference between a clean finish and a session that falls over at file 247.

The whole philosophy behind batch automation is that your creative decisions should happen once, at the design stage, and your computer should execute them as many times as needed without your involvement. Every hour you spend building a reliable action is an hour you stop paying for, on every job, forever.