DNG is a type of RAW file, not RAW's opposite
“RAW” names a family of files that preserve camera capture data for later development. A camera-native RAW uses the maker's own container and metadata. DNG, or Digital Negative, uses a publicly documented container for raw image data. Adobe describes DNG as an archival format and an extension of TIFF 6.0. [1] The DNG specification defines the file structure and tags that compatible readers can interpret. [3]
So the useful question is not “DNG or RAW?” Both can hold a raw capture. The real decision is whether to keep the exact file written by the camera, a converted DNG copy, or both. That choice affects software compatibility, maker-specific metadata, storage, and your ability to revisit the original conversion later.
Conversion can change the container and some interpretation choices
A normal DNG conversion can preserve the sensor mosaic rather than create finished RGB pixels. Adobe's converter calls the mosaic option the default and says it preserves the maximum amount of data. Its linear option stores demosaiced data; the converter cannot turn that linear data back into the original mosaic. [2] Treat mosaic-to-linear conversion as a workflow choice, not a harmless filename change.
The converter can also handle metadata differently. Adobe states that a DNG may ignore some proprietary metadata, and it offers an option to embed the complete original RAW file inside the DNG. [2] The specification includes tags for the original filename and embedded original data. [3] Embedding gives one-file custody of both versions, but it increases the DNG and still requires compatible software to extract the original.
Choose the master that matches your risk
Keep the camera-native RAW when exact maker support, private metadata, or a future re-conversion matters. Use a converted DNG when every required editor reads it correctly and a documented container makes the working archive simpler. Keep both when the photographs are hard to replace, the workflow is new, or the storage saving is small compared with the cost of losing an original.
A DNG file does not guarantee identical rendering across editors. Each RAW developer can apply its own camera profile, demosaicing, noise reduction, lens correction, and defaults. Adobe positions its free converter as a bridge from supported camera-specific files to DNG, not as proof that every editor will reproduce every maker feature. [2]
Run a keep-both test before deleting anything
Copy a small, varied shoot and convert the copies to DNG. Include a high-ISO frame, clipped highlights, deep shadows, a known lens, burst frames, and any camera mode you rely on. Keep the native files read-only. Open both versions in the editor you use today and in any catalog or backup system that must index them.
Compare stored dimensions, orientation, capture time, camera and lens fields, exposure settings, white balance response, highlight recovery, noise, color, crop, and edit speed. Check that sidecars, ratings, previews, backups, and restores still work. If a difference changes your result or removes useful information, keep both. Delete a native original only after a verified backup and a repeatable DNG workflow make that risk acceptable.
Inspect the DNG header, then verify the developed export
Use the imgrove Image Size Checker to read a classic TIFF-based DNG locally. It reports the DNG version, camera name, stored dimensions, mosaic or linear storage, bit depth, and whether an OriginalRawFileData tag is present. The report reads a bounded header subset. It does not decode RAW pixels, prove that an editor supports the file, or confirm that two renders match.
Develop a representative frame and export the delivery copy as JPEG or another format required by the destination. Check its final pixel dimensions and file size, then open it in the receiving app. Keep that derivative separate from the native RAW and DNG masters so a sharing or compression job never replaces the source capture.
Camera-native RAW vs converted DNG vs embedded original
| Decision | Camera-native RAW | Converted DNG | DNG with original embedded |
|---|---|---|---|
| What you keep | The exact file written by the camera | Raw data and metadata mapped into DNG | A DNG plus the complete native file inside it |
| Main strength | Preserves maker-specific source and future re-conversion | Uses a published container supported by many editors | Keeps both forms under one file name |
| Main risk | Needs software that understands that camera format | Some private metadata or behavior can differ | Larger file and extraction depends on compatible software |
| Best default | Keep during every conversion test | Use after the real workflow passes | Use when one-file custody outweighs extra size |
Keep both files when
- The capture is valuable or impossible to repeat
- Maker-specific metadata or future software support matters
- The DNG workflow has not passed a full backup and restore test
Choose one master only after
- Every required editor and catalog opens the converted DNG correctly
- Representative difficult edits match your quality expectations
- Metadata, sidecars, backups, and restores survive the workflow
Related RAW, metadata, and delivery guides
Related imgrove tools
Read the DNG header before you choose a master
Drop a classic TIFF-based DNG into Image Size Checker to read its version, camera, stored dimensions, RAW storage type, bit depth, and embedded-original tag locally. The tool does not decode or judge the photograph, so finish the decision in your real RAW editor.
Try Image Size CheckerTry the workflow and tell us what worked, what failed, or what needs clearer guidance: hi@imgrove.com.