How do I include product files inside source subfolders without accidentally expanding a Photoshop batch too far?

Map the source tree first

Photoshop Batch can take its source from a folder, imported files, opened files, or Bridge. When the source is a folder, Include All Subfolders expands the input scope to include files in nested folders. With the option off, Photoshop does not include those nested-folder files through that recursive setting.

Before choosing the option, write down which folders contain approved products and which contain material that should stay out of the run: for example, rejected shots, alternates, reference images, or unrelated products. This is an editorial safeguard, not a Photoshop validation feature. The option changes discovery scope; it does not decide which files are semantically approved.

1. Identify the exact folder selected as the batch source.
2. Inventory its direct contents and each nested folder that might be included.
3. Decide whether the intended batch includes only files at the selected folder level or files throughout its subfolders.

Illustrative exercise

This illustrative exercise demonstrates the scope decision; it is not a report of a software test. Imagine a test copy of a source tree with two files directly in the selected folder: SKU-Blue-front.jpg and SKU-Blue-back.jpg. A nested folder named Review contains SKU-Blue-retake.jpg and a non-product reference image called lighting-reference.jpg.

First, use Include All Subfolders off and manually record the two expected direct filenames before the fictional run. Afterward, compare the files produced or visibly opened by the batch with that checklist; the expected scope for this exercise is the two direct files. Then, on a separate fictional run, turn Include All Subfolders on and record the expected filenames again, including both files in Review. Compare the resulting files or visible batch outputs with that manually maintained checklist. This demonstrates that the option includes the nested folder, but does not distinguish product files from references.

Branch on that observation: if Review contains only intended product inputs, the expanded scope may be appropriate. If it contains a reference or other excluded material, stop rather than run the production batch with the option on. Refine the source tree or choose a narrower source selection, then compare the manifest again.

1. Use a test copy and preserve the approved originals.
2. Record the expected filenames before each run.
3. Pass condition: the files produced or visibly opened by the fictional run match the manually prepared expected-file checklist in names and intended contents.
4. Stop condition: any unintended file appears, or an expected file is absent.

Keep the selected files from being replaced

Input scope is only one part of a safe batch. An action may contain an Open command that points to a recorded file. Photoshop’s Override Action Open Commands option prevents that recorded Open command from replacing the selected source files. Some actions deliberately need fixed files, so do not enable the override blindly; determine whether the action is supposed to use the batch inputs or a specific file.

Also inspect the destination behavior. None leaves files open unless the action saves them. Save and Close overwrites the originals. Folder sends results to a different destination, and Override Action Save As Commands makes the chosen batch destination take precedence over a recorded Save As folder. If using File Naming, include at least one unique element to avoid overwriting files.

For an initial production run, the editorial recommendation is to use a separate destination and a small, representative input set. Compare output names and content with the intended inputs before expanding the run.

Check errors and approve the result

Photoshop offers Stop for Errors and Log Errors to File. Choose based on whether you need the process to stop at an error or record errors in a file, but do not treat either choice as product-level validation. A batch error setting cannot confirm that the correct SKU, angle, or layer was processed.

After the test run, compare the manually prepared expected-file checklist with the files actually produced, and inspect the output folder for unexpected or missing results. If an unexpected file was included, turn Include All Subfolders off for a direct-folder-only run, or reorganize the test inputs so only intended nested files are in scope. If an expected nested file is missing, confirm that it is under the selected source folder and rerun the test with recursive inclusion enabled.

Proceed only when the input list and outputs agree with the intended product set. Keep the approved originals intact until that check passes.

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.

Illustrative manual source-scope worksheet (CSV)