
To remove only a creator's contact city, target the flattened CreatorCity field rather than assigning a new contact structure containing an empty city. The latter can replace the structure and discard sibling information such as work email or website.
Read the complete contact object
Begin with a structured report:
exiftool -j -struct -XMP-iptcCore:CreatorContactInfo sample.jpg
Identify which field must leave and which authorized fields must remain. This guide concerns CreatorContactInfo, not the city where the image was captured or the location depicted.
The XMP IPTC Core reference maps the serialized CiAdrCity field to the flattened ExifTool name CreatorCity. Similar-looking names are not interchangeable across namespaces.
Delete one field deliberately
On a working copy, the targeted pattern is:
exiftool -XMP-iptcCore:CreatorCity= sample.jpg
Retain normal backups during the trial. The empty assignment deletes this field; it does not mean “replace every contact value with an empty value.”
The Structured Information documentation warns against assigning a structure such as {CiAdrCity=} to accomplish this deletion. That is a new structure assignment, not an in-place request to remove just one member.
Do not copy a contact block from another person's image to restore lost fields. Use the preserved source or authorized contact record.
Compare the siblings after the operation
Read the structured report again. Verify that the city is absent and each intended sibling retains its actual value. For an illustrative contact containing city, email and URL, the desired change is one missing city with the approved email and URL unchanged.
This is a proposed comparison, not an executed edit. If other fields disappear, return to the preserved copy and inspect the assignment used. Do not keep filling fields back into a partially damaged record without confirming its original scope.
A receiving application's display may show only selected contact fields. Use the complete structure to assess retention rather than treating an empty panel as evidence that the entire object vanished.
Keep shared metadata ownership clear
A contact field can be read by more than one application. Shared XMP source metadata illustrates why a field edit should not be assumed private to one project.
When a catalog still holds the old city, resolve catalog-versus-file authority before synchronization. Reimporting the stale catalog value could undo the intended removal.
The deliverable is a narrowly changed contact structure, with retained siblings explicitly checked. It is not a blanket removal of every city field or proof that the image contains no other location information.
Related tasks
- Why Did Editing Premiere Clip Metadata Change What Another Adobe App Shows?
- Lightroom Metadata Conflict: Keep the Disk or Catalog Version?
Sources and scope
- Structured Information: An empty field in a newly assigned structure replaces the structure rather than deleting just that field. Flattened tags can target fields; lists of structures have additional matching and placement rules.
- XMP Tags: IPTC Core and ContactInfo: CreatorCity is the flattened XMP-iptcCore field for CreatorContactInfoCiAdrCity; related sibling names are listed.
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.