It looks like Final Cut Pro is not ready for macOS Tahoe 26.

[Ted_Appleseed]

Updated to macOS Tahoe 26 yesterday. I was expecting to receive updates for Apple's in-house apps from the Mac App Store. Even though there's no update, based on my past experiences, I didn't think compatibility would be a serious issue.

However, Final Cut Pro (version 11.1.1) is totally unusable. It freezes almost every few seconds. I've not experienced this after previous macOS launch day updates.

iWork suites (Pages, Numbers, and Keynotes) work well, although the app icons are not ready for Liquid Glass yet.

I know the pain of upgrading OSes on launch days, such as third-party app compatibility issues. But Apple could do better. Wouldn't it make sense to have their OWN software update ready on day 1 of their OWN new operating system? Especially for FCP since I paid $299.99 for it.

Update 9/24/25: I tried updating to v11.2 and uninstalling & reinstalling it, but the problem is not solved.

 

[chrono1081]

I'd try a reinstall if you haven't already, mine is working just fine.

 

[dedekpo]

It's terrible after the update, it freezes on every click. I tried reinstalling it and no luck. The worst part is I cannot downgrade my macOS version 😩
I'm considering moving to another video editor because work wont wait

 

[Starfia]

Heck. I used it briefly and didn't have any trouble either – the mix of reports suggests something more circumstantial – but I'm really sorry to hear it isn't working properly for some people, and I hope this thread might shed some light on what's happening.

 

[Ted_Appleseed]

It's terrible after the update, it freezes on every click. I tried reinstalling it and no luck. The worst part is I cannot downgrade my macOS version 😩
I'm considering moving to another video editor because work wont wait

I have the same issue. I tried updating to version 11.2 and reinstalling it, but nothing seems to work.

 

[Starfia]

I'm sure you have, but I hope people have tried holding option during the app's launch to try a different (or new) library, just in case it's something to do with the existing library.

And for what (little) it's worth, my one or two previous issues with an Apple pro app failing to function normally after an update were both addressed in subsequent updates.