Mobile application development requires serious resources, and over time, the environment Android Studio can take up tens of gigabytes on your disk. Many users are faced with the need to completely remove the IDE to free up space or solve problems with the software not working correctly. Simply moving the shortcut to the trash is not enough here, since the system stores many hidden configurations and caches.
The uninstallation process differs significantly depending on your operating system, be it Windows, macOS or Linux. Improper uninstallation often results in the next installation having version conflicts or compilation errors due to old libraries. In this article, we will analyze in detail each stage of cleaning so that your system remains completely clean of traces of the development environment.
We will consider not only standard removal procedures through the control panel, but also manual cleaning of the directories where plugins, emulators and Gradle settings are stored. This is critical for those who want to start from scratch or completely stop using this tool at the moment.
Preparing for removal and backing up settings
Before taking drastic actions, you need to make sure that you do not lose important projects or specific configurations. Although the development environment itself is just a tool, its folders may contain signing keys or proxy settings that you spent hours configuring. Save this data separately if you plan to reinstall in the future.
Pay attention to the location of your work projects. By default Android Studio suggests saving them in a folder AndroidStudioProjects, but experienced developers often change this location. Make sure that the source code is in a safe place, for example in a repository Git, and does not depend on the IDE system folders.
⚠️ Warning: Deleting configuration directories will permanently delete all user settings, themes and installed plugins. Make sure you no longer need them.
It's also worth checking the active processes. Sometimes the emulator service or background Gradle process can prevent files from being deleted correctly. Close all app windows and complete related tasks through the process manager before starting work.
☑️ Preparing for complete removal
The removal procedure in the Windows operating system
In the environment Windows the process begins with the standard control panel, but this is only the first step. You need to go to apps and Features or Applications in System Settings. Find it in the list Android Studio and initiate the removal process, following the prompts of the uninstallation wizard.
After the official uninstaller completes its work, numerous traces remain in the system. The development environment stores data in several hidden directories that are not automatically deleted. You will need to manually clear folders in the user profile and the app Files system directory.
The main paths that need to be checked and deleted manually:
- 📂
C:\Users\%USERPROFILE%\.android— debug keys and emulator configurations are stored here. - 📂
C:\Users\%USERPROFILE%\.gradle— dependency cache, which can occupy several gigabytes. - 📂
C:\Users\%USERPROFILE%\AppData\Roaming\Google\AndroidStudio*— settings and plugins of a specific version. - 📂
C:\Users\%USERPROFILE%\AppData\Local\Google\AndroidStudio*— system cache and operation logs.
To access the folder AppData you may need to enable the display of hidden items in Explorer. Just enter %APPDATA% and %LOCALAPPDATA% into the address bar of Explorer for quick navigation. Removing these directories ensures that when you re-install the app, it will behave like the first launch.
Use the Win + R keyboard shortcut and enter %LOCALAPPDATA% to instantly jump to hidden cache folders without a long search in the Explorer settings.
Full cleanup of Android Studio on macOS
Users macOS often make the mistake of simply dragging the application icon to the trash. Although this deletes the executable, all settings, caches, and virtual devices remain on the disk, continuing to take up valuable space. Complete cleaning requires using the terminal or manually deleting files from the user's library.
First, move the application itself Android Studio.app from the folder Applications to the trash. After that, open Finder and press the combination Cmd + Shift + Gto go to hidden folders. You will need to delete a number of directories starting with a dot, which is standard for configuration files on Unix-like systems.
Here is a list of paths that need to be cleared:
- 🗑️
~/Library/Preferences/Google/AndroidStudio*— preferences and interface settings. - 🗑️
~/Library/Caches/Google/AndroidStudio*—temporary files and search indexes. - 🗑️
~/Library/Logs/Google/AndroidStudio*—error logs and debugging information. - 🗑️
~/.android—emulator data and ADB keys.
If you prefer to use the terminal, you can issue a command to bulk delete, but proceed with caution. Enter the command
rm -Rf ~/Library/Preferences/Google/AndroidStudio*⚠️ Attention: The command rm -rf in the terminal deletes files permanently, bypassing the recycle bin. Double-check the path before pressing Enter to avoid accidentally deleting important data.
Removal in Linux distributions
In the ecosystem Linux The removal method depends on how you installed the development environment: through the official archive, Snap repository, Flatpak or distribution package manager. If the installation was done via Snap, the command will look like sudo snap remove android-studio. For Flatpak, use flatpak uninstall com.google.AndroidStudio.
When manually installing from a tar.gz archive, you need to independently delete the directory where you unpacked the files (often this is /opt/android-studio or a folder in /home). However, as in other OSes, configuration files remain in the user's home directory and require manual intervention.
Standard paths for cleaning in Linux include:
- 🐧
~/.config/Google/AndroidStudio*— main configuration files. - 🐧
~/.local/share/Google/AndroidStudio*— application data and plugins. - 🐧
~/.cache/Google/AndroidStudio*— compilation cache and indexes. - 🐧
~/.android— emulator and USB debugging settings.
Don't forget to also check the presence of environment variables. Open your shell configuration file (for example .bashrc or .zshrc) and remove the lines that export ANDROID_HOME or add the path to the tools to PATH. This will prevent errors in the terminal when trying to call Android SDK commands after uninstallation.
How to find hidden files in Linux?
In most file managers (Nautilus, Dolphin, Thunar), hidden files can be displayed by pressing Ctrl + H. In the terminal, use the ls -la command to view all files, including hidden.
Cleaning up residual components: SDK, Emulator and Gradle
The largest part of the data is often located outside the folders of the IDE itself. Android SDKplatform tools and system images for the emulator can take up from 10 to 50 GB of disk space. They are usually located in a separate directory, which is not uninstalled along with the app.
By default, the SDK is located in a folder Android/Sdk in the user's home directory or AppData/Local/Android/Sdk on Windows. If you do not plan to use the command line to build projects or other IDEs (for example, IntelliJ IDEA or VS Code), this folder can be safely deleted.
The table below will help you identify the main components and their approximate weight to understand what exactly you are deleting:
| Component | Location (Windows) | Approximate size |
|---|---|---|
| Android SDK Tools | %LOCALAPPDATA%\Android\Sdk |
2–5 GB |
| System Images (Emulator) | .../Sdk/system-images |
5–20 GB |
| Gradle Cache | %USERPROFILE%\.gradle |
1–10 GB |
| AVD Configs | %USERPROFILE%\.android\avd |
500 MB - 5 GB |
Pay special attention to the cache Gradle. This build system stores all downloaded libraries for your projects. If you have a lot of old projects, this folder can grow huge. Deleting the folder .gradle is safe, but the next time you open any project, loading dependencies will take time.
The largest amount of space will be freed up after deleting the folder with system images of the emulator (system-images), since each image weighs several gigabytes.
Cleaning the registry and environment variables (for Windows)
For users Windows an important step is cleaning the registry, where entries about paths to non-existent files may remain. Although modern uninstallers work well, a manual check will not hurt. Open the registry editor by clicking Win + R and entering regedit.
Go to the branch HKEY_CURRENT_USER\Software\Google and delete the key AndroidStudio. Also check the branch HKEY_LOCAL_MACHINE\SOFTWARE\Googleif administrator rights allowed you to install the app for all users. This will rid the system of “dead” links.
Then you need to clear the environment variables. Right-click on This PC, select Properties → Advanced System Settings → Environment Variables. In the list of system and user variables, find and delete ANDROID_HOME, ANDROID_SDK_ROOT, and also check the variable Path for links to folders platform-tools or tools.
⚠️ Attention: Be extremely careful when editing the Path system variable. Delete only lines that are clearly related to Android so as not to disrupt the operation of other apps.
After all manipulations, it is recommended to restart the computer. This will allow the operating system to complete deleting locked files and update the table of environment variables, applying all changes correctly.
Why delete environment variables?
If you leave the ANDROID_HOME variables, but delete the files themselves, other apps or scripts may try to access a non-existent path, causing errors in the terminal or other IDEs.
Frequently asked questions (FAQ)
Will the standard uninstaller delete all Android Studio files?
No, the standard uninstaller only deletes the files of the app itself. User configurations, Gradle cache, emulator images and SDK settings remain on disk and require manual deletion.
Is it possible to delete the .gradle folder without affecting other projects?
Yes, deleting the folder .gradle is safe. However, the next time you launch any Java or Android project, the system will need time to re-download all the necessary libraries and dependencies from the Internet.
Where are application signing keys stored (Keystore)?
By default, Android Studio does not store keys in its folders, users themselves choose the location for .jks or .keystore files. However, check the folder .androidthere may be a file debug.keystoreused for debugging.
How to completely remove the Android emulator?
The emulator consists of two parts: the app and system images. Delete the folder .android/avdwhere device configurations are stored, and the folder system-images inside the SDK directory where the Android images themselves are stored.
Does deleting Android Studio affect the installed Java JDK?
No, the development environment and the Java Development Kit (JDK) - these are different apps. The JDK will remain on the system unless you uninstall it separately through the Control Panel. It can be used by other applications.