Free tool · RAW preview · Runs in your browser
RAW to JPG
Short answer
Choose a RAW file and the tool saves the full-size JPEG that the camera stored inside it, in your browser with no upload. It does not develop the sensor data.
Nothing is uploaded. The tool takes the full-size JPEG preview that the camera stored inside the RAW file; it does not develop the sensor data.
Key takeaways
- 52 of 79 RAW files we tested held a JPEG preview (79 files from 76 camera models).
- The preview is 0.02 MP to 50.3 MP: Olympus C7070WZ gave 0.02 MP, Canon EOS 5DS gave 50.3 MP. 19 of the 34 with a known sensor size have at least 90% of the sensor's pixels.
- Small: the preview was 0.1% to 19.1% of the RAW file's size, so the JPG is far smaller than the file you started with.
- Estimated JPEG quality of the previews: 32 to 99 on the 1 to 100 scale. Cameras use their own tables, so this is an equivalent, not a setting you can change.
- It is quick: finding the preview took 10 to 117 ms per file in our run, and 37 to 122 ms in a browser for the largest files (43 MB to 64 MB).
- It is the camera's own rendering (white balance, style and sharpening already applied), not your RAW data; you cannot recover shadows or highlights from it.
Measured: which RAW types hold a preview
In our test of 79 files from 27 RAW types, 52 of 79 contained a usable JPEG. Of the 34 where the file also states the sensor size, 19 held a preview with at least 90% of the sensor's pixels; the rest held smaller previews, down to 0.02 MP.
Measured with the tool's own code (the same functions the page runs) on 79 camera RAW files from the CC0 sample collection at raw.pixls.us: 27 file types from 28 makers, from compact cameras to medium format. Every JPEG the tool extracted was then read by ffprobe and decoded end to end by ffmpeg; the size, quality and sensor figures come from the files themselves.
| RAW type | Files tested | Held a JPEG preview | Preview size range | Makers |
|---|---|---|---|---|
| 3FR | 3 | 0 | - | Hasselblad |
| ARW | 5 | 5 | 1.7 to 26.0 MP | Sony, Hasselblad |
| CR2 | 3 | 3 | 2.5 to 50.3 MP | Canon |
| CR3 | 2 | 2 | 17.3 to 24.0 MP | Canon |
| CRW | 3 | 1 | 1.4 MP | Canon |
| DCR | 2 | 0 | - | Kodak |
| DNG | 14 | 5 | 0.52 to 12.2 MP | Adobe, Fujifilm, Pentax, Ricoh, Canon, FIMI, Samsung, XIAOYI, Xiaomi, DJI, Autel, KanDao, RaspberryPi, LG |
| ERF | 2 | 0 | - | Epson |
| FFF | 1 | 0 | - | Hasselblad |
| GPR | 1 | 0 | - | GoPro |
| IIQ | 3 | 0 | - | Phase, Leaf |
| KDC | 2 | 2 | 7.1 to 12.0 MP | Kodak |
| MEF | 1 | 0 | - | Mamiya |
| MOS | 2 | 2 | 0.08 MP | Leaf |
| MRW | 2 | 0 | - | KONICA |
| NEF | 6 | 6 | 10.0 to 24.0 MP | Nikon |
| NRW | 2 | 2 | 15.9 MP | Nikon |
| ORF | 4 | 4 | 0.02 to 7.7 MP | Olympus |
| PEF | 4 | 4 | 10.0 to 39.5 MP | Pentax |
| RAF | 4 | 4 | 1.3 to 12.0 MP | Fujifilm |
| RAW | 2 | 1 | 2.8 MP | Panasonic |
| RW2 | 4 | 4 | 2.8 MP | Panasonic |
| RWL | 2 | 2 | 2.5 MP | Leica |
| SR2 | 1 | 1 | 0.27 MP | Sony |
| SRF | 1 | 1 | 0.31 MP | Sony |
| SRW | 1 | 1 | 28.0 MP | Samsung |
| X3F | 2 | 2 | 4.6 to 14.8 MP | Sigma |
Wikipedia's article on raw files says most of them contain a full size JPEG conversion used to preview the file on the camera's LCD panel. Of our 79 files, 52 held a usable JPEG (66%). Of those where the file states the sensor size, 19 of 34 were within 90% of the sensor's pixels. The claim is true for many modern bodies, and false for plenty of others.
Measured: preview size against the sensor
| Camera | RAW type | Preview | Sensor image | Share of sensor pixels |
|---|---|---|---|---|
| Canon EOS 5DS | CR2 | 8640 × 5760 | 8640 × 5760 | 100% |
| Canon EOS 40D | CR2 | 1936 × 1288 | 1936 × 1288 | 100% |
| Nikon D7200 | NEF | 6000 × 4000 | 6016 × 4016 | 99% |
| Nikon D7200 | NEF | 6000 × 4000 | 6016 × 4016 | 99% |
| Sony DSLR-A230 | ARW | 1616 × 1080 | 3880 × 2600 | 17% |
| Olympus XZ-1 | ORF | 3200 × 2400 | 3680 × 2760 | 76% |
| Pentax K10D | PEF | 3872 × 2592 | 3936 × 2624 | 97% |
| Adobe DNG Converter Canon EOS 5D Mark III | DNG | 3960 × 2640 | 3960 × 2640 | 100% |
| Samsung NX500 | SRW | 6480 × 4320 | 6496 × 4336 | 99% |
| Sony ILCE-7RM5 | ARW | 6240 × 4160 | 6656 × 4608 | 85% |
| Canon EOS 5DS | CR2 | 8688 × 5792 | 8896 × 5920 | 96% |
| Nikon D5600 | NEF | 6000 × 4000 | 6016 × 4016 | 99% |
| Pentax K-r | DNG | 4288 × 2848 | 4352 × 2868 | 98% |
| Samsung GX10 | DNG | 3872 × 2592 | 3936 × 2624 | 97% |
| DJI FC350 | DNG | 960 × 540 | 4000 × 2250 | 6% |
| Autel Robotics XB015 | DNG | 960 × 540 | 4000 × 2250 | 6% |
| Sony DSC-HX99 | ARW | 1920 × 1080 | 4928 × 3708 | 11% |
| Sony DSC-HX95 | ARW | 1920 × 1080 | 4928 × 3708 | 11% |
| Hasselblad Lunar | ARW | 1616 × 1080 | 6048 × 4024 | 7% |
| Leaf Aptus 22 | MOS | 332 × 244 | 4008 × 5344 | 0% |
| Leaf Aptus 75 | MOS | 332 × 244 | 4992 × 6666 | 0% |
| Nikon COOLPIX P950 | NRW | 4608 × 3456 | 4624 × 3470 | 99% |
| Nikon COOLPIX P1000 | NRW | 4608 × 3456 | 4624 × 3470 | 99% |
| Nikon D2Xs | NEF | 4288 × 2848 | 4320 × 2868 | 99% |
| Nikon 1 J1 | NEF | 3872 × 2592 | 3904 × 2606 | 99% |
| Nikon D2X | NEF | 4288 × 2848 | 4320 × 2868 | 99% |
| Olympus C7070WZ | ORF | 160 × 120 | 3088 × 2309 | 0% |
| Olympus STYLUS1,1s | ORF | 3200 × 2400 | 4000 × 2992 | 64% |
| Olympus E-M5 Mark III | ORF | 3200 × 2400 | 5240 × 3912 | 37% |
| Pentax K-r | PEF | 4288 × 2848 | 4352 × 2868 | 98% |
| Pentax K-1 | PEF | 7360 × 4912 | 7392 × 4950 | 99% |
| Pentax 645D | PEF | 7264 × 5440 | 7424 × 5552 | 96% |
| Sony DSC-F828 | SRF | 640 × 480 | 3360 × 2460 | 4% |
| Sony DSC-R1 | SR2 | 640 × 424 | 3984 × 2608 | 3% |
19 of 34 previews had at least 90% of the sensor's pixels. Previews below 1 MP are fine on a phone and poor on paper; 7 of the 34 were that small.
What you get: the camera's picture, not your RAW data
The preview is what the camera rendered at the moment of shooting: its white balance, its picture style, its sharpening, in 8 bits per channel. Wikipedia notes that processing from the sensor to a viewable image involves operations such as demosaicing, color translation and compression, and that a RAW developer lets you change them afterward; the preview has them baked in.
That makes it a good proof and a good file to share quickly, and a poor starting point for rescuing a dark or blown-out frame. If you need that, develop the RAW file in a RAW editor.
Rotation
Phones and cameras record which way they were held in the RAW file, and some previews do not carry that flag. In our samples the tool copied a rotation flag from the RAW container into the JPEG for 1 file so the picture shows upright.
When there is no preview
27 of our 79 files held no JPEG the tool could use: DCR, DNG, 3FR, IIQ, GPR, CRW, ERF, RAW, FFF, MRW, MEF among them. The tool says so instead of guessing. In those files the only picture is the sensor data, and a RAW developer is needed.
The tool saves the largest valid JPEG in the file and lists the others. In a few old compact-camera files that is only a thumbnail, and the table on this page shows its size so you can see when that happens.
Free tools:HEIC to JPGCompress an imageRemove EXIF data
How the preview is found
Most RAW formats are built on the TIFF layout, and others (Canon CR3, Fujifilm RAF, Sigma X3F) have their own. Rather than rely on each maker's tags, the tool walks the file looking for the start of a JPEG and then reads that JPEG segment by segment until its end marker, so a stray byte pair inside compressed data is not mistaken for an image. It keeps baseline and progressive JPEGs and skips the lossless JPEG streams that hold the sensor data themselves.
It then picks the largest picture, lists the others, and saves it unchanged. Scanning took 37 to 122 ms in a browser for files of 43 MB to 64 MB.
How the numbers were measured
The tool's own scanning code ran on 79 CC0 files; the script, the list of files and the full results are saved with the page's evidence. For each file we recorded every JPEG found, the one used, its estimated quality (from the luminance quantization table, compared with the standard table), and the sensor image size where the file states it. Each extracted JPEG was read by ffprobe and decoded by ffmpeg to the end: 52 of 52 passed.
Questions people ask
How do I convert a RAW file to JPG?
Choose the file above. If it holds a JPEG preview, the tool saves it as a JPG. It works in your browser; nothing is uploaded.
Is my file uploaded?
No. The file is read and the JPEG is taken out in your browser.
Is this the same as developing the RAW file?
No. It saves the picture the camera already rendered. Developing reads the sensor data and lets you change white balance, exposure and more; that needs a RAW editor.
Why is the picture smaller than my camera's resolution?
Many cameras store a smaller preview than the sensor image. In our test 15 of 34 previews with a known sensor size had under 90% of its pixels.
Does it lose quality?
The JPEG is saved exactly as the camera stored it, without being compressed again. The only quality limit is the camera's own preview.
Can I convert many files at once?
Yes. Choose several files; download each one or a ZIP.
Does it keep the date and camera settings?
Whatever the camera stored in the preview's Exif is kept. Use the EXIF remover if you want it gone.
How big is the file I get?
In our test the preview was 0.1% to 19.1% of the RAW file's size (6 KB to 10 MB).
Why not just open the RAW file in my photo app?
You can, and a RAW editor gives you more control. This tool is for when you need a JPG quickly, on a device without that software.
Related
Sources and how we checked
- Wikipedia: Raw image format (read 2026-10-10)
- raw.pixls.us: RAW sample database (CC0) (read 2026-10-10)
- FFmpeg Documentation: ffprobe (used to check every extracted JPEG) (read 2026-10-10)
Reviewed October 10, 2026. The measurements ran the tool's own code on 79 camera RAW files from the CC0 collection at raw.pixls.us and decoded every extracted JPEG with ffmpeg. The files and results are in data/seo/hub/evidence/2026-10-10/raw.