Adobe Proposed a Universal Raw Format in 2004 and the Industry Mostly Ignored It
The DNG format's history — Adobe's 2004 proposal, the manufacturers who adopted it natively (Leica, Ricoh, Pentax) and those who did not (Canon, Nikon, Sony), and what the continued proliferation of proprietary raw formats means for long-term file access.
DNG was meant to solve a solvable problem. Two decades later, the problem remains.
The Proposal and Its Logic
In September 2004, Adobe introduced the Digital Negative specification — DNG — as an openly documented, publicly available raw image format. The pitch was straightforward: proprietary raw formats from individual manufacturers were fragile archives. A Nikon NEF or a Canon CR2 depended on software vendors continuing to decode them. Adobe's argument was that an open specification, lodged in the public record, could outlast any single company's product decisions.
Thomas Knoll, who had been instrumental in Photoshop's development, led the technical work. Adobe published the DNG specification openly, and the format was eventually submitted to ISO as a basis for standardisation under the TIFF/EP lineage. The core idea was simple: embed the raw sensor data alongside standardised metadata, publish the decoding rules, and let the file stand on its own indefinitely.
The manufacturers did not see it that way — at least most of them didn't.
Who Said Yes, and Who Didn't
Leica Camera adopted DNG as its native raw output, beginning with the M8 in 2006, and has stayed with it across the M, Q, and SL lines since. Ricoh Imaging — which absorbed Pentax — ships DNG natively from the GR series and from Pentax DSLRs and medium-format bodies. Hasselblad uses a 3FR container that references DNG structures internally. A handful of smaller and niche manufacturers, including some drone-camera platforms, followed suit. For those shooters, the archive problem Adobe identified in 2004 is largely solved: a DNG from a Leica M8 read in Lightroom 1.0 and a DNG read in Lightroom 2024 travel the same specification.
Canon, Nikon, and Sony declined. Canon's CR2 became CR3. Nikon's NEF persisted in evolving, compression-variant forms. Sony's ARW format continued on its own trajectory. All three remain proprietary: documented only to the degree each company chooses, decodable only as long as vendors maintain the relevant read paths.
Timeline of key events
- 2004Adobe publishes the DNG specification and releases the first DNG Converter
- 2006Leica M8 ships as the first major camera body to write native DNG
- 2013Adobe moves Creative Suite to subscription; Camera Raw updates become subscription-contingent
- 2024Canon, Nikon, and Sony still do not write native DNG; Adobe DNG Converter remains a free standalone download
The argument those manufacturers implicitly make is that a proprietary raw format lets them encode sensor-specific metadata — autofocus maps, in-body processing flags, lens correction tables — in tightly controlled ways that tie into their own imaging pipelines. That is a real engineering benefit. It also happens to be a real lock-in benefit, and the two are not easy to separate.
What Proprietary Formats Mean Over Time
Adobe Camera Raw and Lightroom both maintain support for hundreds of proprietary raw variants. So does Capture One, and so do open-source processors like darktable. The practical day-to-day consequence of format fragmentation is invisible to most working photographers: they open the file, it works. The risk sits further out, in a different time register.
Raw format support is not a legal obligation. It is a business decision that software vendors make and unmake. When Adobe dropped perpetual licensing in 2013 and moved the entire Creative Suite to subscription, the continuity of Camera Raw updates became contingent on maintaining an active subscription. Older versions of Photoshop, once the subscription lapses, stop receiving new camera support. A photographer who locks a decade of work in a proprietary raw file and later loses access to current software faces a narrowing set of options.
The US Copyright Office defines works in terms of fixation and originality, not format. The file is the archive; whether it remains readable is an infrastructure question, not a legal one. DNG at least answers that infrastructure question with a published specification that any developer can implement without permission.
Leica, Pentax, and Ricoh made a choice in the years after 2004 that looks increasingly considered as camera files age. Canon and Nikon and Sony made the opposite choice and have not reversed it in twenty years. Adobe still ships a DNG converter — free, standing alone, updated with each camera cycle — that can batch-translate any supported proprietary raw into a DNG. It is a workaround for a problem the industry could have agreed not to create.
