Why does Photoshop batch processing save product images into the action’s old folder instead of the chosen destination?

What Is Being Overridden

A Photoshop action can contain a Save As command with a folder recorded when the action was created. During batch processing, that recorded command can direct files to its old location. The batch’s selected destination and the action’s recorded Save As folder are therefore separate controls.

Enable Override Action Save As Commands when the selected batch destination must win. This is the corrective mechanism for the specific old-folder problem. It is different from Override Action Open Commands, which concerns the files an action opens and whether those recorded Open commands replace the batch’s selected source files.

This guide applies to Photoshop batch and droplet processing options described by Adobe. It is not a Lightroom Classic, Lightroom desktop, web, or mobile workflow. Do not infer that the same override exists in those applications.

Illustrative Exercise

Illustrative exercise: preserve the approved action and work with a disposable copy of two distinguishable product images: `red-mug-front` and `blue-mug-side`. Assume the action contains a recorded Save As location named `Old-Exports`. Choose a separate test destination named `Batch-Test-Destination`, then process only the copies.

First run the batch with the recorded Save As command still controlling the output. The observation to record is the actual folder containing each generated file. Do not treat a completed Photoshop run as proof of the destination; inspect the files.

Repeat the disposable run with Override Action Save As Commands enabled and the same chosen batch destination. Pass means the generated files are found in `Batch-Test-Destination`, with filenames that do not overwrite one another. Fail means either file is written to `Old-Exports` or another unexpected location. If the pass condition is not met, stop before processing the approved originals and investigate the selected destination, action, and batch options.

1. Keep the original action, source images, and cataloged production files unchanged; use copies for the exercise.
2. Record the old folder named by the action and the separate destination chosen for the batch.
3. Compare the observed file paths after each run, rather than relying on the destination label alone.

Configure The Batch

Select the intended Action and choose the source type that contains the disposable copies. Photoshop supports Folder, Import, Opened Files, and Bridge as batch sources. If the source is a Folder, Include All Subfolders expands the input scope, so leave that scope decision intentional.

Choose Folder as the destination when the processed files should go to a different destination. Then enable Override Action Save As Commands so that this selected destination takes precedence over the action’s recorded Save As folder.

File Naming must include at least one unique element to avoid overwriting files. The override does not perform SKU validation, layer validation, or semantic checking, so a successful run only proves that Photoshop processed files and wrote output according to the configured controls.

1. Choose the action and source containing the test copies.
2. Choose Folder for the destination when a separate output location is required.
3. Enable Override Action Save As Commands.
4. Set File Naming with at least one unique element.
5. Choose whether errors should stop processing or be logged to a file.

Separate Similar Behaviors

Destination None is not a destination override: it leaves files open unless the action saves them. Save and Close overwrites the originals. Folder selects a different destination, and Override Action Save As Commands makes that selected destination take precedence over a recorded Save As folder.

Override Action Open Commands addresses a different branch. It prevents a recorded Open command from replacing the files selected as the batch source, although some actions deliberately require fixed files. If the wrong product files are being opened, investigate that control instead of changing Save As behavior.

For the old-folder symptom, the acceptance check remains path-based: locate the produced files and confirm they are in the chosen destination. Error handling can stop the job or create a log, but stopping is not proof that product content, SKU identity, or layers are correct.

Production Acceptance

After the disposable run passes, apply the same configuration to a controlled production subset before processing the full source. Verify that every expected output is physically present in the selected destination and that the filenames contain a unique element. Also confirm that the source scope did not unintentionally include subfolders.

If the files still appear in the old folder, stop. Recheck whether the batch is actually using Folder as its destination, whether Override Action Save As Commands is enabled for that run, and whether the action contains another save-related behavior. Do not delete the catalog, remove the action, disable security, or mass-replace production files as a default response.

Use this question’s review worksheet

The sample rows are fictional exercise data. Preserve the example, save a working copy and record your own inputs, observations and decisions. The example is not a test receipt.

Fictional manual batch-path worksheet (CSV)