Developer storage

Android Studio & Emulator Storage on Mac: What's Safe to Delete

Every Android Virtual Device (AVD) you create carries its own multi-gigabyte disk image, and most developers create more than they ever delete.

Diskfern Team7 min readUpdated October 19, 2026

Short answer

Android Studio stores AVD images, SDK components, and Gradle/build caches. Remove unneeded AVDs and SDK versions through its managers after preserving emulator data. Gradle manages unused caches automatically; manual clearing can need network access and available dependencies to rebuild.

Diskfern view for: Reduce Android Studio emulator storage on Mac

Is it safe to delete an Android Virtual Device (AVD)?

An AVD can hold app data and test state even when it is not running. Export anything needed before deleting it in Device Manager. Its configuration can be recreated, but its stored data is removed; project source outside the AVD is unaffected.

Can I delete old Android SDK platforms and system images?

Yes. SDK platforms and system images for Android API levels you no longer target or test against can be safely removed through the SDK Manager. They're re-downloadable, but only when you have network access, so keep the ones your active projects' minSdk/targetSdk actually need.

Is the Gradle cache safe to clear?

Gradle manages downloaded dependencies and build caches under ~/.gradle/caches and automatically removes unused entries. Prefer that cleanup. If manually clearing a specific cache, close the IDE and stop Gradle daemons first. Rebuilding may need network access, and dependencies that are no longer available remotely may not be recoverable. Keep settings and credentials outside the cache intact.

What’s safe to delete?

Unused Android Virtual Devices (AVDs)

Review first

~/.android/avd

Frees several GB per device; recreate via Android Studio's Device Manager if needed again.

How: Android Studio → Device Manager → select device → Delete.

Old SDK platforms / system images

Review first

Managed by the SDK Manager (~/Library/Android/sdk)

Re-downloadable via SDK Manager; keep versions your active projects require.

How: Android Studio → Settings → Languages & Frameworks → Android SDK → uncheck/apply.

Gradle cache

Safe

~/.gradle/caches

May need dependency downloads and a longer build. Confirm required artifacts remain available before clearing a cache.

How: Close Android Studio, stop Gradle daemons with ./gradlew --stop, then inspect specific caches in Finder. Gradle also cleans unused caches automatically; do not delete your whole ~/.gradle directory.

Android Studio caches

Safe

~/Library/Caches/Google/AndroidStudio*

Rebuilt automatically on next launch; may trigger a one-time re-index.

How: Android Studio → File → Invalidate Caches, or delete the folder directly.

Installed Android SDK itself (if not uninstalling)

Don't touch wholesale

~/Library/Android/sdk

Breaks all Android projects until the SDK is reinstalled.

How: Only remove specific components via SDK Manager, not the whole folder, unless uninstalling entirely.

Don't delete the SDK folder directly

Manually deleting ~/Library/Android/sdk can leave Android Studio in a broken state. Use the SDK Manager to remove specific components instead.

Do it manually

No app needed. These steps use Finder, Terminal, and each tool’s own settings.

1
Quit Android Studio and any running emulators first.
2
Open Device Manager and delete AVDs you're not using.
Android Studio → Tools → Device Manager → ⋮ next to a device → Delete.
3
Open SDK Manager and uninstall old platforms/system images.
Android Studio → Settings → Appearance & Behavior → System Settings → Android SDK.
4
Clear the Gradle cache if it's grown large (stop Gradle daemons first).
$open ~/.gradle/caches
Prefer Gradle's automatic cache cleanup. If manually clearing a specific cache, confirm required dependencies remain available and keep credentials, settings, and other ~/.gradle files intact.

The Diskfern way

How Diskfern helps

Diskfern's Smart Highlights recognize Android SDK and emulator storage as one of its 44 built-in categories for developer clutter.

Scan your Mac with Diskfern.
Open Smart Highlights and find the Android SDK & emulators category.
See each AVD and SDK component's real size, broken out individually rather than lumped into System Data.
Review and move Safe/approved items to the Trash.

Finding and reviewing is free. Moving items to the Trash from Diskfern is part of Pro.

See what your Android tooling is using

Questions

How big is a typical Android emulator?

It depends on the system image and configured disk size chosen when the AVD was created; there's no single fixed number. Check your own AVDs' real sizes with a disk-space analyzer rather than assuming a figure.

Will deleting an AVD delete my app's data on it?

Yes. Deleting an AVD removes its virtual disk, including any app data installed inside that emulator instance. Your project source code on your Mac is unaffected.

Does clearing the Gradle cache affect other projects?

It affects all projects that use that shared cache, in that their next build will re-download dependencies. No project files are changed.

Can I move the Android SDK to an external drive to save space?

It's possible by changing the SDK path in Android Studio settings, but it can slow builds if the drive isn't fast, and some tools assume a local path. Clearing unused components first is usually simpler.