Rosetta stops after macOS 27. Here is what I would check in my Mac app
By Justinas Rolando, maker of MacPip
Apple says macOS 27 is the final release to support Rosetta, so Intel-only Mac apps stop running on Apple silicon Macs after it. From macOS 28, Apple says Rosetta stays only for certain older, unmaintained games. Since macOS 26.4, people have seen a notice when they open an app that relies on Rosetta, and macOS 27 lists those apps in System Settings. If your app is Intel-only, or ships an Intel-only helper or library, build it for Apple silicon now. Run lipo or file on the app and on everything inside it.
If someone opens your Mac app and sees a notice that it "will not work with a future release of macOS", that is Rosetta saying goodbye.
Apple has been clear about this for a while, and the date is getting close. Here is what it has said, and what I would check in a Mac app this week.
What Apple has said
Rosetta is the translation layer that lets Intel apps run on Apple silicon Macs. Apple's developer news post, Upcoming changes to Rosetta support for Intel-based macOS apps, sets out the timeline for makers:
- macOS 26.4 or later: people may get a system notification when they open an app that relies on Rosetta, telling them to update to an Apple silicon version.
- macOS 27: the final release to support Rosetta. Apple writes that Intel-only apps will no longer run on Apple silicon Macs after this update.
- Games: Rosetta keeps working for older, unmaintained games that rely on Intel-based frameworks.
Apple's support page, Using Intel-based apps on a Mac with Apple silicon, is a little more precise. It says Rosetta is available on Apple silicon Macs using macOS 27 or earlier, and that starting with macOS 28 it will work only for certain older, unmaintained games that rely on Intel-based frameworks. So the cut-off for ordinary apps is macOS 28, the next major release. Apple has not said when that ships, and I won't guess.
One more detail from this month. MacRumors reported on October 26 that Apple's enterprise release notes for macOS 27.2 say upgrading to macOS 27 no longer removes an existing Rosetta installation. So a Mac that had Rosetta before the upgrade can keep it, and the Intel apps keep running there for now.
What people see today
On macOS 27, there is a list. In System Settings, under General, then About, the macOS section has a Details button next to Intel-based Apps, and it shows the apps people recently used or that sit in common places. Apple's support page describes it. So a user can already see which of their apps are about to stop working, and whether yours is one of them.
If you use Activity Monitor, the Kind column shows Apple or Intel for each running process, which is a quick way to spot an Intel helper hiding behind an Apple silicon app.
What I would check in my Mac app
1. Is the app itself universal or arm64? Run lipo -archs on the main binary inside the app, in Contents/MacOS. If it says only x86_64, that's the whole problem. If it says arm64 or both, move on. The universal binary checker reads that output for you, right in the browser.
2. What about everything inside it? This is where apps get caught. A universal app can still ship an Intel-only helper tool, framework, plug-in, command-line binary or embedded runtime. Run file or lipo -archs on each one in Contents, including Frameworks, Helpers and XPCServices. One Intel-only piece can still bring up the notice.
3. Your dependencies. Old static libraries, prebuilt SDKs and bundled tools from other projects are the usual culprits. Ask the vendor for an arm64 build, or replace the dependency. A Python, Node or Electron bundle you ship needs to be the Apple silicon build too.
4. Your build settings. In Xcode, check which architectures your target builds for, and that your release build isn't pinned to Intel. Then build, notarize and test the arm64 version on a real Apple silicon Mac, not only under Rosetta.
5. Your website and your listing. Say what your app runs on, in plain words: "Apple silicon native". If you still sell an Intel-only version, say clearly that it will stop working on newer Macs, and tell the people who have it.
If you just use a Mac
Open the Intel-based Apps list in System Settings. For each app on it, check whether the maker has an Apple silicon update, and write to them if you can't tell. It costs a minute now, and it is far nicer than finding out when an app refuses to open on a new Mac.
The MacPip angle
Whether an app runs natively on Apple silicon is one of the first things people want to know, so it belongs on a listing. If you're getting your app ready, the get ready for the next macOS prompt walks a coding agent through the checks above. And listing it on MacPip is free. Listings are scanned automatically when they're submitted, and a blue tick only means MacPip checked the app on a date.
Sources
- Apple Developer: Upcoming changes to Rosetta support for Intel-based macOS apps
- Apple Support: Using Intel-based apps on a Mac with Apple silicon
- MacRumors: macOS 27.2 Stops Upgrades From Removing Rosetta (October 26, 2026)
Keep reading
- Claude Fable 5.2 and Mythos 5.2: what's new, the benchmarks, and what it means for your MacClaude Fable 5.2 and Mythos 5.2 came out on November 9, 2026. Anthropic's benchmarks as charts, the prices, what changes on a Mac, and four free tools.
- Old Developer ID certificates stop on February 1, 2027. Here is what I would do this weekApple's original Developer ID authority expires on February 1, 2027. Packages signed from it stop installing, and certificates from it stop signing. How to tell if yours is affected, and how to move to G2 before the date.
- macOS 27.3 makes Full Disk Access harder to get. Here is what I would change in my Mac appApple said on October 2 that granting Full Disk Access will take very explicit user action, and code in the macOS 27.3 beta stops denied apps from appearing in the list. What changes, who it hits, and what I would change in a Mac app now.
- Apple wrote down how App Review works. Here is what I would change before I submitApple published App Review help articles on review times, the Notes field, Bug Fix Submissions, appeals, screenshots, purpose strings and account deletion. What they say, and what I would change in a Mac app before I submit.
- The Swift Student Challenge takes Mac apps now. Here is what I would buildApple's Swift Student Challenge 2027 opens February 8 to 28 and, for the first time, takes apps for any Apple platform, macOS included. The rules, the dates, and how I would plan a Mac entry.
- macOS 27.2.1 stops curl trusting eMudhra. Here is what I would check in my Mac appmacOS 27.2.1, 26.7.3 and 15.8.3 remove five root certificates from /etc/ssl/cert.pem after the eMudhra key compromise. What changed, who it reaches, and what Mac app makers should test.
- Live Activities are coming to the Mac menu bar. Here is what I would do with my Mac appThe macOS 27.3 beta puts Live Activities in the menu bar of Apple silicon Macs, and Mac apps can start their own. What changed, the limits, and what to try first.
- Memory is making Macs dearer. Here is what I would do with my Mac appApple says memory will keep Macs short and pricier into 2027, and the cheapest Mac has 8 GB. Why that matters for your Mac app, and the checks to run this week.
- Apple now lets you talk to people who cancel. Here is what I would do with my Mac appSince November 4, App Store subscriptions can show a message or offer when someone cancels. The rules, what Apple says it does, and what to check on the Mac.
- Apple is adding two age rating questions. Here is what I would do with my Mac appFrom November 16, App Store Connect asks about shared location and dating features, and every app must answer by January 12, 2027. What changed and what to do.
- Siri AI is open to every developer now. Here is what I would do with my Mac appApple opened Siri AI to all developers in the macOS 27.3 beta. What changed, what you can and cannot ship yet, and a short plan for a small Mac app.
- Touchscreen Macs ship on November 6. Here is what I would check in my Mac appApple's first touch Macs arrive November 6. What changed, what Apple tells developers to do, and a short list of things to test in your own Mac app.
- Introducing MacPipWhat MacPip is, why I built it, how listing and launch day work, what a blue tick really means, and the real numbers from its first days.
- How to launch a Mac app: a checklist that fits on one pageWhat to do before, on and after launch day for a Mac app: signing, your page, directories, Product Hunt, Show HN and what to measure.
- How to write a one-line description that says what your Mac app doesA plain way to write the one line under your Mac app's name: name the job, cut the hype, and test it on someone who has never seen the app.
- Signing and notarization, in plain words, for people making their first Mac appWhat code signing, notarization and stapling each do, in what order, what your users see without them, and how to check your own build.
- What a dofollow link is honestly worth, from a site that offers oneWhat dofollow means, what Google says about links, why a link from a new directory is worth little today, and what to do instead of buying links.
Making apps for iPhone and iPad too? They have their own free home on iPip, MacPip's sister directory.