Developing applications for Android often involves creating many test projects, prototypes and training examples, which over time take up gigabytes of usable space on the hard drive disk. Many new developers are faced with a situation where the integrated development environment (IDE) interface does not provide an obvious "Delete" button for closed or open projects, which leads to confusion and questions about how to free up space. In fact, the procedure for deleting a project in Android Studio is not complex, but it does require an understanding of how the environment stores data on the physical disk, and not just in its list of recent files.
Properly cleaning up old projects involves not just deleting the source code folder, but also eliminating their associated system files, build cache, and configuration settings that may conflict with new developments. In this article we will analyze in detail all stages of the process: from closing the project within the environment to manually clearing hidden directories and resetting global settings Gradle. You will learn which files are safe to delete and which are critical to the operation of the IDE itself, which will allow you to maintain order in the working environment without the risk of damaging the app installation.
Preparing for deletion and closing the project
The first and most important step before any intervention in the file structure is to correctly close the project inside the development environment. If you try to delete project files while it is open in Android Studio, this may result in indexing errors, corrupted temporary files, or even freezing the build process. You must ensure that all active compilation processes are stopped and the code editor windows related to the project being deleted are closed.
To safely shut down, go to the main menu and select File → Close Project. This command will return you to the Welcome Screen, where a list of recently opened projects is displayed. It is important to understand that deleting a project from this list does not erase files from the disk, but only removes the shortcut from the history. If you want to completely get rid of the project, you will have to work with your computer's file system directly using Windows Explorer, Finder on macOS, or Terminal on Linux.
Before you begin deleting folders, it is recommended to back up important data if the project stores unique signing keys or configuration files that may be needed in the future. Deleting source code is an irreversible process without a backup in version control systems, such as Git. Make sure that all your changes are committed and pushed to the remote repository if you plan to completely erase the local copy.
☑️ Preparing to delete the project
⚠️ Attention: Never delete project folders manually while the development environment is running and file indexing is not yet complete. This may damage the search index and require a complete reinstallation of the IDE to restore functionality.
Deleting project files from the hard drive
After closing the project in the IDE interface, physical deletion is carried out using standard operating system tools. By default Android Studio saves projects in a directory AndroidStudioProjectslocated in the user's home folder. The path to this directory may differ depending on the operating system: in Windows it is usually C:\Users\UserName\AndroidStudioProjects, and on macOS - /Users/UserName/AndroidStudioProjects.
Find the folder with the name of your project in the specified directory. Inside it, you will find a directory structure that includes folders app, gradleas well as system configuration files. To completely delete it, just select the entire project folder and move it to the trash or use a key combination to permanently delete it. However, simply deleting the project root folder is sometimes not enough, since the environment may store the build cache in other places.
If you used a version control system Gitthen there will also be a hidden folder in the project root .gitthat takes up additional space. When you delete a project through Explorer, it is deleted along with the rest of the files. However, if you created the project in a non-standard location, make sure that you delete the exact directory that contains the file settings.gradle or settings.gradle.ktsas this is a marker for the project's root directory.
Use hotkeys for quick deletion: on Windows, press Shift+Delete to delete past the trash, and on macOS - Command+Option+Delete. This will save time when clearing a large number of old projects.
Cleaning the cache and temporary system files
Even after deleting the main project folder, “tails” may remain on the disk in the form of cached data that Android Studio created during the work process. These files are stored in system directories and are not automatically deleted when the project is cleaned. Having old caches can slow down the IDE or take up hundreds of megabytes of disk space, especially if you have worked on large applications with many dependencies.
To clear the cache of the development environment itself, use the built-in utility. In the main menu, select File → Invalidate Caches.... In the dialog box that opens, you will see several options, including clearing indexed files, local history cache, and downloaded library cache. Checking the box next to Clear file system cache and Local History will allow you to delete data associated with defunct projects, which is especially useful after mass deletion of files.
In addition to the IDE cache, it is worth paying attention to the package manager cache Gradle. Every time the project is built, Gradle downloads the dependencies to a local repository located at path ~/.gradle/caches. Although these files are used by many projects, an old version of the cache from a remote application may remain there for years. Clearing this folder is safe, but the next time you start any project, the system will have to download the necessary libraries from the Internet again.
| Data type | Location (Windows) | Location (macOS/Linux) | Security removal |
|---|---|---|---|
| Project source code | \Users\Name\AndroidStudioProjects |
~/AndroidStudioProjects |
Completely safe |
| IDE cache | \Users\Name\AppData\Local\Google\AndroidStudio... |
~/Library/Caches/Google/AndroidStudio... |
Safe (will slow down the first launch) |
| Gradle cache | \Users\Name\.gradle\caches |
~/.gradle/caches |
Safe (Internet required) |
| Emulator settings | \Users\Name\.android\avd |
~/.android/avd |
Deletes virtual devices |
Resetting settings and environment configurations
Sometimes the problem lies not in specific project files, but in global settings that were changed while working on it. If you have experimented with launch configurations, versioning schemes, or SDK paths, these settings may have been saved in your IDE user profile. In such cases, simply deleting the project folder is not enough, and a factory reset is required.Run Configurations), versioning schemes, or SDK paths, these settings may have been saved in the IDE user profile. In such cases, simply deleting the project folder is not enough and a factory reset is required.
To perform a reset, you can use the run command with the flag -resetSettings. This action will return all interface settings, fonts, plugins and tool paths to the “as after installation” state. Be careful: this operation will affect all projects, not just the one you want to delete. Therefore, use this method only in extreme cases when the environment behaves incorrectly after deleting the problematic project.
An alternative and softer method is to manually edit the configuration files stored in the settings directory. In these folders you can find files responsible for the list of recent projects (recentProjects.xml). By deleting a specific project entry from this XML file, you will remove it from the list on the welcome screen, even if the folder was physically deleted previously. This helps keep the interface clean and avoids trying to open paths that don't exist.
⚠️ Attention: Resetting settings via launch flags will remove all plugins and custom themes you have installed. Before performing this procedure, make sure that you have a list of required extensions to install again.
Where are the Android Studio settings files stored?
On Windows, the settings are located in the folder C:\Users\UserName\AppData\Roaming\Google\AndroidStudio[Version]. On macOS the path looks like ~/Library/Application Support/Google/AndroidStudio[Version]. This is where configuration files are stored that can be edited manually to remove records of old projects.
Management of virtual devices (AVD)
Often, along with the project, developers create specific emulator configurations (AVD —Android Virtual Device), customized to the requirements of a specific application. These disk images take up a significant amount of space (2 to 8 GB each) and are stored separately from the project code. Deleting a project does not automatically delete the virtual devices associated with it, so they need to be cleaned separately.
To manage emulators, open the device manager in the menu Tools → Device Manager (in older versions AVD Manager). In the list you will see all created virtual devices. Select the device that was used for the project under test and click the trash icon or menu item Delete. This action will permanently delete the system image and all data saved inside the emulator.
If you want to delete emulators manually through the file system, find the directory .android/avd in your home folder. Files with the extension .ini and folders with the extension .avdcorresponding to the names of your devices will be stored there. Deleting these files will free up disk space, but remember that the next time you start any project, you may have to create a new emulator from scratch.
Virtual devices are not strictly tied to a specific project and are stored in the global user profile. They must be deleted separately through Device Manager or a file manager to fully clean the system.
Using the terminal and command line
For advanced users and those who prefer automation, deleting projects can be done through the command line or terminal. This method is especially effective when you need to delete multiple projects at once or clear space on your continuous integration server. Using console utilities allows you to quickly find and delete files by name mask or modification date.
In operating systems of the Unix family (macOS, Linux), you can use the command rm -rf to recursively delete a directory. For example, the command rm -rf ~/AndroidStudioProjects/MyOldApp will instantly delete the project. In Windows PowerShell, the equivalent is the command Remove-Item -Recurse -Force. Be extremely careful when entering paths, as these commands do not ask for confirmation and do not send files to the trash.
You can also clear the Gradle cache with one command via the terminal, which is often faster than searching for folders manually. Running the cleanup script will ensure that any temporary build files remaining from the deleted project are erased. This is especially true if you are working on many microservices or modular applications where dependencies may overlap.
Example of clearing the Gradle cache on Linux/macOS
rm -rf ~/.gradle/caches/build-cache-1
rm -rf ~/.gradle/caches/modules-2
Example of deleting a project in Windows PowerShell
Remove-Item -Path "C:\Users\User\AndroidStudioProjects\OldProject" -Recurse -Force
⚠️ Attention: Deletion commands through the terminal are executed instantly and cannot be restored through the recycle bin. Always double-check the path to the directory you want to delete before pressing Enter to avoid accidentally erasing important data.
How to find the largest files in the projects folder?
On macOS, use the OmniDiskSweeper utility or the du -sh * command in the terminal. On Windows, you can use the free app WinDirStat or TreeSize Free to visualize which project folders are taking up the most disk space.
Frequently Asked Questions (FAQ)
Will a project be removed from the Recent Projects list if I simply delete the folder?
No, simple deleting a folder from the disk will not remove the entry from the list of recent projects on the welcome screen Android Studio. When you try to open such a project, you will receive the error “Project file does not exist.” To remove an entry from the list, you need to click on the three dots next to the project name in the list and select Remove from Recent Projects, or clear the IDE cache through the menu File → Invalidate Caches.
Is it safe to delete the .gradle folder in the project root?
Yes, the folder .gradlelocated inside directory for a specific project, contains temporary build files and cache only for that project. Removing it is safe and is often recommended when strange compilation errors occur. During the next build, Gradle will automatically recreate this folder and download the necessary files again.
How to delete a project if Android Studio does not start?
If the development environment does not start, you can still delete the project through the standard file manager of your operating system (Explorer, Finder). Find the folder with the project along the path you specified when creating it (usually AndroidStudioProjects), and delete it manually. This will not in any way affect the functionality of the IDE itself after it is repaired or reinstalled.
Does the deleted project take up space in the registry or system settings?
The project is not registered in the Windows system registry or similar macOS/Linux services as an installed app. All information about it is stored exclusively in the form of files on disk and entries in the configuration files itself Android Studio. After deleting the project folder and clearing the list of recent projects in the IDE, no traces remain in the system.
Is it possible to restore a deleted project?
If you deleted the project folder past the recycle bin (using Shift+Delete or terminal) and you do not have a backup copy in Git or cloud storage, recovery is almost impossible. The built-in Local History feature in Android Studio only stores data as long as the files exist on disk or until the IDE cache has been flushed. Therefore, always use version control systems.