Why does Android development use so much Mac storage?

Android Studio, Gradle, and the Android SDK each maintain their own caches and downloaded artifacts, largely separate from your actual project files. Combined with emulator disk images that can run several GB apiece, it's common for Android developer Macs to have 30-80GB spread across tooling alone.

Where do Android development caches live?

  • Gradle cache - ~/.gradle/caches - downloaded dependencies and build cache, shared across all your Android and Kotlin projects
  • Android SDK - ~/Library/Android/sdk - platform tools, build tools, and system images for every API level you've installed
  • AVD (emulator) data - ~/.android/avd - each virtual device's disk image and snapshots
  • Android Studio caches - ~/Library/Caches/Google/AndroidStudio* - IDE indexes and internal caches

How to clear the Gradle cache safely

The Gradle cache is fully rebuildable - it just re-downloads dependencies on your next build. To clear it:

rm -rf ~/.gradle/caches

Expect your next build across all projects to be slower as Gradle re-downloads and re-resolves dependencies. For a lighter touch that only clears build outputs for one project without touching the shared dependency cache, run ./gradlew clean from inside that project.

How to remove unused emulators (AVDs)

  1. Open Android Studio
  2. Go to Tools > Device Manager
  3. Find emulators you no longer use
  4. Click the dropdown menu next to each and choose Delete

Emulator snapshots in particular can balloon to several GB per device if you've used the "Quick Boot" snapshot feature heavily. Deleting an AVD you're not actively testing on is one of the fastest ways to reclaim multiple gigabytes at once.

How to clean up old Android SDK versions

  1. Open Android Studio
  2. Go to Settings > Languages & Frameworks > Android SDK
  3. Review the SDK Platforms and SDK Tools tabs
  4. Uncheck and apply removal for old API levels and build tools you no longer target

Keep the API level(s) your current projects' minSdkVersion and targetSdkVersion actually require - removing an SDK version a project depends on will break your next build until you reinstall it.

Is it safe to delete these caches?

Gradle caches and Android Studio IDE caches: yes, fully - both rebuild automatically. SDK platforms and emulators: only remove versions and devices you've confirmed you don't need, since re-downloading a full SDK platform or recreating an emulator takes real time and bandwidth.

Finding what's actually using the space

Rather than guessing which caches are worth clearing, DustByte's Large & Old Files tool can scan your Library and home folder to show exactly which Android tooling directories are the biggest, so you clean up the ones actually worth the effort.