By ByteBot
macOS 27, announced at WWDC 2026, draws a line in the sand Apple has been approaching since 2020. Rosetta 2 — the translation layer keeping 22,000+ Intel-only Mac apps alive on Apple Silicon hardware — enters its final phase. The general-purpose version ships through macOS 27, then it’s gone. If your app still ships x86_64-only code, you have one macOS cycle to fix it before macOS 28 breaks it permanently.
What “Final Phase” Actually Means
Rosetta 2 does not disappear with macOS 27. It’s still fully operational through the fall 2026 release cycle. The cutoff is macOS 28, expected fall 2027. After that, Apple retains only a narrow carveout: “older unmaintained gaming titles that rely on Intel-based frameworks.” Everything else — enterprise line-of-business software, audio plugins, design tools, custom utilities — simply stops launching.
“Rosetta was designed to make the transition to Apple silicon easier, and we plan to make it available for the next two major macOS releases — through macOS 27 — as a general-purpose tool for Intel apps to help developers complete the migration of their apps.”
Apple
That’s a shutdown notice, not a deprecation warning.
The Scale of the Problem
The community-maintained RosettaCheck database currently tracks 22,754 Intel-only Mac apps across 5,432 machines — and that number represents only the apps users have reported. The real count is almost certainly higher. Apple started pushing in-OS warnings about Rosetta-reliant apps back in February 2026 via macOS 26.4, so this isn’t coming out of nowhere. But 22,000+ unresolved apps in mid-2026 is not a footnote problem.
The affected categories cluster around a few predictable pain points: legacy enterprise line-of-business applications, DAW plugins for Pro Tools, Ableton, and Logic Pro, older CAD and specialist design tools, and unmaintained utilities whose developers stopped shipping updates years ago. Most major consumer apps went Universal Binary in 2021-2022. This is the long tail — stubborn, often business-critical, and harder to replace.
Who Gets Hit the Hardest
Three groups are most exposed. IT administrators managing enterprise Mac fleets running proprietary or custom software face the worst-case scenario: a line-of-business app built in 2019, never updated, that just stops working in fall 2027. Audio engineers are similarly at risk — the DAW plugin ecosystem is full of small vendors, discontinued products, and apps from developers who have long since moved on. And any solo developer who shipped a Mac app in 2019-2020 and hasn’t touched it since is sitting on a ticking build target.
How to Check Your Exposure Now
If you maintain a Mac app or manage a fleet, the fastest check is a single Terminal command:
lipo -info /Applications/YourApp.app/Contents/MacOS/YourAppIntel-only output reads: Non-fat file: ... is architecture: x86_64. A Universal Binary shows both: Architectures in the fat file: ... are: x86_64 arm64. The RosettaCheck app automates this across your entire system in one scan.
For developers shipping an app: in Xcode, set Architectures to “Standard Architectures (Apple Silicon, Intel)” — that’s arm64 x86_64 — and flip Build Active Architecture Only to No. Apple’s Universal Binary guide covers the edge cases around dependencies and CocoaPods. Build, test on both architectures, and ship before macOS 28.
Apple Has Done This Before
The first Rosetta — the one that bridged PowerPC to Intel — launched in 2005 and was retired in 2011. Six years. Rosetta 2 launched in 2020 and sunsets in 2027. Seven years. Apple is not being aggressive here. By platform-transition standards, seven years is a generous window.
What’s different this time is the ecosystem scale. There were far fewer apps in 2005 than in 2020. That’s why 22,000+ Intel-only apps are still outstanding despite six-plus years of warnings. But the math doesn’t change the deadline.
You have one more macOS cycle. If an app you depend on is Intel-only and the vendor hasn’t moved, now is the time to pressure them, fork it, or find an alternative. If you’re the developer, the migration path is well-documented and Apple’s support page covers it clearly. macOS 28 won’t care about your reasons.
