What Is a CR3 File?

The useful way to think about the format is that a JPG is a photograph and a CR3 is the reading that a photograph gets made from.

When light hits the sensor, each photosite reports one number: how much energy arrived. It has no idea what colour that light was — colour comes from a mosaic of red, green and blue filters laid over the sensor, so any individual site measures only one channel. Turning that mosaic into a full-colour image means guessing the two missing channels at every position from the neighbours, a reconstruction called demosaicing. On top of that sit white balance, tone curve, contrast, sharpening, noise reduction and colour rendering.

Shoot JPG and the camera does all of it in the instant after the shutter closes, then throws the measurements away. Shoot raw and it keeps the measurements. Every decision in that list stays open, which is the entire argument for the format: highlight detail that a JPG has already clipped is often still sitting in the raw data, and a white balance chosen badly at capture costs nothing to change later.

The price is that a raw file is not directly viewable. Something has to perform that reconstruction before there is an image to look at, and "something" means software that understands this particular manufacturer's particular format.

Here is the part that surprises people. A CR3 is not one image. It is a container holding several, and the container is a general-purpose one: the same ISO base media file format that MP4 video uses, built from nested boxes each carrying a four-character type code. Canon's raw data sits inside it in a proprietary codec, but the scaffolding is ordinary.

Open one up and you find, roughly:

The metadata blocks are worth a second look. CMT1, CMT2 and CMT4 are each a self-contained little-endian TIFF structure, which is to say Canon stores your Exif using the same tag layout that has described photo metadata since the 1990s and is still maintained as a published standard. That is why a converter can move exposure information from a CR3 into a JPG intact: both ends speak the same dialect.

The full-resolution JPEG is the detail with the most practical consequence. Your camera has to render the shot anyway — to show it to you on the rear screen — so it writes that rendering into the file at full size, complete with the picture style and white balance in force when you pressed the shutter. That image is a real, ordinary JPEG sitting inside a file most software claims it cannot read.

Canon used CR2 from 2004 until the EOS M50 arrived in April 2018 carrying the new format. The EOS R followed that September, and CR3 has been standard on Canon bodies since.

Two changes matter to anyone handling the files. The first is structural: CR2 was a TIFF-based format, CR3 moved to the ISO container described above. That is invisible in use but it is the reason software support had to be written again from scratch rather than extended — and the reason a program can happily open a CR2 from 2010 while refusing a CR3 from a camera released last year.

The second is C-RAW, an option the format introduced. Choose it in the menu and files come out roughly 30 to 40 percent smaller than the standard setting for the same shot, at the same pixel dimensions. The saving is real and the mechanism is a wavelet transform with a quantisation step, which means — unlike the standard setting — some information is genuinely discarded. Whether that matters is a fair question, and it has been tested: DPReview's examination found the difference invisible in normal use, with faint artefacts appearing only when shadows were pushed about four stops. Most photographers can shoot C-RAW without thinking about it. If your work routinely involves rescuing badly underexposed frames, shoot the standard setting.

One naming trap: CRM, not CR3, is what Canon's Cinema RAW Light video files use. They share family resemblance and neither is a still photograph you can convert with a photo tool.

The frustrating thing about raw compatibility is that it is not one problem with one fix. Support is granted per camera model, not per format, and it arrives through several independent channels.

Apple builds raw support into macOS, iOS and iPadOS as a system-level feature, and publishes the list of exactly which cameras each OS release understands — the EOS R5, R6, M50 and M50 Mark II are all named there. Microsoft ships support for Windows as a separate Raw Image Extension you install from the Microsoft Store, after which File Explorer and Photos can render thumbnails. Adobe adds models in Camera Raw updates. Canon's own Digital Photo Professional handles its own cameras from the start.

Every one of those lists is versioned. That is what produces the experience people find maddening: the same file opens on the laptop and not on the desktop, or opened fine last year and fails for the camera you bought last month. The format did not change. The list your software was compiled against did.

Getting a CR3 file to open is therefore mostly a question of which platform you are on and how recently it was updated — which is why that has its own guide rather than a paragraph here.

Expect somewhere between 20 MB and 60 MB per frame on a modern Canon body, against two or three megabytes for a JPG of the same shot. Three things drive that.

Bit depth is the first. A JPG stores 8 bits per channel, giving 256 possible levels; Canon's raw files carry up to 14, which is 16,384. Most of that extra resolution lives in the shadows and highlights, exactly where editing latitude is decided.

Sensor resolution is the second, and it multiplies. The third is the embedded JPEG and previews described above — you are carrying a complete conventional photograph inside every raw file, which is a few megabytes of the total on its own.

The practical consequence is downstream rather than on the card. A 45-megapixel frame converted at full size and high quality is still an eight-megabyte JPG, which is far too heavy to email or put on a web page. Conversion and compression are two separate steps, and skipping the second is the usual reason a "converted" photo still will not upload. Compressing the output afterwards is the fix.

Which route you want depends on what you are trying to achieve, and the honest answer is that most people need only the first one.

You want shareable pictures. Extract the camera's own rendering and re-encode it as a JPG. Nothing is installed, nothing is uploaded, and a card's worth of frames takes a couple of minutes. The step-by-step guide is here.

You want to see the photos on this computer. That is a platform question — a Windows extension, an OS version, or a viewer that reads the format. The per-platform routes are here.

You want to edit properly. Develop the raw data in software built for it: Canon's Digital Photo Professional is free for owners of its cameras, and Lightroom, Capture One, darktable and RawTherapee all handle current Canon bodies. This is the only route that buys you the highlight recovery and white-balance freedom the format exists for.

You are deciding what to shoot in the first place. That trade-off — card space and workflow friction against editing latitude — is set out side by side here.

Something has gone wrong. Conversions that fail, files that produce errors, thumbnails that stay blank: the failures that actually happen have their own guide.

One rule cuts across all of them: keep the raw files. A JPG is a decision made permanent, and once you have discarded the CR3, the measurements it held are gone for good. Storage is cheap and re-shooting is not.