Why Did My Tethered Capture Overwrite an Earlier Product Photo After the Camera Filename Counter Restarted?

Find where two source identities become one destination path

Start with the capture destination and the original camera files. Record the source camera, card or session, original filename, capture metadata and the exact destination path.

Two different files can both be named IMG_0001.JPG. That does not establish they depict the same product or belong to the same capture session. If an ingest application writes both to one directory using only the original basename, the destination names collide.

Inspect the actual ingest tool's behavior when a destination already exists. It may skip, rename, ask for confirmation or overwrite, depending on its documented settings. Do not infer destructive overwrite solely because one expected image is missing; the second may have been skipped or placed elsewhere.

Keep the camera originals or untouched card copies available while investigating. Do not run a bulk rename against the only remaining source archive.

Create a unique ingest identifier

A useful destination identity combines a session identifier with a capture sequence or other unique ingest token. Preserve the original filename separately so that camera logs and external references remain traceable.

ExifTool's official documentation provides file-renaming and copying facilities, including collision-avoidance numbering through its documented filename formatting. It also warns that some rename operations move files rather than creating copies, so use the documented copy behavior when protecting originals.

Do not rely on capture timestamp alone for uniqueness. Several cameras can record the same second, and a camera clock can be incorrect. A camera model name is also insufficient when two bodies of the same model are used.

Choose a deterministic naming policy and test it on two different files with the same basename. Record the expected destination names before executing the test.

Hypothetical two-session collision

Hypothetical illustration—not an executed file import: a fictional merchant photographs mug M21 during session S-A and lamp L08 during session S-B. Both cameras produce DSC_0001.JPG after a counter reset.

A proposed unsafe ingest path places both files in a common folder as DSC_0001.JPG. The merchant cannot establish which image would remain without inspecting the actual ingest tool's collision behavior.

The proposed safe path uses distinct identities such as S-A_0001.JPG and S-B_0001.JPG, while retaining DSC_0001.JPG as the original source name in the ingest ledger.

The file contents must still be checked. A collision-resistant name prevents one class of overwrite but does not prove that the correct SKU was assigned.

The worksheet describes expected states, not observed software output.

Reconcile the archive before continuing the batch

Compare source counts and destination counts by session. Investigate every skipped, renamed or missing file. A total count matching the expected number is useful but cannot establish that all files are unique or correctly identified.

For suspected overwrites, compare any retained originals, backups and ingest logs. Do not assume that renaming the surviving file reconstructs a missing photograph.

Test the naming policy with RAW/JPEG pairs as well. Related files may legitimately share a basename with different extensions, but they should not be paired across unrelated sessions simply because the names match.

Record the session ID, original filename, destination filename, source hash when available, SKU and capture order. Keep collision handling separate from creative approval and product accuracy.

Close the ingest only when each expected source has a distinct, traceable destination or a documented unresolved exception. Do not continue automated processing on an ambiguous file identity.

Record your own observations

The filled rows are illustrative examples. Use the blank row for your own files and observations.

Download the editable CSV worksheet

What the references establish

• ExifTool — FileName and Directory tags: Documents file renaming, collision numbering and distinctions between copying and moving.
• ExifTool — Application documentation: Provides primary filename-format and output-copy behavior, including avoiding existing-file overwrites.