Apple Confirms Rosetta Retirement Timeline: Intel App Support Ends After macOS 27

Rosetta's Historical Mission Is Coming to an End

In 2020, Apple launched its landmark transition from Intel chips to its own Apple Silicon. To ensure the vast library of Intel-based apps could run smoothly on new Mac hardware, Apple introduced the Rosetta 2 translation layer — a technology that dynamically translates Intel (x86_64) instructions into Apple Silicon (ARM) instructions at runtime, enabling seamless compatibility with older apps.

Now, in its latest developer announcement, Apple has made clear that this multi-year transition is nearing its conclusion. As previewed at last year's WWDC, support for Rosetta is entering its final countdown. macOS apps that still rely on Intel frameworks and have yet to complete migration will soon be left behind.

Rosetta 2 operates in two phases: Ahead-of-Time (AOT) translation and Just-in-Time (JIT) translation. When a user first installs or launches an Intel app, the system automatically translates the x86_64 binary into ARM machine code in the background and caches it locally — subsequent launches use the cached version with virtually no additional overhead. For dynamic code that can't be translated ahead of time, the system falls back to JIT translation in real time. This design meant that many Intel apps actually ran faster on Apple Silicon Macs than on original Intel hardware, which led some to underestimate the urgency of native migration and gave certain developers justification to delay. Rosetta 2's impressive performance was both a testament to Apple's transition strategy and, paradoxically, part of the reason a final push is now necessary.

Rosetta Retirement Timeline: Two Key Milestones

Apple has provided a clear retirement roadmap. Both developers and users should take note of the following two milestones.

macOS 26.4: System Begins Issuing Warning Notifications

Starting with macOS 26.4 and later, when users launch an app that relies on Rosetta, the system will display a notification alerting them that the app needs to be updated to a native Apple Silicon version. This is Apple's first warning shot — the app will still run, but it will be flagged as "soon to be obsolete."

macOS 27: The Last Version to Support Rosetta

macOS 27 will be the final release to support Rosetta. After that, Intel-only apps will no longer run on Apple Silicon Macs. macOS 27 is expected to ship this fall, leaving developers with a tight window to complete migration.

It's worth noting that Apple has carved out one exception: legacy games that depend on Intel frameworks and are no longer actively maintained will continue to receive Rosetta compatibility support. This decision reflects Apple's commitment to preserving the classic gaming ecosystem and preventing large numbers of older titles from becoming completely unplayable due to the technology transition.

Developer Migration Guide: Strategies for Different Scenarios

Apple's announcement includes clear action guidance, with the core goal of ensuring apps remain available while preventing users from being repeatedly interrupted by system warnings.

Apps Not Yet Adapted for Apple Silicon: Start Migrating Now

If your app hasn't been adapted for Apple Silicon, Apple's advice is straightforward — start migrating immediately. The recommended approach is to build and distribute your app as a Universal Binary, a format that runs natively on both Apple Silicon and Intel-based Macs. This ensures a great experience for users on new hardware while still supporting those who haven't upgraded.

Apple provides a range of migration resources, including official documentation on "Optimizing Your App for Apple Silicon," a porting guide for "Porting Your macOS Apps to Apple Silicon," and technical support on the developer forums. For most apps built with Xcode, generating a Universal Binary typically requires only a change to build settings — a manageable amount of work.

Universal Binary is Apple's core distribution format for architecture transitions. It works by packaging binaries compiled for different CPU architectures into a single executable file, letting the operating system automatically select and run the appropriate native code at launch. Apple first introduced this format during the PowerPC-to-Intel transition (also called Universal Binary at the time), and carried it forward for the Apple Silicon migration with support for both x86_64 and ARM64. For Xcode developers, the change usually involves setting "Architectures" to "Standard Architectures (arm64, x86_64)" in the Build Target settings and recompiling — the overall effort is relatively low. The main challenges tend to involve whether third-party libraries and frameworks also provide ARM64 builds, and compatibility testing for ARM-specific instruction set behavior.

Apps That Already Have a Native Version: Drive Users to Update

If your app already has a native Apple Silicon version, there are no technical blockers — the key challenge is on the user side. Apple recommends that developers in this situation proactively reach out to users and encourage them to download and install the latest native version.

This matters for two practical reasons: it prevents users from seeing repeated system warning notifications starting in macOS 26.4, and it ensures that when macOS 27 ships, apps don't suddenly stop launching because users are still running the old Intel build. Software migration isn't just about compilation — it encompasses the entire chain of version distribution and user communication.

The Strategic Wisdom Behind Apple's Architecture Transitions

Looking back, Rosetta's role is a textbook example of Apple's approach to platform transitions. This isn't the first time Apple has used a translation layer — when moving from PowerPC to Intel, Apple deployed the original Rosetta. This strategy of "providing a transitional bridge, then gradually removing it" has allowed Apple to overhaul its underlying hardware while keeping its vast software ecosystem intact.

Since its debut in 2020, Rosetta 2's exceptional translation performance allowed many Intel apps to run smoothly even without optimization, dramatically easing the pain of the early transition. Announcing its retirement now is a signal that the Apple Silicon ecosystem has matured sufficiently — the vast majority of mainstream apps have long since completed native migration, and the translation layer has largely fulfilled its purpose.

For the broader industry, this is also an instructive signal: the success of a technology transition depends not just on the merits of the new architecture itself, but on how thoughtfully the existing ecosystem is handled. By providing roughly five years of transition time, a clear and well-communicated timeline, and flexible handling of edge cases, Apple has given both developers and users ample room to adapt.

Apple's three major CPU architecture transitions share a remarkably consistent rhythm: from Motorola 68k to PowerPC in 1994, from PowerPC to Intel in 2006, and from Intel to Apple Silicon in 2020. Each followed a three-phase pattern: "introduce a compatibility translation layer → roughly two-year transition period → officially end support for the old architecture." By comparison, the Apple Silicon transition has stretched to approximately five years — far longer than either of its predecessors. This reflects both the richer ARM-native resources available thanks to the mature iPhone/iPad ecosystem, and the greater scale and complexity of enterprise and professional software accumulated during the Intel era. The original Rosetta was retired alongside macOS 10.6 Snow Leopard (2009), roughly three years after the last PowerPC Mac shipped; the Rosetta 2 retirement follows a similar timeline, consistent with Apple's long-standing approach to pacing these transitions.

Conclusion

The retirement of Rosetta marks the formal conclusion of Apple's Apple Silicon transition. For developers, this is a critical final window to complete migration — whether that means building for Apple Silicon from scratch or driving existing users to upgrade to a native version. Acting sooner rather than later is essential to avoid being caught off guard when macOS 27 ships. For everyday users, keeping apps up to date is the best way to ensure an uninterrupted experience. The era of Intel Mac is slowly drawing to a close.