Back to Blog

Is It Safe to Delete the ~/.android/avd Folder on Mac?

What ~/.android/avd holds, which file makes an Android emulator large, what you lose when you delete it, and how to wipe or remove a virtual device instead.

Published October 25, 2026 Author Vladimir Chemeris Read time 4 min read
AndroidEmulatorDeveloper Cleanup

Deleting ~/.android/avd removes every Android emulator on your Mac, with the apps, accounts and snapshots inside each one. Your Mac does not care, and Android Studio can create new devices. The data inside the old ones does not come back. When one emulator has grown large, wipe its data or delete that one device from Android Studio, and leave the folder to the tools.

Main rule: wipe the devices you still use, delete the ones you do not, and touch the folder by hand only for devices Android Studio no longer lists.

Quick answer

  1. Measure with du -sh ~/.android/avd/*.
  2. List the devices with ~/Library/Android/sdk/emulator/emulator -list-avds.
  3. Wipe a device you still use: Device Manager, Wipe Data.
  4. Delete a device you no longer need: Device Manager, Delete.
  5. Remove unused system images separately, in the SDK Manager.
  6. Delete by hand only leftovers, and remove NAME.avd and NAME.ini together.

What lives in ~/.android/avd

Each virtual device is two items: a NAME.ini file and a NAME.avd folder it points to. I measured mine on 25 October 2026. It held one device, the Medium Phone profile on API 37 with the Google Play image, and took 2.8 GB:

Inside NAME.avdWhat it holdsOn my Mac
userdata-qemu.img.qcow2the data partition: installed apps, their data, accounts2.2 GB
sdcard.imgthe emulated SD card512 MB
encryptionkey.img and .qcow2the device’s encryption key image94 MB
snapshotsQuick Boot snapshots, when the emulator saves themnone
config.inithe hardware profile and the path to the system imagea few KB

The data partition grows as you install and use apps. This device’s config.ini sets disk.dataPartition.size=10G, so that one file can reach 10 GB.

What is not in this folder

The Android system itself lives in the SDK, not in the AVD folder. config.ini points to it with a line like image.sysdir.1=system-images/android-37.0/google_apis_playstore/arm64-v8a/. On my Mac ~/Library/Android/sdk/system-images took another 2.7 GB, the emulator binaries 1.2 GB and the NDK 2.1 GB.

That split has two consequences:

  • Deleting a device does not free its system image. Several devices can share one image.
  • Deleting a system image leaves the devices that use it unable to boot until you install the image again.

Android Studio’s SDK Manager lists the installed images and removes the ones you do not need.

Wipe or delete

Wipe Data resets a device to factory state and keeps its definition. The data partition shrinks back, and you sign in and install your test apps again. In Device Manager it sits in the device’s menu. From the terminal, start the device once with the flag:

~/Library/Android/sdk/emulator/emulator -avd Medium_Phone_API_37.0 -wipe-data

The emulator’s help describes -wipe-data as “reset the user data image (copy it from initdata)”.

Delete removes the device and its files. Use it for devices you created for one test and forgot.

Snapshots matter when Quick Boot saves large states. -no-snapshot-save starts the emulator without saving a snapshot on exit, and the device’s snapshots folder shows what earlier sessions left.

Deleting by hand

Manual deletion makes sense for leftovers: devices from an Android Studio you already removed, or devices pointing at system images you deleted. Remove both the NAME.avd folder and its NAME.ini file, since the .ini file exists only to point at the folder.

Do not clear the whole ~/.android folder while you are at it. It also holds:

  • debug.keystore, the key that signs your debug builds. A new one gets a new fingerprint, so API keys restricted to the old debug SHA-1 stop working for debug builds.
  • adbkey, the key your physical test devices authorized for USB debugging. They ask again after it changes.

Bottom line

Deleting ~/.android/avd breaks nothing on your Mac and removes every emulator you have, with its data. Measure the folder, wipe the devices you keep, delete the ones you do not, and remove system images from the SDK Manager when the devices that used them are gone.

About the author

Vladimir Chemeris

Founder, StorageRadar

Vladimir Chemeris builds StorageRadar, a privacy-first macOS storage analysis app focused on review-first cleanup, developer storage, and before-and-after visibility.

Frequently asked questions

Is it safe to delete ~/.android/avd?

It is safe for your Mac and final for your emulators. Every virtual device disappears with its installed apps, accounts and snapshots. Android Studio can create new devices, but the data inside the old ones does not come back.

Does deleting an AVD remove the Android system image?

No. System images live in the SDK folder, ~/Library/Android/sdk/system-images by default, and each device's config.ini only points to one. Remove system images in Android Studio's SDK Manager.

How do I shrink an emulator without deleting it?

Wipe its data. In Android Studio's Device Manager choose Wipe Data for the device, or start it once with emulator -avd NAME -wipe-data. The device keeps its definition and boots like a new phone.

Can I delete the whole ~/.android folder?

Do not delete all of it. Next to avd it holds debug.keystore, the key that signs your debug builds, and adbkey, which your physical test devices have authorized. Android Studio creates new ones, but devices ask for authorization again and API keys restricted to the old debug fingerprint stop working.

Where does Android Studio store emulators on Mac?

In ~/.android/avd, unless the ANDROID_AVD_HOME environment variable points somewhere else. Each device is a NAME.ini file plus a NAME.avd folder.

Sources & references

See your emulators next to the rest of your developer storage.

StorageRadar's Dev Cleanup sizes Android emulator data, Gradle caches, Xcode folders and package caches side by side, labels each by risk, and walks risky profiles through a Dry Run and Guided Preflight.