Convert Canon CR2 to JPG
Drop in your CR2 files. A shoot's worth of 25 MB files converts locally, at whatever speed your CPU manages.
Options
All processing runs in your browser. No file leaves this device.
CR2 is Canon Raw version 2, the format Canon wrote from the EOS-1D Mark II in 2004 until the CR3 transition around 2018. If you shoot a 5D Mark II, III or IV, a 7D, a 6D, a 70D or an 80D, your files are CR2. It is built on the TIFF container, which is why some tools can extract the embedded preview from a CR2 without understanding the sensor data at all — and why those tools give you a small, camera-rendered JPEG rather than a true conversion.
This converter does the real thing. It decodes the sensor mosaic rather than pulling out the embedded preview, so the output is at full resolution and comes from the 14-bit capture rather than from an 8-bit thumbnail the camera made. That distinction is worth checking whenever a converter seems suspiciously fast.
Canon's own Digital Photo Professional does an excellent job of this and is free, but it is a desktop install, it is Windows and macOS only, and it is not what you want when you are on a borrowed machine and need six files as JPGs right now. That is the situation this page is for.
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
- Does this work with CR3 files as well?
- CR3 is a different container and has its own page. Canon switched to it around 2018 with the EOS M50 and the R series. If your files came from an EOS R, R5, R6, M50 or 90D, use the CR3 converter instead — though the general RAW page accepts both.
- Is this the same as extracting the JPEG preview from the CR2?
- No, and the difference matters. Every CR2 contains a camera-rendered JPEG preview, and some converters simply pull that out — it is nearly instant but gives you the camera's rendering, sometimes at reduced resolution. This tool demosaics the actual sensor data at full resolution.
- Are my CR2 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