EN
Explore apps

Use ADB in Your Browser with WebUSB (No Install)

· 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:

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.

What you can do once connected

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

Because it is local-first, the data moves between your browser and the phone over USB and is not sent to a server. The tool is free.

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, wireless debugging workflows 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:

Troubleshooting checklist

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

FAQ

Which browsers support ADB over WebUSB?

Chrome, Edge and other Chromium-based desktop browsers. Firefox, Safari and mobile browsers on iOS do not support WebUSB, so the tool will not work there.

Do I need to install platform-tools or drivers?

Not for the browser tool itself. You still need Developer options and USB debugging enabled on the phone, and on Windows you may need a vendor USB driver if the device is not recognised.

Is my data sent to a server?

ADB Kit is local-first: the connection runs between your browser and the phone over USB, and your screen, files and logs are not uploaded to a server.

ADB Kit

A local-first browser workspace for Android: mirror and control a device, capture screenshots and recordings, install APKs, stream logcat and move files over WebUSB.

View app →

More guides