Picture Batch DNG to JPG
DNG to JPG
A DNG holds one brightness reading per photosite behind a coloured filter, plus the calibration data needed to interpret them. Turning that into a JPEG means interpolating the two missing colours at every pixel, applying the white balance the camera recorded, and mapping sensor primaries through the camera's colour matrix. All of it happens here, in this browser tab, using the same decoding library desktop raw software uses.
Drop DNG images here
DNG files — or any of PNG, JPEG, WebP, AVIF, BMP, ICO, TIFF, GIF or camera raw (CR2, CR3, NEF, ARW, RAF, ORF, RW2). Everything runs on this device.
Your images never leave this device. They are decoded and re-encoded by your own browser, and the security policy on every page blocks this site from sending them anywhere.
Lossy, no transparency, opens absolutely everywhere, small for photographs.
The standard range for photographs. Hard to distinguish from the original.
Images keep their original dimensions.
JPEG cannot store transparency. Nothing in the queue currently has transparent pixels, so this has no effect yet.
Exif is carried across where both formats can hold it. Nothing currently in the queue has any.
Every pixel gets its two missing colours interpolated from its neighbours, at the full sensor resolution. The slower and more detailed option.
The value your camera recorded when the shutter fired — what you saw on the back of the camera.
Camera, lens, exposure and capture time are written into the JPEG when those fields are present. The file details show whether GPS data exists, but coordinates are deliberately not written, and colour comes out as sRGB.
What happens to your image
Expect a much smaller file than a lossless source, at the cost of some detail.
| Property | Outcome |
|---|---|
| Transparency | Preserved: DNG images have no transparency to lose. |
| Image quality | Partly preserved: JPEG is lossy: the image is re-compressed and detail is discarded to make the file smaller. The quality control decides how much. |
| Colour | Partly preserved: Converted to sRGB. Decoding an image colour-manages it into the browser's own space, so the output is sRGB and is left untagged, which every viewer reads as sRGB. A wide-gamut source is reported before conversion. |
| Exif metadata | Preserved: Carried across if you leave metadata switched on, or removed completely if you switch it off. Camera, date and any location tag travel together. |
| Orientation | Preserved: Applied to the pixels, and the tag is reset to upright afterwards so nothing rotates the image a second time. |
This is a conversion, not a preview extraction
Some lightweight converters extract the JPEG preview stored inside a DNG instead of decoding its image data. That is fast and can look plausible, but it is not a conversion of the raw data: the preview may be smaller and already has the camera's contrast and sharpening baked in.
Here the sensor data is decoded properly. The file is unpacked, the black level is subtracted, the colour filter array is interpolated, the camera's colour matrix is applied and a tone curve is mapped, and the result is what comes out. The queue tells you the true sensor dimensions before you start, and the finished row records which decoder ran and what it did.
The embedded preview exists here only as a fallback, for the case where a file's sensor data genuinely cannot be decoded. When that happens it is labelled as the camera's preview in the row, in the result and in the ZIP manifest, because a preview presented as a raw conversion is a lie about the picture you are getting.
DNG comes in two quite different shapes
Most DNG files hold undemosaiced sensor data, exactly like a CR2 or an NEF — that is the point of the format. But DNG also allows already-demosaiced pixels, which is what some cameras, drones and converters write, and what the format calls a linear DNG. Both are handled, and the queue says which one it found before you convert.
The difference matters because a linear DNG has already had someone else's demosaicing applied. Nothing here can undo that, and nothing here needs to: the file is decoded from where it actually starts.
DNG is also the container used by Apple ProRAW and the one Adobe's converter can produce from other manufacturers' raw files. If a proprietary raw is too new for this decoder, converting it to DNG first is often a useful workaround. DNG is documented, although individual camera data and optional DNG features can still affect compatibility.
What you will not get, and why that is honest
This is a converter, not a raw editor. It applies no lens corrections, no picture style, no noise reduction beyond what the decoder does by default, and no local adjustments. A JPEG from your camera or from Lightroom will not look identical, because both of those apply a manufacturer's or a vendor's interpretation on top of the same sensor data.
The output is eight bits per channel in sRGB. A raw file holds more than that — twelve or fourteen bits, and a wider gamut — and if you need those, a raw editor writing sixteen-bit TIFF is the right tool. What this page is for is turning a folder of raw files into pictures you can send, upload and open anywhere, without them leaving your machine.
If something goes wrong
The photograph is flatter or less contrasty than the camera showed you.
You are seeing the sensor data with a standard tone curve rather than your camera's picture style. The rear screen showed a JPEG the camera had already styled.
What to do: Expected, and it is the raw file being honest. Raise the quality if you plan to edit afterwards; a raw editor is the right tool if you want the camera look back.
The colours are slightly different from your raw editor's.
Every raw converter chooses its own tone curve and colour rendering. There is no single correct answer, only different ones.
What to do: Try switching white balance from the camera's recorded value to the automatic one, which sometimes matches better. For colour-critical work, export from the editor you trust.
Converting is slower than you expected.
Interpolating colour for twenty-four million pixels is real arithmetic, and it is running in WebAssembly in a browser tab.
What to do: Set the sensor detail control to half resolution. It skips interpolation entirely — one output pixel per group of four photosites — and is several times faster at a quarter of the memory.
Questions
Is my raw file uploaded anywhere?
No. The decoder is WebAssembly served from this site and it runs in a worker on your machine. There is no upload route or server-side image processing, and the security policy blocks cross-origin connections that could carry your file elsewhere. Browser tests also verify that conversion sends no file request.
Will this replace my raw editor?
No, and it is not trying to. It has no exposure slider, no lens profiles and no local edits. It is for the job of turning raw files into ordinary images in bulk, which is a different job from developing a photograph.
Can I convert a whole card of DNG files at once?
You can add a batch, watch real per-file progress, cancel or retry individual files, and download the finished set as a ZIP with a manifest. The queue caps concurrency from the device profile, and browser memory is the practical limit; very large batches are safer in smaller groups.
Why is the JPEG so much smaller than the DNG?
Because a raw file stores sensor readings at twelve or fourteen bits with little or no compression, and a JPEG stores an eight-bit picture with a lot of it. A 25 MB raw file becoming a 4 MB JPEG is the format working, not detail going missing unexpectedly.