Is it safe to delete the Android SDK folder?
- No, not all of it while you build Android apps: Android Studio, Gradle and the emulator all run from it. The packages you don’t use, such as old system images, platforms and build tools, are safe to remove in Android Studio’s SDK Manager.
- What it costs you: a package you remove is gone until you install it again from the SDK Manager. Remove one a project still needs, and that project won’t build until it’s back.
- Does it come back? Only by downloading it again. Delete the whole SDK and Android Studio can’t build or run apps until you reinstall it.
- SiftMac’s verdict: Leave it
1. What it is
The Android SDK is the toolkit Android Studio uses to build, run and debug apps. Google’s SDK Manager downloads it as separate packages, each in its own folder:
platforms/: one Android platform per API level you compile against.build-tools/: the tools that package apps, one folder per version.platform-tools/:adband other tools for talking to devices.system-images/: the Android versions emulators run, shared by every emulator of that version.emulator/,cmdline-tools/and, if you installed them, the NDK and CMake for native code.
Many packages install side by side, one folder per version, so an SDK that has followed a few Android releases holds several platforms, build tools versions and system images you may no longer use.
2. Where it is
~/Library/Android/sdk
That’s the SDK’s usual home on a Mac and the path Google uses in its ANDROID_HOME examples. Android Studio shows the folder it actually uses as the Android SDK Location in the SDK Manager (Tools › SDK Manager). System images sit inside it, in system-images/android-<API level>/<variant>/<architecture>.
3. How big it gets
Every system image is a complete Android version, and every NDK is a full native toolchain, so those folders add up fastest. To see which parts take the space on your Mac:
du -sh ~/Library/Android/sdk/* | sort -h
du -sh ~/Library/Android/sdk/system-images/*/* | sort -h
4. How to delete it safely
- In Android Studio, choose Tools › SDK Manager.
- In the SDK Platforms and SDK Tools tabs, clear the checkbox next to each package you don’t use any more: system images no emulator needs, platforms for API levels you no longer compile against, old build tools and NDK versions. A red X marks each pending removal.
- Click Apply or OK, check the list, and confirm.
Without Android Studio, the SDK’s sdkmanager lists packages and uninstalls them by their SDK path. Google now marks it as deprecated in favour of its new android sdk command:
~/Library/Android/sdk/cmdline-tools/latest/bin/sdkmanager --list
~/Library/Android/sdk/cmdline-tools/latest/bin/sdkmanager --uninstall "system-images;android-<API level>;<variant>;<architecture>"
Either way, you see each package’s name and version before anything goes, which beats guessing from folder names in Finder.
5. What happens afterwards
- A project that compiles against a removed platform, or uses a removed build tools version, won’t build until you install that package again in the SDK Manager.
- An emulator whose system image you removed can’t start until the image is back. Delete those emulators in Device Manager too.
- Keep
platform-tools,emulator, the build tools your projects use and the platforms they target: removing those stops builds,adbor the emulator until they’re back.
6. If you’ve stopped doing Android work
Then the SDK can go with Android Studio itself: remove the app, then ~/Library/Android/sdk. The emulators in ~/.android/avd and Gradle’s caches are separate folders, and often big ones too. When you open a new major version of Android Studio, it also offers to delete the caches, settings, indexes and logs of versions you no longer have installed.
Questions
Will deleting the Android SDK break Android Studio?
Yes, until you reinstall it: Android Studio needs the SDK to build apps, run emulators and talk to devices. Remove single packages instead, or the whole SDK only if you’re done with Android development.
Which system images can I remove?
Any that no emulator uses. Device Manager shows which Android version each emulator runs; the system images for the others can go.
Is the SDK the same as ~/.android?
No. The SDK holds the tools and system images. ~/.android holds your emulators’ own data and the tools’ settings; see Android emulators.
Can I move the SDK to another drive?
Yes. Google’s steps: copy the SDK folder to the new place so nothing downloads again, then change the Android SDK Location in Android Studio’s settings, under Appearance & Behavior › System Settings › Android SDK.
How SiftMac handles it. SiftMac leaves the SDK to Android Studio. Its space map shows the folder’s size and notes that it holds build tools, platforms and emulator images, best removed from Android Studio’s SDK Manager.
Download SiftMac · scanning is free, and so is your first 2 GB of cleaning · See how it works