Convert Canon CR3 to JPG
CR3 is what current Canon bodies write. Drop the files in and they are decoded here, not on a server.
Options
All processing runs in your browser. No file leaves this device.
Canon introduced CR3 with the EOS M50 in 2018 and it is now what every current body writes — the R, RP, R5, R6, R7, R8, R10, plus the 90D and 250D. It replaced CR2 entirely, and the two are not interchangeable: CR3 uses an ISO Base Media container, the same family as MP4 and HEIF, rather than the TIFF structure CR2 was built on. Software that reads CR2 fine will often reject CR3 outright.
That container change is why CR3 support arrived late in a lot of open-source tooling, and why an older copy of Lightroom or a NAS thumbnailer may show your files as unreadable. LibRaw added it in the 0.20 series, and this converter uses a build well past that point.
If you shoot C-RAW rather than standard RAW, those files are also CR3 — C-RAW is a lossy compression option inside the same container, roughly halving the file size. It decodes here the same way; the only difference is that some fine detail was discarded in-camera and cannot be recovered by any converter.
What happens on conversion: LibRaw demosaics the sensor mosaic with adaptive homogeneity-directed interpolation, applies the white balance your camera recorded at capture, and hands back 16-bit linear data. That linear buffer is then encoded to sRGB — the gamma encoding every display expects, applied correctly rather than approximated. Because the whole path stays in floating point until the final encode, there is no intermediate 8-bit step to quantise away highlight detail.
Your files never leave this device. The decoder runs as WebAssembly inside this page, so there is no upload step and no server that could retain a copy. With RAW this is not just a privacy point — it is why the tool is usable at all, since uploading a card full of 30 MB files over a home connection would take longer than the shoot did.
Common questions
- Why will my older software not open CR3 files?
- CR3 moved to a completely different container format from CR2 — ISO Base Media rather than TIFF. Applications written before roughly 2019, and anything that has not updated its RAW library since, have no decoder for it even though they handle CR2 perfectly.
- Does it handle C-RAW as well as standard RAW?
- Yes, both are CR3 files and both decode here. C-RAW applies lossy compression in-camera to roughly halve the file size; the detail it discarded is gone before the file ever reaches a converter, but everything else works identically.
- Are my CR3 files uploaded to a server?
- No. Decoding and encoding both run in your browser via WebAssembly. Nothing is transmitted. You can verify it in the Network tab of your devtools during a batch, or by disconnecting from the internet once the page has loaded — the tool keeps working.
- How many files can I convert at once?
- There is no limit in the tool. RAW files are large, and each one is decoded to a full floating-point buffer, so memory is the real constraint. Batches of a few dozen are comfortable on a typical laptop; for a whole card, work through it in groups rather than dropping a thousand files at once.
This converter is part of a full editing pipeline — tone, colour, lens correction and batch export all run the same way, without uploading.
Open the full pipeline