Rosetta 2 is the translation layer that lets an app built for Intel Macs run on an Apple silicon Mac. It is not an emulator in the classic sense and it is not installed by default — macOS offers it the first time you launch an app that needs it, and nothing else on the system uses it.
What It Actually Does
Intel apps are compiled for x86-64 instructions. Apple silicon executes ARM64. Rosetta translates the app’s instruction stream so the processor can run it, and translates the system calls the app makes back into the native frameworks.
The important detail is when that translation happens. Most apps are translated once, when they are installed or first launched, and the result is cached. The running app is not being translated instruction by instruction — the expensive part happened earlier. That is why the first launch of an Intel app is slow and later launches are not.
It also means Rosetta is not a virtual machine. There is no guest operating system, no separate desktop, no Windows. It runs Mac apps that were compiled for a different Mac processor.
How to Tell Whether an App Needs It
Open System Information → Software → Applications — the “Kind” column shows whether each app is Apple silicon, Intel, or Universal. Universal apps contain both builds and never touch Rosetta.
From the command line, for a specific app:
file /Applications/SomeApp.app/Contents/MacOS/SomeAppAn output mentioning arm64 means native. x86_64 only means Rosetta will be
involved.
Installing It
Normally you do not install it — the first Intel app you open triggers a prompt and macOS downloads it. If you need it without that prompt, for a script or an offline machine:
softwareupdate --install-rosettaThe --agree-to-license flag skips the interactive confirmation, which is what
you want in automation.
When to Look for a Native Alternative
Rosetta is a compatibility bridge, not a destination. Three cases where the bridge is the wrong long-term choice:
Apps that do heavy sustained computation. Video encoding, audio processing and 3D rendering run for minutes at a time inside their own code, which is exactly where translation costs accumulate. A native alternative is worth seeking.
Apps that need tight hardware integration. Anything driving a GPU or a peripheral directly is more likely to behave oddly under translation.
Anything long-lived in a workflow. An app that is Intel-only today may stop being updated entirely; a native replacement is a smaller risk than a bridge that depends on Apple continuing to ship it.
For running a different operating system rather than a translated Mac app, the tools are a different category — UTM and Parallels run actual virtual machines. Our guide to VM apps for Mac and the guide to running Windows apps on Mac cover that, and neither of them involves Rosetta.
Frequently Asked Questions
Does Rosetta slow apps down?
It adds overhead, but the amount varies enormously. An app that spends most of its time inside Apple frameworks pays little; one doing heavy computation in its own code pays more. For most apps the difference is not noticeable in daily use.
Can I remove Rosetta after installing it?
Yes, but any Intel-only app will then refuse to launch. There is no selective removal — it is one shared component. Reinstalling it is a single command, so removing it is reversible.
