What Is a RAW Photo? DNG vs JPEG on Android Explained

A RAW photo is the unprocessed data straight off your camera's sensor, saved before the phone turns it into a finished JPEG. On Android that file is almost always a DNG. It's several times larger than a JPEG, looks flat until you edit it, and isn't ready to post — but it holds information the JPEG has permanently thrown away. What exactly gets thrown away, and when that matters, is the whole question behind computational photography.

What your sensor actually records

A camera sensor does not see colour. Each photosite is a light meter: it counts photons and reports a number. Left alone, a sensor produces a grayscale image.

Colour comes from a colour filter array glued over the top — on nearly every phone a Bayer array: a repeating 2×2 pattern of red, green, green, blue, with two greens because human vision is most sensitive to green. Each photosite therefore records one colour channel and is blind to the other two.

A RAW file is that mosaic saved as-is: one number per photosite, at 10 to 14 bits, and — critically — linear, meaning the value is roughly proportional to the photons that hit that spot.

Turning it into a picture requires demosaicing: estimating each pixel's two missing channels from its neighbours. A good guess, but a guess — and every step after it is another. A JPEG is the record of your camera making all of them, then discarding the evidence.

What the ISP throws away when it bakes a JPEG

Between the sensor and your gallery sits the image signal processor, running roughly this order: demosaic, white balance, tone curve, colour matrix, noise reduction, sharpening, a squeeze from 12-bit to 8-bit, then lossy compression. Three of those steps are one-way doors.

The bit-depth crush. A 12-bit RAW channel holds 4,096 brightness levels; an 8-bit JPEG channel holds 256. Around 94% of the tonal steps are gone before you open an editor — which is why pushing a JPEG's exposure bands the sky.

The baked-in decisions. White balance, the tone curve, noise reduction and sharpening are applied, then flattened into the pixel values. You can't un-sharpen a JPEG, only pile more processing on top — which is how photos end up crunchy and plastic. (See our guide to avoiding over-processing.)

The compression. JPEG is lossy by design, subsampling colour and discarding fine detail you're unlikely to miss — until you crop in.

None of this makes the ISP wrong. Its guesses are usually good, and its output is a small file you can send immediately. RAW just preserves your right to disagree later.

RAW (DNG) vs JPEG, side by side

Two of those rows do most of the real work.

White balance is the cleanest win. In a RAW file the camera's estimate is recorded as metadata but never applied, so changing it later just means picking different multipliers on untouched linear values. In a JPEG they were already applied and clipped to 8 bits, so correcting a bad guess means stretching what survived. Mixed indoor light and neon is where this rescues the most photos.

Highlight recovery is the biggest practical win. As a highlight brightens the channels don't clip together — green usually saturates first while red and blue still hold real values, so a converter can rebuild plausible colour from the survivors, typically one to two stops' worth. A JPEG mapped that area to 255 and threw the difference away. The limit matters though: if the photosite saturated in every channel, the data is gone. Nothing recovers a truly clipped highlight — which is exactly why multi-frame cameras underexpose.

What DNG is, and why Android standardised on it

Every sensor's raw output is idiosyncratic, so manufacturers each wrapped theirs in a proprietary container — Canon's CR3, Nikon's NEF, Sony's ARW — and every new model meant new decoding support.

DNG — Digital Negative — is Adobe's answer: an open, documented, TIFF-based RAW container published in 2004. It carries the sensor mosaic plus the metadata needed to interpret it: filter pattern, black and white levels, colour matrices, as-shot white balance. Android adopted it with the Camera2 API in 2014, which added RAW capture and a DngCreator class to write the file. One open format across thousands of different phones was the only workable choice.

The caveat is real: RAW capture depends on your phone exposing it through Camera2, and that varies a lot by device. Phones reporting a LIMITED or LEGACY hardware level may not offer RAW at all, and many that do offer it only on the main camera, not the ultrawide or telephoto.

Why a merged RAW burst beats a single RAW frame

Here's the point most RAW explainers miss: a single RAW frame is not automatically better than a well-processed JPEG. It carries exactly the noise the sensor produced, with none of the multi-frame denoising your stock camera quietly performs. Shoot one DNG at night and you'll often get a worse looking file than the phone's own JPEG. What one RAW frame buys you is latitude, not quality.

