# Manage Android Studio SDK and Emulator Storage on Mac

> Find Android SDK packages, system images and virtual devices on Mac, remove unused items, and keep the test data you still need.

Published: 2026-07-01 | Updated: 2026-10-31

Android Studio's disk usage is not just the editor. SDK packages, Android system images and each virtual device have different owners and different recovery costs. Start by identifying the largest store, then remove one unused package or device through Android Studio before touching folders by hand.

## Find the SDK and Virtual Devices

Open **Tools › SDK Manager** and record **Android SDK Location**, as documented in Google's [SDK Manager instructions](https://developer.android.com/studio/intro/update). Use that displayed location if it differs from the usual Mac path below. Android Studio labels in this guide follow the English interface.

Google's [emulator directory reference](https://developer.android.com/studio/run/emulator-commandline) separates shared system images from writable virtual-device data. These are the usual locations, not instructions to delete their parent folders:

```text
~/Library/Android/sdk
~/Library/Android/sdk/system-images
~/.android/avd
```

| Store | What it holds | First action |
| --- | --- | --- |
| SDK platforms and tools | Packages used to build Android apps | Review installed packages in SDK Manager |
| System images | Android versions and variants used by emulators | Check which virtual devices still need them |
| AVD data | Installed test apps, settings and writable device storage | Inspect the device in Device Manager |
| Snapshots | Saved emulator state | Remove only states you no longer need |

Use folder sizes to choose where to investigate, not as an estimate of disposable data. If a configured path is elsewhere, inspect that location instead of creating a missing default folder.

## Remove Unused SDK Packages

In SDK Manager, inspect **SDK Platforms** and use [**Show Package Details**](https://developer.android.com/about/versions/15/setup-sdk) to distinguish a platform from its system images. Google's [package descriptions](https://developer.android.com/studio/intro/update) explain their separate roles. Keep packages required by current projects and your device test matrix.

1. Note the installed platform or image you intend to remove, including its API level and variant.
2. Clear only that package's checkbox, then choose **Apply**.
3. Read the removal list before confirming, leaving unrelated tools selected.
4. Build a project you still maintain and start a retained virtual device.

If the build now needs the removed platform, install that package again in SDK Manager. Recovery needs the package to remain available and a working download connection. Do not delete the entire SDK because one old image is large.

## Wipe Data or Delete a Virtual Device

Google's [Device Manager guide](https://developer.android.com/studio/run/managing-avds) documents **View › Tool Windows › Device Manager** within a project. Use the device menu's **Show on Disk** to identify its actual files, and **Stop** before changing its stored data.

Choose **Wipe Data** when you want to keep the virtual device but reset its user data. Choose **Delete** when you no longer need that device. Export any test data or reproduction evidence first, because creating another device does not restore the old device's state.

These are separate from uninstalling a shared system image in SDK Manager. Review the remaining devices before deciding that an image is unused. A clean device is not a backup of the one you erased.

## Trim Snapshots Without Erasing the Device

Google's [snapshot documentation](https://developer.android.com/studio/run/emulator-snapshots) explains that snapshots hold operating-system settings, app state and user data. Open the emulator's snapshot pane, select an unwanted snapshot and use its delete control, preserving named states still needed for debugging.

Quick Boot saves a startup state by default, so deleting that snapshot can trade disk space for a cold start and a later replacement snapshot. A snapshot that preserves a failing test is useful data, even if another snapshot can be generated.

If a saved state fails to start, try **Cold Boot** from Device Manager before wiping the device. That starts without loading the snapshot, rather than using a data reset as the first troubleshooting step.

## Check the Result Before Removing More

Revisit the same SDK and AVD locations after one change. Check that the intended package or device disappeared, then run a retained project and device before removing another item. If space barely changes, return to the table and check whether the other store dominates.

SDK Manager removals and device resets are not a promise of recovery through the Mac Trash. Keep an independent copy of anything irreplaceable before using those controls. If you moved files manually, Apple's [app-removal guidance](https://support.apple.com/en-us/102610) explains that Trash contents do not release their storage until permanently removed, so keep them there during checks.

Gradle is a separate cleanup decision, covered in [developer caches on Mac](https://mole.fit/blog/how-to-clear-dev-caches-mac). For Apple toolchains, use the [Xcode storage guide](https://mole.fit/blog/how-to-clean-up-xcode-mac), rather than applying Android paths to another SDK.

## Where Mole Fits

In Mole Mac, **Clean** groups eligible Android rows under **Developer Tools**. **Android Emulator Quick Boot Snapshots** targets automatic `snapshots/default_boot` folders, not your named snapshots. **Unused Android System Images** lists images with no known AVD reference, unchecked for review; an incomplete reference inventory prevents an image from being offered.

Mole checks the emulator owner again before deletion and refuses these rows while the relevant emulator is running or the process check cannot establish that it is stopped. System-image references are also checked again before removal. Unchecked is a review decision, not a guarantee that selected data will be retained. The [Android Studio uninstall guide](https://mole.fit/tested-apps/android-studio) covers removing the editor while keeping the SDK and signing keys.

## FAQ

### Does Wipe Data Remove the System Image?

It resets the selected device's user data. Shared system images are managed separately in SDK Manager, so choose that route only after checking the remaining devices.

### Can I Delete the Whole AVD Folder?

Use Device Manager to delete devices individually after preserving needed test data. A parent-folder deletion is harder to audit and gives no assurance that the old state can be recovered.

### Why Does Emulator Storage Grow Again?

Quick Boot can save another snapshot and apps create new device data as you test. Check which store grew before repeating a cleanup; repeated resets also discard the state you may be trying to debug.

---

Canonical HTML page: https://mole.fit/blog/android-studio-sdk-emulator-storage-mac
Blog index for agents: https://mole.fit/blog/llms.txt
Site index for agents: https://mole.fit/llms.txt