DNG to JPG: one open format, many very different files
DNG is the closest thing photography has to a universal raw format, but a DNG from a Leica, a drone and a phone can behave very differently. Here is what is inside them and how to get a good JPG out.
Most raw formats belong to one camera maker. DNG (Digital Negative) is different: Adobe published it in 2004 as an openly documented specification, built on the same TIFF structure that photographers have used for decades, so that any camera or program could write and read raw data without reverse engineering. That openness is why you find DNG files coming out of cameras, drones, phones and conversion software alike.
It also means "DNG" tells you less than "ARW" or "NEF" does. The container is standardized, but the data inside can be untouched sensor values, partly processed values, or something closer to a finished image. Knowing which kind you have explains almost every surprise you will run into when turning one into a JPG.
Where your DNG probably came from
| Source | Typical devices | What to expect |
|---|---|---|
| Cameras that shoot DNG natively | Leica M, Q and SL bodies; Ricoh GR series; Sigma fp | Real sensor (mosaic) data. Develops like any camera raw file. |
| Cameras with DNG as an option | Many Pentax DSLRs (choice of PEF or DNG) | Same sensor data as the proprietary format, just in an open wrapper. |
| Drones and action cameras | DJI Mavic, Air and Mini series | Sensor data from a small sensor; noisy at high ISO, strong lens distortion uncorrected. |
| Smartphones | iPhone ProRAW, Samsung Expert RAW, many Android "Pro" modes | Often computational, already demosaiced ("linear") data. Handled very differently. |
| Conversion software | Adobe DNG Converter, Lightroom "Copy as DNG" | A re-wrapped copy of an original ARW, CR3, NEF and so on. |
Mosaic DNG versus linear DNG
A camera sensor records only one color per pixel through a color filter array, usually a Bayer pattern of red, green and blue. Turning that mosaic into full-color pixels (demosaicing) is the first big step in any raw developer. A mosaic DNG stores the data before that step, exactly like a proprietary raw file would. Leica, Ricoh, Pentax and DJI files are of this kind, and so are most files made with Adobe DNG Converter.
A linear DNG stores data after demosaicing. The pixels already have three color values, but the tone curve and color rendering have not been applied, so you still get raw-like latitude in white balance and highlights. Phone makers like this variant because their pipelines merge several frames, reduce noise and sharpen before the file is written. Apple ProRAW is the best-known example.
Why this matters for conversion: a developer built around a classic raw engine (LibRaw, which RAWSnap uses, or dcraw before it) is most at home with mosaic data. Phone DNGs often carry extra tags for multi-frame processing, local tone maps and semantic masks that general-purpose decoders do not interpret. When RAWSnap cannot develop the sensor data in a file, it falls back to the JPEG preview that the camera or phone embedded inside the DNG. That preview is already processed and is usually smaller than full resolution, so treat it as a quick share copy rather than a true raw development. Our phone raw guide covers when that is good enough and when to use the phone maker's own editor instead.
Converting a DNG with RAWSnap
- Open RAWSnap and choose one or several .dng files. They are read locally and never uploaded.
- Check the preview. If the image looks normal, the sensor data was developed; if it looks fully finished and you cannot recover a blown sky, you are probably seeing the embedded preview.
- Pick a preset or adjust Temp, Exposure, Highlights and Shadows.
- Use "Save for phone" for a 2048 px JPEG or "Save full quality" for full resolution. With several files open, "All as ZIP" exports the batch.
Notes by source
Leica
Leica has used DNG as its raw format for years, so M, Q and SL files are well supported across editors. Developed in a generic converter, Leica files often start out fairly neutral and low in contrast. Start with the Natural preset, add Contrast in the +10 to +20 range and a little Vibrance before reaching for a stylized look. Monochrom bodies record only luminance; their DNGs have no color to recover, so color sliders such as Temp and Saturation will have little useful effect.
The Leica D-Lux compacts are close relatives of Panasonic LUMIX models but write DNG rather than RW2. If you also own LUMIX gear, the Panasonic RW2 page has handling tips that carry over.
Pentax and Ricoh
Pentax DSLRs let you choose between the proprietary PEF format and DNG in the menu. Both contain the same sensor data; DNG simply opens in more programs without waiting for an update. If you shoot Pentax and care about long-term compatibility, DNG is the easy choice. The Ricoh GR line writes DNG only, and its files are straightforward mosaic DNGs that develop like any camera raw.
One thing does not travel: in-camera settings such as Pentax custom images or the GR's image controls are applied to the camera JPEG, not to the raw data. A generic developer will show the neutral version. Recreate a favorite look once with sliders and save it as a preset in RAWSnap so you can apply it in one tap next time; see using presets.
DJI drones
Drone DNGs come from small sensors and wide lenses. Expect two things. First, noise: aerial shots at dusk at ISO 800 and up will be grainy, and RAWSnap has no noise reduction slider, so for night or twilight shots a dedicated editor or DJI's own processing may give cleaner results. Our high-ISO noise guide explains how to minimize it at capture. Second, geometry: drone lenses rely on software distortion correction, and that correction is not baked into the raw data. RAWSnap does not apply lens profiles, so horizons near the frame edges may bow slightly. The Straighten slider fixes tilt, not curvature.
Aerial landscapes tend to have hazy distance and bright skies. Dehaze in the +15 to +30 range and Highlights around -40 are a good starting point, with Vibrance rather than Saturation to keep greens from turning neon.
Files from Adobe DNG Converter
Adobe DNG Converter is free and turns proprietary raw files into DNG. People use it for archiving, or when an older version of Lightroom or Photoshop does not support a new camera: converting with the current DNG Converter produces a file the old software can open. A few settings decide what you get:
- Compression. Lossless compression keeps every value and is the normal choice. Lossy compressed DNG is much smaller but discards data and stores demosaiced pixels, so it is better for proxies than for masters.
- Embed original raw file. Stores the original ARW, CR3 or NEF inside the DNG so it can be extracted later. Safe, but the file roughly doubles in size.
- Compatibility. Newer DNG versions add options such as JPEG XL compression. Older readers may not understand those files, so choose a conservative compatibility setting if the files must open in older or third-party software.
Whether converting your whole library to DNG is worth it is a separate question, covered in archiving raw files.
When a DNG won't open or looks wrong
- Looks finished and has little latitude: you are seeing the embedded preview, common with phone DNGs. Use the phone's editor or Lightroom for real raw development.
- Error on open: the file may use compression or tags newer than the decoder supports, such as JPEG XL in recent DNG versions, or it may be truncated from an interrupted card transfer. Re-copy it from the card, or re-convert with a conservative compatibility setting.
- Strong color cast: some DNGs carry unusual as-shot white balance data. Correct with Temp and Tint; the white balance guide has a quick method.
- Curved horizons or dark corners: missing lens corrections, typical of drones, phones and compact zooms. Use an editor with lens profiles if that matters for the shot.
Is DNG "better" than a proprietary raw?
Image quality is the same; the data is the same sensor data. The advantages are practical: an open specification that any developer can implement, wide support, and embedded previews and metadata that make files easier to manage. The downsides are that converting proprietary files adds a step, some maker-specific data (for example certain lens or focus information used by the camera maker's own software) may not carry over, and the maker's own converter usually will not read the converted file. If you use the maker's software, keep the originals. The raw formats comparison puts DNG side by side with the proprietary formats.
FAQ
Can I convert a DNG to JPG without uploading it?
Yes. RAWSnap decodes the DNG in your browser with LibRaw compiled to WebAssembly, and the file never leaves your device.
Why does my iPhone ProRAW DNG look the same as the JPG preview?
ProRAW is a linear, computationally processed DNG. When RAWSnap cannot develop its data, it uses the embedded preview, which is already processed. Apple Photos, Lightroom or other editors that understand ProRAW fully will give you the real latitude.
Should my Pentax shoot PEF or DNG?
Both hold the same data. DNG opens in more third-party software without waiting for updates, while PEF is the native Pentax option. If you rely on third-party editors, DNG is the simpler choice.
Does the JPEG keep my DNG's metadata?
No. RAWSnap does not copy EXIF data such as camera model, date or GPS into the exported JPEG. That is useful for privacy, especially with drone and phone files that often contain location data, but keep the DNG if you need that information.
Is lossy DNG safe for archiving?
It is fine for space-saving copies, but it discards data and stores already demosaiced pixels. For an archive master, use lossless DNG or keep the original raw file.
Open the converter