
Use ExifTool's result-category filename logs when a metadata batch needs a precise retry set. A total such as “90 updated, 10 unchanged” does not identify failed files, and an unchanged result is not automatically an error.
Define what each result means for the batch
Before writing, record the explicit input set and intended field changes. A file may already contain the approved value. That unchanged result should not be mixed with a file that could not be opened or written.
The ExifTool application documentation defines -efile result categories, including errors, unchanged and updated files. It also specifies that existing log files are appended to unless the overwrite form is selected.
Use fresh, run-specific log paths for a rehearsal. Appending to last week's error list without noticing can make an old failure look like part of today's run.
Produce separate result sets
This is an illustrative write request for two disposable copies:
exiftool -efile run-errors.txt -efile2 run-unchanged.txt -efile8 run-updated.txt -XMP-xmp:Rating=3 copies/a.jpg copies/b.jpg
The rating is merely an example authorized trial value, not a recommended rating for real photographs. Preserve originals and inspect the normal output as well as the filename lists.
Keep the category numbers with the command record. An updated file belongs in the updated set; that does not by itself prove the new field meets the receiving application's needs.
Reconcile before retrying
For each reported error, retain the actual diagnostic and address its cause. An unavailable path, unsupported write target and access failure need different responses. Repeating the identical write does not fix the cause by virtue of being a retry.
For unchanged files, inspect whether the required value was already present or whether another condition explains the outcome. Do not force an arbitrary change merely to move a filename into the updated list.
For updated files, read back the target field on a representative sample and every exceptional item relevant to the handoff. Catalog-versus-file metadata can still disagree even after a successful file write.
Build a justified retry selection
The error list supplies identities for investigation, not an instruction to open every path unreviewed through a shell. Keep path handling as data in the calling workflow and retain the original input manifest.
If the original operation changed, give the retry a new run identifier. Do not merge its logs into the first run and then lose which settings produced which result.
For a separate batch policy, shared-setting allowlists help determine which changes belong on every input.
No metadata batch was executed here. The proposed acceptance artifact is the reconciled input set, category-specific lists, diagnostic causes and a scoped retry set. Aggregate success counts alone cannot provide that record.
Related tasks
- Lightroom Metadata Conflict: Keep the Disk or Catalog Version?
- Which Photo Edits Should I Copy to a Whole Set, and Which Should Stay Individual?
Sources and scope
- ExifTool Application Documentation: Documents numbered ready markers, categorized filename logs, Unicode filename argument handling, in-place write behavior and signed coordinate output. Read the exact option section before drafting each operational recipe.
Official-documentation synthesis researched on 23 October 2026 (Asia/Shanghai). Public search returned readable official deep-page body text; direct ExifTool application and PDF/XMP reference fetches encountered HTTP 403. No command, image edit, GPS matching, protocol integration or filesystem-attribute test was executed. All sample paths, dates, values and acceptance exercises are illustrative. Source-defined boundaries and installed-version/file-format limitations remain part of the procedure.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: Mak Cézar / Pexels, Pexels License. This is an illustrative source photograph, not an application screenshot or a generated test result.