Next-Gen App & Browser Testing Cloud

Trusted by 2 Mn+ QAs & Devs to accelerate their release cycles

How to Install Android Emulator Mac?

To install the Android Emulator on a Mac, download and install Android Studio, open the SDK Manager to install the emulator and an Android system image, then open the Device Manager (AVD Manager) to create and launch an Android Virtual Device. On Apple Silicon (M-series) Macs, choose arm64-v8a system images so the emulator runs natively and is accelerated automatically by macOS Hypervisor.framework. You do not need HAXM, which has been deprecated and removed.

Before You Begin: macOS Prerequisites

The Android Emulator runs on Intel Macs and on Apple Silicon (M1, M2, M3, M4 and later). The setup is the same for both, but the system image architecture differs, and that one choice is what determines whether the emulator is fast or unusable. Make sure the following are in place before you start.

Supported macOS version: a current release of macOS. Android Studio publishes its own minimum, but any actively supported macOS version is fine.
Free disk space: budget at least 8 to 10 GB. Android Studio, the SDK, the emulator, and a single system image add up quickly.
Your chip type: click the Apple menu, then About This Mac. If it says Apple M-series, you will use arm64-v8a images. If it says Intel, you will use x86_64 images.
Acceleration: nothing to install. On macOS the emulator uses the built-in Hypervisor.framework. The old Intel HAXM driver is no longer required or available on modern macOS.

Method 1 - Install via Android Studio

Android Studio is the standard route and the easiest to keep updated. It bundles the SDK, the emulator, and a graphical Device Manager. Follow these steps in order.

Download Android Studio: get the macOS build from the official Android Developers site. The installer is universal and runs natively on both Apple Silicon and Intel, so you do not need to pick a separate package for your chip.
Install the app: open the downloaded DMG and drag Android Studio into the Applications folder, then launch it from there.
Run the Setup Wizard: on first launch the wizard downloads the latest Android SDK, platform tools, and the Android Emulator. Choose the Standard setup type to accept the recommended components.
Open the SDK Manager: from the welcome screen choose More Actions, then SDK Manager (or Settings, then Languages and Frameworks, then Android SDK). In the SDK Platforms tab select an Android API level to target. In the SDK Tools tab confirm that Android Emulator and Android SDK Build-Tools are checked, then apply.
Add a system image: still in the SDK Manager, expand an Android version and install its system image. On Apple Silicon choose an arm64-v8a image; on Intel choose x86_64. Pick a Google APIs or Google Play image if your app needs Google services.
Open the Device Manager: from the welcome screen choose More Actions, then Virtual Device Manager (called the AVD Manager in older versions). This is where you create and launch Android Virtual Devices.
Create an AVD: click Create Device, pick a hardware profile such as Pixel 8, click Next, and select the system image you installed. Name the device, adjust RAM and storage if needed, and click Finish.
Launch the emulator: press the play (Run) button next to your new AVD. The virtual Android device boots in a separate window, ready for you to install APKs, browse, and test.

That is the complete install. Once an AVD exists, you can relaunch it any time from the Device Manager or from the command line.

Hardware Acceleration on macOS

Acceleration is the difference between a snappy emulator and one that crawls. On macOS this is handled for you, but it is worth understanding what is happening.

Hypervisor.framework: macOS ships with Apple's own virtualization framework, and the Android Emulator uses it automatically. There is nothing to download or enable.
HAXM is gone: the Intel Hardware Accelerated Execution Manager (HAXM) is deprecated and is no longer available on current macOS or shipped with the emulator. Any older guide telling you to install HAXM on a Mac is out of date, so ignore that step.
Apple Silicon is native: M-series Macs run an arm64-v8a image as native ARM code, which is why these images are fast. Pairing an x86 image with an Apple Silicon Mac forces full CPU emulation and is the number one reason an emulator feels slow.
GPU acceleration: leave graphics set to Automatic or Hardware in the AVD settings so the host GPU renders the screen instead of software.

Method 2 - Install via the Command-Line Tools

If you want the emulator without the full IDE, for example on a build machine or in a lightweight setup, install the standalone Android command-line tools and drive everything from the terminal. After downloading the command-line tools and pointing the SDK environment variables at them, set your shell up like this in ~/.zshrc:

# Point macOS at the Android SDK
export ANDROID_HOME=$HOME/Library/Android/sdk
export PATH=$ANDROID_HOME/cmdline-tools/latest/bin:$PATH
export PATH=$ANDROID_HOME/emulator:$PATH
export PATH=$ANDROID_HOME/platform-tools:$PATH

