Photoshop Batch saves to the wrong folder: check the recorded Save As step

Stop the batch and inspect its saving instructions

Before another attempt, protect the originals and use two disposable copies with clearly different names. Put the next output in an empty folder. This makes accidental overwriting or duplicate output visible before it affects a full project.

Check the action before changing Batch settings

Open Window > Actions, expand the action, and inspect its saving steps. Note any recorded filename or destination. If a supported command needs different settings, Adobe documents editing an action command by double-clicking it and adjusting its dialog.

For a simple action, it can be easier to record a clean replacement using a disposable file than to keep modifying an unfamiliar sequence. Save the original action for reference. Adobe’s recording guide explains how to capture a sequence and stop recording when it is complete.

Match the symptom to the saving rule

In File > Automate > Batch, choose the intended action, source folder, and a separate destination folder. For an action containing a recorded Save As command, Override Action "Save As" Commands uses the Batch location and naming instead of that recorded path. It does not supply a missing Save As command or replace its format-specific settings. See Adobe’s detailed override rules.

Adobe’s Batch guide distinguishes this destination from saving into another folder. During the small check, use names that remain unique; do not assign the same output name to both inputs.

Verify two distinct inputs before scaling up

After the sample, open both results and compare their subjects with their source files. Confirm the destination, file type, filenames, and whether the originals remained unchanged. The correct number of files alone is not enough if the action repeatedly processed one recorded input.

If output is still wrong, write down the actual files created and the expanded action steps before seeking help through Adobe Photoshop Help. Remove confidential filenames from screenshots. This is documentation-based troubleshooting; we have not run the action or tested it against your files.