How to Install Split APKs on Android (Complete 2026 Guide)

If you’ve ever downloaded an app from a third-party source and ended up with a folder of oddly named files — base.apk, split_config.arm64_v8a.apk, split_config.en.apk— you know the pain. Tapping any single one fails with “App not installed” or “There was a problem parsing the package.”

That’s a Split APK. It’s a packaging method Android introduced in 5.0 and that Google Play has enforced since 2021. This guide explains splits clearly and gives you the step-by-step install methods that actually work.

Key idea: Split APKs can’t be installed one by one. You must submit allsplits to the system at once — via SAI or adb install-multiple.

1. What is a Split APK, and why split at all?

A traditional APK is one big file bundling native libraries for every CPU architecture, strings for every language, and images for every screen density. The problem: your phone downloads tons of resources it will never use.

Google’s fix is unbundling (App Bundles):

base.apk — core code and resources every device needs. Required.
split_config.<arch>.apk — cut by CPU architecture (arm64_v8a, x86_64…). You only need yours.
split_config.<lang>.apk — cut by language (en, zh…).
split_config.<density>.apk — cut by screen density (xxhdpi…).

The upside: much smaller downloads. The cost:the system must assemble all splits together at install time — miss one and it won’t assemble.

Critical rule: base + all splits must belong to the same app, same version, same signature. Mixing versions fails outright.

2. Before installing: make sure your split set is complete

You should be looking at a group of files, not one:

com.example.app/
├── base.apk                    ← core, required
├── split_config.arm64_v8a.apk  ← your CPU architecture
├── split_config.xxhdpi.apk     ← screen density
└── split_config.en.apk         ← language (optional)

Find your phone’s CPU architecture (decides which arch split you need): check Settings → About phone → processor info, or use CPU-Z / AIDA64. Since ~2020, nearly all phones are arm64-v8a.

Minimum needed: base + the matching architecture split. Density and language splits can usually be skipped (base carries defaults), but the architecture split is mandatory— skip it and you get crashes.

3. Method 1: SAI (Split APKs Installer) — recommended, no PC

SAI exists purely for split apps. GUI, right on your phone.

Steps:

Install SAI from a trusted source (open-source, available on GitHub).
Put the downloaded split folder in your phone storage.
Open SAI → tap “Install APK” → select the whole folder (or all splits together).
SAI auto-detects base and splits — tap “Install.”
If you hit a signature conflict, uninstall the old version first, then install.

Note:SAI needs “Install unknown apps” permission. Some skins (MIUI, etc.) also require enabling SAI in Developer Options.

4. Method 2: ADB install-multiple — cleanest for desktop users

One command installs the whole set, no phone-side app.

# Put all splits in one folder, cd into it
cd /path/to/com.example.app/

# Submit base + all splits at once
adb install-multiple base.apk split_config.arm64_v8a.apk split_config.xxhdpi.apk split_config.en.apk

Or with a wildcard if there are many:

adb install-multiple base.apk split_config.*.apk

Error reference:

ADB error	Meaning	Fix
INSTALL_FAILED_INVALID_APK	Incomplete or mismatched splits	Ensure base + splits are same version
INSTALL_FAILED_UPDATE_INCOMPATIBLE	Signature conflict	`adb uninstall <pkg>` then reinstall
INSTALL_FAILED_NO_MATCHING_ABIS	Arch split doesn’t fit phone	Use arm64-v8a or the correct arch
INSTALL_PARSE_FAILED_UNEXPECTED_EXCEPTION	Corrupt file	Redownload

5. Method 3: Merge into a single APK, then install normally

If you’d rather have “one file to rule them all,” merge the splits into a standard APK:

MT Manager:long-press base.apk → open with the APK editor → use “merge split packages / load external package” → save.
APKEditor (open source): CLI-oriented, good for batches.

java -jar APKEditor.jar m -i ./com.example.app/ -o merged.apk

The result is a single tappable APK. But merging changes the signature— apps with signature checks (some games, banking apps) may refuse to open. It installs, but doesn’t always run — a normal tradeoff.

6. If it won’t install, check in this order

Are all splits present? Did you grab only base and skip the arch split?
Right architecture? arm64 phone + x86 split = guaranteed failure. Use arm64_v8a.
Same version?Don’t mix splits from different downloads.
Signature conflict? Fully uninstall the old copy (including clones/work profiles), reboot, reinstall.
Corrupt download? Verify file sizes, redownload.

7. Bottom line

Split APK installation in one sentence: submit all splits (base + arch + density + language) to the system at once — never one by one.

On phone: use SAI, select the whole folder, done in one shot.
On desktop: adb install-multiple, one line, cleanest.
Want a single file: merge with MT Manager / APKEditor— signatures change.

Remember the two most common traps — a missing architecture split guarantees crashes, and mixed versions always fail.Nail those and Split APKs go from “a confusing pile of files” to “installed in three steps.” Need one app fast? Grab the matching APK by package name from gptoapk.com.