How to install an APK on modern Android, step by step
Most sideloading instructions online still describe Android 7, where one global switch allowed installs from unknown sources. That switch is gone. Since Android 8 the permission is per-app, and since Android 11 the OBB folder is protected, which is why hand-copying game data now fails silently.
Grant the permission to the right app
The permission belongs to the app that hands the file to the installer, not to the file. Download in Chrome and open from Chrome, and Chrome needs it. Open the same file from Files, and Files needs it.
- Open Settings and search for "unknown apps" The exact path differs by manufacturer; searching avoids hunting through menus.
- Pick the app you download with Usually your browser, your file manager, or the installer app.
- Turn on Allow from this source This is remembered per app, so you only do it once each.
- Open the file and confirm the install Play Protect may scan it first; that scan is normal and can take a few seconds.
广告
Then follow the file type
| File | What to do | Why |
|---|---|---|
| APK | Tap it | Android installs it natively |
| XAPK | Open with an installer app | It is an archive, not an installable package |
| APKS | Open with an installer app | Several split APKs that must install together |
| OBB alone | Let the installer place it | Since Android 11 apps cannot write to other apps' OBB folders |
Unpacks XAPK and APKS files, installs the base and every split in a single session, and writes OBB data where Android 11 and newer still allow it.
When it refuses
- Uninstall any existing copy first, signatures must match to update
- Confirm the app supports your Android version
- Free two to three times the file size
- Re-download if the file was interrupted
- Rooting the phone, which is never required
- Disabling Play Protect, which only skips the scan
- Changing the file extension, which does nothing
Grant the permission to the app you download with, use an installer for anything that is not a plain APK, and uninstall the old copy when an update refuses.
Frequently asked questions
Is sideloading safe?
It is as safe as the file. An APK carrying the developer's original signature is the same app the Play Store would install. The risk is repackaged files from unknown sources, which Android cannot install over the original anyway.
Do I need to turn the permission off afterwards?
Not really, but it is a reasonable habit for a browser. The permission only lets that app start an install, and every install still needs your confirmation.
Will sideloaded apps update themselves?
Only if the app has its own updater. Otherwise you update it the same way you installed it, and the new file must carry the same signature.
Read next
This is not a rivalry. Each does something the other cannot.
You are not buying encryption. You are buying an operator whose income does not depend on you.
For a plain ZIP either works. For a split, password-protected archive, only one does.
