Canon CR3 raw files on a Mac, and when Preview quietly gives up

You import Canon raw files and the Finder shows thumbnails, so everything looks fine. Then Preview opens one and shows an error, or shows an image that looks flat and oddly coloured compared to the camera’s own screen.

Both symptoms come from the same place: raw support on a Mac is per camera model, it ships inside macOS updates, and a thumbnail is not evidence that the raw data can be read.

Why the thumbnail is misleading

Every raw file contains two things: the sensor data, and a JPEG preview the camera generated at the moment of capture so it has something to show on its own screen.

The Finder and Quick Look display that embedded JPEG. It requires no raw decoding at all, which is why thumbnails appear instantly even for a camera macOS has never heard of. Opening the file for real means decoding the sensor data, and that needs a decoder specific to your camera model.

So a thumbnail proves the file is structurally intact. It proves nothing about support.

Check whether your Mac knows the camera

macOS keeps a list of supported cameras, and you can see what it has decided about a particular file:

mdls -name kMDItemAcquisitionModel -name kMDItemContentType photo.CR3

If it reports the camera model and a content type of com.canon.cr3-raw-image, macOS recognises the file. If the content type comes back as public.data, it does not, and it is treating the file as an unknown blob.

sips will attempt an actual decode, which is the real test:

sips -g pixelWidth -g pixelHeight photo.CR3

Real dimensions mean the raw decoder worked. An error means it did not, regardless of what the thumbnail shows.

The fix, in order

Update macOS. This resolves most cases and is the only supported route to new camera support. Apple ships decoders for new models in point releases, so a camera released after your current macOS version may simply not be known yet. System Settings, General, Software Update.

Check the model is supported at all. Apple publishes a list of cameras with raw support. A body released recently, or an unusual variant, may not be on it even in the latest macOS.

Use the manufacturer’s software. Canon’s own utility understands its own files regardless of what macOS knows, and can export a DNG or TIFF that everything else will open.

Convert to DNG. Adobe’s free DNG Converter turns a proprietary raw into an open one, and macOS has broad DNG support. This is the practical answer for an older Mac that will not be updated.

When the file will not open in anything

If the manufacturer’s own software also refuses the file, you are past a support problem and into a damaged file.

Raw files are large, and they are usually written to a card and copied off it, which gives two opportunities for truncation. Check the size against its siblings from the same shoot: raw files from one camera in one session are broadly consistent, and one that is markedly smaller was probably cut short.

ls -lS *.CR3 | tail -5

A file of zero bytes, or a fraction of the usual size, was interrupted. A file of normal size that will not decode may have damage in the middle.

Manatee reads what structure survives in a damaged image file and writes a clean copy from a duplicate, leaving the original untouched. For raw files the realistic outcome is often the embedded JPEG preview, extracted intact, which is a full-resolution image in most cameras even when the sensor data is unrecoverable. That is a considerably better result than nothing, and it is worth knowing it exists before you write the shot off. Whether a corrupted photo can be repaired covers what recovery realistically looks like for images.

The flat, wrong-looking rendering

A separate complaint: the file opens, and the picture looks duller and less contrasty than the camera’s screen showed.

Nothing is broken. The camera’s screen was showing you the embedded JPEG, which has the camera’s picture style, sharpening and colour profile baked in. The raw file is the sensor data before any of that. A raw converter applies its own interpretation, and its defaults differ from Canon’s.

This is the point of shooting raw: the decisions are yours rather than the camera’s. If you want the camera’s look as a starting point, most raw software can apply a matching profile.

Keeping raw files usable long term

Proprietary raw formats are tied to their manufacturers, and support for old ones is not guaranteed forever. If you are archiving,

• Convert to DNG for the archive, keeping the original raw alongside if storage allows.
• Store the embedded JPEG separately for anything irreplaceable, so there is a readable image even if the raw becomes unopenable.
• Verify the archive with checksums, since raw files are large and sit untouched for years, which is exactly the situation where silent corruption goes unnoticed. Verifying a file arrived intact covers the method.

Questions

Why do my CR3 files open on my newer Mac but not the old one? Different macOS versions, different decoder sets. The newer machine has support for your camera; the older one does not and will not until it is updated.

Can I rename a CR3 to DNG? No. They are genuinely different formats, not the same data with different extensions. Converting requires software that reads one and writes the other.

Preview opens it but Photos will not import it. Photos is stricter, and sometimes lags Preview by a version. Converting to DNG resolves it.

Is CR3 better than CR2? It is more efficient, storing comparable image data in a smaller file. The practical consequence for this problem is that CR3 is newer, so support for a given camera arrived later, which is why older Macs struggle with it more often.