The announcement that DNG has been formally adopted as an ISO standard after more than two decades as an Adobe-originated format shifts something that most photographers only half-noticed was unresolved: there was never a neutral, third-party guarantee that a DNG file written today would remain fully interpretable by software that didn’t exist yet. That guarantee now exists, at least in principle. Whether it changes anything for your day-to-day workflow depends on what you’re actually doing with RAW files and where your current setup is already leaning.
For a fuller account of how the standardization came about, our article After Over 20 Years, DNG Becomes the Official RAW Standard covers the announcement itself. What follows here is the format-level question: what does the spec actually lock down, and what does that mean for the files sitting in your archive right now?
What the ISO Standard Actually Specifies
DNG’s structure has always been built on a TIFF/EP foundation — a tiled or stripped container carrying raw sensor data, one or more embedded JPEG previews, and a metadata block that follows the Exif and XMP schemas. What the format added on top of TIFF/EP was a set of Adobe-defined tags for describing how sensor data maps to linear light: the ColorMatrix tags, ForwardMatrix entries, camera calibration illuminant blocks, and the OpcodeList fields that carry lens correction, noise profiles, and similar processing hints.
The ISO standardization fixes the meaning of those tags. A tag’s numeric ID, its data type, its allowed value ranges, and its interpretation are now part of a published, versioned specification that any implementer — a camera maker, a software vendor, an archival system — can implement without negotiating with Adobe. This matters because the historical fragility of proprietary RAW formats is exactly this: Canon’s CR3 or Nikon’s NEF carry their own undocumented sensor linearization math, and when the manufacturer stops publishing decoders, the data becomes opaque. DNG’s spec was always more readable than those formats, but “more readable” is not the same as “formally specified.”
There’s a practical subtlety here: the standard covers what’s in the container and what the metadata fields mean. It doesn’t mandate that every software tool implement every optional feature — OpcodeList lens corrections, for example, are legitimate to skip. So a file that’s valid DNG under the spec is not automatically processed identically by every decoder. Color rendering, tone mapping, and noise handling are still encoder and decoder choices layered on top of the standardized data.
What This Means for Long-Term Archiving
The strongest practical argument for converting proprietary RAW files to DNG was always archival: a format with a documented structure is more likely to be decodable in thirty years than one that depends on reverse engineering. The ISO designation strengthens that argument considerably, because standardization creates an obligation for implementers to document conformance and for the spec to be publicly available independent of any single company’s continuity.
If you have been sitting on proprietary RAW files from older cameras — CR2 files from cameras no longer in production, Olympus ORF files from a discontinued product line, older Fujifilm RAF variants — the calculus for converting them to DNG has shifted. Converting to DNG 1.7 or later (the version that corresponds to the ISO-standardized feature set; check the exact version string in your converter’s release notes) produces files with a public, stable specification. That’s a meaningful difference from a format whose documentation lives on a corporate server that could go offline.
A few things to verify before converting an archive:
- Lossless compression is preserved. Converting with lossless DNG compression retains all original pixel values. The option to use lossy DNG (which applies JPEG 2000 compression to the raw mosaic) exists and produces smaller files, but it is irreversible and discards sensor data. Don’t confuse the two modes.
- Original embedded files. Adobe’s DNG converter can optionally embed the original proprietary RAW file inside the DNG container. This roughly doubles the file size but gives you a fallback. Useful for files from cameras that have manufacturer-specific quirks not fully captured by the DNG metadata.
- Preview quality. DNG containers include a rendered JPEG preview; the size and quality of that preview is set at conversion time. A low-quality preview still yields a valid DNG, but it can cause preview-only applications to show a significantly degraded image — worth specifying explicitly when batch-converting.
The Workflow Impact for Photographers Shooting Today
For photographers already shooting in a format that outputs native DNG — several Leica models, Pentax bodies, some Ricoh hardware — the standard changes nothing operationally. The files your camera produces were already DNG; they’re now DNG covered by an ISO specification.
For everyone else, the practical question is whether to convert at import or keep proprietary RAW files and rely on continued software support. The standard doesn’t force that decision, but it does reduce one historical objection to conversion: the concern that DNG was an Adobe proprietary format dressed up to look open. The ISO process, imperfect as it is for formats with complex optional feature sets, makes that objection harder to sustain.
Lightroom and Camera Raw have supported DNG as a first-class format throughout the format’s history, so the editing workflow for converted files is essentially unchanged. Metadata edits — develop settings, keywords, color labels, star ratings — write directly into the DNG container’s XMP block rather than requiring a separate sidecar file, which is a genuine organizational convenience regardless of standardization status. If you’re already using Lightroom and wondering how this intersects with export decisions, the RAW vs JPEG: Compression Cost in Professional Workflows article is worth reading alongside this one.
What the Standard Doesn’t Resolve
Standardization doesn’t collapse the variation in how different cameras expose the sensor data that ends up inside a DNG. Camera profiles — the ColorMatrix and ForwardMatrix entries — are still written by whoever produces the DNG, whether that’s the camera manufacturer or a converter like Adobe’s. Two different converters can produce technically valid DNG files from the same raw capture that render to noticeably different colors under the same editing software, because their camera profiles encode different assumptions about how the sensor’s spectral response maps to the standard color space.
The standard also doesn’t resolve the ongoing situation with HDR and high-bit-depth display rendering. DNG can carry floating-point sensor data and extended-range metadata, and the spec describes how to encode it — but how a display pipeline handles that data varies by application, operating system, and monitor hardware in ways that remain unsettled across the industry.
Where to Start If You’re Reconsidering Your Archive Strategy
If the standardization announcement has you thinking about converting an existing proprietary RAW archive, the most defensible approach is to convert a representative sample of files first, verify that your editing software reads them correctly, and spot-check that the embedded color data renders as expected before committing to a full conversion. Pay particular attention to any camera bodies that are more than five or six years old, where the DNG converter’s camera profile may be based on older calibration data — not a reason to avoid conversion, but a reason to verify.
The formal spec doesn’t change the pixel data inside the files you already have. What it changes is the probability that the pixel data remains interpretable by software you haven’t installed yet.