macOS support for CR3 flies from EOS R5 mark ii

[cdel3133]

I am unable to open CR3 files from my new R5 mark ii on my Macbook pro using Preview or (Mac) Photos.

My camera is using latest firmware. My computer is using latest OS (Sequoia 15.2 (24C101)). I rebooted the computer a couple of times.

"Get info" correctly reads the file type, size, other data. However, it can't give a preview and the icon has no image.

I was able to import the CR3 files into Photos, but I cannot see previews or open them for editing. I was able to export CR3 files, but not jpgs, from Photos.

I am able to open the files (including the ones exported from Photos) using Canon's Digital Photo Professional 4.

In researching the problem online, I was able to download someone else's CR3 file from an R6 - it opens ok.

I realize I am probably part of a small group that buys the R5 mark ii and uses Mac Photos for editing. My previous camera was a Canon 5D mark iv and I never had problems with this computer and workflow.

EOS R5 Mark II 

[gordonsick1]

I have spent some time with Apple on this problem on February 11, 2026 and the tech support promised to send it up the line for a fix. The day after that, Apple shipped the Tahoe 26.3 update, and clearly the fix was not ready for that update. In the meantime, I've been saving my Canon R5 Mark II photos to two memory card: one gets the Compact Raw CR3 and the other gets the HEIF version of the photo. I take a lot of bird photos, so I'm forced to edit the HEIF versions to see what I want to save. When I finally get the fix for the CR3 bug, I'll reprocess the top photos from raw.

The problem seems clearly to be with Apple, since DPP 4 handles the files fine. 

Here are some interesting features of the issue for me.

• I have been doing weekly photo shoots of Compressed CR3 files with my Canon EOS R5 Mark II. My shoot from Feb 3 was processed fine in Apple Photos, but the problem first appeared when I tried to process files that I took on February 10: the problem appeared, and I worked with Apple on February 11 to find a resolution (none appeared, so they escalated the problem to a higher level, and I've heard nothing since).
• I changed nothing in my camera firmware or my Apple software (Sequoia at the time), between Feb 3 when everything worked and Feb 10 when ALL of my CR3 files failed. Something happened behind my back. It seems likely that Apple silently slipped an update onto my machine with an automatic update.
• I subsequently updated my computer to Tahoe 26.3 in a failed effort to solve the problem.
• The problem was not restricted to the latest Compressed CR3 files that I downloaded on Feb 10. I went back to earlier CR3 files (Compressed and not Compressed) and the problem suddenly appeared with them if I attempted to edit them further with Photos. I exported unmodified originals from Photos from these earlier CR3 shots and the exports showed the same problem, even though I had successfully edited them with Photos earlier.

Looking back over threads discussing Apple problems with Canon Raw photos, it seems that Apple has a history of solving the problems and then breaking them with a later update. This certainly isn't consistent with what I normally expect from Apple.

[jrhoffman75]

I checked the info for the Photos app and my computer shows an update on February 5,  2026. 

[kvbarkley]

Raw support is a separate update than photos. Usually major Photos releases are with the Major OS release. RAW support is *sometimes* updated during point releases.

[justadude]

"I blame Apple 80% for being slow to accept .CR3 and shortly after reneging, and Canon 20% for not coordinating a significant new software launch seemingly without coordinating with a major, necessary workflow partner needed by their customers.

I've stayed with Apple computers primarily because of my photography. When I've tried PCs for editing they've never been as good as Apple, until now."


Apple was not slow to accept .CR3 files.  They have been working just fine from other cameras for years.  I've been editing CR3 files on my iMac since I bought my RP back in 2019, and have continued with the R8 and R6 Mk ll.  I'm guessing that Apple had zero idea that Canon changed something in the CR3 files with the new R5 Mk ll release, until someone finally brought it to their attention - then it takes time to issue a fix. Compatibly changes on one file type from one of many companies they have to coordinate with - they can only fix so many things at a time, and adjusting one changed existing file where everything has been working fine for years doesn't quite make the top of the "Fix this immediately" list... just like it wouldn't if Windows had the same issue with this file.

Apple Vs. PC is kind of like the old Ford Vs. Chevy friendly arguments.  They are both good in their own ways.  I've primarily preferred Apple for anything media related, and would never want to go back to a PC.  But that's just me.  

[justadude]

"Looking back over threads discussing Apple problems with Canon Raw photos, it seems that Apple has a history of solving the problems and then breaking them with a later update. This certainly isn't consistent with what I normally expect from Apple."

But keep in mind that CR3 files in general have been working perfectly with Apple since at least 2019.  This is something that Canon changed inside the CR3 files ONLY with the new R5 Mk ll.  The CR3 files from all other models still are easily editable files.  Apple didn't change a thing... nor can they be expected to constantly monitor every type of existing files that other manufacturers (Canon this time) change out of the blue with no warning.  When they do find out, it takes time to get them fixed.  

[jrhoffman75]

Each camera's .CR3 file is different and it's not surprising to me that software updates are required. Even Canon DPP4 needs to be updated to accommodate new camera models.

What is surprising is that folks are claiming that it worked with Tahoe 26.3 for a while and then stopped.

Apple claimed compatibility with R5MII and R6MIII in February 2026.

https://support.apple.com/en-us/122870

Some have postulated a "behind the scenes" update of some sort. I have never heard of Apple doing that. Apple won't even install an updated OS unless it is specifically authorized (automatically or manually). 

There were updates to Photos and Preview after the February 3 date that a poster said things were working, but kvbarkley said that the compatibility is OS based and not program based.

Apparently Tahoe 26.4 will restore functionality.

[Curamantel]

Hello John, I know it doesn't sound right, but there might have been a behind the scenes update. I did not update from 26.2 and did not update the R5M2 version either. All my R5M2 files stopped working (including ones from the past that I had edited in Photos) in Apple Photos, iPad Photos and iPhone Photos. After experiencing the issue with R5M2 CR3, I then updated the R5M2 Version and also to Tahoe 26.3. R5M2 CR3 still continues to be broken after the updates. I also have a R6M2 and no problems there!

[kvbarkley]

They used to have standalone raw updates, so it is possible. Now they include them in the point updates.

(You can see this by checking out the various "Raw files supported by Tahoe" support article on the apple site.)

[justadude]

Each camera's .CR3 file is different and it's not surprising to me that software updates are required. Even Canon DPP4 needs to be updated to accommodate new camera models.

I probably should have worded part of my comment differently.  Not surprising that updates are required at all, but I simply meant that Apple isn't constantly watching for a change in the file.

What is surprising is that folks are claiming that it worked with Tahoe 26.3 for a while and then stopped.

Yeah, that didn't make sense to me either.  Of course CR3 files from other cameras were perfectly fine, but Apple doesn't backtrack on what works for things like this, then suddenly not work in the same OS version.  If something had to be turned off for a reason, it would have been in another update... 26.3._ for example, but that didn't happen.

Apple claimed compatibility with R5MII and R6MIII in February 2026.

https://support.apple.com/en-us/122870

Some have postulated a "behind the scenes" update of some sort. I have never heard of Apple doing that. Apple won't even install an updated OS unless it is specifically authorized (automatically or manually). 


While I haven't been with Apple forever (it was on and off for many years until 15 years ago when I went completely to Apple products), but I've never heard of that either.  I've always had to confirm and initiate every single update, even the most minor ones.  Conspiracy theories?  (haha).  

[Curamantel]

The latest MacOS update 26.3.1 did not fix this issue! I guess we have to wait for 26.4!