How to Install an APKS File on Android

You downloaded a file ending in .apks and tapping it does nothing. That's expected — a .apks isn't a single app package, it's a set of them. This guide explains what an APKS file actually contains, how it differs from .apk, .xapk and .apkm, and how to install one on your phone in a single tap — no root, no PC and no bundletool.

What is a .apks file?

A .apks file is a ZIP archive produced by bundletool, Google's official command-line tool for turning an Android App Bundle (.aab) into installable packages. Rename one to .zip, open it, and you'll typically find:

• toc.pb — a small binary table of contents describing every package inside;
• splits/ — the base APK plus the split APKs: one per CPU architecture (arm64_v8a, armeabi_v7a, x86_64), one per screen density (hdpi, xxhdpi…) and one per language.

This is exactly how Google Play delivers modern apps: instead of shipping one giant APK to everyone, it sends your device only the parts it needs. When you get the app from outside Play, you get the whole set at once — as a .apks.

And that is why nothing happens when you tap it. Android's built-in package installer takes one .apk. Hand it an archive of several and there is simply no handler registered for that file type, so the system does nothing at all.

.apks vs .apk vs .xapk vs .apkm — which one do you have?

The practical difference between .apks and .xapk is small: an XAPK also carries OBB expansion data for large games, while a bundletool .apks normally does not. Everything else is the same problem with the same solution — you need an app that installs several packages in one session.

Install a .apks file in one tap

The straightforward route is a dedicated split-APK installer. We build a free one called SAI+ (Split APKs Installer): it reads .apks, .xapk, .apkm and loose split APK folders, works fully offline, needs no root or computer, and shows the real error message if Android refuses the install instead of failing silently.

Step-by-step: installing a .apks file

1. Get an installer. Install SAI+ (or another split-APK installer) from Google Play and open it.
2. Allow "install unknown apps". When prompted, grant the installer permission to install apps. Since Android 8 this is granted per app, so allowing it once for your browser is not enough.
3. Pick the .apks file. Browse to wherever you saved it — usually Download/.
4. Confirm the splits if you're asked to (see the next section — the defaults are usually right).
5. Tap Install and wait. The installer unpacks the archive and installs every part in one session, then offers to open the app.

That's the whole flow. There is no PC step, no ADB and no manual unzipping.

Choosing the right splits: architecture, density, language

A .apks often contains far more than your phone needs — every CPU architecture, every screen density and every language the developer shipped. A good installer preselects the correct ones, but if it asks you to choose, here is what to pick:

• Architecture — pick arm64_v8a. Practically every phone made in the last several years is 64-bit ARM. Older or budget devices may need armeabi_v7a; x86_64 is for emulators and a handful of Intel tablets. You must select exactly one — an app installed with no native code either refuses to install or crashes on launch.
• Screen density — pick the one matching your display (a modern 1080p phone is usually xxhdpi). Choosing a different density still works; the UI just uses slightly larger or smaller assets.
• Language — pick your own. Selecting several is fine and only costs a little space.

If your installer reports an error about needing an architecture split selected, that is this exact step — the full wording and the fix are covered in the error messages section of the main XAPK guide.

Where .apks files come from (and the bundletool route)

Developers create a .apks by running bundletool build-apks against an .aab. The same tool can install it over ADB:

bundletool install-apks --apks=app.apks

That works, but it needs a computer, the Android SDK platform-tools and USB debugging enabled — which is why on-device installers exist. If you only want to run the app on your own phone, the one-tap route above does the identical job.

One related case worth knowing: if someone hands you an .aab file directly, it cannot be installed at all. An App Bundle is a publishing format for Google Play; it has to be converted into APKs first. Ask for a .apks or an .apk instead.

If your .apks still won't install

The failures are the same handful you get with any split bundle:

• "Install unknown apps" is off for the installer — grant it per app, not globally.
• An older copy is already installed with a different signing key — uninstall it first.
• Partial download — an interrupted transfer produces an invalid ZIP; download it again.
• Xiaomi / MIUI — turn off MIUI optimization and the pre-install scan.

→ Full troubleshooting guide: 10 fixes when a bundle won't install

Frequently asked questions

← back to the XAPK guide