A commonly asked question. A not-so-common answer.
Every now and then I get queries about the DNG format, usually when articles appear elsewhere about why you should convert to DNG. As many of you probably know, I like the idea of an open and well defined raw format, yet I'm not particularly supportive of using DNG, for reasons I'll get to in a moment.
The usual benefits that are ascribed to DNG are:
- It's an open definition and now an International Standard (ISO 12234-4), so it'll be around forever.
- Most software products support DNG naturally; you don't need a new raw converter update when a new DNG-capable camera comes out.
- Your files will likely get smaller due to the way a DNG file stores things, at least if you let the DNG converter throw away the original data file.
- DNG relieves you from the tyranny of the manufacturer's proprietary formats (okay, that's a bit overstated, but I've had DNG supporters actually say this to me).
DNG was proposed and documented by Adobe back in 2004, and Adobe supplies a free DNG converter that will take your raw files (e.g. Nikon NEFs) and spit out DNG files.
Adobe asserted that they'd hand the DNG specification over to a standards board, which has now been ratified (again, ISO 12234-4). A few camera companies have adopted DNG as their raw format, particularly Leica and Ricoh, but not Canon, Fujifilm, Nikon, or Sony, the four largest camera makers whose products create raw files.
Note the Drawbacks
When people ask me if they should convert their NEFs (or other proprietary raw file) to DNG, my usual answer is "no."
The reason is simple: the potential benefits seem to be greatly overshadowed by the drawbacks. That may change someday, but the bottom line is that the drawbacks currently outweigh benefits in my opinion. Consider:
- If you're photographing with a non-DNG camera (such as a NEF-creating Nikon), you increase your workflow steps and import time by adding another step: the DNG conversion.
- Some Nikon compressed NEFs will grow in size when converted, not decrease in size as claimed.
- The black point is established during the conversion to DNG (usually it's only set in the final conversion). Masked black pixels aren't carried over, either, which can be used by some raw converters.
- The DNG converter doesn't always contain the embedded JPEG and thumbnail files from the raw file (this is optional). This is important because:
- No raw converters that interpret the DNG file will match what the cameras do in-camera (embedded JPEG). By converting to DNG you're essentially saying that you'll forgo the camera maker's settings, styles, and color rendering for an interpretation of that. (That's a big issue, in my mind, as the camera makers don't document the spectral response of the Bayer filtration, for one thing.)
- If you elected to keep the original raw file with the DNG (recommended), you've escalated your storage and backup requirements.
- Sidecar modification files should be kept with the original DNG. This means you need to watch your backup systems and make sure they keep file and folder structures intact.
Again, I'm not against the idea of open, documented raw file formats. I'm actually very much for it. But unless Canon, Nikon, and others decide to support DNG and start documenting the inner specifications of their systems, we're in a "manufacturer-knows-best" versus "we-can-reverse-engineer-it" type of fight, with the maker's raw formats on one side and DNG on the other. The downstream benefits of converting to DNG are just not dramatic enough to move savvy users into the DNG camp, in my opinion.
The Legacy Argument
Some DNG proponents keep trying to scare people with: "some day your camera maker might no longer support your raw format." So what? We already have open source code that interprets NEF (see libraw.org, amongst others). If the future some day will require you to move to another file format, you can do so then. In the meantime, for DNG to succeed the short-term benefits need to be bigger and clear. I don't believe they are.
Let the arrow-slinging begin...