Intel Macs and macOS 27: What the End of Support and Rosetta Means

macOS 27 Golden Gate shipped on September 14, 2026, and it does not install on any Intel Mac. Rosetta 2 is a separate deadline. It is the translation layer that lets Apple silicon run x86_64 binaries, and it survives one more release. If you own an Intel Mac, you stay on macOS 26 Tahoe. If you own an M-series Mac, you have one OS cycle to find and replace every Intel-only app, driver, and helper tool.

Quick Takeaways

• Intel Macs cannot install macOS 27. Tahoe (macOS 26) is the last supported release for Intel hardware.
• Intel Macs keep getting security patches. Apple said those systems will continue to receive security updates for three years, which puts the end date around fall 2028. They get no new features.
• Rosetta 2 works fully in macOS 27, then shrinks. General-purpose Rosetta 2 support ends with macOS 28, expected in fall 2027.
• After macOS 28, Rosetta covers two niches only. A limited version remains for Intel binaries in Linux virtual machines and for a subset of older games that rely on Intel-based frameworks.

Timeline: Intel Support and Rosetta by macOS Release

The security-update window comes from Apple’s WWDC 2025 statement. Apple has not published a per-release patch calendar, so treat 2028 as an estimate.

Which Intel Macs Are Affected

Every Intel Mac is excluded from macOS 27. Apple’s earlier statement confirmed macOS 27 requires a Mac with Apple silicon. The last four Intel models that could run Tahoe were:

• 16-inch MacBook Pro (2019)
• 13-inch MacBook Pro (2020) with four Thunderbolt 3 ports
• 27-inch iMac (2020)
• Mac Pro (2019)

Older Intel Macs were already stuck on Sequoia, Sonoma, Ventura, or earlier.

Identify your machine from the terminal:

sw_vers
uname -m
sysctl -n machdep.cpu.brand_string

• sw_vers prints the macOS version and build.
• uname -m returns x86_64 on Intel and arm64 on Apple silicon.
• sysctl -n machdep.cpu.brand_string prints the CPU model string.

What Rosetta 2 Does (and Why Apple Is Removing It)

Rosetta 2 translates x86_64 instructions to arm64. Most apps are translated ahead of time at first launch. Just-in-time translation covers code generated at runtime. The runtime is hosted by the oahd daemon, and the translated code is cached on disk.

Rosetta has been the safety net since the M1 launched in 2020. By the time macOS 28 ships, it will have lasted about seven years. Apple removes legacy translation layers on a schedule, and the original PowerPC Rosetta followed the same pattern.

Rosetta 2 only matters on Apple silicon. An Intel Mac runs x86_64 code natively and has no translation layer. If you are on an Intel Mac, Rosetta’s retirement does not affect you. Your limit is the Tahoe cutoff.

Prerequisites for the Audit

You need:

• An Apple silicon Mac (for the Rosetta audit) or an Intel Mac (for the upgrade-path decision).
• Terminal access and admin rights.
• A current Time Machine or cloned backup before any major OS upgrade.

Step-by-Step: Audit Intel-Only Software Before macOS 28

Step 1: Check Whether Rosetta Is Installed and Running

pgrep -q oahd && echo "Rosetta is active" || echo "Rosetta not running"

pgrep -q suppresses output and returns an exit code. The oahd process exists only after Rosetta has been installed and used.

Some reports say the macOS 27 installer removes Rosetta from a Mac that had it, and that apps then prompt you to reinstall it. Sources disagree on this behavior, so verify on your own machine after upgrading. Reinstall it with:

softwareupdate --install-rosetta --agree-to-license

• --install-rosetta fetches the translation runtime from Apple.
• --agree-to-license skips the interactive license prompt, which is useful in scripts and MDM payloads.

Step 2: Find Intel Apps in the GUI

Open Activity Monitor and check the Kind column. Anything marked Intel is running through Rosetta. You can also select an app in Finder, press Cmd+I, and read the Kind line. Since macOS 26.4, users opening Intel-based apps see a warning that those apps will stop working once Rosetta 2 support ends in macOS 28.

Step 3: Inventory Every Installed App from the Terminal

system_profiler SPApplicationsDataType | grep -B 6 "Kind: Intel" | grep -E "^\s{4}[^ ].*:$"

This lists the names of apps whose Kind is Intel. For a script that checks the binary architecture directly, use this:

#!/bin/bash
# intel-audit.sh: list x86_64-only apps in /Applications
for app in /Applications/*.app /Applications/*/*.app; do
  exe=$(/usr/libexec/PlistBuddy -c "Print :CFBundleExecutable" \
        "$app/Contents/Info.plist" 2>/dev/null) || continue
  archs=$(lipo -archs "$app/Contents/MacOS/$exe" 2>/dev/null) || continue
  [[ "$archs" == "x86_64" ]] && echo "INTEL-ONLY: $app"
done

• PlistBuddy reads CFBundleExecutable from the app bundle’s Info.plist.
• lipo -archs prints the architectures inside a Mach-O binary: arm64, x86_64, or both for a universal binary.
• An app showing only x86_64 will break when Rosetta leaves general use.

Step 4: Check Background Components

The riskiest items are not the apps you launch. They are launch daemons, privileged helpers, and drivers. Scan them too:

