Next-Gen App & Browser Testing Cloud
Trusted by 2 Mn+ QAs & Devs to accelerate their release cycles

To uninstall Android Debug Bridge (ADB), first stop the ADB server with adb kill-server, then delete the platform-tools folder (or uninstall the package you installed it with) and remove any platform-tools entry from your PATH. This removes the ADB tool from your computer. It is different from How to Turn Off Android Debug Bridge? on a device (which only disables USB Debugging) and from using ADB to uninstall apps. The steps below cover Windows, macOS, and Linux, plus the Android Studio SDK Manager route and how to verify the removal.
ADB runs a background daemon that holds open file handles on adb and the platform-tools directory. If you try to delete those files while the server is running, the removal can fail with a "file in use" error, especially on Windows. Stop it first:
adb kill-serverIf you installed ADB by extracting the platform-tools ZIP, follow these pointers:
C:\platform-tools) and delete the entire folder.Path and click Edit.platform-tools directory, then click OK to save.If you installed ADB through the Chocolatey package manager, uninstall it in one command (the adb package also bundles fastboot):
choco uninstall adbDelete the platform-tools directory. On macOS, Android Studio installs the SDK under ~/Library/Android/sdk, while manual installs often sit in ~/Android/Sdk, so remove whichever path applies:
rm -rf ~/Library/Android/sdk/platform-tools
rm -rf ~/Android/Sdk/platform-tools~/.zshrc or ~/.bash_profile and delete any line that adds platform-tools to PATH, then run source ~/.zshrc or open a new terminal.If you installed ADB with Homebrew, uninstall the cask in one command:
brew uninstall android-platform-toolsThe command depends on your distribution and package manager. Pick the one that matches your system:
sudo apt remove adb fastboot
# deep clean (purge configs and orphaned packages)
sudo apt-get --purge autoremove android-tools-adb android-tools-fastbootsudo dnf remove android-toolssudo pacman -R android-tools~/.bashrc or ~/.zshrc.If ADB came in through Android Studio and you want to remove only the ADB component while keeping the rest of the SDK, use the SDK Manager:
Prefer the command line? The sdkmanager CLI does the same thing:
sdkmanager --uninstall "platform-tools"Open a fresh terminal or command prompt and run the version check. If ADB is gone, the command should fail:
adb version
# expected: 'adb' is not recognized (Windows) / command not found (macOS, Linux)If adb version still prints a version number, a stray copy or a stale PATH entry remains. Track it down and clean it:
# macOS / Linux
which adb
# Windows
where adbUninstalling ADB from your computer does not change anything on your phone. The USB Debugging toggle in Developer Options stays exactly as it was, because that setting lives on the Android device, not on your machine. If you also want to disable debugging on the device, do it separately, see How to Turn Off Android Debug Bridge? for the steps.
Removed ADB locally but still need to install APKs, debug, or run Appium tests on Android? You do not have to maintain platform-tools on your machine at all. With a Real Device Cloud you upload your APK and run it on a remote, physical Android handset straight from the browser, with logs, screen recording, and ADB-backed debugging handled in the cloud. It is a clean way to keep testing right after you have uninstalled ADB from your local setup.
No. Turning off USB Debugging in Developer Options only disables the debug channel on your Android device, it does not remove the ADB tool from your computer. To uninstall ADB you have to delete the platform-tools folder or uninstall the package you installed, and clear any platform-tools entry from your PATH.
No. Removing ADB only deletes the platform-tools component (adb and fastboot). The rest of the Android SDK, the SDK Manager, and Android Studio remain installed. If you later need ADB again you can re-add platform-tools from the SDK Manager without reinstalling Android Studio.
Use the same package manager you installed it with: choco uninstall adb on Windows (Chocolatey), brew uninstall android-platform-tools on macOS (Homebrew), sudo apt remove adb fastboot on Debian/Ubuntu, sudo dnf remove android-tools on Fedora/RHEL, and sudo pacman -R android-tools on Arch/Manjaro.
On Windows, open Environment Variables, edit the Path variable, and delete any entry pointing to platform-tools. On macOS and Linux, remove the export lines that add platform-tools to PATH from your shell profile (~/.bashrc, ~/.zshrc, or ~/.bash_profile), then restart the terminal so the change takes effect.
Reinstall it the same way you would set it up the first time: download the official platform-tools bundle and add it to PATH, install it through a package manager, or open the Android Studio SDK Manager and re-check Android SDK Platform-Tools. See How to Setup Android Debug Bridge? for the full walkthrough.
It is strongly recommended. Running adb kill-server stops the background ADB daemon and releases the file locks it holds on adb and the platform-tools folder. On Windows in particular, deleting the folder while the server is running can fail with a file-in-use error.
KaneAI - Testing Assistant
World’s first AI-Native E2E testing agent.

TestMu AI forEnterprise
Get access to solutions built on Enterprise
grade security, privacy, & compliance