
A tag disappearing after you load ExifTool's MWG module does not by itself mean the file lost that tag. MWG applies a reconciliation policy and strict location rules when reading. Compare an ordinary physical-field report with the MWG view before making a write.
Capture the ordinary report first
Read the unchanged file without loading MWG:
exiftool -a -G1 -s sample.jpg
Preserve that report with the file identity and ExifTool version. Group qualifiers help distinguish a value's physical metadata location from a policy-derived field with a familiar name.
Then request the MWG view:
exiftool -use MWG -a -G1 -s -MWG:all -Warning sample.jpg
Neither request assigns a value. A changed report is therefore not evidence of a metadata write.
Understand why the read set changes
The MWG tag reference documents derived Composite values based on underlying metadata and strict conformance that ignores nonstandard EXIF, IPTC or XMP locations. It describes a warning when such information is encountered.
An ordinary report might expose data that the strict interpretation intentionally excludes. Conversely, an MWG Description can reconcile underlying fields rather than simply repeat whichever physical tag happened to appear first.
Do not remove the warning before recording the excluded location. Disabling strict behavior just to make the output look familiar can hide the policy distinction you are trying to understand.
Compare a field's evidence chain
Choose one disputed value and record:
- Where the ordinary report found it.
- Whether the MWG view reports a derived value.
- Whether a nonstandard-location warning explains a difference.
- Which application's interpretation the delivery actually requires.
These are proposed audit entries, not findings from a tested image. A standard-location preference does not establish that a caption's wording is factually correct.
If several stored descriptions disagree, retain them long enough to decide authority. A read policy cannot determine which photographer or editor supplied the approved text.
Do not turn a read experiment into synchronization
MWG also has write behavior, but adding assignments is a separate operation affecting associated fields. Do not combine the diagnostic comparison with a blanket metadata rewrite.
Catalog-versus-disk conflict resolution asks which state should win; the present task first explains why the same unchanged file yields different policy views.
For shared-source XMP fields, retain the application's own scope decision as well. A source description and an edit-specific note may legitimately have different owners.
Accept the investigation when the difference can be traced to stored location or documented derivation and any unresolved source authority remains explicit. “MWG did not show it” is a reading observation, not proof that the file contains no such information.
Related tasks
- Lightroom Metadata Conflict: Keep the Disk or Catalog Version?
- Why Did Editing Premiere Clip Metadata Change What Another Adobe App Shows?
Sources and scope
- MWG Tags: Loading MWG changes reconciliation behavior and ignores non-standard metadata locations under strict conformance. Composite fields use underlying EXIF/IPTC/XMP and digest inputs; a policy-derived value is distinct from a raw field audit.
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: William Liu / Pexels, Pexels License. This is an illustrative source photograph, not an application screenshot or a generated test result.