What Is a DNG File? A Raw Photo in a Format Anybody May Read
DNG holds sensor data, in Adobe's open Digital Negative format. Jump to your question below, or read it through in order.
DNG holds sensor data, in Adobe's open Digital Negative format. Jump to your question below, or read it through in order.
A DNG file is a raw photo, stored in Adobe's Digital Negative format. Inside sits what your camera sensor measured, before any color, sharpening or white balance got baked in.
Every camera maker has its own raw format and keeps the details private. Adobe published theirs. That one difference explains the format. Since 24 March 2026 it carries an ISO number to prove it.
DNG stands for Digital Negative, and in Adobe's own documents the full name is Adobe Digital Negative. Developed by Adobe and announced on 27 September 2004, it took its name from film. Film negatives behave the same way. You cannot hang one on your wall. You print from it. And you keep printing new versions for decades, because nothing in it was decided for you.
Raw photos work like that. Your sensor measures light and records numbers. Turning those numbers into colors anyone can look at takes dozens of choices. JPEG makes every one of them at the moment you press the shutter. Raw formats put all of them off.
What makes DNG different from CR3, NEF or ARW is not what sits inside. It holds the same measurements. What differs is that Adobe published how those readings are stored. So software built by anyone reads one without guesswork.
.dng49 49 2A 00 or 4D 4D 00 2Aimage/tiffThe conversion runs one direction. Adobe DNG Converter reads more than 600 raw formats and writes DNG. No software goes back the other way. One option changes that, and you have to tick it before you convert.
No. You cannot convert one back, not with Adobe software, not with anyone else's, not for money. The older version of this page promised you could convert DNG to NEF, CR2 and ARW. That claim is backwards.
Here is why. You cannot convert back, and the reason is structural. Converting to DNG rewrites your camera maker's private structures, MakerNote and all, into the ones Adobe published. The sensor values survive intact. Everything around them gets translated, and translation loses the original wording even when it keeps the meaning.
Canon's exact byte layout is not reconstructed by any tool from what came out. Which is why no converter offers DNG to CR2, at any price, from anybody.
The Adobe DNG Converter has an option called Embed Original Raw File. Tick it and your untouched CR2 or NEF rides along inside the DNG. It is ZIP compressed and stored in tag 50828, with its filename in 50827.
Later, open the converter and click Extract. Point it at your folder and your files come back out byte for byte. That is retrieval of something you decided to carry, not conversion.
Your original is inside. Roughly double the file size. Extract in Adobe DNG Converter gives your CR2 back whenever you want it.
Your original is wherever you left it. Delete those files and nothing brings them back. Keep them until you are certain.
The Copy as DNG option in Lightroom does not embed anything. It converts and moves on. Plenty of photographers discovered that only after clearing a memory card.
Convert with Adobe DNG Converter instead when you want that safety net. Check the option before you start a batch.
Every camera model ships a raw dialect of its own and no one writes it down. The software makers reverse engineer them one by one, and the support for older cameras quietly stops. DNG exists to end that.
Buy a camera and its raw files arrive in the maker's own format. Buy two cameras and you have two formats. Canon alone has written CRW, CR2 and CR3. None of them reads with the software built for the next.
Worse, those formats are undocumented. Adobe, Apple, darktable and everyone else work out how new cameras store their data by examining files. Which is why support for any camera launched today arrives weeks after the camera does.
Nobody knows, which is the problem. A raw format lives while somebody maintains the code for it. Canon supports its own files. Adobe supports hundreds, going back years. Neither promises anything about 2046.
Archives care about this a lot. The Library of Congress lists DNG among its accepted formats for photos. It even names the spec version it holds files against. No proprietary raw format gets treated that way, because there is nothing to hold them against.
| Question | Proprietary raw | DNG |
|---|---|---|
| Is the layout published? | No | Yes, since 2004 |
| Can anybody write a reader? | By reverse engineering | From the specification |
| Is there a standard? | No | ISO 12234-4:2026 |
| Can you verify the pixels later? | No | Yes, a stored fingerprint |
| Do edits live in the file? | Sidecar files | Inside, no sidecar |
| Who decides its future? | One camera maker | Adobe, now with ISO |
That fifth row saves real trouble. Edit a CR2 in Lightroom and your edits live in .xmp files beside it. Move photos without them and your work vanishes. DNG stores edits inside, so one file travels alone.
Adobe never charged for it. The DNG license grants a worldwide, royalty-free, nontransferable, nonexclusive right to build software that reads or writes DNG. Adobe can revoke it from anyone who sues Adobe over patents. That is the only real string attached.
A DNG is an extension of TIFF, with extra vocabulary. Two bytes naming the byte order, then the number 42, then directories of numbered tags, one IFD after another. One directory holds a preview, another holds sensor data and the rest describe how to develop it.
Open one in an editor that shows bytes and you see II or MM. Then the number 42. That is TIFF, unchanged since 1992. Adobe built DNG on top rather than starting fresh. That is why DNG files often carry a .tif extension. It also explains why some viewers show one without knowing what it is.
The Adobe spec says readers must support either byte order, even from a single camera model. That sounds pedantic until you meet a file from a camera that switched.
| Part | Size | What it does |
|---|---|---|
| Byte order mark | 2 bytes | II or MM, telling readers which way round numbers run |
| Version number | 2 bytes, at offset 2 | The number 42, or 43 for a BigTIFF file past 4GB |
| IFD0, the first directory | Varies | Small preview, plus camera make, model, date and shutter settings |
| SubIFD, the raw directory | Most of the file | Sensor values, color profile, black levels, lens corrections |
| Preview directories | 1MB to 4MB | Ready-made JPEG versions, so software shows something instantly |
| Private data | Varies | Your camera maker's own tags, kept rather than discarded |
| Original raw file | Optional, large | Your untouched CR2 or NEF, when you asked for it |
Those preview images explain something people notice. Import DNG files into Lightroom and the thumbnails appear at once, while proprietary raws take a moment. Adobe writes previews during conversion and every reader finds them in a known place.
Camera sensors do not see color. Every photosite measures brightness through one colored filter, red, green or blue, arranged in a grid. Working out the full color for every pixel is called demosaicing. Raw photos normally arrive before it happens.
DNG supports both. A mosaic DNG stores just what came off the sensor, one number per photosite. Adobe marks it 32803 in the tag for pixel meaning. A linear DNG stores demosaiced pixels instead, marked 34892. That is how sensors that work differently fit into DNG at all.
Your camera maker's private data survives conversion. Adobe stores it in two tags built for the job. It asks the software that edits DNG files to keep them. Software that obeys leaves a door open for the maker's own tools later. The software that ignores them quietly throws that away.
On 24 March 2026, DNG was published as ISO 12234-4:2026 by the photography committee. One hundred pages, a first edition, 22 years after Adobe announced the format. Nothing about your files changed. What changed is who stands behind them.
Adobe announced the format in September 2004 and published the layout the same day. For 22 years DNG was open in every real sense. Adobe published the specification, gave away a royalty-free license and shipped free tools. The camera makers still declined. The reason they gave was control. DNG belonged to a single company, and that company competed with them.
March 2026 removed that argument. The International Organization for Standardization published DNG as ISO 12234-4:2026, titled Digital imaging, Image storage, Part 4: Digital negative format. Its scope runs to one sentence. The document specifies the DNG image file format, and a DNG file meets the requirements it provides.
| Property | Value |
|---|---|
| Number | ISO 12234-4:2026 |
| Title | Digital imaging, Image storage, Part 4: Digital negative format |
| Published | 24 March 2026 |
| Edition | 1 |
| Committee | ISO/TC 42, Photography |
| Length | 100 pages |
| Status | Published international standard |
Robert Edwards, an Australian photographer, put the idea to Adobe in March 2004. Thomas Knoll, who wrote the first version of Photoshop, agreed it would work. Adobe announced the format six months later. Edwards then spent years arguing for a standard, campaigning hardest after an ISO meeting in February 2013.
On publication he said the goal had been achieved after more than two decades of discussion, persistence and advocacy. What began as an idea, he said, is now a globally recognized standard.
Does anything change for files you already have? No. Photos converted in 2010 are unchanged, and the software reads them exactly as before. Standards describe the formats, they do not rewrite the files.
Watch what camera makers do next. The reason they gave for skipping DNG was that it belonged to Adobe. From March 2026 it belongs to ISO/TC 42, alongside every other photographic standard they already follow. Whether any of them changes course is worth watching over the next few years.
On macOS, Preview and Photos open DNG with nothing installed. On Windows, Photos needs Microsoft's free Raw Image Extension. darktable and RawTherapee are free everywhere and edit properly rather than just showing a picture.
Two jobs, and mixing them up causes most of the confusion. Viewers show you the preview JPEG already sitting in the file. Quick, and it tells you nothing about what raw data can do. Raw editors read the sensor values and let you change decisions your camera never made.
| Software | Cost | Why choose it |
|---|---|---|
| Apple Preview, Apple Photos | Included with macOS | The easy answer on Mac. Double-click and it opens, ProRAW included |
| Microsoft Raw Image Extension | Free, from the Store | The fix on Windows. Teaches Photos and File Explorer to read raw |
| darktable | Free, open source | Windows, macOS and Linux. Closest free match for Lightroom |
| RawTherapee | Free, open source | Finer control over demosaicing than anything else free |
| Adobe DNG Converter | Free, from Adobe | Converts, extracts embedded originals, adds Embed Fast Load Data and rewrites for older software |
| GIMP, XnViewMP, IrfanView, FastStone | Free | Quick viewing and batch export, when editing is not the point |
| Adobe Lightroom, Photoshop | Subscription | Where DNG was designed to live, with every tag understood |
| Capture One, DxO PhotoLab, ACDSee, Affinity Photo | Paid | Rival raw editors, all reading DNG without complaint |
The old version of this page recommended Picasa, which Google discontinued in 2016. It also listed something called Eltima corel paint-shop pro, which is two companies welded to one product name. Both are gone from the table above.
Just want to see what is in it? On Windows, install Raw Image Extension from the Microsoft Store and thumbnails start appearing in File Explorer. Free, official and roughly a minute of work.
Free raw editors are genuinely good here. DNG is documented, so darktable and RawTherapee handle one as completely as the paid software does. That is the payoff for an open format. It does not apply to CR3 or NEF files, where free tools are always a step behind.
Nearly every failure has one of two causes. Your software predates the file, or your software never read raw photos to begin with. A DNG carries a tag naming the oldest reader that copes, and readers obey it.
Adobe put two version tags in every DNG. The first says which spec version wrote it. The other names the oldest version that can still make sense of it. Adobe tells readers to refuse anything newer than they understand. Refusing beats guessing, though it looks like a fault from outside.
| What you see | What it usually means | Start with |
|---|---|---|
| Double-click does nothing on Windows | Photos cannot read raw without help | Raw Image Extension, free in the Store |
| No thumbnails in File Explorer | Same cause, same fix | Raw Image Extension, then reopen the folder |
| File format not supported | A newer version of DNG than your software knows | Update, or rewrite it with Adobe DNG Converter |
| Opens tiny, or rotated | Windows Photos mishandling the orientation tag | darktable, IrfanView or XnViewMP |
| Photoshop opens Camera Raw first | Working exactly as designed | Nothing. Adjust, then click Open |
| Colors look flat and gray | Raw before development, which is normal | Any raw editor, then add contrast |
| Nothing opens it anywhere | Possibly not a photo. See section 1 | Check where the file came from |
Stuck with old software you cannot update? Run your files through Adobe DNG Converter and set Compatibility to an older release. It rewrites them in an earlier DNG version, which is what the setting exists for.
Flat and gray is not damage. Raw photos hold measurements, not pictures, so they look dull until the software applies contrast and color. JPEG looks better straight away because your camera already did all of that, permanently.
The DNG 1.4 release added lossy compression in October 2012, and it shipped first in Lightroom 4. The files land near a quarter of their original size and stay editable. The detail goes permanently, there is no way back and nothing warns you afterwards.
Two file sizes used to bracket photographers. Raw at 25MB held everything and JPEG at 6MB held almost no flexibility. Adobe built lossy DNG to sit between them. Tom Hogarty of Adobe described it as allowing something in between, while keeping the room to adjust white balance and hold detail.
It works by demosaicing first, dropping to 8-bit LinearRaw data and then applying JPEG compression. The files often land at a third or a quarter of their source size. The white balance still adjusts, the shadows still lift and the fine detail has gone.
The default, and the safe one. The sensor values survive intact. The files run roughly 20 percent smaller than the maker's own raw, and nothing is lost.
A choice you make once. Roughly one quarter of the size, still editable, with the detail it discarded gone for good.
A lossy DNG looks identical to a lossless one in your file browser. Same icon, same extension, roughly plausible size. Nothing marks the difference until you open it in a program that reports compression.
So run lossy conversion deliberately, on folders you chose, never across an entire library at once.
Converting helps if you keep photos for decades, want smaller files or use free software. It hurts if you rely on your camera maker's own editor, shoot tethered or need your original files for any reason.
Photographers argue about this and both sides have a real case. The answer turns on whether you value your archive in 2046 more than convenience in 2026.
The middle ground exists and plenty of professionals sit in it. Convert with Embed Original Raw File ticked, keep both inside one file and decide later. Files run roughly double the size, and you have given up nothing.
Shooting Canon? Compare against the CR2 raw format and older CRW files. On Sony, the ARW format covers the same ground.
Whatever you decide, decide once and write it down. Half-converted libraries cause more grief than either choice. Photographers who convert it all and those who convert nothing both cope fine. People with six years of CR2 files and four years of DNG files spend weekends sorting it out.
More DNG files come from phones and drones now than from cameras. Apple ProRAW, Google Pixel, Samsung Expert RAW and DJI all write DNG. Building on a published format beats inventing another private one.
Apple shipped ProRAW with iOS 14.3 in December 2020, on the iPhone 12 Pro. ProRAW is DNG with Apple's processing data added, carrying 12-bit color and, by Apple's figure, 14 stops of range. The files run around 25MB against roughly 2MB for the same shot as HEIC.
Turn it on at Settings, then Camera, then Formats, then Apple ProRAW. Tap RAW in the camera app when you want it. Leave RAW off the rest of the time or your storage disappears in weeks.
| Source | Writes DNG? | Note |
|---|---|---|
| Leica, Pentax, Ricoh, Hasselblad | Yes, in camera | About 12 camera manufacturers and 38 camera models in all |
| Sigma, Casio, Sinar, DxO | Yes, in camera | The Sigma fp writes CinemaDNG as well |
| iPhone 12 Pro and later | Yes, as ProRAW | iOS 14.3 or later, switched on in Settings |
| Google Pixel, Samsung Galaxy | Yes | Pixel raw capture, and Samsung's Expert RAW app |
| DJI and Autel drones | Yes | Still photos, and CinemaDNG on some camera payloads |
| Blackmagic cinema cameras | Yes, as CinemaDNG | Every frame is a DNG, numbered in sequence |
| Canon, Nikon, Sony | No | CR3, NEF and ARW, all undocumented |
| Fujifilm, Panasonic, OM System | No | RAF, RW2 and ORF, all undocumented |
Adobe announced CinemaDNG on 14 April 2008. One clip is a sequence of raw video frames with audio and metadata. It is held either as a folder of numbered DNG files or wrapped inside an MXF container. Every frame is an ordinary DNG. Blackmagic cinema cameras, the Sigma fp and DJI's Zenmuse X5R all write it.
Which is why a drone or cinema camera sometimes produces folders holding thousands of numbered .dng files. Nothing is broken. Open any one in a photo editor and you get a single frame. Adobe never submitted CinemaDNG to ISO, so it stands apart from the March 2026 standard.
One directory lists Apple, DJI and Autel Digital Negative Format as three separate formats it has not analyzed. They are one format. Every vendor adds private tags for its own processing. Every DNG reader skips tags it does not recognize, which is just what TIFF was built to allow.
Open since 2004, and an ISO standard since March 2026. Nine spec versions, the current one from September 2023. Underneath it is TIFF 6.0, which is why a DNG sometimes opens in software that has never heard of DNG.
Nothing here helps you open your photos. It is on record for two reasons. DNG is one of very few formats on this site with a published spec anyone may download. And the older version of this page filled its format section with software names instead.
| Property | Value |
|---|---|
| Full name | Adobe Digital Negative (DNG) |
| Kind | Binary raster container for camera raw data |
| Published spec | Yes. Free from Adobe since 2004 |
| International standard | ISO 12234-4:2026, 24 March 2026 |
| Built on | An extension of TIFF 6.0, following TIFF/EP |
| Byte order | Either byte order. Readers must support both |
| Signature | 49 49 2A 00 or 4D 4D 00 2A, then 42 at offset 2 |
| Media type | image/tiff |
| Extensions | .dng, and .tif is permitted |
| Directories | IFD0 for the preview, SubIFD trees for the rest |
| Bit depth | BitsPerSample, 8 to 32 bits per sample |
| Compression | 1 uncompressed, 7 JPEG, 8 Deflate, 34892 lossy JPEG |
| What 7 means | Either baseline DCT JPEG or lossless Huffman JPEG |
| Current version | 1.7.1.0, September 2023 |
| Files past 4GB | A 64-bit BigTIFF variant, marked 43 rather than 42 |
| Version | Released | What it brought |
|---|---|---|
| 1.0.0.0 | September 2004 | The format, announced on the 27th |
| 1.1.0.0 | February 2005 | Early corrections |
| 1.2.0.0 | May 2008 | Camera profiles |
| 1.3.0.0 | June 2009 | Lens correction opcodes |
| 1.4.0.0 | September 2012 | Lossy compression, floating point, proxies, transparency |
| 1.5.0.0 | May 2019 | Enhanced image data |
| 1.6.0.0 | December 2021 | Semantic masks, triple illuminant profiles, 64-bit files |
| 1.7.0.0 | June 2023 | Newer compression choices |
| 1.7.1.0 | September 2023 | Current. Corrections to 1.7 |
Popular format guides still list five versions and stop at 2012. Anything reading a DNG written since then needs the later releases. Which is why version tags matter more in DNG than in most formats.
| Tag | Number | What it holds |
|---|---|---|
DNGVersion | 50706 | Four bytes, one per tier. 1 7 1 0 in current files |
DNGBackwardVersion | 50707 | The oldest reader that copes. Why old software refuses new files |
RawImageDigest | 51111 | An MD5 digest of the raw image data. Adobe's own wording |
RawDataUniqueID | 50781 | A 16-byte identifier for the sensor data in the file |
OriginalRawFileName | 50827 | What your CR2 or NEF was called before conversion |
OriginalRawFileData | 50828 | The original file itself, compressed in 64K blocks |
OriginalRawFileDigest | Adobe | An MD5 digest of that original, so extraction is checkable |
DNGPrivateData | Adobe | Your camera maker's own data, carried rather than dropped |
MakerNoteSafety | Adobe | Whether the MakerNote is safe to copy into an edited file |
ActiveArea | Adobe | Which pixels are real, when masked edge pixels were kept |
PhotometricInterpretation | 262 | 32803 for CFA, 34892 for LinearRaw |
NewSubFileType | 254 | 0 for the full raw, 1 for a preview, 16 for enhanced data |
BitsPerSample | 258 | 8 to 32, and the same depth for every sample |
Camera makers pack their own settings into raw files. DNG keeps that material rather than discarding it. It lives in DNGPrivateData, in a private IFD and in a private MakerNote. Adobe asks writers to set MakerNoteSafety so editors know whether copying it is safe.
Standard metadata sits in its normal TIFF places. EXIF tags go where TIFF and TIFF/EP put them, IPTC lives in tag 33723 and XMP lives in tag 700. Nothing here is a DNG invention, which is the point.
That digest tag is the strongest argument for DNG and the one most guides miss. Adobe stores an MD5 digest of the raw image data when a file is written. Lightroom recomputes it on demand and reports anything that no longer matches. The command sits under Library, then Validate DNG Files.
Storage does fail quietly. Bit rot flips a bit, a copy goes wrong and nothing announces it. A CR2 or a NEF gives you no way to tell, because nothing inside records what the pixels should be. A DNG does, and the older version of this page listed that under disadvantages by mistake.
Adobe never registered a media type of its own. A DNG identifies as image/tiff, because that is what it is. The Library of Congress catalogs it under the PRONOM identifier fmt/1842. It lists DNG among formats it accepts for photos.
Two questions sort out most of what is left. Answer them in order.
Install Raw Image Extension. Free from the Microsoft Store, and the end of most DNG trouble on Windows. See section 6.
Nothing is wrong. Raw photos hold measurements rather than pictures, so they need developing. Section 7 covers the rest.
Comparing raw formats? Canon CR2 files, older Canon CRW files and Sony ARW files all convert into DNG. None of them convert back.
Exporting finished photos? Photoshop PSD documents hold your layers, and PDF documents are where printed portfolios end up.
Stuck on your computer rather than your file? Our Windows fixes and macOS guides cover the system side.
New to all of this? What a file format is covers the ground underneath, and our file format guides list the rest.
Found something here that does not match your own file? Send us the exact wording on screen and we will check it against the Adobe spec.