
If ExifTool reads a PNG caption that another application ignores, inspect the text chunk's location before recreating metadata. PNG permits text after the image-data chunk, but some readers do not handle that placement. Presence in one parser and visibility in another are different observations.
Identify the actual field and source file
Read the relevant metadata from the exact delivery PNG:
exiftool -a -G1 -s -XMP-dc:Description -IPTC:Caption-Abstract sample.png
Record which representation exists. An application might display a different field, or still show a cached catalog value. Do not assume chunk placement is the cause merely because the symptom resembles a documented case.
The ExifTool PNG reference describes reader limitations for text after IDAT and ExifTool's documented practice of writing text chunks before it.
Inspect the file layout
Use a verbose read when examining the chunk sequence:
exiftool -v sample.png
Locate the relevant text or XMP entry relative to IDAT. Retain the report for the actual candidate file. The purpose is determining a storage-layout condition, not changing the visible PNG pixels.
If the desired field is absent even in ExifTool, investigate metadata creation or the source copy first. Moving a nonexistent chunk cannot restore a caption.
Rehearse a documented text write
When placement is the supported diagnosis, work on a copy with the approved text retained in your notes. For example:
exiftool -XMP-dc:Description="Existing approved description" sample.png
Replace the illustrative text with the exact intended description. ExifTool's reference explains that supported text writes place new text before IDAT and move existing text there in the documented versions.
Do not treat this sample assignment as permission to replace every caption in a collection. Inspect the saved candidate's relevant values and layout again.
Reopen through the receiving reader
Have the actual receiving application open the new file from its destination. Check both metadata visibility and retained image appearance. A cached display or a different source revision can otherwise hide whether the storage-layout change mattered.
This task is different from shared XMP ownership: the field can be present and correctly assigned while one reader ignores its location.
If a catalog continues to disagree with disk, resolve its metadata authority separately. Avoid repeated rewrites that change correct values to solve a caching issue.
The proposed result is an interoperable metadata-bearing candidate for the tested reader. No software test or universal PNG-reader compatibility is claimed, and a caption appearing in one application is not evidence that every embedded field survived.
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
- PNG Tags: Some readers ignore text chunks after IDAT even though PNG permits them there. ExifTool writes text before IDAT in the documented versions. It also preserves data after IEND unless explicitly removed.
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: Paparazzi Ratzfatzzi / Pexels, Pexels License. This is an illustrative source photograph, not an application screenshot or a generated test result.