You get both when the frames are merged. Capture a burst, align it and average it, and random noise partly cancels while the scene signal stays put — noise falls roughly with the square root of the frame count. Because RAW values are linear, that averaging is physically meaningful arithmetic rather than a cosmetic blur, so the result keeps RAW's latitude and gains clean shadows. The mechanism is broken down in what RAW HDR+ actually is.

This is where Android's RAW apps diverge. Open Camera and ProShot save a DNG, but it's one frame, one file — no merging. Adobe Lightroom captures DNG and edits it well, but wants an Adobe account and a subscription for the full feature set. GCam ports do merge, but they're per-model builds with device-dependent results that lock you to auto exposure — a gap covered in GCam vs an AI camera app.

When to shoot RAW — and when not to

Worth it: high-contrast scenes where you're protecting a sky or a window; mixed or coloured artificial light; low-light shots you intend to edit; anything you'll print or crop into hard; and product work where colour accuracy beats turnaround.

Not worth it: fast candids, kids and pets; anything going straight to a chat; documents and receipts; and any case where you know you won't edit the file. A DNG you never open is strictly worse than the JPEG you'd have had.

If your app offers RAW + JPEG, that's the pragmatic default. RAW is a starting point, not a look — turning one into a finished photo is an editing skill, covered in making phone photos look professional.

Why SensePose

Most Android phones can hand a RAW frame to an app and then do nothing interesting with it. SensePose captures a burst of RAW frames and merges them on-device — the same multi-frame method Pixel and iPhone cameras use — so you get RAW's editing latitude and a merged file's lower noise together, on hardware that shipped without that pipeline. Feeding it is a real-time AI Pro Mode that reads the scene and sets ISO, EV, aperture and shutter live, so the burst is exposed to protect highlights before merging starts. Optional cloud steps add 2× AI upscaling and cinematic tone grading.

Pro Mode, the RAW HDR+ merge and full-resolution export are free forever, plus 10 cloud AI enhancements a month; free exports carry a small watermark that a Pro plan removes. It needs a one-time Google sign-in, after which capture and the on-device merge work offline. It runs on any Android 10+ phone at around 28 MB — though as with any RAW app, DNG capture depends on what your device exposes through Camera2. SensePose is an AI camera app, not a posing or pose-coaching app, and it's in pre-registration on Google Play, launching 2026-08-06.

FAQ

What is a RAW photo?

A RAW photo is the unprocessed data read straight off a camera's image sensor, saved before the camera converts it into a viewable JPEG. It stores one 10- to 14-bit linear value per photosite, with no white balance, tone curve, noise reduction or sharpening applied — flat-looking straight out of the camera, but far more editable than a JPEG.

Is DNG better than JPEG?

DNG is better for editing; JPEG is better for sharing. A DNG keeps 10–14 bits of linear sensor data, so white balance can be changed with no penalty and clipped-looking highlights can often be pulled back one to two stops. A JPEG is crushed to 8 bits with those decisions baked in permanently, but it's far smaller and opens anywhere.

Do RAW photos take up more space on Android?

Yes, substantially. A DNG typically runs 15–30 MB against 2–5 MB for the same shot as a JPEG — roughly five to ten times the storage. DNG is only lightly compressed and keeps every sensor reading at full bit depth, so there's no way around it. Most people shoot RAW selectively rather than for everything.

Can every Android phone shoot RAW?

No. RAW capture requires the phone to expose sensor data through the Camera2 API, and support varies widely by device. Phones reporting a LIMITED or LEGACY Camera2 hardware level may not offer RAW at all, and many that do offer it only on the main camera, not the ultrawide or telephoto lens.

Should I shoot RAW or JPEG on my phone?

Shoot RAW when you plan to edit and the scene is difficult — harsh backlight, a bright sky you want to keep, or mixed lighting where white balance is likely to guess wrong. Shoot JPEG for fast candid moments and anything you'll post immediately. A RAW file you never edit is just a larger, duller JPEG.