If you have spent any time around RAW photography, you have seen files ending in DNG and wondered how they differ from the CR2, NEF and ARW files your camera produces. DNG, short for Digital Negative, is Adobe's open, documented RAW format, created to solve a real problem: every camera maker uses its own secret RAW container, and those formats change with every new model. DNG explained simply is this: it is a standardized box for the same kind of RAW sensor data, designed to be readable for decades by any compliant software.
This article unpacks what a DNG actually is, how it relates to proprietary RAW files, and whether you should adopt it. When you are ready to turn any RAW file, DNG included, into a shareable image, the free RAW to JPG converter from jpeg2raw handles the job.
What is a DNG file
A DNG file stores the same fundamental content as any RAW file: the unprocessed, high-bit-depth Bayer-mosaic data from a camera sensor, plus metadata describing the camera, lens, exposure and white balance. The difference is the container. Where Canon, Nikon and Sony each invented private formats, Adobe published the full DNG specification openly and based it on the well-understood TIFF/EP standard. Any developer can implement DNG support without reverse-engineering a manufacturer's secrets. If you want the underlying concepts of sensor data first, our what is a RAW file article lays the groundwork.
Because the format is open and documented, the photography world treats DNG as a strong candidate for long-term archival. A CR3 from a discontinued camera might one day be hard to open if support fades; a standardized DNG is far more likely to remain readable.
Two ways DNG files come to exist
DNG files arrive by two routes:
- Native DNG capture. Some cameras, notably many Leica, Ricoh and Pentax models, and most smartphones that shoot RAW, write DNG directly. There is no proprietary intermediate format.
- Converted DNG. Most photographers create DNGs by converting their proprietary CR2, NEF or ARW files into DNG using Adobe's free DNG Converter or their editor's import options.
In both cases the result is the same kind of open RAW file, fully developable with the same flexibility as any other RAW.
DNG vs proprietary RAW: the trade-offs
Should you convert your camera's native RAW files to DNG? It depends on what you value. Here is an honest comparison:
- Longevity: DNG is open and documented, a safer bet for long-term readability than proprietary formats that can lose support.
- File size: DNG usually compresses slightly smaller than uncompressed proprietary RAW, and can embed a full-size preview.
- Single file: DNG can embed editing instructions and metadata inside the file itself, avoiding the separate sidecar XMP files that proprietary RAW workflows generate.
- Original fidelity: a converted DNG can optionally embed the original proprietary RAW, but if you discard the original you lose the exact manufacturer file. Some photographers prefer to keep the untouched CR2 or NEF.
- Camera-specific features: a few manufacturer-specific tags or in-camera adjustments may not carry over perfectly into DNG.
For most people the decision is about archival philosophy. If you want the most future-proof, self-contained library, DNG is attractive. If you prefer to keep exactly what the camera wrote, stick with native RAW and back it up carefully.
Does converting to DNG lose quality?
No. Converting a proprietary RAW to DNG is a lossless re-containerization of the same sensor data, not a re-development. The Bayer mosaic, bit depth and metadata are preserved. You are moving the data into a different, open box, not throwing any of it away. The only thing you might discard, if you choose, is the original proprietary file alongside it.
This is fundamentally different from converting RAW to JPG, which is a one-way development into an 8-bit lossy image. A DNG remains a full RAW file with all the latitude that implies, including freely adjustable white balance and high bit depth, the same advantages described in RAW vs JPEG photography.
How to use a DNG file
Like any RAW file, a DNG is not a finished image, so you cannot simply email it and expect it to display. To share it you develop it. The process mirrors any other RAW conversion:
- Upload the DNG to the converter.
- Adjust white balance, exposure and tone on the preview.
- Choose JPG for sharing or TIFF for further editing.
- Download the finished file and keep the DNG as your negative.
If your edit will be extensive, develop the DNG into a 16-bit TIFF using the RAW to TIFF converter, as explained in RAW to TIFF for editing, so you keep maximum tonal headroom for retouching. And if a finished image is destined for a print lab, the JPG to TIFF converter packages your delivery JPG into the lossless container labs prefer, a workflow covered in JPG to TIFF for print.
How DNG handles editing instructions and metadata
A subtle but powerful feature of DNG is how it stores your edits and metadata. With proprietary RAW formats like CR2 or NEF, editors cannot safely write changes inside the manufacturer's file, so they create a separate sidecar file (usually an XMP) alongside it. That sidecar holds your crop, white balance, tone adjustments and keywords. If the sidecar is lost or separated from the RAW during a move or backup, your edits vanish even though the image data survives.
DNG can store those same instructions and metadata inside the single file, so there is nothing to lose or separate. For people who manage large libraries across multiple drives and backups, this self-contained behavior reduces a real category of risk. It also makes sharing simpler: hand someone a single DNG and they receive the image, your edits and your metadata together, rather than a RAW plus a fragile companion file.
DNG also supports embedding a full-resolution preview, so other applications can display the image quickly without re-developing it, and it can carry a checksum that lets software verify the data has not been corrupted. None of this changes the underlying sensor data; it simply makes the container more robust and convenient for long-term storage, which is the heart of DNG's appeal.
When DNG may not be the right choice
DNG is not automatically the best option for everyone. If you rely on a manufacturer's own software for specific in-camera adjustments, lens corrections or film simulations, some of those proprietary refinements may not translate perfectly into DNG, because they were designed around the native format. Photographers who want every last manufacturer-specific feature, or who simply prefer to preserve exactly what the camera wrote, often keep native RAW and treat DNG as optional. The conversion is reversible in the sense that you can embed the original, but if you discard originals to save space, that decision is permanent. As with most archival choices, the right answer depends on whether you prioritize openness and self-containment or absolute fidelity to the camera's output.
DNG in a mixed-camera workflow
One quietly powerful benefit of DNG is consistency. If you shoot Canon, Nikon and Sony bodies, converting everything to DNG gives you one format to manage instead of three. That said, a good converter already reads all three proprietary formats directly, so you do not need DNG just to develop them; our Canon CR2 to JPG guide and how to convert RAW to JPG walk through developing native files. DNG's appeal is mainly about archival uniformity, not whether your files will open today.
The bottom line on DNG
DNG is the photography world's attempt at a universal, open RAW format: the same sensor data and full editing flexibility as proprietary RAW, but in a documented container designed to outlast any single camera maker. Converting to DNG is lossless and can simplify and future-proof your library, though keeping native originals is a valid choice too. Whatever format your negatives take, when you are ready to share, develop them with the free RAW to JPG converter and keep the RAW or DNG safe as your archival master.