How to Install an APK on Android from Your Browser

13 October 2026 · guide · install apk · sideload apk · android · adb

Sideloading an APK usually means one of two routes: copy the file to the phone and tap through the installer, or open a terminal and run adb install. The first is slow and needs extra permissions on the phone. The second needs Google’s platform-tools on your computer.

ADB Kit gives you a third route. You open a web page in Chrome or Edge, connect the phone, pick the APK from your computer and install it. Under the hood it is the same ADB install a developer would run, without the setup.

Who this is for

• Developers pushing a debug or release build to a test device
• QA testers installing a build attached to a ticket
• Power users sideloading an app they downloaded from a source they trust

If you only need the command-line version, our ADB cheat sheet lists the adb install flags.

Before you start

You need:

1. A desktop or laptop running Chrome, Edge or another Chromium-based browser. Firefox and Safari cannot connect over USB because they do not support WebUSB.
2. A USB data cable, or the phone and computer on the same Wi-Fi network.
3. Developer options and USB debugging turned on (or Wireless debugging for a Wi-Fi connection).
4. The .apk file saved on your computer.

To turn on USB debugging: open Settings > About phone, tap Build number seven times, then go to Developer options and enable USB debugging.

Step 1: Connect the phone

Over USB

1. Plug the phone into your computer with a data cable.
2. Open adbkit.com/app.
3. Click connect and choose your phone in the browser’s device chooser.
4. Accept the “Allow USB debugging?” prompt on the phone.

Our WebUSB setup guide covers this step in more detail, including Windows driver issues.

Over Wi-Fi

If the cable is inconvenient, connect over the network instead. ADB Kit uses a small agent on your own computer for Wi-Fi, TCP/IP and Wireless debugging (Android 11+, paired by code or QR). See how to use ADB over Wi-Fi with ADB Kit for the pairing steps.

Step 2: Install the APK

1. In the ADB Kit workspace, open the APK install tool.
2. Pick the .apk file from your computer.
3. If you are updating an app that is already on the phone, turn on the replace existing app option.
4. If the app is already installed, confirm the overwrite when ADB Kit asks.
5. Wait for the result. ADB Kit shows a clear success or failure message.

That is the whole flow. The app now appears in the phone’s launcher.

Step 3: Check the app

A quick sanity check saves time later:

1. Open the live screen in ADB Kit and launch the app with the mouse.
2. Open live logcat and filter by the app’s tag or by error level to watch for crashes on start-up.
3. Take a screenshot or start a screen recording if you need evidence for a ticket.

Because everything is in one workspace, you can install, launch and watch logs without switching tools.

Installing on several devices

ADB Kit can hold up to six devices at once. To test the same build on a phone and a tablet, connect both and repeat the install for each device. This is much quicker than copying the APK to each one and tapping through the installer.

Common install errors and fixes

The app is already installed with a different signature. Android refuses to update an app with an APK signed by a different key. This often happens when moving between a debug and a release build. Uninstall the existing app on the phone first, then install again.

Downgrade not allowed. You are installing a lower version than the one already on the device. Uninstall the newer version first.

Not enough storage. Free up space on the phone and retry.

Incompatible with this device. The APK may target a newer Android version than the phone runs, or only include code for a different processor type. Get a build that matches the device.

Split APK bundles. Files such as .apks, .xapk or .aab are not single APKs. Use a regular .apk file built for installation.

Nothing happens after picking the file. Check that the device is still connected and unlocked, and that no other tool, such as a running adb server, is holding the USB connection.

Why install over ADB instead of on the phone

Installing through the phone’s own installer works, but ADB has a few advantages:

• You do not need to grant Install unknown apps to a browser or file manager.
• You do not need to copy the APK to the phone first.
• You can replace an existing build in one step.
• You can watch logcat straight away to catch a crash on first launch.

Stay safe when sideloading

An APK has the same power as any app from a store, so treat files from unknown sources with care:

1. Install only APKs you built yourself or downloaded from a source you trust.
2. Turn off USB debugging and Wireless debugging when you finish, especially on a personal phone.
3. Revoke debugging authorizations in Developer options if you used a shared computer.

ADB Kit itself is local-first. The APK travels from your computer to the phone directly over USB, or through the agent on your own computer for Wi-Fi, and is not uploaded to a server. It is free and does not need an account.

Installing from a phone instead of a computer

ADB Kit is also available as a mobile app on Google Play and the App Store. It supports APK install, live screen, logcat and file transfer over Wireless ADB, which is useful when you are away from your desk.

Summary

1. Enable USB debugging (or Wireless debugging) on the phone.
2. Connect it to adbkit.com/app in Chrome or Edge.
3. Pick the APK, turn on replace mode if updating, and confirm.
4. Check the result, then launch the app and watch logcat.

Try it with ADB Kit the next time you have a build to test.

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 →