Apple Sets macOS 27 as Rosetta's Final Full Release

Apple sets the release where general Rosetta support stops

Apple told developers on Sept. 1 that macOS 27 will be the final release to fully support Rosetta, the translation layer that lets Intel-built Mac apps run on Apple silicon. Starting with macOS 26.4, Macs will show a system notification when a user launches an Intel-only app, prompting them to look for an Apple silicon version. Apple carved out one exception: Rosetta will keep working for "older, unmaintained gaming titles that rely on Intel-based frameworks," even after general support narrows. Developers who want to drop Intel entirely now were told to set their Xcode build architecture to arm64 only and resubmit; those who want to keep serving both architectures were told to ship a universal binary instead.

The support page fills in the version the developer note left out

Apple's own consumer-facing support article on Rosetta adds the detail the developer note doesn't spell out: "Rosetta is available for any Mac with Apple silicon using macOS 27 or earlier," and starting with macOS 28, "Rosetta functionality will be available only for certain older, unmaintained games that rely on Intel-based frameworks." Read together, the two pages describe one timeline: macOS 27 is the last version where a typical Intel-built app, not just a game, keeps running, and macOS 28 is where general support actually ends.

Milestone	What happens	Apple's source
macOS 26.4	Notifications appear when launching Intel-only apps	Developer News
macOS 27	Last release with full Rosetta support for ordinary apps	Developer News, Support article
macOS 28	Rosetta narrows to older, unmaintained games only	Support article

A documentation mixup, caught and named

That consistency wasn't always there. MacObserver's Mike Peterson reported on Sept. 12 that a separate Apple developer-news page, dated Sept. 9, had told developers that "macOS 26 is the final release supporting Intel Mac computers and Rosetta, macOS 27 will be Apple silicon only," a full version ahead of what the Sept. 1 note said. Peterson wrote that Apple had not published a correction or said which page was authoritative, an eight-day gap between two developer announcements that disagreed on a version number developers need to plan hardware support around. By the time this article checked the same page Apple's developer-news system now shows the macOS 27 timeline, matching the Sept. 1 note and the support article, whether because Apple corrected it or because the page was retired and its identifier reused is not something Apple's own site says. Peterson's report, published three days after the version he flagged went live, is itself the only record that the macOS 26 claim existed at all; nothing on Apple's site links back to it or acknowledges it was ever posted.

What the gaming exception actually preserves

The carve-out for "older, unmaintained gaming titles that rely on Intel-based frameworks" is narrower than it sounds. Apple's support article ties the exception specifically to games, not to any Intel-only app a user still depends on, so a small studio's discontinued accounting tool or a niche audio plug-in gets no equivalent grace period once macOS 28 ships. The distinction matters because gaming libraries tend to sit on middleware, physics engines and DRM layers that are expensive to rebuild for a platform where the original publisher may no longer exist, while most professional software is still maintained by a company with a reason to ship an Apple silicon build. Apple did not say how it will technically distinguish a qualifying game from any other Intel-only app when macOS 28 enforces the narrower rule, only that the distinction will exist.

What a version-number mixup costs a developer

A discrepancy like this is not cosmetic for a small Mac software shop. A developer planning to keep an Intel build alive through macOS 27, based on the Sept. 1 note, would have shipped a dead app to some users a full release early if they had instead trusted the Sept. 9 page. Apple's guidance already puts real work on developers either way: the company's own porting documentation asks teams that have already gone Apple silicon-only to "reach out to users directly" and encourage them to upgrade before macOS 26.4 ships, without saying how many users that affects or what share of the installed base is still running Intel hardware. That gap sits next to a related one on the software side: Homebrew 7.0.0 dropped support for macOS 10.15 and moved Intel Macs to a lower support tier earlier this month, a separate project making its own call about how much longer Intel hardware is worth maintaining for.

What would change this read

The number Apple has not published is how many Macs still in daily use are Intel-based six years after the Apple silicon transition began with the M1 in 2020. Without that figure, there's no way to tell whether the macOS 26.4 notification is warning a handful of holdouts or a meaningful share of the installed base. Apple's silicon roadmap keeps moving regardless: the same reverse-engineered fix that nearly tripled the M3's Neural Engine bandwidth is evidence the current chips still have headroom nobody outside Apple has fully mapped, which makes six-year-old Intel hardware an even harder sell to hold onto.