Cookies for analytics and advertising
We use cookies for analytics and advertising, both sent to Google. Refusing changes nothing you can see.Read the privacy page
DNG
Adobe's open raw format. The one raw container that is not tied to a single camera maker.
DNG
DNG is a container: a wrapper that holds streams encoded by something else. It stores a grid of pixels, so enlarging it past its own resolution softens it. It is used for photography, editing and archiving.
The extension is .dng, and the full name is Digital Negative. Both matter less than what the file can hold, which is what the rest of this page is about.
Adobe published it in 2004. The specification is ISO 12234-4. It comes out of Leica, Pentax, Ricoh and phone cameras, plus anything converted bodies.
Age is worth knowing here for one practical reason: the older a format is, the more programs have had time to learn it.
It is published in full, so anyone can implement it from the document rather than by inspection, which is why it turns up in so many programs and why files written twenty years ago still open. A published specification is not the same thing as a royalty-free one: where a format wraps a codec, the patent licensing is a separate question the standard does not settle.
DNG stores its content exactly. Saving it again changes nothing, so it can be opened, edited and re-saved as often as you like without accumulating damage — which is what makes it a working format rather than a delivery one.
DNG has nowhere to record transparency. Anything transparent in the source is filled with a solid colour on the way in — white, unless something chooses otherwise.
Up to 16 bits per channel. It can work in RGB.
More than eight bits per channel is what stops a gradient from stepping when it is edited, which is why it matters in a working file and rarely in a finished one.
Adobe Lightroom, Adobe Camera Raw and darktable read it, and so do most programs of the same kind.
If a file will not open, the format is rarely the problem — it is more often that the program predates it. Converting to something older is the reliable way past that, and it is what the rest of this site is for.
No browser reads it.
That is the single most common reason to convert it: not that the format is bad, but that the place you want to show the file cannot read it.
DNG can hold EXIF, XMP and GPS coordinates.
The GPS coordinates are the field worth thinking about before sending a file anywhere: they say where the photograph was taken, and almost nothing warns you that they are still in there.
DNG is meant to be opened and changed. Keep the file in this format for as long as the work is going on, and export from it whenever a finished copy is needed.
The recurring complaints: programs often show an embedded preview rather than the real data.
None of these is a reason to avoid the format. They are the things worth knowing before you are surprised by one, which is a different claim and a more useful one.
Every other raw file is a manufacturer’s private format: ARW is Sony’s, CR3 is Canon’s, NEF is Nikon’s, and none of them are published. Software supports them by reverse engineering, one camera model at a time, forever.
DNG is Adobe’s answer to that, released in 2004 with a public specification anyone may implement. It is built on TIFF, so its structure is familiar and readable, and it holds the same sensor data the manufacturer’s file did. The argument for it is not technical superiority — it is that the format can still be read in thirty years by software nobody has written yet.
Three places, and they behave differently. Some cameras write it natively — Leica, Pentax, Ricoh and a number of drones, notably DJI. Phone cameras produce it when shooting raw, which is now the largest source by volume. And photographers convert to it deliberately as an archiving step, using Adobe’s free converter or Lightroom’s import option.
The third case is the one worth understanding, because it is a decision rather than a default, and because it is the reason the format exists at all.
Converting a manufacturer raw to DNG typically produces a file 15 to 20 per cent smaller, using lossless compression. The sensor data is bit-for-bit the same; the saving comes from better packing rather than from discarding anything.
That is unusual enough to be worth stating plainly: the conversion reduces size, improves longevity and loses no image information. The costs are elsewhere, and they are real.
The manufacturer’s own software may no longer recognise the file. Sony’s Imaging Edge, Canon’s Digital Photo Professional and their equivalents read their own format and generally not DNG, so any processing that relies on the manufacturer’s lens corrections or colour profiles is no longer available.
Some maker-specific metadata does not survive either — focus point positions, certain proprietary settings, occasionally the manufacturer’s own picture styles. Adobe’s converter can embed the original raw file inside the DNG to hedge against this, at the cost of a file larger than either alone. That option exists precisely because the loss is not hypothetical.
With a proprietary raw, adjustments are stored in a sidecar — an XMP file sitting beside the image that must travel with it. Separate the two and the editing is gone.
DNG can hold those adjustments internally, so one file carries both the negative and the interpretation. That is genuinely convenient and has one drawback worth knowing: the file changes every time the editing does, so a backup system that deduplicates or versions by file will re-copy the whole thing after a small adjustment. With sidecars, only the small file changes.
A normal DNG holds the sensor mosaic exactly as the camera recorded it, one value per photosite. A linear DNG has already been demosaiced — three full colour channels per pixel — which triples the data and removes the ability to choose a different demosaicing algorithm later.
Most DNGs are the first kind. The second turns up from some drones, from certain phone processing pipelines, and from software that has done partial work before writing the file. If a DNG is unexpectedly three times the size of its neighbours, this is almost certainly why.
Camera manufacturers discontinue software. Formats from bodies sold in the 2000s are already awkward to open outside a handful of programs that maintain support out of goodwill. A private format has no guarantee behind it beyond a company’s continued interest.
DNG has a published specification and multiple independent implementations, which is the same argument that makes PDF/A and OpenDocument attractive to archives. For photographs meant to outlast the camera that took them — which is most photographs anyone keeps — that is the substance of the case.
It is an Adobe specification, and Canon, Sony and Nikon have never had a reason to hand format control to a software company they compete with commercially. Each has instead kept its own format as a reason to use its own tools.
So DNG occupies an odd position: technically the sensible choice, unsupported by the three manufacturers who matter most, and used mainly by photographers who converted deliberately or by phones and drones with no legacy format to defend.
To share, print or publish, convert to JPG at high quality — the result is a photograph rather than a set of measurements, and it opens everywhere. For further work outside a raw editor, or where every pixel must survive, PNG or TIFF.
Keep the DNG. As with any raw file, the converted copy has the white balance, the contrast curve and the colour interpretation baked in permanently, and those decisions cannot be revisited. The DNG is the negative — and unlike a proprietary raw, it is a negative in a format that will still be readable when the camera is a museum piece.
| Extension | .dng |
|---|---|
| Media type | image/x-adobe-dng |
| Published by | Adobe |
| First published | 2004 |
| Specification | ISO 12234-4 |