PNG HDR metadata belongs in the image transformation contract
PNG’s third edition makes HDR color meaning explicit. Preserve valid metadata through transformations or define an intentional SDR conversion and its limits.
By 
Paul. Architecture and infrastructure
An image transformation is correct when its output preserves the meaning the product promised, or performs an explicitly agreed conversion. Smaller bytes cannot establish that correctness. With HDR images, the interpretation of pixel values depends on color information that an otherwise successful resize or export can discard. The product needs to decide what its image pipeline preserves before choosing an optimization target.
This November 2026 retrospective concerns the PNG third-edition Recommendation of 24 June 2025. The earlier pinned explainer revision already discussed HDR while the edition was under development. Its commit was authored on 24 February and committed on 26 February 2025. That earlier explanation is background, not evidence that the Recommendation existed before June.
The numbers need an interpretation
A pixel’s numeric channels do not independently describe the intended light and color. A consumer needs the associated interpretation. The third edition defines cICP for color primaries, transfer function, matrix coefficients and range signaling. It also specifies mDCV mastering-display information and cLLI content-light information. These serve related but distinct purposes; treating every color chunk as interchangeable loses that distinction.
The Recommendation gives cICP the highest precedence among color chunks when the decoder understands it. It requires accompanying cICP when mDCV is used. Those relationships matter when a processor carries metadata forward: retaining an isolated piece while dropping its required context is not preservation of the same description. A file can remain parseable while no longer expressing the intended rendering contract.
That is a format-level observation. It does not prove identical appearance on every display, operating system or browser. Rendering also depends on the capabilities and behavior of the receiving software and hardware. A product promise should identify its supported destinations instead of presenting an HDR format label as a universal visual guarantee.
Follow one image through the product
Consider a proposed upload service that retains an original, generates a thumbnail and offers an export. These are illustrative product choices, not an AL+ image experiment. Each output has a separate purpose. The original may support later editing; the thumbnail may prioritize broad viewing; the export may be intended for another color-aware tool.
At ingestion, record what the service recognizes and what it promises to retain. “PNG accepted” is too broad if the processor recognizes the container but ignores color signaling. A service can reasonably restrict supported input combinations. It should expose that restriction in the product contract rather than silently accept an image whose meaning it cannot carry through the promised route.
At resizing, the important question is what representation the operation uses and how the resulting metadata describes it. Copying every input chunk without considering transformed pixels is not a universal solution. If a conversion changes the color representation, the old description may no longer apply. Preservation means maintaining valid meaning, which can require updating or removing information for a documented reason.
At export, verify the actual derivative supplied to the recipient. Checking only the retained original misses the artifact people download or embed. A later processing stage can strip information that an earlier stage preserved. Ownership should follow the image across those stages, including any external transformation service selected by the product.
SDR can be the deliberate output
The strongest counterargument is a product whose supported destinations are better served by a consistent standard-dynamic-range result. Keeping HDR throughout may increase implementation and support costs without helping the reader’s task. An explicit SDR conversion can therefore be a better product decision than promising HDR preservation across a pipeline the team cannot validate.
That decision needs a conversion contract. Specify the target color representation and the intended tone-mapping behavior, then ensure metadata describes the converted pixels. Removing HDR signaling while leaving the same sample interpretation unresolved is not equivalent to converting the image. Likewise, preserving an HDR label on an SDR result can misdescribe what the recipient receives.
Retaining the original can preserve future options, where storage and data policy allow it. The derivative can then be deliberately limited without pretending that the limitation never existed. The application should distinguish the original from the converted output so that downstream users do not mistake one for the other.
This argument does not require every upload product to implement every third-edition feature. A narrow, tested SDR route can be useful. An archival or professional imaging product may have stronger preservation obligations. The right boundary follows the use of the image, rather than a general preference for the newest format feature.
Acceptance evidence should match the promise
A proposed acceptance collection should include representative input signaling and the transformations actually offered. Inspect output metadata and evaluate rendering through the supported receiving path. Neither a chunk listing alone nor a visual glance alone covers the whole contract: metadata can be internally inconsistent, while one display can conceal a problem relevant elsewhere.
Include unsupported input and conversion failures in that plan. Decide whether the product rejects the file, retains only the original or supplies a clearly identified derivative. These are proposed verification cases. No images were generated, resized, displayed or benchmarked for this article, and no browser compatibility result is claimed.
In custom software development, give image meaning an owner alongside storage and delivery. Record whether each output preserves the supported color representation or intentionally converts it. Then optimize size and speed inside that boundary. The June Recommendation supplies precise vocabulary for the contract; the product still has to honor it along the complete route.