Use ADB in Your Browser with WebUSB (No Install)

18 August 2026 · adb · webusb · android · developer tools

Android Debug Bridge (ADB) normally means downloading Google’s platform-tools, unzipping them, fixing your PATH and opening a terminal. That is fine for developers, but it is a lot of ceremony when you only want a screenshot, an APK installed or a quick look at logs. Modern browsers can talk to a phone directly over USB using WebUSB, which removes most of that setup.

What WebUSB changes

WebUSB is a browser API that lets a web page communicate with a USB device after you grant explicit permission. A web app can implement the ADB protocol in JavaScript and speak to your phone just as the command-line tool would.

Limits to know up front:

• It works in Chrome, Edge and other Chromium-based desktop browsers.
• It does not work in Firefox, Safari or any iOS browser.
• You need a USB cable that carries data, not a charge-only cable.
• Only one ADB client can use the phone at a time, so stop any running adb server first.

Step 1: Enable Developer options and USB debugging

On the phone:

1. Open Settings, then About phone.
2. Tap Build number seven times until you see a message that developer mode is on. On some brands it sits under Software information.
3. Go back to Settings, open Developer options.
4. Turn on USB debugging.

Menu names vary by manufacturer, but the pattern is the same.

Step 2: Connect and authorize

1. Plug the phone into your computer with a data cable.
2. Open adbkit.com/app in Chrome or Edge.
3. Click connect. The browser shows a device chooser; select your phone.
4. On the phone, a prompt asks whether to allow USB debugging from this computer. Confirm it, and optionally tick the remember option.

If the device is missing from the list, check the cable, unlock the phone and make sure no desktop adb process is holding the connection. On Windows, install the manufacturer’s USB driver if Device Manager shows an unknown device.

Prefer Wi-Fi? Use the ADB Kit agent

WebUSB needs a cable. ADB Kit can also connect over Wi-Fi, TCP/IP or Wireless debugging (Android 11+, paired by code or QR) through a small open-source ADB Kit agent that runs on your own computer and never calls the internet. Install the agent once, then pair the phone from the workspace. You can connect up to six devices at once.

What you can do once connected

ADB Kit runs entirely in the page and covers the everyday tasks:

• Live screen mirror with mouse and keyboard control, so you can operate the phone from your desktop
• Screenshots with markup, saved straight to your computer
• Screen recording exported as WebM
• APK install by choosing a file from your computer
• Logcat streaming with filtering and export, so you can watch just the tag or level you care about
• File manager and ADB shell for moving files and running commands
• Reboot and boot modes

Because it is local-first, the data moves between your browser and the phone (directly over USB, or through the local agent for Wi-Fi) and is not sent to a server. The tool is free and needs no account. If you would rather work from a phone, ADB Kit is also available as a mobile app for Android and iPhone/iPad.

A quick workflow example

Say you are testing a build and need a bug report with evidence:

1. Connect the phone and open the mirror.
2. Start a screen recording and reproduce the problem.
3. Open logcat, filter by your app’s tag or by error level, and copy the relevant lines.
4. Take a screenshot of the final state.
5. Attach the recording, screenshot and log snippet to your ticket.

That sequence replaces several terminal commands and a separate recording app.

When the command line is still better

A browser tool is convenient, but the CLI remains the better choice for scripting, CI pipelines and anything that needs a command you cannot find in a UI. If you want to learn those commands, see our ADB cheat sheet for screenshots, recording and logcat.

Security notes

USB debugging gives a connected computer wide control over the phone, so treat it accordingly:

• Only authorize computers you trust.
• Turn USB debugging (and Wireless debugging, if you used it) off when you are finished, especially on a daily-driver phone.
• Revoke USB debugging authorizations in Developer options if you used a shared machine.

Troubleshooting checklist

• Device not listed: try another cable or port, unlock the screen, reconnect.
• Authorization prompt never appears: toggle USB debugging off and on, or revoke authorizations and reconnect.
• Connection fails immediately: close any other tool using ADB, including a running adb server or an emulator manager.
• Wrong USB mode: choose File transfer when the phone asks which mode to use.

To try it, open ADB Kit in Chrome or Edge, plug in your phone and authorize the prompt.

ADB Kit

A local-first workspace for Android in your browser and on your phone: mirror and control a device, capture screenshots and recordings, install APKs, stream logcat and move files over USB or Wi-Fi.

View app →