What happens to Photoshop batch files when Destination is None, Save and Close, or Folder?

Choose the output state

These three options are different release paths, not interchangeable ways to save one batch. Decide what should exist when processing finishes: open documents for review, updated source files, or separate output files.

With None, Batch does not specify an output folder. The processed files remain open unless the action includes a save operation. With Save and Close, the originals are overwritten. With Folder, output goes to a selected destination; Override Action Save As Commands makes that batch destination take precedence over a folder recorded in the action.

Run a contained exercise first

Illustrative exercise: make disposable copies of two product images, one with a light background and one with a dark background. The distinction makes it easier to notice if an action produces an unexpected result. Do not treat this as a completed Photoshop test or a universal specification.

Process the copies using the same action and source selection, changing only the destination between trials. For None, observe whether each document remains open and whether the action saved it. For Save and Close, compare the resulting source copies with their starting state. For Folder, confirm that output files appear in the chosen folder and that the source copies remain unchanged.

Pass only when the observed file state matches the intended release path for both inputs. If one output is missing, lands somewhere unexpected, or changes an input you meant to preserve, stop before using production files and investigate the action's save behavior.

1. Keep the approved originals untouched; create disposable copies for the exercise.
2. Use the same action and source selection for each trial, changing only Destination.
3. Record whether files remain open, whether source copies change, and where output files appear.
4. Proceed only after both inputs meet the intended result; otherwise stop and revise the destination or action.

Resolve action and naming conflicts

An action may contain a Save As command pointing to an older folder. When Folder is the intended destination, enable Override Action Save As Commands so the chosen batch destination takes precedence. Then verify where the files actually appear; the setting is not a substitute for checking the result.

File Naming must include at least one unique element to avoid overwriting files. If distinct inputs produce colliding names, do not run the production batch until the naming scheme distinguishes them. Keep the approved source set intact while correcting the test setup.

Keep the batch scope and review separate

Batch source selection determines which files are processed: Folder, Import, Opened Files, or Bridge. Include All Subfolders expands the input scope, so use it only when nested files belong in the run. This is separate from Destination: selecting the right output path does not prove that the input set was correct.

Errors can be set to Stop for Errors or Log Errors to File. Stopping on an error can halt processing, but it does not validate product identity, layers, or visual quality. Treat error handling as a processing control, then review the actual outputs.

1. Confirm the intended inputs before starting; include subfolders only if they are part of the job.
2. After processing, compare output count and filenames with the intended input set.
3. Open representative results and inspect the image content and required layers or other job-specific details.
4. If an error occurred or an output fails review, hold the batch and diagnose it; do not assume that a completed or stopped run passed visual review.

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 destination check (CSV)