How To Uninstall Android Studio Completely

Deleting the Android Studio app from Applications or Control Panel does almost nothing by itself, which surprises most people the first time they try it. The SDK downloads, the emulator images, the Gradle cache: none of that goes anywhere unless you clear it out separately, folder by folder. Uninstalling Android Studio properly means going after all of it, not just the app.

Google builds and maintains Android Studio as the official IDE for native Android development. It bundles the SDK, an emulator, and the Gradle build system into one install, distributed for Windows, macOS, and Linux, and it’s built on the IntelliJ Platform from JetBrains.

Not everyone who tries it sticks around, either. The Stack Overflow Developer Survey 2025 found only 43.2 percent of Android Studio’s current users want to keep using it, a lower share than every other JetBrains-built IDE the same survey tracked.

What Is Android Studio

One install here covers the code editor, a device emulator, and the Android SDK, built specifically for Android development. Nobody has to stitch together separate tools just to get a project compiling. Google publishes and maintains the IDE itself.

A handful of things separate it from a general-purpose code editor. It’s built on the IntelliJ Platform from JetBrains, which is where its menus, shortcuts, and settings dialogs come from, and it ships with the Gradle Build System for compiling projects and resolving dependencies. There’s also an Android Virtual Device manager built in, so testing an app doesn’t require a physical phone plugged in, and its own JetBrains Runtime (a packaged JDK) comes bundled too, meaning there’s no separate Java install to manage just to open the IDE.

Google standardized Android tooling around this one IDE years ago, and that decision still shows up in the numbers. Android Studio sat at 15 percent of all developers in the Stack Overflow Developer Survey 2025, down slightly from 16.1 percent in 2024, even as several competing editors gained ground that same year.

Release names change every version, which is where things get confusing later. Ladybug, Meerkat, Narwhal, Otter, Panda, and the current Quail line are all the same product under different codenames, and that naming habit shows up directly in file paths, which matters once you’re hunting for leftover folders.

Not ready to remove anything yet? A walkthrough of how to use Android Studio covers the editor, the emulator, and the build tools in more depth than an uninstall guide needs to.

What Happens When You Uninstall Android Studio

Removing the Android Studio application only removes the application. Everything it downloaded to actually build and run an app sits in separate folders that no standard uninstall method touches, on any of the three major operating systems.

A normal uninstall takes care of the program files and its shortcut, dock icon, or desktop launcher, and if you installed through the Toolbox App, that entry disappears too. What it leaves behind is the bigger pile: the Android SDK (platform tools, build tools, every API level you ever downloaded), AVD system images and emulator snapshots, Gradle’s dependency cache and daemon logs, plus the versioned configuration, plugin, and log directories tied to your specific install.

The numbers behind that gap are worth knowing before you go looking for space. Android Developers documentation puts the minimum free disk space at 8 GB, combined across the IDE, the SDK, and the emulator, and gives the default SDK path on Windows as %USERPROFILE%\AppData\Local\Android\Sdk. The default Gradle user home, per Gradle Documentation, sits at ~/.gradle on macOS and Linux, or C:\Users\[username]\.gradle on Windows.

That gap is why the Android SDK tools downloaded on day one are usually still sitting there, untouched, after the uninstall wizard says it’s finished. It’s also why a fresh install often goes faster than the first one did. Most of what a clean install of Android Studio needs is already cached locally from before.

Where Android Studio Stores Its Files on Each Operating System

Android Studio keeps its own settings split across four spots on disk: configuration, plugins, system cache, and logs. That pattern isn’t unique to this one IDE, either. It comes straight from the IntelliJ Platform that Android Studio shares with IntelliJ IDEA, so anyone who has cleaned up a JetBrains IDE before will recognize these folder names on sight.

Android Developers documentation, last updated March 2026, confirms these exact paths and notes that AndroidStudio becomes AndroidStudioPreview for canary and RC builds.

Windows file locations

Beyond what’s in the table, the Android SDK defaults to %USERPROFILE%\AppData\Local\Android\Sdk. AVD images and the debug signing keystore live under %USERPROFILE%\.android, and Gradle’s cache sits at C:\Users\[username]\.gradle.

Command line tools such as adb live inside the SDK’s platform-tools folder. An ADB commands cheat sheet is worth keeping handy if you plan on checking any of this from a terminal before deleting anything.

macOS file locations

The SDK sits at ~/Library/Android/sdk by default on macOS. AVD data and the debug keystore both live in ~/.android, a dotfile folder that Finder hides from view unless you go tell it to show hidden files, which trips people up more often than it should.

