Many novice developers and testers are faced with a situation where the installed software begins to take up a critical amount of disk space. Standard removal of an integrated development environment (IDE) often does not affect virtual devices, which continue to lie “dead weight” in system folders. This leads to the fact that even after uninstalling the app, gigabytes of data remain untouched. Android emulator begins to take up a critical amount of disk space. Standard removal of an integrated development environment (IDE) often does not affect virtual devices, which continue to lie “dead weight” in system folders. This leads to the fact that even after uninstalling the app, gigabytes of data remain untouched.
The complete cleaning procedure requires a careful approach, since virtual machine files are scattered in different directories depending on the operating system. You will not only have to remove a shortcut or app, but also manually clean out hidden configuration files, disk images and registry keys. Below we will analyze in detail each stage of this process for Windows, macOS and Linux.
Preparing for deletion and creating a backup copy
Before you take drastic action, you need to understand what data you are losing. The emulator stores not only system images, but also user data, installed applications and debug logs inside the virtual device. If you have important projects or test data inside a particular AVD (Android Virtual Device), it is worth saving them.
Find the directory where your virtual devices are stored. By default on Windows, this is path C:\Users\UserName\.android\avd. Copy the folders with the extension .avd and their corresponding files .ini to a safe place. This will allow you to restore the state of the emulator in the future if the deletion was erroneous.
Before deleting, check the size of the .android folder - sometimes it can take up more than 20 GB if you created many images with different versions of Android.
It is also recommended to close all running development-related processes. Open the task manager and make sure that processes adb.exe, qemu-system or itself Android Studio are not active. Working with files that are used by running apps may lead to access errors or data corruption.
☑️ Preparing for cleaning
Removal through standard operating system tools
The most obvious, but often insufficient step is to use a standard uninstaller. In Windows, this is done through the Control Panel or System Settings. Find in the list of installed apps Android Studio or individual components of the emulator if they were installed as an independent package.
Run the removal wizard and follow the instructions on the screen. However, it is worth remembering that a standard uninstaller often leaves behind user data. It removes the app's executable files, but is careful about the configurations, assuming that you may want to use them later.
⚠️ Attention: Standard removal does not affect the SDK folder and directories with virtual machines. You must delete them manually, otherwise the disk space will not be freed.
The process looks different on macOS. Usually it is enough to drag the application Android Studio.app from the Applications folder to the trash. But even here, hidden libraries remain in the system. For complete cleaning, you will need to find and delete files in the directory ~/Library/Application Support/Google/AndroidStudio.
Manually cleaning emulator files and AVD images
This is the most important step that guarantees real freeing up space. Virtual device files are stored in hidden folders in the user profile. You need to turn on show hidden files and folders in Explorer to see them.
On Windows, go to path C:\Users\YOUR_USER\.android. Here you will find a folder avdthat contains all the disk images. Deleting this folder will completely erase all virtual phones and tablets you have created. Also check the folder C:\Users\YOUR_USER\AppData\Local\Android\Sdkif the emulator was installed with it.
For macOS and Linux users, the path will look like ~/.android/avd. Use a terminal or file manager to navigate to this directory. The command rm -rf ~/.android/avd in the Linux or macOS terminal will instantly delete all virtual device configurations.
| OS | Path to AVD files | Path to emulator cache | Action |
|---|---|---|---|
| Windows | %USERPROFILE%\.android\avd |
%LOCALAPPDATA%\Android\Emulator |
Delete folders |
| macOS | ~/.android/avd |
~/Library/Android/sdk/emulator |
Move to trash |
| Linux | ~/.android/avd |
~/.android/emulator |
Command rm -rf |
Don't forget to also clear the emulator cache, which can take up a significant amount of space. Cache files are often stored in subfolders with names like cache or snapshots inside the directory of a specific device. Deleting them is safe, but the next time you start the emulator it will take a little longer to load, since it will have to re-create temporary files.
What are .qcow2 files?
These are disk image files in the QEMU format, which take up the bulk of the space. They dynamically expand as applications are installed in the emulator and can reach tens of gigabytes.
Cleaning the Windows registry and environment variables
After deleting files, you need to get rid of entries in the system registry that may point to non-existent paths. This is especially true on Windows, where leftover entries may conflict with future installations of other development software.
Click Win + Rtype regedit and press Enter. Follow the branch HKEY_CURRENT_USER\Software\Android or HKEY_LOCAL_MACHINE\SOFTWARE\Android. If you see keys associated with Android Studio or the emulator that relate to removed components, you can delete them. Be extremely careful: deleting the wrong keys may disrupt the operation of other apps.
⚠️ Attention: Before editing the registry, be sure to create a backup copy of it through the “File” → “Export” menu. An error in the registry can lead to system instability.
Also check your environment variables. Open system properties, go to the "Advanced" section and click the "Environment Variables" button. Find the variable ANDROID_HOME or ANDROID_SDK_ROOT. If you have completely removed the SDK, these variables should be deleted or the path should be changed to the current one if you plan to use other tools.
The variables Path may also contain links to folders tools or platform-tools. Remove lines leading to non-existent directories to avoid errors when calling commands in the terminal. This will ensure the cleanliness of the system environment.
Using the command line for deep cleaning
For advanced users, the most effective method is to use the command line or terminal. This allows you to perform the removal quickly and check the result immediately. On Windows, use PowerShell or Command Prompt with administrator rights.
You can use the command to force directory deletion. For example, the command below will delete the avd folder and all its contents without additional confirmation:
rmdir /s /q %USERPROFILE%\.android\avdIf you are using Linux or macOS, a similar operation is performed through the terminal. The command rm -rf is a powerful tool, so make sure the path is correct. An error in one letter can lead to the deletion of important system files.
It is also worth checking processes that could be stuck after an unsuccessful closing of the emulator. The command taskkill /F /IM qemu-system* in Windows will forcefully terminate all QEMU emulator processes, which will unlock files for deletion.
Using the command line speeds up the process significantly and allows you to delete files that may be blocked by the Explorer GUI.
Checking results and freed up space
After performing all the manipulations, you need to make sure that the system is actually cleaned. Use built-in disk analysis tools or third-party utilities like WinDirStat or DaisyDiskto visually assess the free space.
Pay attention to the folder Temp. The emulator often creates temporary files there while running. Emptying this folder using the standard Windows Disk Cleanup utility will help remove residual sessions that were not automatically deleted.
If you plan to reinstall the emulator or use alternative solutions, your system is now ready for a clean install. The absence of old conflicts and junk files will ensure more stable operation of the new software.
Alternatives to Android Emulator
There are lightweight emulators, such as Genymotion or NoxPlayer, which use other virtualization mechanisms and can work faster on weak hardware.
⚠️ Attention: Operating system interfaces and file paths may differ slightly in different update versions. Always check the latest documentation if the standard paths are not suitable.
Frequently asked questions (FAQ)
Will my Android Studio project be deleted along with the emulator?
No, your projects are stored in a separate folder that you specified when creating (usually in AndroidStudioProjects). Removing the emulator and SDK does not affect the source code of your applications, unless you deleted these folders manually.
Is it possible to delete only one specific virtual phone, and not all?
Yes, you do not need to delete the entire folder to do this. avd. Go to the directory .android/avd and delete only the folder whose name matches the name of the device being deleted (for example, Pixel_4_API_30.avd), as well as the corresponding file .ini.
Why, after deleting the emulator, the disk space was not freed up?
Most likely, you only deleted the app, but not the files disk images. Check hidden folders .android and AppData. Also empty the Recycle Bin, as the files may have been moved there rather than permanently deleted.
Does Java (JDK) need to be uninstalled when uninstalling the emulator?
No, Java Development Kit is an independent component. You may need it for other programming tasks or running other applications. Remove the JDK only if you are sure that it is no longer used anywhere.
How to prevent the emulator from rapidly growing in size in the future?
Regularly Cold Boot the emulator and use the “Wipe Data” function when creating new devices. Also try not to install unnecessary heavy applications inside the virtual machine if they are not needed for tests.