
ExifTool does not treat a metadata CSV as a list of files to open. Its SourceFile column identifies the row for each input, while the command line supplies the files to process. If the CSV has 200 rows but you pass one JPEG, the other rows are not a request to find and edit 199 more files.
Draw the two sets before changing the spreadsheet
Imagine an archive with two authorized working copies, samples/a.jpg and samples/b.jpg. A CSV exported from a different folder may still identify originals/a.jpg. The basename looks familiar, but that is not a reliable identity match.
Create a two-column note: actual command input and matching SourceFile value. Check paths as well as extensions. A row for a RAW file is not automatically a row for its rendered JPEG. The ExifTool application documentation describes this row-lookup behavior and says extra CSV rows are ignored.
For a controlled rehearsal, work in a small folder containing only copies intended for the exercise. Start by generating the CSV from those exact files:
exiftool -csv -XMP-dc:Title samples/a.jpg samples/b.jpg
Save the displayed text as a UTF-8 CSV using a text-preserving editor or your shell's documented text-output method. Keep the header and SourceFile identities. In a spreadsheet, avoid automatic date conversion or removal of leading zeros from descriptive fields.
Import into explicit inputs
After editing authorized title values, the corresponding import is:
exiftool -csv=edited.csv samples/a.jpg samples/b.jpg
This is a write operation. Keep ExifTool's normal backup behavior and read its messages. Do not add overwrite flags just to remove clutter during the first trial.
The writable column must be an ExifTool tag name. A human heading such as “Approved exhibition label” does not become a metadata field by being placed in the first row. Also, changing FileName or Directory in this CSV is not a rename workflow; those columns are ignored on import.
Blank cells need a separate decision
An empty cell normally leaves an existing value unchanged. Do not mark an old caption as removed merely because the spreadsheet cell is now blank. ExifTool documents explicit deletion behavior involving -f and a deletion marker; adopt that only after reviewing the complete import policy. A mixture of “leave untouched” and “delete” needs intentional representation, not a spreadsheet-wide find-and-replace.
For catalog users, check whether the application is still displaying its stored value rather than the changed file. Catalog-versus-disk conflicts are a later synchronization decision, distinct from CSV identity.
Accept the mapping, not the row count
Read both sample files again with exiftool -G1 -s -XMP-dc:Title followed by their paths. Compare the actual values to the intended rows. Include an unchanged control file when testing a partial import.
If no row matched, repair identity first. If the row matched but a field stayed unchanged, inspect the header, writability and blank-cell policy. If the wrong file changed, stop before widening the input set. A spreadsheet with the right number of rows proves none of these conditions.
When delivering RAW companions, keep the file-and-sidecar package separate from this CSV worksheet; a metadata exchange table is not a rendered appearance or a complete editing project.
Related tasks
- Lightroom Metadata Conflict: Keep the Disk or Catalog Version?
- Why Does My RAW Photo Lose Its Edits on Another Computer?
Sources and scope
- ExifTool FAQ: Grouped duplicate-tag inspection, metadata character encodings, CSV exchange and validation limits are documented; validation is not a general image-repair guarantee.
- ExifTool Application Documentation: CSV identity uses SourceFile; list separators and append differ from scalar strings. The -o, -if, -b, -w, -struct and backup utility options have explicit scopes.
Documentation-based guidance researched on 23 October 2026 (Asia/Shanghai). Commands and acceptance procedures are proposed examples, not reported hands-on tests. Official ExifTool documentation was readable through search-indexed page text; a direct application-documentation fetch returned HTTP 403. Historical official-forum examples, where cited, demonstrate specific questions rather than current demand frequency. ExifTool version and file-format support must be checked on the receiving system.
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: Pignatta / Pixabay, Pixabay Content License. This is an illustrative source photograph, not an application screenshot or a generated test result.