Apple will wind down Rosetta support for Intel-only macOS apps (what changes for teams)
Apple says macOS 27 will be the final release to support Rosetta. If your macOS app is still Intel-only, users on Apple silicon will first see warnings (macOS 26.4+), then lose compatibility. This is a release-cadence and revenue risk, not a ‘nice to have’ refactor.
Original post (source): Apple Developer News - “Upcoming changes to Rosetta support for Intel-based macOS apps” (September 1, 2026)
The gist
Apple is closing out the Apple silicon transition: macOS 27 is the final release to support Rosetta. If your macOS app still relies on Rosetta (Intel-only), this becomes a hard deadline.
What Apple is signalling (and why it matters)
- macOS 26.4 or later: users may see a system notification when launching apps that rely on Rosetta.
- macOS 27: Intel-only apps will no longer run on Apple silicon after the update.
In practice, this creates two risks:
- Support load spikes first (users asking why they are seeing a warning, or why the app “suddenly got worse”).
- Revenue and retention risk later (the day macOS 27 lands and Intel-only builds stop working on Apple silicon).
What to do (tiny wins)
- Treat “universal binary shipped” as a growth task, not a platform chore. Put it on the same plan as your next major campaign.
- Add one customer-facing comms path now. A short in-app message, release note, or help-center snippet that says “update to the latest version to stay compatible with macOS updates”.
- Run a dry-run build + distribution check this week. The point is to surface build pipeline issues early (signing, dependencies, CI, notarization).
Want help with ASO?
If you want this implemented for your app, check out our services - or run your workflow in APPlyzer.