Next-Gen App & Browser Testing Cloud

Trusted by 2 Mn+ QAs & Devs to accelerate their release cycles

How to open APK files on Chromebook?

Most Chromebooks run Android apps natively through the Google Play Store, so if the app you want is on Play, install it from there and you never need an APK. To open or install a raw APK file directly, the recommended route is the Linux (Crostini) development environment with ADB: enable Linux, turn on ADB debugging, then run adb connect arc followed by adb install yourfile.apk. This keeps your Chromebook secure and never wipes it. Developer Mode can also install APKs but it powerwashes (factory-resets) the device, so it is a last resort.

First, Check the Google Play Store

Almost every current Chromebook ships with the Google Play Store and the Android subsystem (ARC) enabled. Before sideloading anything, open the Play Store and search for the app. Installing from Play means the app is signed, scanned by Play Protect, and updates automatically, none of which you get with a sideloaded APK.

You only need to deal with raw APK files when an app is not on the Play Store, for example a region-locked app, an internal or enterprise build, a beta release, or a developer build you compiled yourself. For those cases, the methods below apply.

What You Need Before Sideloading

Play Store support: Your Chromebook must support Android apps. Nearly all models since 2019 do; older or managed school devices may have it disabled by an administrator.
An up-to-date Chrome OS: Go to Settings then About Chrome OS and apply any pending update before you start.
Free disk space: The Linux container needs room. Allocate at least 10 GB when you set it up so both the Linux runtime and your APK have space.
A trusted APK: Download the .apk only from the developer's official site or a reputable mirror such as APKMirror. Sideloaded files are not scanned by Play Protect.

Method 1 - Install an APK with Linux (Crostini) + ADB

This is the official, supported way to deploy an APK to Chrome OS. It has worked since Chrome OS 81, keeps Verified Boot intact, and never factory-resets your machine. The Android Debug Bridge (ADB) talks to the on-device Android subsystem (ARC) from inside the Linux container.

Enable Linux: Open Settings, go to Advanced then Developers, and turn on the Linux development environment. When asked, allocate at least 10 GB of disk space. Chrome OS downloads and sets up the container.
Turn on ADB debugging: In Settings, open Linux, select Develop Android apps, and toggle Enable ADB debugging. Click Restart and continue. Your Chromebook reboots.
Install ADB in the terminal: Open the Terminal app and run the install command below.
Connect ADB to the Android subsystem: Run adb connect arc. An "Allow USB debugging?" prompt appears on screen; check "Always allow from this computer" and approve it.
Move the APK where Linux can see it: The terminal can only read files in the Linux container. In the Files app, drag your .apk into My files then Linux files. Rename it to something short to make it easier to type.
Install the APK: Run the install command with your file name, then launch the app from the App Launcher (the Search/Everything button).

Install ADB:

sudo apt update && sudo apt install adb -y

Connect and install the APK:

adb connect arc
adb install yourfile.apk

A successful run prints Success and the app appears in your launcher alongside Play Store apps. If you see more than one device/emulator, run adb devices to confirm the connection, then retry the install.

Method 2 - Developer Mode (Riskier, Powerwashes Your Device)

Developer Mode unlocks deeper access and lets you install some APKs directly, but it comes at a real cost. Switching it on factory-resets (powerwashes) your Chromebook, removes the standard boot-time security verification, shows an OS verification warning on every startup, and may void your warranty. Only use it if the Linux plus ADB route is not available to you.

Back up everything first. Enabling Developer Mode wipes local data, so move important files to Google Drive or an external drive.
Power off the Chromebook, then hold Esc + Refresh and press the Power button to enter recovery.
At the recovery screen, press Ctrl + D and confirm to turn on Developer Mode. The device powerwashes and reboots, which can take several minutes.
Once set up again, you can use the Files app or an ADB session to install your APK, accepting any security prompts that appear.

Because of the powerwash and weakened security posture, most users and testers should stay on Method 1. Developer Mode is rarely the right answer for simply opening an APK.

Security and Compatibility Caveats of Sideloading

No Play Protect scan: Sideloaded APKs skip Google's automatic malware scanning. Only install files you trust from their original source.
No automatic updates: A sideloaded app will not update through the Play Store. You have to re-download and re-install newer versions yourself.
Architecture mismatches: Chromebooks ship with either ARM or x86 processors. An APK built only for the architecture your device doesn't have may refuse to install.
Google Play Services gaps: Apps that depend on Play Services such as Maps, sign-in, or push messaging can crash if those services aren't fully available in the Android subsystem.
Form-factor quirks: Many Android apps assume a phone screen and touch input. On a large Chromebook display with a trackpad, layouts and gestures may behave oddly even when the app installs fine.

Testing Android Apps Beyond a Single Chromebook

Sideloading an APK onto one Chromebook only shows how the app behaves inside that machine's Android subsystem (ARC). For real testing, that is not enough. Behavior around camera APIs, biometric prompts, push notifications, hardware sensors, and OEM skins like Samsung One UI or Xiaomi MIUI can differ significantly from what ARC reproduces, and a single device tells you nothing about other screen sizes or OS versions.

This is where a cloud device lab helps. You can upload the same APK from any machine, including a Chromebook, and run it on remote, physical Android handsets straight from your browser. With TestMu AI'sReal Device Cloud, you install the build on current Samsung, Pixel, OPPO, Vivo, OnePlus, and Xiaomi devices, capture logs, record video, and reproduce bugs across thousands of real device and OS combinations, none of which a lone Chromebook can give you.

Frequently Asked Questions

Can I open an APK on a Chromebook without Developer Mode?

Yes. The Linux (Crostini) plus ADB method has worked since Chrome OS 81 and does not require Developer Mode. You enable the Linux development environment, turn on ADB debugging under "Develop Android apps", then run adb connect arc and adb install yourfile.apk. Verified Boot stays intact and your device is never wiped.

Why does the terminal say "no such file" when I run adb install?

The Linux terminal can only see files inside the Linux files container. If your APK is still in Downloads, the path is invalid. Open the Files app and move the APK into My files then Linux files, then run adb install from that directory.

Does enabling Developer Mode delete my data?

Yes. Switching a Chromebook into Developer Mode triggers a powerwash, which factory-resets the device and erases local data. It also shows an OS verification warning on every boot and may void warranty. Use the Linux plus ADB method instead, which avoids all of this.

Why won't my sideloaded APK install or open on Chrome OS?

Chrome OS runs Android apps inside a subsystem called ARC, and not every APK is built for it. An APK compiled only for a CPU architecture your Chromebook doesn't support, or one that depends on Google Play Services on a build without them, can fail to install or crash on launch. Confirm the app supports Chrome OS or test it on a real Android device instead.

Is sideloading APKs on a Chromebook safe?

Sideloaded APKs bypass Play Protect scanning and do not auto-update, so they are only as safe as their source. Install APKs only from the developer's official site or a trusted mirror such as APKMirror, and avoid random forum downloads, which are the biggest malware vector on Android.

What is the best way to test an Android app from a Chromebook?

Sideloading onto one Chromebook only tells you how the app behaves inside ARC on that single machine. To validate functionality across OEM skins, screen sizes, and OS versions, upload the same APK to a cloud real device cloud and run it on physical Android handsets from your browser.