Android Studio is Eating 100GB of Your Mac. Here's How to Stop It.

Android development on Mac is a storage nightmare. The IDE itself is 2GB. But the real damage? Hidden AVD disk images and Gradle caches that silently grow to 100GB+ without any warning.

We noticed this when our 512GB MacBook Pro showed 80GB free, but we couldn't figure out where it all went. Turns out, there were 6 old emulators sitting around unused. Each one: 15GB.

Here's the cleanup routine I run every month.

First: Back Up Your Keystores

Before you touch anything in ~/.android, make sure your release signing keys are backed up somewhere safe. Caches are replaceable. Your app signing identity is not. Lose that, and you lose your app's Play Store listing.

The Emulator Black Hole

Every Android Virtual Device creates a virtual disk in ~/.android/avd. These are .img files ranging from 6GB to 20GB each. Create 5 emulators over a year for different API levels? That's potentially 100GB sitting in a hidden folder.

How to clean it:

1. Open Android Studio → Device Manager
2. Delete any emulator you haven't touched in 30 days
3. Or manually nuke the folders in ~/.android/avd

In DissectMac, these show up as massive monolithic blocks in your home directory. If you see a 15GB file in a dot-folder, that's your culprit.

Gradle: The Cache Monster

Gradle downloads and caches every dependency for every project you've ever synced. It also keeps old wrapper versions around forever.

Where it lives: ~/.gradle/caches and ~/.gradle/wrapper/dists

Our approach: Don't nuke the entire ~/.gradle folder—your next build will take much longer. Instead:

• Delete old Gradle versions in ~/.gradle/wrapper/dists (keep only the latest one you use)
• Clear ~/.gradle/caches/modules-2/files-2.1 if you're desperate (it's just downloaded JARs)

Why Standard Cleanup Tools Miss This

Most Mac "cleaner" apps don't scan hidden dot-folders by default. They focus on ~/Library/Caches, which is valid, but they completely miss ~/.android, ~/.gradle, and other developer-specific paths.

DissectMac ignores the "hidden" flag entirely. It scans everything and shows you the raw truth. You'll see exactly which AVD image or which old Gradle version is the problem, right-click, and reveal it in Finder.

Quick Checklist

• Delete unused emulators in Android Studio Device Manager
• Clear ghost disk images in ~/.android/avd
• Purge old Gradle wrappers in ~/.gradle/wrapper/dists
• Run DissectMac to find any dot-folder bloat you missed

Pro Tip

If you use both Android Studio AND IntelliJ IDEA, you might have duplicate Gradle caches. Check ~/.gradle carefully—sometimes clearing the IDE cache in one doesn't affect the other.

Scan Your Dev Environment →