
Setting IPTC:CodedCharacterSet to UTF-8 is not enough to convert legacy IPTC text. The text must be decoded using its actual old encoding and rewritten in UTF-8. Otherwise the declaration changes while the underlying bytes may still describe a different character set.
Identify the IPTC data, not just the visible caption
This guide concerns legacy IPTC IIM fields. Do not assume a correct-looking XMP caption proves that the separate IPTC copy is correct.
Start with a read-only, grouped inspection:
exiftool -a -G1 -s -IPTC:all sample.jpg
Inspect accented names, punctuation and non-English place names. Keep an authoritative spelling outside the photograph. If the intended text is unknown, repeatedly trying encodings until a caption looks plausible is not verification.
ExifTool's character-encoding FAQ explains how CodedCharacterSet and the IPTC charset option affect interpretation. An absent UTF-8 declaration does not reveal which legacy encoding the original application actually used.
Re-encode a copy using a known source interpretation
ExifTool documents this conversion pattern:
exiftool -tagsfromfile @ -iptc:all -codedcharacterset=utf8 sample.jpg
The self-copy rereads IPTC fields and writes them with the UTF-8 declaration. This is a write operation; rehearse on a disposable copy and retain the normal backup. Its interpretation of existing bytes must be correct before the conversion can be correct.
If the documented source is a different legacy encoding, supply the appropriate -charset iptc=... setting from the FAQ during conversion. For example, the FAQ's latin2 example concerns Windows Latin2, not a universal answer for every European or Asian caption. Do not apply that name to unidentified text.
Test a meaningful sample of characters
The proposed acceptance sample should include characters that distinguish the suspected encodings, not only plain ASCII. Compare the rewritten person's name or location against the approved spelling and inspect the charset declaration again.
Read the file through the receiving IPTC-aware application as well. A successful command and a UTF-8 label establish neither that the original bytes were decoded correctly nor that every receiving program uses the same metadata representation.
If the rewritten text contains replacement characters or wrong letters, return to the intact original copy. Re-encoding the already misdecoded result can preserve the mistake rather than recover the original spelling. Resolve the input encoding or transcribe from an authoritative source.
Keep synchronization separate
An application may still display a catalog caption or XMP value while you are checking IPTC. Resolve file-versus-catalog metadata authority deliberately; do not overwrite all representations merely to make two panels agree.
The output of this task is correctly encoded IPTC text with a truthful charset declaration. It is not translation, ownership verification or a RAW development handoff. If editing settings also need to travel, package the RAW companions separately.
Related tasks
- Lightroom Metadata Conflict: Keep the Disk or Catalog Version?
- Why Does My RAW Photo Lose Its Edits on Another Computer?
Sources and scope
- ExifTool FAQ: Grouped duplicate-tag inspection, metadata character encodings, CSV exchange and validation limits are documented; validation is not a general image-repair guarantee.
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: Mak Cézar / Pexels, Pexels License. This is an illustrative source photograph, not an application screenshot or a generated test result.