Gradle’s cache follows the same ~/.gradle pattern as on Linux, since both are Unix-style home directories underneath.

Linux file locations

Linux keeps the SDK at ~/Android/Sdk when the IDE’s own setup wizard did the installing, though a distribution package can put it somewhere else entirely.

A few things are worth checking before assuming a file is missing. AVD configuration and images live in ~/.android, mirroring the macOS layout, and Snap-installed copies keep their data under /snap/android-studio, isolated from the manual paths above. There’s also Android Studio for Platform, a separate product entirely, which defaults to /opt/android-studio-for-platform instead.

How to Uninstall Android Studio on Windows

Removing Android Studio on Windows takes two passes. First the built-in uninstall wizard handles the application itself, then a manual sweep catches whatever it leaves behind.

Close Android Studio, any running emulator, and any background Gradle daemon before starting. Windows will refuse to delete files that are still in use.

1. Open Settings, go to Apps, then Installed apps (or Control Panel, then Programs and Features on older builds)
2. Find Android Studio in the list and select Uninstall
3. Work through the wizard, which offers a separate checkbox for Android user settings, covering your AVDs, SDK caches, and signing keystores
4. Leave that checkbox ticked if you want a full removal rather than a partial one
5. Restart if Windows asks for it, since one locked file can quietly block the rest of the process
6. Open File Explorer and check %LOCALAPPDATA%\Google and %APPDATA%\Google for any AndroidStudio folder still sitting there

That wizard checkbox does more work than most people expect from it. Skipping it is the single most common reason a Windows uninstall still leaves a multi-gigabyte SDK folder behind.

How to Uninstall Android Studio on macOS

macOS has no built-in uninstaller for third-party applications. Removing Android Studio means moving the app bundle to Trash, then clearing out what Trash never reaches.

1. Quit Android Studio, and stop any running emulator still listed in Activity Monitor
2. Open Finder, go to Applications, and drag Android Studio to the Trash
3. Empty the Trash to actually reclaim the space
4. Open Terminal and remove the configuration and plugin files with rm -Rf ~/Library/Application\ Support/Google/AndroidStudio*
5. Remove cached data with rm -Rf ~/Library/Caches/Google/AndroidStudio*
6. Remove the log files with rm -Rf ~/Library/Logs/Google/AndroidStudio*

If Homebrew handled the original install, running brew uninstall --cask android-studio takes care of the app bundle. It still leaves the SDK, AVD, and Gradle folders exactly where the section above describes, so that part doesn’t change.

Dragging the icon to Trash feels complete. The app disappears from Launchpad right away.

It isn’t complete, though. Nothing under ~/Library gets touched by that one drag.

How to Uninstall Android Studio on Linux

The right removal command depends entirely on how Android Studio got installed in the first place, and Linux offers more than one path here.

Snap installs

1. Run snap list to confirm the exact package name, usually android-studio
2. Run sudo snap remove android-studio
3. Confirm the /snap/android-studio directory is actually gone

Tarball installs

1. Delete the extracted folder, commonly ~/android-studio or /opt/android-studio
2. Remove the desktop launcher entry, typically at ~/.local/share/applications/jetbrains-android-studio.desktop
3. Clear the hidden configuration, cache, and share directories under ~/.config/Google, ~/.cache/Google, and ~/.local/share/Google

A Snap-installed copy has one real advantage here: a single sudo snap remove call takes the application with it in one pass, with no separate desktop entry to go hunting for afterward. Tarball installs don’t get that shortcut, since nothing ever registered them with a package manager to begin with.

How to Remove Android Studio Installed Through JetBrains Toolbox App

When JetBrains Toolbox App handled the install, removing the IDE and removing Toolbox are two separate actions. Doing one doesn’t do the other, and skipping that distinction is where most of the confusion starts.

1. Open Toolbox App and find Android Studio in your list of installed tools
2. Click the menu next to it and choose Uninstall
3. Confirm the removal; Toolbox deletes that one Android Studio instance but leaves Toolbox itself, plus the SDK, AVD, and Gradle folders covered earlier, untouched

Removing Toolbox App itself

On Windows, run its own uninstaller directly, at %LocalAppData%\JetBrains\Toolbox\bin\Uninstall.exe, a path confirmed in JetBrains’ own Toolbox App documentation.

On Linux, uninstall every application Toolbox manages first, then delete ~/.local/share/JetBrains/Toolbox and everything inside it, plus ~/.local/share/applications/jetbrains-toolbox.desktop.

