Development of mobile applications for the platform Android is a process that requires a stable and predictable environment. The development environment Android Studio over time accumulates a huge number of temporary files, index cache and user settings. This can lead to slow performance, strange compilation errors, or even complete UI failure to respond to user input. In such situations, standard cleaning methods are often not effective enough.
Sometimes the only correct solution is a complete reset of the configuration to the “fresh installation” state. This process removes all user data, key settings, plugins and cache, returning the app to its original state. It is important to understand that this irreversible operationwill delete all your personal settings, so a preliminary backup of critical settings is a mandatory step before starting the procedure.
In this article we will analyze in detail all the ways to restore the IDE's functionality, from softly clearing the cache to radically deleting system configuration folders. You will learn where hidden settings files are stored in different operating systems and how to properly delete them to avoid version conflicts in the future.
Preparing for a full configuration reset
Before you begin deleting files, you need to assess the extent of potential data loss. The reset will affect not only visual themes and fonts, but also SDK paths, emulator settings, and signed debug keys. If you are using VCS (version control system), make sure that all local code changes are committed and pushed to the server, since resetting the IDE does not affect the project files, but may reset the Git integration settings.
It is recommended to export the current settings if you plan to restore some of them later. In the menu File select item Manage IDE Settings, and then Export Settings. This will create an archive .jar or .zip with your current configuration. However, if the purpose of the reset is to fix a critical error, restoring old settings may bring back the problem itself.
⚠️ Attention: Deleting configuration folders will affect all versions of Android Studio installed on the computer if they use a common settings directory. Make sure that you are not using other versions of the IDE in parallel for different projects.
It is also worth checking for active licenses or connected Google accounts. After the reset, you will need to log in again to access some features, such as syncing settings via the cloud or using paid plugins. Write down the names of critical plugins that you installed manually to quickly restore your working environment.
Using built-in cleaning functions
The safest and easiest way to try to fix problems without completely deleting files is to use built-in diagnostic tools. Modern versions Android Studio (starting with versions based on IntelliJ IDEA 2020+) implement a powerful cache management mechanism. It allows you to clear file indexes, which are often the reason why search does not find classes or navigation does not work correctly.
To access this function, go to the menu File and select item Invalidate Caches.... A dialog box will open with several options. Here you can choose which data you want to delete. Usually it is enough to check the boxes Clear file system cache and Local History and Clear VCS Log caches and indexes. This action will restart the IDE and rebuild the indexes from scratch, which can take from a few minutes to half an hour depending on the size of the projects.
If the standard cache clear does not help, you can try a deeper reset through the help menu. In some versions, an option is available Help -> Edit Custom Properties or Edit Custom VM Options, where you can force change the memory allocation parameters, which sometimes solves problems with crashes. However, this is not a complete reset, but only fine-tuning of the environment.
Before clearing the cache, close all open projects. This will prevent possible file locking conflicts and speed up the process of rebuilding indexes after a restart.
Remember that the operation Invalidate Caches / Restart does not delete your custom interface settings, plugins, or keymaps. It only affects temporary data generated during operation. If the problem lies in a damaged configuration file idea.properties or plugin settings, this method will be useless, and you will have to move on to manually deleting folders.
Manually deleting configuration folders in Windows
In the Windows operating system, configuration files and cache are stored in hidden system folders of the user profile. You can access them through File Explorer, by turning on show hidden items, or by directly entering the path in the address bar. The folder structure has changed with the release of new versions, so it is important to know the exact location for your version Android Studio.
The main configuration folder for versions 2020.1 and later is usually located along the path C:\Users\%USERNAME%\AppData\Roaming\Google\AndroidStudio[Version]. Settings files, plugins and logs are stored here. The cache folder that takes up the most space is located at C:\Users\%USERNAME%\AppData\Local\Google\AndroidStudio[Version]. Removing these directories is equivalent to the first launch of the app after installation.
For versions older than 2020 (for example, 3.x or 4.x), the paths are different. The configuration was stored in C:\Users\%USERNAME%\.AndroidStudio[Version], and the cache in C:\Users\%USERNAME%\.AndroidStudio[Version]\system. When manually deleting, make sure that the process studio64.exe is completely completed in the task manager, otherwise some files may be blocked and will not be deleted.
| Data type | Path (Windows 10/11) | What is stored |
|---|---|---|
| Configuration (Roaming) | %APPDATA%\Google\AndroidStudio... |
Settings, plugins, key maps |
| Cache (Local) | %LOCALAPPDATA%\Google\AndroidStudio... |
Indexes, temporary files, logs |
| System settings | %APPDATA%\Android... |
Configuration of emulators and SDK (partially) |
☑️ Check before deleting in Windows
After deleting the folders, the next time you start Android Studio you will be prompted to go through the initial setup wizard, as during the first installation. You will have to re-select a theme, install plugins and specify the path to the Android SDK if it was not found automatically. This ensures that no corrupt configuration files remain on the system.
Clearing settings in macOS and Linux
Operating system users macOS should look for configuration files in the user library. The path to the settings for new versions of the IDE looks like ~/Library/Application Support/Google/AndroidStudio[Version]. The cache is located in ~/Library/Caches/Google/AndroidStudio[Version]. It is convenient to use the terminal to delete, since some folders may be hidden in the Finder by default.
B environment Linux file structure follows XDG standards. The configuration is usually located in a hidden folder ~/.config/Google/AndroidStudio[Version], and the cache is in ~/.cache/Google/AndroidStudio[Version]. It's also worth checking for old files in your home directory starting with a dot if you've previously used older versions of studio. The command rm -rf should be used with extreme caution.
⚠️ Attention: On macOS, the Library folder is hidden. To quickly navigate to it in the Finder, click
Command + Shift + Gand enter the path manually. Do not delete the entire Library folder, just the Google or AndroidStudio directory.
If you are using different versions of Android Studio (for example, Stable and Canary), make sure to delete only the folders of the version that is causing problems. Removing the stable version configuration will not affect the Canary configuration as they use different IDs in their folder names. This allows you to test the reset without the risk of losing the working environment of the main version.
Commands for quick reset in the terminal (macOS/Linux)
For macOS: rm -rf ~/Library/Application\ Support/Google/AndroidStudio* && rm -rf ~/Library/Caches/Google/AndroidStudio*|For Linux: rm -rf ~/.config/Google/AndroidStudio* && rm -rf ~/.cache/Google/AndroidStudio*|After executing the commands, restart the system to apply the changes.
Resetting the emulator and SDK settings
Often the problems are not with the IDE itself, but with the tools that it manages. The Android emulator (Android Virtual Device) has its own settings files and disk images that can become corrupted. Resetting Android Studio does not always clear the emulator data completely. To do this, you need to use a tool Device Manager inside the app or a command line utility avdmanager.
To reset the emulator to factory settings, open Device Manager, select the desired device and click on the three dots in the action bar. Select item Wipe Data. This will delete all user data inside the virtual device, but will preserve its configuration (screen resolution, Android version). If a complete removal is required, use the command Delete.
As for Android SDKresetting it means removing all loaded platforms, build tools and system images. This is a last resort and takes a long time to reload. Usually it is enough to delete the folder build-tools or platform-tools inside the SDK directory to force the package manager to download them again. The path to the SDK can be found in the settings Appearance & Behavior -> System Settings -> Android SDK.
Resetting the emulator via Wipe Data solves 90% of problems with the virtual device freezing on the splash screen or ADB connection errors.
Sometimes there is a version conflict between the build tools (Gradle) and the SDK. In this case, it is recommended to clear the global Gradle cache. In Windows this is the folder C:\Users\%USERNAME%\.gradle, in macOS/Linux - ~/.gradle. Deleting the folder caches internally will force the system to redownload all project dependencies, which can correct synchronization errors.
Restoring work after a reset
After all configuration folders are deleted and the app is launched for the first time, you will see a welcome screen. At this stage, it is important to configure the basic settings correctly to avoid repeated problems. Choose a theme that's easy on the eyes and customize the code editor font. Don't install all the plugins at once - add them as needed to identify potential conflicts.
Be sure to check your compiler settings. Go to Settings (or Preferences on macOS) and make sure the correct JDK is selected. In modern versions, the built-in JBR (JetBrains Runtime) is used by default, which is the optimal choice. Also check the memory allocation settings in the Appearance & Behavior -> System Settings -> Memory Settingssection, increasing them if necessary for larger projects.
If you used export settings before the reset, now is the time to try importing them. However, do this with caution: if the problem was caused by an error in the settings, the import will bring it back. It is better to configure the environment manually, using export only for key maps or color schemes if they were complex.
⚠️ Attention: The interface and location of settings may vary slightly depending on the version of Android Studio and the installed updates. Always check the official documentation when looking for specific parameters.
After the first launch, create a simple test project "Hello World". If it builds and starts without errors, then the reset was successful and the environment is ready to work on basic tasks.
Frequently asked questions (FAQ)
Will resetting my settings delete my projects and source code?
No, a full reset of Android Studio affects only the configuration files of the app itself, cache and plugins. Your projects, source code and resource files, stored in separate folders on disk, will remain intact. However, project-specific settings stored in a folder .idea within the project may require resynchronization.
What to do if Android Studio does not start even after a reset?
If clearing the configuration folders did not help, the problem may be an incompatible Java version, corrupted installation files of the app itself, or a driver conflict video cards. Try completely uninstalling the app through the control panel, downloading a fresh installer from the official website and installing it again, checking the system requirements.
Is it possible to reset only the plugin settings without touching the rest?
Yes, you don’t need to delete all folders for this. Just go to the configuration directory (for example, .../AndroidStudio[Version]/plugins) and delete the contents of this folder. Or, inside the IDE itself, go to the plugin settings and disable all third-party extensions, leaving only the pre-installed ones.
Where are error logs stored for diagnosing problems?
Android Studio operation logs are located in the folder log inside the configuration directory. In Windows, the path is usually %APPDATA%\Google\AndroidStudio[Version]\log, and in macOS/Linux - ~/Library/Logs/Google/AndroidStudio[Version] or ~/.config/Google/AndroidStudio[Version]/log. The file idea.log contains basic information about errors.