for f in /Library/PrivilegedHelperTools/* /Library/LaunchDaemons/*.plist; do
  file "$f" | grep -q "x86_64" && ! file "$f" | grep -q "arm64" && echo "Check: $f"
done

Background processes do not get a reinstall prompt. Vendors have reported that legacy print drivers and similar helpers just stop working with an unhelpful “Software is not compatible with this device” error.

Step 5: Test Under Each Architecture

arch -x86_64 /bin/zsh     # open a shell under Rosetta
arch -arm64 /bin/zsh      # open a native shell
uname -m                  # confirm which one you are in

Use this to verify whether a CLI tool runs natively or only under translation.

Architecture Comparison: Native vs. Translated

Decision Guide: What Should You Do?

Keeping Old Intel Software Alive

Option 1: Virtualize an Older macOS

You can run an older macOS guest on a newer host, and the guest keeps its own Rosetta. If your Intel-only app runs in Sonoma or later through Rosetta translation, it should run well in a VM of the same version of macOS on a host running macOS 28. Tools like UTM, Parallels Desktop, and VMware Fusion can host it. Feature coverage in guests is narrower than on bare metal. GPU acceleration and some USB passthrough are limited.

Option 2: Keep One Mac on macOS 27

Pin a single Apple silicon machine to Golden Gate for legacy work. Disable auto-upgrade on it:

sudo softwareupdate --schedule off
defaults write /Library/Preferences/com.apple.SoftwareUpdate AutomaticallyInstallMacOSUpdates -bool false

This stops automatic major-version installs on that machine, but you must still apply security patches manually.

Option 3: Linux Containers and VMs

Rosetta for Linux remains available after macOS 28. Docker and similar tools can still run x86_64 Linux images on Apple silicon:

docker run --platform linux/amd64 ubuntu:24.04 uname -m

• --platform linux/amd64 requests the x86_64 image variant.
• The output should print x86_64 if translation works.

Prefer native linux/arm64 images wherever your registry publishes them.

Repurposing an Intel Mac That Is Stuck on Tahoe

You have three sensible routes:

Many 2018 to 2020 Intel Macs have a T2 security chip. Linux can boot on them with the t2linux project’s patched kernels and drivers. Expect to handle Wi-Fi firmware, audio, and keyboard backlight configuration manually. Check hardware support for your exact model before wiping macOS.

Troubleshooting and Real-World Scenarios

Scenario 1: A Print Driver Stops Working After Upgrade

Symptom: The printer queue shows an error, and logs mention incompatibility.

1. Check for an x86_64-only filter in the driver bundle:

   file /Library/Printers/*/Contents/Filters/* 2>/dev/null | grep x86_64
   

2. Download the latest manufacturer driver. Most current drivers ship as universal binaries.
3. If none exists, switch to AirPrint or the generic IPP Everywhere driver.
4. Remove the old queue and re-add the printer.

Scenario 2: Homebrew Installs to the Wrong Prefix

Apple silicon Homebrew lives in /opt/homebrew. Intel Homebrew lives in /usr/local. A Homebrew installed under Rosetta puts x86_64 packages in the wrong place.

which brew
brew config | grep -E "HOMEBREW_PREFIX|Rosetta"

If HOMEBREW_PREFIX is /usr/local on an M-series Mac, you are running an Intel installation. Install the native version under /opt/homebrew and migrate your packages.

Scenario 3: A Rosetta Prompt Never Appears for a Helper

Command-line tools and daemons fail silently without a reinstall dialog. Pre-install Rosetta in your deployment, then test:

softwareupdate --install-rosetta --agree-to-license
pgrep -q oahd && echo OK

Scenario 4: MDM Compliance Check

Push a script to the fleet that reports Rosetta state and Intel-only apps. Pair it with an Extension Attribute in your MDM. Roll out macOS 27 first to a pilot ring, then expand once the inventory is clean.

Scenario 5: Third-Party Kernel Extensions

Apple silicon does not load legacy kexts by default. Vendors have moved to system extensions. If a tool relies on an Intel-only kernel extension, Rosetta cannot save it. Ask the vendor for an Apple silicon release.

Developer Checklist: Shipping Universal Binaries

Build for both architectures during the transition, then drop x86_64 when you no longer support Tahoe:

xcodebuild -scheme MyApp -configuration Release \
  ARCHS="arm64 x86_64" ONLY_ACTIVE_ARCH=NO build
lipo -info MyApp.app/Contents/MacOS/MyApp

• ARCHS="arm64 x86_64" builds a universal binary.
• ONLY_ACTIVE_ARCH=NO forces both slices to compile.
• lipo -info confirms both slices are present.

FAQ

Can I install macOS 27 on an Intel Mac?

No. macOS 27 requires Apple silicon, and the installer will not run on Intel hardware. The newest release an Intel Mac can run is macOS 26 Tahoe.

Is Rosetta 2 removed in macOS 27?

No. Rosetta 2 stays fully functional in macOS 27 on Apple silicon Macs. Apple’s current plan ends general-purpose support in macOS 28, with a narrow carve-out for older games and Linux VMs. Reinstall Rosetta with softwareupdate --install-rosetta --agree-to-license if an upgrade leaves it missing.

How long will my Intel Mac get security updates?

Apple said Intel Macs supported by Tahoe will receive security updates for three years. That points to roughly fall 2028. Apple publishes no firm calendar, and those updates carry no new features.

Will my Intel apps stop working on an Intel Mac?

No. Intel Macs run x86_64 apps natively, and Rosetta is irrelevant to them. Apps may stop receiving updates as developers drop Tahoe, but they will not stop launching because of Rosetta.