Mobile application development requires significant resources, and the environment Android Studio is known for its gluttony in terms of disk space. Over time, cache folders, system images, and outdated SDK versions can take up tens of gigabytes, significantly slowing down the entire operating system. Many users are faced with a situation where standard uninstallation of a app through the control panel does not solve the problem, leaving behind huge amounts of “garbage.”
The uninstallation process may be required for various reasons: from the desire to free up space on the SSD to switching to another IDE or completely reinstalling the environment to correct critical configuration errors. It is important to understand that simply moving the shortcut to the trash or using a standard uninstaller deletes only executable files, leaving user settings and libraries untouched.
In this guide, we will look in detail at how to correctly and safely remove Android Studio in all popular operating systems. We will not just remove the app, but also clear hidden directories, environment variables and registry entries to return your computer to maximum performance.
Preparing for removal and saving projects
Before starting radical actions, you need to make sure that all important data is saved. Deleting the development environment does not directly affect your source codes if they are stored in a separate directory, however, project settings may be tied to specific paths within the IDE folders.
It is recommended to create a backup copy of the directory AndroidStudioProjectsif you are not using version control systems such as Git. It's also worth exporting your settings if you plan to later restore them on another computer or after a reinstall. This can be done through the menu File → Manage IDE Settings → Export Settings.
⚠️ Attention: Deleting the SDK folder will irreversibly erase all downloaded system images, platforms and build tools. If you have custom emulator configurations, you will have to create them again.
☑️ Preparing for deletion
Make sure that all processes associated with Gradle and emulators are completed. Sometimes background services continue to run even after the main app window is closed, which may block the deletion of some files. Check the task manager and forcefully end processes studio.exe or studio64.exeif they are frozen.
Uninstalling Android Studio in Windows
The uninstallation process in the Windows environment begins with the standard procedure through the control panel, but the work is not limited to this stage. First, you need to find the installed package in the list of apps and run the built-in removal wizard.
Go to Control Panel → apps and Features, find it in the list Android Studio and click the "Delete" button. Follow the wizard's instructions to confirm the removal of components. However, this is only the tip of the iceberg, since the main data is stored in hidden system folders.
After completing the wizard, you must manually delete the remaining directories. The main paths where data is accumulated are in the user profile and in the common app folder. To access them, enable the display of hidden files in Explorer.
- 🗑️ Delete the configuration folder:
C:\Users\YOUR_USER\.AndroidStudioX.X - 🗑️ Delete the folder settings:
C:\Users\YOUR_USER\AppData\Local\Google\AndroidStudioX.X - 🗑️ Delete cache and logs:
C:\Users\YOUR_USER\AppData\Local\Google\AndroidStudioX.X\log
Don't forget to check the directory AppData\Roaming, where plugin settings and keys can also be stored. The full path usually looks like C:\Users\YOUR_USER\AppData\Roaming\Google\AndroidStudioX.X. Cleaning up these folders will ensure that when you reinstall, the environment will be clean, free of old configuration conflicts.
Use the Win + R key combination and enter %APPDATA% or %LOCALAPPDATA% to quickly navigate to hidden settings folders without manually searching in Explorer.
Cleaning SDKs and emulators in Windows
The largest trace that leaves Android Studio is the software development kit (SDK) and images of virtual devices. By default, they are installed in a folder AppData\Local\Android, which is not deleted automatically.
To free up space, which can reach 20-30 GB or more, you must manually delete the directory C:\Users\YOUR_USER\AppData\Local\Android. Inside it there are folders sdk, avd (emulators) and build-tools.
⚠️ Warning: If you use other tools that depend on the Android SDK (for example, Unity or React Native), deleting this folder will break them work. Make sure that these apps do not require access to SDK data.
It is also worth checking your environment variables. Open System Properties, go to Advanced and click Environment Variables. In the list of system and user variables, find the lines ANDROID_HOME or ANDROID_SDK_ROOT and delete them so that the system does not try to access non-existent paths.
| Data type | Location (Windows) | Approximate volume | Importance of deletion |
|---|---|---|---|
| IDE configuration | %USERPROFILE%\.AndroidStudio... |
~100 MB | High |
| System cache | %LOCALAPPDATA%\Google\... |
~1-2 GB | Average |
| Android SDK | %LOCALAPPDATA%\Android\sdk |
5-30 GB | Critical |
| Emulators (AVD) | %USERPROFILE%\.android\avd |
2-10 GB | High |
Complete removal on macOS
In the operating system macOS deleting applications often comes down to moving the icon to the trash, but for professional software like Android Studio this is absolutely not enough. Support files are scattered across the user's various system libraries.
First, move the application itself Android Studio.app from the folder Applications to the trash. Next, you need to open a Terminal or Finder and navigate to the hidden library folders. In macOS, the path to them is ~/Library.
For a complete cleanup, delete the following directories through the Terminal or Finder. Be extremely careful when entering commands so as not to delete unnecessary files from other apps. Using the command rm -rf requires care.
rm -Rf ~/Library/Preferences/AndroidStudio*rm -Rf ~/Library/Preferences/Google/AndroidStudio*
rm -Rf ~/Library/Caches/AndroidStudio*
rm -Rf ~/Library/Caches/Google/AndroidStudio*
rm -Rf ~/Library/Logs/AndroidStudio*
rm -Rf ~/Library/Logs/Google/AndroidStudio*
Do not forget about emulators and SDKs, which in macOS are also located in the home directory or in Libraryby default. The folder .android contains AVD debugging and configuration keys, and the folder Android in the user root stores the SDK itself.
How to find hidden folders in the Finder?
Press the key combination Command + Shift + G in the Finder window and enter path, for example ~/Library, to go to hidden system directories.
Clearing the Gradle cache and dependencies
The build system deserves special attention Gradle, which independently downloads huge volumes of libraries and dependencies for each project. These files are stored in a separate directory and are not deleted along with the development environment.
The folder .gradle in the user's home directory can grow to an impressive size, especially if you worked on many projects with different versions of libraries. Deleting this folder is safe because Gradle will download the dependencies again if necessary.
- 📂 Windows:
C:\Users\YOUR_USER\.gradle - 📂 macOS/Linux:
~/.gradle
If you used a local Maven repository or other package managers, check for the presence of the folder .m2. Although it is not directly owned by Android Studio, it is often filled with artifacts related to Android development.
⚠️ Warning: Deleting the Gradle cache will cause the system to take a long time to download dependencies again the next time you open old projects. Do this only if disk space is critical to you.
The Gradle cache is IDE-independent storage. It can be deleted separately, without affecting the settings of Android Studio itself, if you plan to leave the development environment.
Removing registry entries and variables (Advanced level)
For Windows users who strive for a perfectly clean system, it is recommended to check the registry for orphaned keys. Although modern uninstallers work well, sometimes entries about file types or context menus are left behind.
Launch Registry Editor by entering regedit in the search. Follow the thread HKEY_CURRENT_USER\Software\Google and delete the key AndroidStudio. Also check the branch HKEY_LOCAL_MACHINE\SOFTWARE\Googleif the installation was carried out for all users.
After cleaning the registry and files, be sure to restart your computer. This is necessary so that the operating system correctly resets file descriptors and updates the list of environment variables, eliminating errors in accessing remote resources.
If you plan to completely abandon development for Android, also check for installed ADB and Fastboot drivers in the device manager. They can be removed through the device's context menu by selecting "Remove device" with the "Remove driver apps" checkbox.
Why restart the computer?
Restarting ensures that all locked files are permanently removed from memory, and environment variables are updated for all new running processes.
Often asked questions (FAQ)
Will the standard uninstaller delete the SDK folder?
No, the standard uninstaller only deletes the files of the app itself (IDE). The SDK folder, emulators and Gradle cache are stored separately in the user profile and must be deleted manually.
Is it safe to delete the .android folder?
Yes, it is safe if you do not plan to use emulators right away. This folder stores virtual device settings and debug keys adbkey. If necessary, they will be created anew.
Is it possible to remove Android Studio, leaving the SDK for another IDE?
Of course. You can delete only the Android Studio app directory, leaving the folder Android\sdk touched. Then, in another development environment (for example, IntelliJ IDEA or VS Code), specify the path to the existing SDK.
Where can I find the hidden AppData folder in Windows?
The folder AppData is hidden by default. To see it, open Explorer, go to the “View” tab and check the “Hidden items” box, or type %appdata% in the address bar.
How much space will a complete deletion free up?
On average, a complete deletion with all components frees up from 15 to 40 GB of disk space, depending on number of installed versions of Android and emulator images.