
An ExifTool -@ argument file contains one argument per line, not one complete shell command per line. Shell quotation marks that group a path in a terminal normally do not belong around the same path inside the argument file. This difference explains why a copied command can work interactively but fail from a saved recipe.
Translate the arguments, not the terminal appearance
Consider this read-only shell command:
exiftool -a -G1 -s -sep "||" -XMP-dc:Subject "Working Photos/sample.jpg"
The corresponding inspect.args text is:
-a
-G1
-s
-sep
||
-XMP-dc:Subject
Working Photos/sample.jpg
The || line is the separator value, not another option. Keeping this value free of padding makes the saved argument easy to inspect.
Run the saved file with:
exiftool -@ inspect.args
The option -sep and its value occupy different lines. The path with spaces remains a single argument because the newline supplies the boundary. There is no exiftool program-name line inside the file.
Remove shell syntax
The ExifTool application documentation explains the one-argument rule and the absence of ordinary shell interpretation. Blank lines and comment lines beginning with # may be used for organization.
Do not paste >, pipelines, shell variable assignments or a shell's continuation characters into the recipe expecting them to behave as they do in the terminal. They are not instructions to the shell when ExifTool reads the file. A filename containing spaces should not acquire literal enclosing quotes.
Keep options that have special command-line requirements outside the recipe. In particular, the documentation says -config and -common_args may not be used in an argument file. For a custom configuration, follow the documented invocation order rather than moving it into the recipe for convenience.
Make the first recipe observational
Begin with the read-only metadata query above. Use one existing path and confirm that it reports the intended file and field. If it cannot find the source, inspect the working directory and path spelling before adding any metadata assignments.
If a value appears to become a filename, inspect the preceding option's required arguments. If a path seems to include quotation marks in the error, inspect the saved text rather than repeatedly changing the file's name.
This boundary problem differs from FFmpeg's next-file option scope: ExifTool's recipe first needs the correct argument tokens, while FFmpeg's guide addresses which input or output an already parsed option affects.
Promote a checked recipe into a write workflow
Only after the read-only version addresses the correct input should you introduce authorized metadata writes on copies. Keep a readable diff between the observational recipe and the write recipe so the assignments are visible.
Use a deliberate batch-setting allowlist to decide which changes belong in the reusable recipe. The argument file makes a command reproducible; it does not establish that every file should receive the same value.
Related tasks
- Why Didn’t My FFmpeg Output Options Affect the AI Short I Expected?
- Which Photo Edits Should I Copy to a Whole Set, and Which Should Stay Individual?
Sources and scope
- 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: Mariya Eskina / Pexels, Pexels License. This is an illustrative source photograph, not an application screenshot or a generated test result.