Android debugging in the browser
ADBKit connects to Android phones and tablets over USB, Wi-Fi or your local network. You get a live screen you can tap and type on, plus everyday ADB tools: screenshots, screen recording, APK installs, logcat, a shell and file transfer. No platform-tools to install and no desktop app.
The workspace needs Chrome, Edge or another Chromium-based browser on a desktop or laptop computer.
Why ADBKit
Checking a build on a real device often means installing the Android SDK platform-tools, adding them to your PATH, and juggling separate tools for mirroring, logs and screenshots. ADBKit removes the setup and keeps the work in one tab.
Installing platform-tools and getting a device recognised takes time. On a locked-down work laptop you may not be allowed to install anything at all.
Mirroring, logcat, screenshots, APK installs and file transfer usually live in different apps and terminal commands. Switching between them breaks your flow.
Screens, logs and files from test devices can be sensitive. Many online tools route them through someone else's servers. ADBKit does not.
Features
Connect once, then view, control, type, capture, install, inspect and transfer, all from the same workspace.
See the device's display in real time and use it with your mouse and keyboard: click to tap, drag to swipe and type to enter text.
Capture the device screen in one click, then crop it, draw arrows and boxes or add text before you save the PNG.
Record the live device screen, trim the start and end, and save the video to your computer.
Pick an .apk file from your computer and install it on the connected device, with a clear success or failure result.
Stream device logs next to the screen to see what an app is doing while you use it.
Browse the whole device storage, download files to your computer and upload files into any folder you can write to.
Open a full shell on the device in a panel under the screen. Run commands while you watch the result live.
Reboot or power off the device, or restart it into recovery, bootloader, fastbootd or Samsung download mode, with a confirmation first.
Plug in a USB cable, or connect over your network with TCP/IP or Wireless debugging, paired with a code or a QR code. A step-by-step guide shows where you are and what to do next.
The connection runs between your browser and your device, directly over USB or through a small agent on your own computer for Wi-Fi and network. Screens, logs, files, APKs and serial numbers are never uploaded to ADBKit.
Screenshots
The device screen sits in the middle, tools open on the left, and logcat runs on the right.
Demo
A short walkthrough: controlling the screen, typing with the keyboard, taking a screenshot, reading logcat, browsing files and installing an APK.
How it works
Pick the way that suits you: a USB cable, or your network through the small ADBKit agent. The connect screen walks you through each step.
On the device, open Settings › About phone and tap Build number seven times to enable Developer options. Then turn on USB debugging, or Wireless debugging on Android 11 and newer.
Plug the phone into your computer with a USB data cable. For a network connection, run the one-line agent install shown on the connect screen.
Open ADBKit in Chrome or Edge and click Connect device. Choose your device in the browser's USB picker, or let the agent find it on your network.
Tap Allow on the “Allow USB debugging?” prompt, or pair with a code or a QR code for Wireless debugging. The live screen appears and every tool is ready.
Privacy
ADBKit is a web page, but the device connection is local. Over USB, your browser talks to the device directly with WebUSB. Over your network, including TCP/IP and Wi-Fi Wireless debugging, it goes through the small ADBKit agent running on your own computer. Either way there is no ADBKit server in the middle.
USB cable
Network or Wi-Fi
Screen frames, screenshots, recordings, logs, files, APKs and device identifiers stay between your browser, your computer and your device. Nothing goes to ADBKit.
You choose the device in the browser's permission prompt, and you approve debugging on the device itself. For network connections you also allow your browser to reach the agent on this computer. Each can be revoked at any time.
For Wi-Fi and network connections, the agent listens only on your computer, talks only to your phone on your own network and never calls the internet. Its source code is open to read on this site.
Built on the open-source Tango (ya-webadb) libraries for ADB in the browser and scrcpy for screen mirroring.
Requirements
Pricing
Everything on this page is free to use, with no account. A paid plan for automation is planned for later.
$0
Manual control of your connected devices.
Coming later
For repeating the same device tasks.
Not available yet. Manual control stays free.
Roadmap
Define a sequence of device operations once and run it again whenever you need it.
The ADB Kit mobile app is on Google Play today. The App Store version is coming soon.
FAQ
No. Over USB, ADBKit talks to the device directly from the browser with WebUSB, so you don't need platform-tools, a desktop app or a browser extension. For Wi-Fi and network connections you run one small ADBKit agent on your computer, with a one-line install.
Yes. Everything available today is free and needs no account. That includes screen control, typing, screenshots, recording, APK installs, logcat, a shell, file transfer and connecting several devices. A paid Pro plan for automation is planned for later.
No. Screen frames, logs, files, APKs and device identifiers travel only between your browser, your computer and your device, over USB or through the agent on your own network. ADBKit has no server that receives them.
For USB, Chromium-based desktop browsers with WebUSB, such as Google Chrome and Microsoft Edge. Firefox and Safari do not support WebUSB. The page must be opened over HTTPS.
Over USB, most often another program is already using the connection, for example Android Studio, scrcpy or an adb server. Close it (or run “adb kill-server”), make sure USB debugging is on, and approve the prompt on the device. Over Wi-Fi, check that the agent is running and that the phone and computer are on the same network. The connect screen shows which step is stuck.
To show and control the screen, ADBKit copies the open-source scrcpy server helper to a temporary location on the device. No app is installed unless you install an APK yourself.
Yes, in two ways. Classic TCP/IP works on any Android and needs a USB cable once to switch it on. Wireless debugging (Android 11 or newer) pairs with a code or a QR code and needs no cable. A browser cannot open network connections on its own, so a small agent runs on your computer, and the connect screen shows how to start it. Its source code is public on this site.
Yes, up to six, in any mix of USB and network connections. Each device gets its own tab, and only the selected tab streams video so the others stay light.
Yes. Click the screen and type, including accented and non-Latin text. Esc is Back, and Ctrl+A, C, V and X work in text fields.
No. The adbkit npm package is a Node.js library. ADBKit at adbkit.com is an independent browser workspace and is not affiliated with it.
Free, no install, no account. Your device data stays on your computer.
Open workspace