Convert CR3 to JPG

Canon changed the container in 2018, and it was not a version increment. CR2 is a TIFF derivative — a format from 1986 that half the imaging world can parse — which is why software with no particular Canon knowledge could often extract something from a CR2, even if it got the colours wrong. CR3 is built on the ISO base media file format, the same structural family as MP4, with Canon’s own boxes inside it.

The practical consequence is that support for CR3 is not partial, it is binary. A program either has code written for CR3 or it produces "unsupported file type". That is why an application that has been opening your Canon files for a decade stopped the day you bought an EOS R body, and why updating the application — not converting the file — is the only thing that fixes it inside that program.

CR3 arrived with the EOS M50 and became universal across the mirrorless line: the R, RP, R5, R6, R7, R8, R10 and R50, plus the later DSLRs including the 90D and 250D. If your camera is a Canon bought since about 2019, it is writing CR3.

Everything earlier writes CR2 — the 5D series through the Mark IV, the 6D, 7D, 80D and the Rebel line of that era. The two file types are frequently mixed on one drive by anyone who upgraded a body and kept the old one, which is exactly when the compatibility difference surfaces, because half the archive opens and half does not.

Inside every CR3 the camera has written a finished JPEG, produced by its own processor at the instant of capture and, on almost every body, at the full pixel dimensions of the sensor. It is what the rear screen displays, what a card reader’s file browser shows as a thumbnail, and what this converter pulls out.

It is not the sensor data. The 14-bit readings that give raw its latitude are still in the file and are untouched by this — the converter never decodes them. What you receive is Canon’s own rendering with the picture style you had loaded, which for looking at, sending and uploading is precisely the picture you approved on the back of the camera.

The extraction works on CR3 for a slightly unusual reason. It does not parse the container at all. It scans the file for JPEG start markers, validates each candidate, and keeps the largest by pixel count above 640 by 480, discarding the small thumbnails cameras also embed.

A parser that walked TIFF image file directories would handle CR2, NEF, ARW, ORF and DNG and fall over on CR3 and Fujifilm’s RAF, which are laid out differently. Scanning is less elegant and it works on all seven, which is the trade that matters when the whole point of the page is that your existing software has a container it cannot read.

Canon uses the CR3 container for two different things: full raw and C-RAW, a compressed variant that produces files roughly forty per cent smaller with a small quality cost that most people never see. Both have the .CR3 extension and both open the same way in software that supports them.

For this conversion the distinction is irrelevant, because the sensor data is not read. Whether it is full raw or C-RAW, the embedded preview beside it is an ordinary JPEG of the same dimensions, and that is what comes out.

Canon’s Digital Photo Professional handles CR3 and is free with the camera. Adobe Lightroom and Camera Raw support it in current versions. The registry behind this site lists both of those for CR3 and notably not darktable, which is the difference from CR2 — open-source raw support arrives later for a proprietary container that had to be reverse-engineered first.

If you plan to keep shooting on this body, updating to software that reads CR3 is the right answer, and converting is the stopgap. If the CR3 files are a one-off — a wedding photographer’s delivery, a batch from a friend’s camera — extracting the JPEGs and getting on with it is entirely reasonable.

A blown highlight stays blown. A shadow lifted three stops falls apart. White balance set wrongly in the camera is baked in, and correcting it in an 8-bit JPEG shifts the colours in a way that correcting it against 14-bit sensor data does not.

That is the trade, and it is the entire reason to keep the CR3 rather than delete it once you have the JPG. Converting takes nothing away from the original file — it only produces a second one — so there is no reason to treat this as a migration.

Drop the whole selection. Each file is scanned in turn with its own progress, and the finished JPGs can be taken together as a ZIP. Because there is no decoder to run — the JPEG is already there, it just has to be found — this is fast even on a laptop that would struggle with a raw developer.

The free tier accepts up to 100 MB per file. A 45-megapixel EOS R5 CR3 runs around 45 MB and a C-RAW frame considerably less, so the ceiling is not something you will meet.

Everything happens in your browser: the file is read locally, scanned locally, and the result is written locally. Nothing is transmitted, and you can check that rather than take it on trust — open the developer tools, watch the network tab during a conversion, or pull the network connection and see the page keep working.

For anyone converting a paid shoot, an embargoed product, or photographs of their own family, that is a materially different proposition from uploading the files to a site whose retention policy is a paragraph nobody reads.