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

Turning off Android Debug Bridge (ADB) happens in two places. On your computer you stop the adb server with adb kill-server, and on your Android device you disable USB debugging (and Wireless debugging, if you used it) from Developer options. Doing both stops ADB completely without uninstalling it, so you can switch it back on whenever you need it.
People mean different things by "turn off ADB." The table below maps each action to where it happens and whether it is reversible, so you can pick the right one before running any command.
| Action | Where it runs | What it does | Reversible? |
|---|---|---|---|
| Kill the server | Computer | Stops the host-side adb process only | Yes, restarts on next command |
| Disable on device | Android device | Phone stops accepting ADB connections | Yes, re-enable in Settings |
| Uninstall | Computer | Removes platform-tools and the adb binary | No, must reinstall |
If you only want ADB to stop running for now, you need the first two rows. The third row, removing ADB for good, is covered in our How to Uninstall Android Debug Bridge? guide.
The adb server is a background process on your machine that brokers traffic between your terminal and any connected device or emulator. Stopping it is the cleanest way to halt all ADB activity from the host side:
adb is on your PATH.adb kill-serverHost-only: This terminates the adb server process on your computer and disconnects any attached devices and emulators from that session. It does not stop the adbd daemon on the phone and changes nothing on the device itself.
It restarts automatically: The server relaunches the next time you issue any adb command, so killing it is a pause rather than a permanent off switch. To start it again deliberately, run adb start-server.
If you only want to drop one connection instead of stopping the whole server, for example a single networked device, use the disconnect command:
adb disconnectKilling the server only pauses ADB on the host. To stop the phone from accepting ADB connections at all, including from any other computer, turn off USB debugging on the device:
Turning off USB debugging is the most important step for security, because ADB has no transport-level authentication beyond the one-time RSA prompt. Revoking authorizations is a useful extra step if you have connected the phone to shared or untrusted machines.
If you ever paired your device for ADB over Wi-Fi, killing the USB session is not enough; the wireless channel stays available until you close it. Shut it down on both sides:
adb disconnectThese three actions are often confused, but they operate at completely different levels. Knowing the difference saves you from, say, deleting platform-tools when you only wanted ADB to stop for a few minutes:
adb kill-server stops the adb process on your computer and removes nothing; the next adb command brings it straight back.One way to avoid managing the adb lifecycle by hand is to run your Android sessions on a cloud platform. With a Real Device Cloud, devices are provisioned and released for you, so there is no local adb server to start, kill, or secure between test runs.
No. adb kill-server only stops the adb server process on your computer. The platform-tools files, the adb binary, and your PATH entry all stay in place. To actually remove ADB you delete the platform-tools folder or uninstall it through your package manager.
No. The command terminates only the host-side server on your computer. It does not stop the adbd daemon on the phone, does not reset the device, and does not touch any device settings. USB debugging stays enabled, and the phone will accept ADB again as soon as a server is running.
Run any adb command, such as adb devices, and the server starts again automatically. You can also start it explicitly with adb start-server. If you disabled USB debugging on the device, re-enable it from Settings > System > Developer options before reconnecting.
For most users, yes. Turning off USB debugging stops the phone from accepting ADB connections, which is the main reason to disable it when you are done. For added safety, also tap Revoke USB debugging authorizations to clear trusted computers, and turn off Wireless debugging if you ever used ADB over Wi-Fi.
Turning off ADB is reversible and removes nothing: killing the server stops the host process, and disabling USB debugging stops the device from accepting connections, but the tools stay installed. Uninstalling deletes the platform-tools folder permanently and is what you do when you no longer need ADB at all.
Run adb disconnect to drop active wireless connections, then open Settings > System > Developer options > Wireless debugging on the device and toggle it off. To remove a paired computer, tap its name under Paired devices and select Forget.
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