# Reload the shell config
source ~/.zshrc

Use sdkmanager to install the emulator, platform tools, and an arm64-v8a system image (swap in x86_64 on an Intel Mac):

# Install the emulator, platform tools, a platform, and an ARM system image
sdkmanager "platform-tools" "emulator" \
  "platforms;android-34" \
  "system-images;android-34;google_apis_playstore;arm64-v8a"

Create an Android Virtual Device with avdmanager, then launch it with the emulator command:

# Create a virtual device from the installed system image
avdmanager create avd -n Pixel_API_34 \
  -k "system-images;android-34;google_apis_playstore;arm64-v8a" \
  --device "pixel_6_pro"

# Confirm it was created
avdmanager list avd

# Launch the emulator
emulator -avd Pixel_API_34

To remove an AVD you no longer need, run avdmanager delete avd -n Pixel_API_34. This command-line route produces exactly the same emulator as Android Studio, just without the GUI.

Choosing the Right System Image

Picking the wrong image architecture is the most common setup mistake on Mac. Use this as a quick reference.

Your Mac	System Image ABI	Notes
Apple Silicon (M1/M2/M3/M4)	arm64-v8a	Runs natively and is the fast, correct choice.
Intel Mac	x86_64	Accelerated by Hypervisor.framework on Intel.
Google services needed	google_apis or google_apis_playstore	Use the Play image when the app needs the Play Store.

Alternatives to the Android Studio Emulator

The Android Studio emulator is the right tool for app development, but a few alternatives suit different needs.

Genymotion: a developer-focused emulator available as a desktop app and a cloud service. It offers quick device presets and sensor simulation, and the cloud version sidesteps local resource limits.
BlueStacks: aimed at running consumer Android apps and games rather than development. It works on Mac but is not built for QA workflows or automation.
Cloud Android devices: instead of installing anything, you can run Android emulators and real Android devices in the cloud and test straight from your browser. This is the easiest way to cover many Android versions, screen sizes, and OEM skins that a single Mac cannot reproduce.

If your goal is broad test coverage rather than local development, you can run apps on TestMu AI'sReal Device Cloud of Android handsets and emulators from any Mac, with no local SDK or emulator setup required.

Common Issues and Tips

Emulator is extremely slow: you are almost certainly running an x86 image on Apple Silicon. Delete the AVD, install an arm64-v8a system image, and recreate the device.
"command not found: sdkmanager": your PATH does not point at the command-line tools. Recheck the export lines for cmdline-tools/latest/bin and reload the shell with source ~/.zshrc.
AVD fails to boot: increase the RAM allocated to the device in the AVD settings and confirm graphics is set to Automatic or Hardware rather than Software.
Out of disk space: each system image and AVD snapshot is large. Remove API levels and AVDs you no longer use from the SDK Manager and Device Manager.
Old HAXM tutorials: ignore any step that tells you to install HAXM on macOS. It is removed and Hypervisor.framework handles acceleration automatically.

Frequently Asked Questions

Do I need HAXM to run the Android Emulator on a Mac?

No. HAXM is deprecated and has been removed. On macOS the Android Emulator uses Apple's built-in Hypervisor.framework for hardware acceleration, which works automatically on both Intel and Apple Silicon Macs with no extra installation.

Which Android system image should I use on an Apple Silicon Mac?

On M-series (Apple Silicon) Macs you should download arm64-v8a system images. They run natively and are accelerated by Hypervisor.framework. x86 and x86_64 images are built for Intel and will either fail to start or run very slowly on Apple Silicon.

Can I install the Android Emulator on Mac without Android Studio?

Yes. You can install the standalone Android command-line tools and use sdkmanager to download the emulator and a system image, avdmanager to create a virtual device, and the emulator command to launch it. This avoids installing the full Android Studio IDE.

Why is my Android Emulator slow on my Mac?

The most common cause on Apple Silicon is using an x86 system image instead of arm64-v8a, which forces slow CPU emulation. Other causes include too little RAM allocated to the AVD, software graphics instead of hardware GPU, and running too many AVDs at once.

Is the Android Emulator free on Mac?

Yes. Android Studio, the Android SDK, the Android Emulator, and the system images are all free to download and use from Google. You only need enough disk space and a supported version of macOS.

Should I use a local emulator or a cloud Android device for testing?

A local emulator is ideal for day-to-day development and quick checks. For wide coverage across many Android versions, screen sizes, and OEM skins, a cloud platform with real Android devices and emulators is more practical because it removes local setup and lets you test combinations your single Mac cannot reproduce.