![android emulator directory mac android emulator directory mac](https://docs.expo.dev/static/images/android-studio-sdk-location.png)
What we want to achieve here is to define the ANDROID_AVD_HOME environment variable in a way that makes it available to applications launched from the Finder.
ANDROID EMULATOR DIRECTORY MAC HOW TO
And of course, the thousands of documents about how to do it in Windows are of no help at all, and the few that are about the Mac are really, really outdated. But if you try to set them under Appearance & Behavior > Path Variables in the Android Studio Preferences, because you think it would be a reasonable thing to do, then you might waste a lot of time, because it does not work.
![android emulator directory mac android emulator directory mac](https://docs.microsoft.com/en-us/xamarin/android/troubleshooting/questions/android-sdk-location-images/win/01-locations-sml.png)
It’s easy enough to find out that you should modify either the ANDROID_SDK_ROOT, ANDROID_EMULATOR_HOME, or ANDROID_AVD_HOME environment variables (or even ANDROID_HOME, if you’re unlucky enough to find some really outdated documents).
![android emulator directory mac android emulator directory mac](https://i.stack.imgur.com/3uEUc.png)
To move it to a new location perform following steps. This is meant for AMD users on Windows who want a faster AVD experience on par with HAXM, or cannot run with Hyper-V / WHPX enabled (e.g., running other virtual machine engines such as VMware/VirtualBox or not running Windows 10 however, note that we are still committed to WHPX / Hyper-V for the use cases where that is optimal, such as interop with Docker on Windows).
It’s possible, but if you’re lucky like I am, you might run into some hurdles. Default Android Virtual Device Manager (AVD) folder is located is in C:UsersImagine you’d like to reclaim space on your Mac’s main hard drive by moving your Android Studio Virtual Devices (the phones and tablets you run in the Android Emulator to test your applications).