How do I prevent a Photoshop batch from overwriting product exports with duplicate filenames?

Set the batch’s naming pattern

In Photoshop’s Batch processing options, choose the Action and Source for the job, then set File Naming so it includes at least one unique element. The documented reason is to avoid overwriting files when names would otherwise repeat. A naming pattern that merely preserves the same base name for every input does not meet that requirement.

Treat uniqueness as a batch-level safeguard, not as proof that each export depicts the right SKU or product view. The documented naming control addresses filename collisions; it does not validate image content.

1. Work from copies of the approved source images and direct the batch to a separate output folder.
2. Build File Naming with at least one unique element. Choose a pattern whose resulting names can be distinguished when two inputs have the same base filename.
3. Before processing the full set, prepare two test copies that would otherwise resolve to the same output name.

Illustrative exercise: test a collision

Illustrative exercise, not a completed Photoshop test: imagine two product images in separate source folders, both named “front.jpg,” but showing different items. First consider a pattern that uses only the original filename: both inputs could resolve to “front.jpg,” so the naming pattern has not demonstrated collision resistance. Next, add a unique element to the File Naming pattern and process only the two test copies to a separate destination.

Inspect the destination after processing. Pass only if both outputs exist as separate files with distinguishable names and neither test input has replaced the other. If there is still only one output, or the names remain indistinguishable, stop; revise the pattern and repeat the small collision test before expanding the batch.

1. Record the two inputs and the names you expect from the revised pattern before running the test.
2. After processing, compare the actual filenames and count the outputs. Do not infer success from the batch completing without an error.
3. Release the wider batch only when the two-input test passes and the output folder is the intended destination.

Keep source and destination behavior separate

Photoshop’s Batch options let you select a source such as a folder, imported files, opened files, or Bridge. Include All Subfolders expands the input scope, so use it only when nested folders are meant to be included. The Override Action Open Commands option prevents a recorded Open command from replacing selected source files, although some actions deliberately require fixed files. If the action depends on such a file, assess that dependency before overriding it.

For output, Destination None leaves files open unless the action saves them; Save and Close overwrites originals; Folder sends output to a selected folder. For a controlled product export, a separate destination folder helps preserve the approved inputs while you inspect results. If the action contains a recorded Save As folder, Override Action Save As Commands makes the chosen batch destination take precedence over that recorded folder.

1. Confirm the selected source contains only the intended test copies; avoid Include All Subfolders unless those nested inputs are part of the job.
2. Choose Folder as the destination for the test output. Do not use Save and Close for this collision check because it overwrites originals.
3. If the action has recorded Open or Save As commands, decide whether the corresponding override is appropriate for that action before processing.

Release only after the observable check

A successful batch run is not the acceptance condition: the naming test must produce separate, distinguishable outputs for the two same-base-name inputs. If that condition fails, stop and adjust File Naming rather than running the full set. Once the test passes, use the verified pattern and destination for the production batch, then inspect the output names as part of release.

Photoshop can be configured to stop on errors or log errors to a file. Those choices concern processing errors; they do not establish that filenames are unique or that an export represents the intended SKU. Keep collision checking as a separate manual acceptance step. Do not suppress color-profile warnings as a default remedy for a naming problem.

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