
Use ExifTool's -struct option with JSON when auditing XMP face regions. It retains nested structures, so each region's name, type and area can remain together in the exported record. A list of flattened names beside a separate list of coordinates is a weaker handoff because the reader may lose which properties belong to which region.
Request the actual region structure
For a local image containing MWG region metadata, read:
exiftool -j -struct -XMP-mwg-rs:all sample.jpg
This request reads metadata; it does not assign or recognize a face. Save the text as JSON through an appropriate text-output route if a file is needed.
ExifTool's Structured Information documentation describes nested extraction. Its MWG tag reference identifies the XMP-mwg-rs group, RegionInfo, AppliedToDimensions and the RegionList entries.
A result without this group is not proof that the image contains no region metadata of any kind. Another application may use a different namespace. Record what this query found, then inspect the actual application and relevant tag reference before broadening the claim.
Validate associations, not just names
Within a returned region entry, inspect Name, Type and its own Area. Check the area's units as well as its numbers. Keep AppliedToDimensions with the region set instead of replacing it with whatever dimensions happen to be convenient for a spreadsheet.
For a hypothetical two-person image, verify two separate entries rather than accepting two names and two coordinate strings somewhere in the file. A name is not independently proof of identity, and region metadata is not a consent record.
The structured-information reference distinguishes nested structures from flattened properties. For this audit, keeping each region object intact makes its name-to-area association explicit; no compatibility test with a current Lightroom release is claimed.
Preserve the source image's geometry context
If a crop, rotation or resize happened after the regions were authored, do not assume their coordinates automatically describe the new pixels. This audit exports what is stored; it does not recalculate the geometry.
Have the receiving application display the regions against the exact associated image where possible. The proposed acceptance is that each intended name stays attached to its recorded area and the receiver's interpretation is checked. If the receiving tool cannot read the schema, deliver the JSON as an audit record and mark interactive region support as unverified.
Choose the handoff scope
The JSON may contain personal names and location-like image coordinates. Share only the scope authorized for the recipient. Keeping structures intact is useful for data integrity; it does not itself justify public release.
A RAW-and-sidecar editing package serves a broader editing purpose and may contain other application data. Keep this narrow region audit clearly named so it is not mistaken for a complete editable project.
If the catalog disagrees with the embedded file, resolve the metadata authority before writing anything back. A read-only structured report is the evidence to examine, not an automatic instruction to replace the source metadata.
Related tasks
- Why Does My RAW Photo Lose Its Edits on Another Computer?
- Lightroom Metadata Conflict: Keep the Disk or Catalog Version?
Sources and scope
- Structured Information: The -struct option keeps XMP structures together; structured JSON is different from separate flattened properties.
- MWG Tags: XMP-mwg-rs RegionInfo associates AppliedToDimensions with RegionList entries containing Area, Name and Type.
Documentation-based guidance researched on 23 October 2026 (Asia/Shanghai). The linked official ExifTool technical pages were retrieved with HTTP 200 and their relevant text was checked. Commands and acceptance procedures are proposed examples, not reported hands-on tests. 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: Rumeyda Tutak / Pexels, Pexels License. This is an illustrative source photograph, not an application screenshot or a generated test result.