Downloaded an app as a single .apks or .apkm file and tapping it does nothing? That’s because you’re dealing with split APKs — and learning how to install split APKs requires a different approach than normal APKs. Android’s built-in installer can only handle one APK at a time, but a split bundle is several APKs that must be installed together as a set. This guide explains what splits are, why the default installer fails, and two reliable ways to install them.
What Are Split APKs?
Instead of one giant APK containing every language, screen density, and processor variant, modern Android apps ship as splits:
- base.apk — the core app: code and default resources.
- config splits — e.g., config.arm64_v8a (processor-specific native code), config.en (English language resources), config.xxhdpi (high-resolution images).
Your phone only needs the splits matching its hardware — which is why Play Store downloads are smaller than they used to be. When these splits are bundled into one distributable file, you get the .apks (or .apkm) extension. It’s a ZIP container holding the whole set, conceptually similar to how XAPK bundles an APK with OBB data — but for splits, every piece is an APK.
Why Split APKs Exist
Google introduced app bundles so developers publish one artifact and Google Play generates optimized APK sets per device. Benefits: smaller downloads, faster installs, less wasted storage. The side effect: when you obtain such an app outside the Play Store, you get the set rather than a single file — and installing it needs tooling that understands sets. For the publishing-side story, see APK vs AAB.
Why the Default Installer Fails
Tap a lone base.apk and Android installs it — but the app will likely crash, because its language or native-code splits are missing. Tap the .apks bundle and Android says “can’t open file” because the extension isn’t a package at all, just a container. Either way, you need a tool that installs all splits in one atomic session — Android’s package manager supports this via a multi-APK install session, but the stock file-tap flow can’t trigger it.
How to Install Split APKs With an Installer App (Easiest)
Installer apps built for this purpose handle the whole session automatically:
- Install a reputable split-APK installer from the Google Play Store (search “split APK installer” / “APKS installer” — choose one with strong ratings and recent updates).
- Open it, grant file access, and select your .apks or .apkm file.
- The app shows the bundle’s contents (base + config splits) for confirmation.
- Tap Install. Grant the install unknown apps permission if prompted.
- Android installs all splits as one app. Launch it from your app drawer.
Tip: if you have loose split APKs (not bundled), most installer apps let you multi-select them and install as a set. This also works for bundles you created by extracting APKs from an installed app.
How to Install Split APKs With ADB install-multiple
For full control — or when installer apps fail — ADB’s multi-install command does exactly what the Play Store does:
- Enable USB debugging (Settings > About phone > tap Build number 7 times, then Developer options > USB debugging).
- Install Android SDK Platform-Tools on your PC from Google’s official developer site.
- Extract the .apks file (rename to .zip and unzip) so you have the individual APKs: base.apk, config.*.apk.
- Connect the phone, accept the debugging prompt, then run:
adb install-multiple base.apk config.en.apk config.arm64_v8a.apk config.xxhdpi.apk
(list every split file, in any order — base first is conventional). - Wait for the Success message. The app appears in your drawer, fully assembled.
Turn off USB debugging when finished. This method is also the most trustworthy when a bundle behaves oddly, since you see exactly which pieces go in.
Troubleshooting
- “App not installed” during split install — same root causes as single APKs: storage, signature conflicts, corrupt files. Work through fix app not installed error.
- App installs but crashes on launch — a required split is missing (often the architecture config). Reinstall with the complete set.
- Installer app can’t see the .apks file — move it to internal storage’s Download folder; some apps can’t browse SD cards or restricted folders.
- Confusingly similar: XAPK installation looks similar but involves OBB data, not APK splits — make sure you’re following the right guide for your file type.
Frequently Asked Questions
What’s the difference between APKS and APKM?
Both are containers for split APK sets. APKS is the more common convention; APKM is used by some installer apps and tools. Functionally they’re the same idea — a bundle of base + config APKs.
Can I convert split APKs into a single APK?
Not properly. Merging splits into one APK breaks the signing and resource-table structure. Install them as a set instead — that’s what the format is designed for.
Do split APKs update through the Play Store?
Only if the identical app (same package name and signature) is registered to your Google account via the Play Store. Otherwise, update by installing a newer split set the same way.
Is installing split APKs safe?
The mechanism is the same official Android install session the Play Store uses. Safety depends on the source of the bundle — apply the standard checks from are APK files safe.
Conclusion
Split APKs look intimidating, but the concept is simple: one app, several pieces, installed together. Use a split-APK installer app for convenience or ADB install-multiple for precision, and always install the complete set — base plus every config split. With that, even APKS and APKM bundles become as routine as the single-file installs in our APK installation guide.