How To Enable Unknown Sources On Chromebook | APK Sideloading

On a Chromebook, enabling “unknown sources” requires using Android’s install-unknown-apps settings or Developer Mode — there is no single ChromeOS toggle that does this by itself.

If you typed “enable unknown sources on Chromebook” expecting a simple checkbox, you’re not wrong — but the answer lives in two different places depending on what you’re actually trying to install. One path works for Android APKs on Chromebooks that support Google Play, and a completely separate path unlocks system-wide app installation through Developer Mode. Here is exactly what each method involves, when to use it, and the trade-off you need to know before flipping any switch.

What “Unknown Sources” Actually Means On A Chromebook

ChromeOS never had a standard “Unknown sources” toggle the way Android does. When people search for this setting, they usually mean one of two things: installing an Android APK from outside the Google Play Store (which uses the Android subsystem’s permission system) or installing any non-Play-Store app on ChromeOS itself (which requires Developer Mode). Google’s own support threads confirm that ChromeOS has never allowed sideloading outside of Developer Mode in normal operation.

The confusion is understandable — earlier Android tablets and phones made “Unknown sources” a single master switch in Security settings. On a Chromebook running Android apps, that switch isn’t in the main ChromeOS settings at all. You reach it through the Android settings panel, and only after you’ve enabled Google Play support. For anything beyond Android APKs, Developer Mode is the only door in.

Method 1 — Turn On “Install Unknown Apps” Inside The Android Subsystem

If your Chromebook supports Android apps (most modern models do), you can grant permission to a specific app — like Chrome or the Files app — to install APKs without entering Developer Mode. This is the safest route and the one most people actually need.

Here is the step-by-step:

1. Open Settings on your Chromebook and turn on Google Play Store if it isn’t already enabled.
2. Go to Apps > Google Play Store > Manage Android preferences. This opens the full Android settings panel inside ChromeOS.
3. In Android settings, tap Apps & notifications > Apps special access > Install unknown apps.
4. Select the app you want to use for installing APKs — usually Chrome or Files — and toggle Allow from this source to on.

On older versions of Android inside ChromeOS (Android 7.x and below), the path was Lock screen and security > Unknown sources as a single toggle, but any Chromebook still running that version is rare. The “Allow from this source” per-app permission is the current standard.

After toggling the permission on, you can download an APK in Chrome and tap the notification to install it — the system will no longer block it. If nothing happens when you tap the downloaded APK, move it into the Downloads folder and open it from the Files app instead.

This method only works for Android APKs. If the app you need is a Linux program, a Chrome extension outside the Web Store, or a full system tool, you need Developer Mode.

Method 2 — Enable ChromeOS Developer Mode For Full Sideloading

Developer Mode is the ChromeOS-level setting that lets you install apps from anywhere, run Linux containers with full privileges, and modify the system. It also disables OS verification, which means your Chromebook will warn you every time it boots with a beep and a screen that says “OS verification is OFF.”

The procedure is the same across most Chromebooks:

1. Hold Esc + Refresh and press the Power button to enter Recovery Mode.
2. At the “ChromeOS is missing or damaged” screen, press Ctrl + D.
3. The screen changes to “OS verification is OFF” and prompts you to press Enter to enable Developer Mode.
4. Press Enter — the device wipes local data and reboots.
5. After reboot, press Ctrl + D again at the warning screen to boot into Developer Mode.

On Chromebook tablets (convertibles and detachables), the key combination is different: press Volume Up + Volume Down simultaneously at the recovery screen, then press Power to confirm, according to community documentation maintained by MrChromebox. After the data wipe, you press Ctrl + D at each boot to continue past the warning.

Developer Mode stays active until you disable it — which requires another wipe. You cannot toggle it on and off without erasing your local files each time.

How To Sideload APKs Once Developer Mode Is Active

With Developer Mode on, you have two ways to install APKs. The simplest is to enable ADB debugging through the Android subsystem and push APKs from Linux.

1. Go to Settings > Apps > Google Play Store > Manage Android preferences.
2. In Android settings, scroll to About phone and tap Build number seven times to enable Developer Options.
3. Go back to System > Developer options and turn on USB Debugging and ADB debugging.
4. Enable Linux from ChromeOS settings if you haven’t already.
5. Open the Linux terminal and install ADB: sudo apt update && sudo apt install adb.
6. Connect ADB to the Android container: adb connect arc.
7. On the Chromebook screen, approve the RSA key fingerprint prompt.
8. Move your APK into the Linux files folder. Linux can only access that folder, so the APK must live there.
9. Run: adb install your-app.apk.

For Intel and AMD Chromebooks, some users need to specify the emulator serial: adb -s emulator-5554 install your-app.apk. The terminal will report “Success” when the installation finishes.

What You Lose When You Enable Developer Mode

Google describes Developer Mode as a “do not enter” sign for a reason. Once it is on, your Chromebook no longer verifies its operating system at boot — meaning a malicious bootloader or kernel modification could go undetected. The device also displays a stark warning screen every time it powers on, and the Space key no longer boots the OS; you must press Ctrl+D instead.

The iFixit guide on enabling Developer Mode notes that the process is intended for developers who understand the security implications, not for everyday users who just want one app from outside the Play Store. If all you need is a single Android APK, use Method 1 (the Android subsystem’s install-unknown-apps permission) and leave OS verification on.

One more gate: some Chromebooks — particularly older models or low-end education devices — do not support Android apps at all. If you don’t see Google Play Store in your Apps list, you cannot use Method 1, and Developer Mode is the only option. The Google support thread on this topic confirms that even on those devices, Developer Mode is the only path to sideloading.

Android Unknown Sources Settings By Version

Most Chromebooks running Android apps use a version of Android 9 or newer inside the container, so the per-app permission screen is the one you will see. If your Chromebook is still on an older Android build, the single-toggle path appears instead.

Which Path Should You Take?

Start with Method 1. Open the Android settings panel, find the Install unknown apps permission, and grant it to Chrome or Files. That covers 90% of the reasons someone searches for this setting — installing a single APK that isn’t in the Play Store. No data wipe, no boot warning, no security exposure.

If the APK still won’t install after granting permission, the file may be incompatible with your Chromebook’s processor architecture (ARM vs x86), or the app may require features your Android container doesn’t support. In that case, you need Developer Mode and ADB sideloading — but understand that you are trading everyday security for that capability. Turn it on, sideload what you need, and plan to powerwash back to normal mode when you’re done.

Google’s Chromebook support thread on app installation confirms that no general “unknown sources” setting exists in standard ChromeOS — the paths above cover every legitimate way around that limitation.