
A persistent ExifTool process does not exit after each request. Match a numbered -execute request to its corresponding {readyNUMBER} response instead of waiting for process termination or assuming that the last closing JSON bracket ends every response.
Establish a request boundary
The ExifTool application documentation describes persistent reading through -stay_open True -@ -. The final dash uses standard input as the argument stream.
For an integrating application, a proposed launch is:
exiftool -stay_open True -@ -
This is an integration example, not a command run on the user's system. The controller must own the process input and output rather than spawning a new shell for every image.
Frame one read request
Send these argument lines through the process input:
-j
-XMP-dc:Title
sample.jpg
-execute101
Flush the controller's input buffer. Read the response until the matching {ready101} marker. The numeric suffix distinguishes this completion from another request's marker.
Keep normal output and diagnostic handling deliberate. A ready marker means the request finished processing, not that a file was found, a field existed or a write succeeded. Parse and retain the relevant error information separately.
The documentation states that a numbered execute marker remains available even with quiet mode. Do not build a controller around the assumption that every unnumbered quiet request will emit the same completion marker.
Separate protocol failures from metadata failures
If no marker arrives, inspect whether the final execute line and newline were sent and flushed. If the marker arrives with no title, inspect file identity and the reported field rather than restarting the process blindly.
An application should not attach the first response received to whichever thumbnail is selected now. Maintain its own request-to-file mapping and wait for the corresponding identifier.
A batch-setting allowlist remains necessary before introducing write requests. The framing protocol does not authorize every pending asset to receive the same metadata assignment.
Close the stream deliberately
The documented shutdown uses two argument lines:
-stay_open
False
Handle remaining output and normal process exit according to the integration. Do not equate closing the application's preview window with completing every queued request.
This protocol issue differs from FFmpeg option placement: here the controller must first keep requests and responses distinct inside one long-lived process.
The acceptance test is a small sequence of distinguishable read requests whose output, diagnostics and numbered completion markers remain correctly associated. No throughput benchmark or successful integration test is claimed.
Related tasks
- Which Photo Edits Should I Copy to a Whole Set, and Which Should Stay Individual?
- Why Didn’t My FFmpeg Output Options Affect the AI Short I Expected?
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: Rumeyda Tutak / Pexels, Pexels License. This is an illustrative source photograph, not an application screenshot or a generated test result.