What Is DNG (Digital Negative)? Adobe's RAW Format
What DNG Actually Is
DNG stands for Digital Negative. It's an open RAW image format that Adobe released in 2004 to solve a genuine nightmare for photographers. At the time, every camera maker had its own proprietary RAW format — Canon's CR2, Nikon's NEF, Sony's ARW — and there was no guarantee your software would be able to read those files in ten or twenty years. DNG was Adobe's answer: a single, documented, publicly available container format based on TIFF/EP that could store the full, unprocessed sensor data from any digital camera. At its heart, a DNG file holds the raw light data captured by the camera sensor before any in-camera processing gets applied. That means no sharpening, no noise reduction, and no white balance is baked in. This is the same principle behind any RAW format. The key difference is that the DNG specification is openly published. Any developer can write software to read or write it without paying licensing fees or reverse-engineering a secret format. The full spec, running over 100 pages, is available for free on Adobe's website. A single DNG file can act like a tidy little package. It can contain the original proprietary RAW data embedded right inside it, or it can store the data converted into the DNG structure itself. It also supports embedding a full-resolution JPEG preview for quick viewing, XMP metadata for editing instructions, and even the original camera profile. No matter which camera brand produced the original sensor data, the file extension is always a simple .dng.
How DNG Differs from Other RAW Formats
When you shoot in a proprietary RAW format, you're living by the manufacturer's rules. A Canon R5 spits out .CR3 files. A Nikon Z9, .NEF files. A Fujifilm X-T5, .RAF files. Each is a specific binary container, and its internal structure is usually a secret. Software companies like Adobe, Capture One, and DxO have to reverse-engineer each new camera's format to support it. Anyone who has bought a brand-new camera only to find Lightroom can't open its files knows this pain well; it often takes weeks or months for an update to arrive. DNG cuts through that delay by standardizing the container. If a camera manufacturer ships a camera that natively records DNG (which Leica, Pentax, Ricoh, and some Hasselblad models do), the files work immediately in any DNG-aware software. Adobe Camera Raw, Lightroom, Capture One, RawTherapee, and darktable all speak DNG fluently. There are also real differences in file size. A Canon CR3 from an EOS R5 is typically 25–35 MB. Convert that same file to DNG using Adobe's DNG Converter (without embedding the original) and you'll get a file that's around 20–28 MB. That's a 15–25% reduction in size with absolutely no loss of image data, thanks to lossless compression. Adobe also offers a 'lossy' DNG option, but it's a different animal entirely, used more for archiving final edits than for active work. DNG isn't perfect, though. It doesn't support every proprietary RAW feature. Some manufacturers embed private metadata for things like in-camera HDR compositing or specific focus stacking parameters. That data might not survive a conversion to DNG. For most of us, this is a non-issue. But if you rely heavily on those specific in-camera features, you'll want to test your workflow before committing.
The Case for Long-Term Archiving in DNG
The single best reason to use DNG is for long-term archiving. Full stop. Open formats outlast proprietary ones. Remember Kodak's Photo CD format from the 90s? Probably not, because you need specialist software to read it on a modern computer. Minolta's MRW RAW format from the early 2000s is fading fast. There is simply no guarantee that your .CR3 or .ARW files will be readable by whatever software we're using in 2045. DNG's specification is public and versioned, with 1.7.1 released in 2023. The format has even been submitted to ISO for formal standardization. Because the spec is public, a developer could write a perfect DNG reader from scratch even if Adobe disappeared tomorrow. That's the entire ballgame compared to a secret format locked inside a single company. For working photographers building archives that need to last for decades—photojournalists, documentary shooters, commercial studios—this is a critical business consideration, not some theoretical debate. The Library of Congress even lists DNG as a preferred format for digital image archiving, citing its open specification and wide support. So what's the practical step? If you shoot with a camera that produces CR2, NEF, or ARW files, grab Adobe's free DNG Converter. It handles batch processing with ease. You can drag a whole folder of RAWs onto it, pick a compatibility level (the default 'Camera Raw 7.1 and later' is usually fine), and let it run. A batch of 500 CR2 files from a Canon 5D Mark IV can be converted in under ten minutes on a modern machine.
DNG in Practice: Lightroom, Camera Raw, and Other Tools
If you're a Lightroom Classic user, you can convert to DNG right on import by simply checking the 'Copy as DNG' option. For files already in your library, just select them and go to Library > Convert Photos to DNG. Lightroom takes care of the conversion and automatically updates your catalog. In Adobe Camera Raw, the engine behind Photoshop's RAW processing, DNG files behave identically to any other RAW format. You get the same powerful sliders for Exposure, Highlights, Shadows, and White Balance. The big practical win here is file management. When you save edits to a DNG file, the XMP editing data is written directly *into* the file. This keeps your archive clean: one file per image, with no separate sidecar .xmp files to get lost or separated. Capture One supports DNG natively, but its behavior can be a little different. Capture One's famous color science is built around specific camera profiles. A DNG converted from a NEF file might not automatically trigger the same camera-specific profile as the original NEF would. It's an easy fix—you can manually assign the correct camera profile in Capture One's Color > ICC Profile dropdown—but it's something to be aware of. Open-source tools like darktable and RawTherapee also read DNG files without a problem. RawTherapee, in particular, has excellent DNG support because it uses the robust LibRaw library. For photographers looking to escape subscription models, a workflow of converting to DNG and editing in RawTherapee is a completely legitimate and powerful option.
Converting to and from DNG with CocoConvert
CocoConvert makes DNG conversion simple, especially if you want to avoid installing more software. You can upload a proprietary RAW file—CR2, CR3, NEF, ARW, ORF, RW2, and others—and convert it to DNG for archiving or compatibility. The process is lossless, preserving all the original sensor data while embedding standard DNG metadata. It's a very convenient option for quickly converting a batch of files from a recent shoot. You can also go the other way, converting DNG files to more universal formats like JPEG, TIFF, or PNG. This is perfect for sharing images with clients or collaborators who don't have RAW-capable software. A DNG-to-JPEG conversion at 90% quality can shrink a 24-megapixel DNG from 15–25 MB down to a practical 3–8 MB file, perfect for email or web delivery. Let's be clear about what CocoConvert does not do. It is not a RAW processor. You can't adjust white balance, exposure, or tone curves during the conversion. The output from a DNG-to-JPEG conversion uses either the embedded JPEG preview or a default rendering of the RAW data, not a polished edit. For any serious editing, you must process your DNG files in a dedicated application like Lightroom, Camera Raw, or Capture One before exporting. Think of CocoConvert as a powerful file-format utility, not a replacement for your editing software. The current upload limit on CocoConvert is 100 MB per file. This covers the vast majority of camera RAW files, but it could be a limitation if you're working with medium-format files from cameras like the Fujifilm GFX 100S, whose RAWs can top 200 MB.
When You Should (and Shouldn't) Use DNG
So, when does DNG actually make sense? It shines in a few key situations. For long-term archiving, where you want to ensure your files are readable in 20 years, converting to DNG is a very smart move. It's also great for collaborative workflows; sending a DNG to a retoucher who uses different software eliminates compatibility headaches. And of course, if you own a Leica M11, Pentax K-3 III, or a DJI drone, you're already shooting in DNG, so the choice has been made for you. But you don't always need DNG. If your workflow is simple and self-contained—say, you shoot Canon CR3, edit everything in Lightroom, and deliver JPEGs—there's no compelling reason to add a conversion step. The proprietary format works perfectly fine, Lightroom reads it, and converting just adds time without adding any real value to that specific process. You should also stick to the native format if you rely heavily on manufacturer-specific metadata. In-camera tricks like Nikon's Active D-Lighting flags, Canon's Dual Pixel RAW data for micro-adjustments, or Sony's Pixel Shift data might not survive the DNG conversion process. If those features are critical to your work, stay native. Finally, a note for videographers: while CinemaDNG is technically DNG-based, it's a different beast from the still-image DNG format discussed here. And formats like Blackmagic RAW (BRAW) are completely separate. RAW video has its own world of format considerations.
DNG's Place in the Broader RAW Landscape
More than twenty years after its launch, where does DNG stand? It’s established, but it never took over the world as Adobe might have hoped. Despite their efforts, only a handful of camera makers adopted DNG as a native format. The big players—Canon, Nikon, Sony, and Fujifilm—have all stuck with their own proprietary formats. Their reasoning is partly technical (their formats can carry proprietary data DNG can't) and partly strategic business. What has changed is the tooling. The free Adobe DNG Converter, now at version 16.x in early 2026, supports almost every camera from the last fifteen years. The conversion is reliable and the output files work everywhere. The format itself has also evolved. DNG 1.6 added support for floating-point data to handle computational photography, while DNG 1.7 added better support for depth maps and semantic masks, keeping pace with advances in both smartphones and dedicated cameras. The bottom line is this: for photographers who think about their work in terms of decades, not just seasons, DNG remains the most rational choice for an archival format. It's not a magic bullet, but it's a well-specified, broadly supported, and actively maintained format with a public specification. That's far more than you can say for most proprietary alternatives. If you want to start converting your archive, Adobe's DNG Converter is free and excellent for large batches. For quick, no-install conversions of individual files or small sets, CocoConvert's DNG conversion tool handles the most common RAW formats without any local software setup.