JetBrains treats Toolbox removal on macOS as a standard drag-to-Trash operation, same as any other Mac app, and doesn’t document any separate steps there for clearing out leftover cache or preference files the way it does for Linux.

Linux stays fully manual, regardless of how smoothly the original install went.

Manual Removal Versus Third-Party Uninstaller Tools

Deleting Android Studio’s folders yourself costs nothing but time. A dedicated uninstaller trades that time for a subscription fee and a scan you have to trust without actually seeing what it touches.

CleanMyMac X’s own store page lists that $39.95 annual rate for one Mac, starting at $3.33 a month, current at version 4.15.14 as of December 2025, per MacPaw.

Doing it by hand is free, and nobody but you decides what gets deleted and when. No third-party app gets to scan your whole file system in the process, either. The tradeoff is time: it’s slow, and it’s easy to miss a folder that even a guide like this one skipped somewhere.

Third-party tools flip that. They catch leftovers a manual pass would probably miss, and that’s a real advantage. But a paid tool like CleanMyMac X adds a recurring cost for something most people do once or twice a year at most, and a scan-and-delete tool can flag files it doesn’t fully understand, so trusting a blanket “select all” button is a real risk.

Manual removal stays the safer choice on a machine running other JetBrains software. A broad automated scan has no reliable way to know which cached files belong to Android Studio alone and which ones a tool like PyCharm still needs.

How to Delete Leftover Android Studio Files Manually

Everything named in the file locations section earlier is fair game once the application itself is gone. Delete in this order, though, to avoid breaking anything else running on the same machine.

1. Confirm no other JetBrains IDE is installed, since some share the same parent Google or JetBrains folder structure
2. Delete the versioned configuration, plugin, system, and log directories named earlier, one version folder at a time
3. Delete the SDK folder only after checking whether Flutter, React Native, or a separate command-line toolchain still points to it
4. Delete individual AVD system images from inside the avd subfolder rather than the whole hidden folder, if a debug keystore or other credential still lives there
5. Clear the Gradle cache last, since an active project outside Android Studio may still be reading from it mid-build

Android Studio actually automates part of this on its own. On first launch of a new major version, it scans for directories tied to versions with no matching installation left, and offers to remove them through a Delete Unused Android Studio Directories dialog that lists each folder’s size and last-modified date before you confirm anything, per Android Developers documentation.

That built-in cleanup only fires on launch. It does nothing for someone who has already uninstalled the application, since there’s no version left around to trigger it.

Verify nothing named android or AndroidStudio remains by searching the AppData and user profile folders on Windows, or the Library and home folders on macOS and Linux. Old emulator system images are usually the single biggest recoverable chunk here. A project tested against three or four API levels can easily be carrying that many separate downloads nobody has opened in months.

Why Android Studio Fails to Uninstall

An uninstall that hangs or throws an error almost always comes down to one of a few things going on underneath. A running emulator, a Gradle daemon still active in the background, or an open project holding a file handle can all block the operating system from deleting that file mid-process, and this is the most common culprit by far.

Permission mismatches cause a fair share of the rest. If Android Studio or its SDK folder was ever installed or modified using sudo on macOS or Linux, a normal user account can lack the rights to delete what root created. Windows has its own version of this problem: it keeps a record of how to run each program’s uninstaller, and if that record points to a file that no longer exists, Programs and Features shows the entry but can’t actually act on it.

Antivirus software gets blamed less often than it should. Real-time protection sometimes locks a file it’s actively scanning, and that alone can stall a Windows uninstall wizard partway through with no clear error message at all.

Android Developers troubleshooting documentation describes a closely related case directly. An IDE update can fail on Windows with a message like “Can’t delete C:\some\path\file”, caused by a process such as a leftover Gradle daemon still holding that file open. The documented fix is to open Task Manager, end any Java or Gradle process still running, and retry. That fix applies just as well to a stalled uninstall, not only a stalled update, since both fail for the same reason: something still has the file open.

Before assuming the worst, close every Android Studio window and any standalone emulator instance, check Task Manager or Activity Monitor for a lingering java or gradle process, and confirm the account running the uninstall actually has admin or sudo rights on the folders the IDE created.

When Uninstalling Android Studio Does Not Free Up Disk Space

Removing Android Studio, even thoroughly, sometimes changes nothing on a disk usage graph. There’s a fairly simple explanation, and it usually comes down to what else on the machine is still quietly relying on those same folders.

Flutter’s own setup documentation has its Android toolchain read the ANDROID\_HOME or ANDROID\_SDK\_ROOT environment variable to locate the SDK, independent of whether Android Studio itself is even installed. Delete Android Studio without checking those variables first, and a Flutter or React Native project on the same machine keeps referencing an SDK folder you assumed was already gone, or breaks outright the moment you delete that folder too.

Gradle plays into this as well. Its own documentation places dependency caches under one shared user home directory rather than inside each project, specifically so multiple projects can reuse the same downloaded libraries. A plain Java or Kotlin backend built with the same build automation tool draws from that identical cache, so removing Android Studio never actually touches it.

Then there’s the emulator itself. AVD system images and hardware acceleration components install through the SDK Manager, not through the Android Studio installer, so an uninstall that only removes the application leaves them exactly where they were.

Put those three together and a before-and-after disk usage comparison often shows the same total. From the file system’s point of view, almost nothing large actually left the drive.

Should You Reinstall or Repair Android Studio Instead of a Full Uninstall

A full uninstall isn’t always the fix a broken Android Studio actually needs. Most corruption and indexing problems respond to something far smaller, and it’s worth trying those first.

File, then Invalidate Caches and Restart clears the IDE’s internal indexing cache without touching the SDK or any project. File, then Repair IDE goes further: a guided recovery process inherited from the IntelliJ Platform that covers index rescans and project reopening before it ever clears a cache. For build errors that trace back to stale compiled output rather than the IDE itself, Build, then Clean Project is usually enough on its own.

JetBrains’ own IntelliJ Platform documentation describes Repair IDE as a step-by-step recovery process, letting you stop after any stage once the problem clears rather than wiping every cache at once.

A version downgrade is a different case, though. Moving to an older major version, rather than an older patch release within the same one, is where a clean uninstall earns its place, since updating Android Studio normally only moves forward, and old version-specific settings can conflict with a downgraded install.

Repair IDE or Invalidate Caches takes minutes, with no lost disk space and nothing to redownload. A full uninstall and reinstall can run an hour or more once the SDK, platform tools, and at least one system image have to come back down. Reach for the heavier option only after the lighter ones have actually failed, not as a first step out of habit.

FAQ on How To Uninstall Android Studio

What is the difference between an Android Studio uninstall and an update

An update replaces the current build in place, through the stable, RC, or canary channel, and keeps your SDK, plugins, and settings intact the whole time. Uninstalling is a different operation entirely: the application goes away completely, but the SDK, AVD, and Gradle cache stay behind as separate folders that nothing touched.

Does the AVD emulator get removed automatically when you uninstall Android Studio

No. AVD profiles and system images live in a separate folder that no application-level uninstaller touches, whether that’s Windows, macOS, or Linux. Removing them means deleting that folder by hand, or working through the AVD manager, before the IDE itself is gone.

Do you need to remove the Android SDK separately if other tools use it

No, not if something like Flutter, React Native, or a standalone build still references that SDK path. Check what’s actually pointing to it before doing anything. Deleting a shared Android SDK breaks any other project relying on it, immediately and without warning.

Is it safe to delete the ANDROID\_HOME environment variable after uninstalling

Yes, once nothing on the machine still points to that SDK path. Deleting ANDROID\_HOME while a tool like Flutter or a CI pipeline still expects it will break that tool’s builds, and it stays broken until you restore the variable or reinstall the SDK it needs.

What Should You Verify Last in How To Uninstall Android Studio?

Confirming Android Studio is fully removed comes down to checking things in a specific order: the application entry itself first, then the versioned configuration and cache directories, and only after that any SDK-dependent tool elsewhere on the machine that still expects the old install path.

That order matters. Deleting a shared dependency before confirming nothing else needs it risks breaking a project that has nothing to do with the IDE at all.

Android Developers documentation and Flutter’s own setup guide describe the SDK path and the ANDROID\_HOME variable separately. Put together, though, they point to a shortcut neither source states outright: leaving that variable and its target folder untouched keeps every existing project buildable through a command-line toolchain, even once the IDE itself is gone.

Reaching that point is usually also where people start comparing cross-platform app development tools against the native workflow they just left behind.

• Author
• Recent Posts

Bogdan Sandu

Bogdan Sandu is a front-end developer at TMS Outsource with 8+ years of experience in web technologies. He writes about developer tools, software platforms, and web workflows based on daily hands-on use.

Latest posts by Bogdan Sandu (see all)

• Google Play Account Suspended: What to Do - October 5, 2026
• How to Plan a Successful Data Migration Without Disrupting Business Operations - October 5, 2026
• How to Turn On Dark Mode in Notepad++ (Built-In, No Plugin) - October 3, 2026