APK vs XAPK: What the Difference Is and How to Install Both

One file or a zip of files. When you need each, how to install them, and why an XAPK isn't safer.

APK and XAPK files on an Android phone screen

An APK is one file that installs one app. An XAPK is a zip that holds several APKs and a small manifest, and it exists because a single file stopped being enough once Android started splitting apps by processor, language and screen density.

That's the whole difference, and it explains almost every symptom people hit in the APK vs XAPK question: the "App not installed" error, the game that launches to a black screen, the download that looks bigger than the app store said it would be. This guide covers what each file contains, when you genuinely need the XAPK, how to install both, and why an XAPK isn't automatically the safer choice.

What an APK is

APK stands for Android Package. It's a zip archive with a fixed internal layout: compiled code in classes.dex, compiled resources in resources.arsc, native libraries under lib/ in per-architecture folders, and signatures in META-INF/. Android's package manager reads the manifest inside, checks the signature, and installs it.

One package, one version, one signature. That last part matters later, because Android refuses to update an app with a file signed by a different key, and refuses to install a second copy of the same package name.

What an XAPK adds

An XAPK isn't an Android format. Android has never heard of it. It's a container that a store or an installer defines, and the only thing that makes it work is the manifest inside.

Here's a real one, taken apart: Smart Launcher 6.6 build 025, 24.5 MB as downloaded.

File inside

Size

Role

ginlemon.flowerfree.apk

24.3 MB

Base APK, the app itself

config.arm64_v8a.apk

49 KB

Native code for 64-bit ARM

config.en.apk

57 KB

English resources

config.mdpi.apk

41 KB

Medium-density graphics

manifest.json

1.8 KB

Tells the installer what the above are

The manifest declares xapk_version: 2, the package name, the version name and code, min_sdk_version: 32, and a split_configs list that names each split. That's the entire trick: the archive carries the base plus its configuration splits, and the manifest tells an installer to hand all of them to Android in one session.

This is the same structure Google Play builds when it delivers an App Bundle. Play generates splits on its server and installs them silently. An XAPK is what that set looks like when it's packaged for download outside Play.

When you actually need the XAPK

Three cases, and only three.

The app ships as split packages only. Smart Launcher above is one: the base APK alone has no native code and no English strings, so installing just ginlemon.flowerfree.apk either fails or gives you an app with missing pieces. Some launchers, most modern games, and anything built as a Play App Bundle behaves this way.

The app needs an OBB file. Large games keep assets outside the APK, in a file ending .obb, which has to land in Android/obb/[package name]/ with an exact filename. Those XAPKs carry the OBB alongside the APKs, and the installer's job is to put it in the right folder with the right permissions. Copy it to the wrong folder and the game opens to a black screen or a download prompt.

You're installing on a device with a different architecture than the one the APK was built for. A single-ABI APK built for arm64-v8a won't run on a 32-bit-only device. An XAPK that includes multiple ABI splits gives the installer a chance to pick the right one.

If none of those apply, a plain APK installs faster, needs less free space, and is easier to verify. Bigger isn't better here.

How to install an XAPK

Two routes. The installer route is the one that works without a computer.

With an installer that understands XAPK. This is the easiest way to install XAPK files. Open the downloaded file from your downloads list, or from inside the store app that produced it. The installer unpacks the archive, reads the manifest, and passes the base plus the split APK set to Android in one install. You see the normal Android install prompt once, then the app appears in your drawer.

By hand, with adb. This is the route for people who want to see what's happening, or whose phone refuses the container:

  1. Rename the .xapk to .zip and extract it.
  2. Open a terminal on a computer with adb installed and the phone connected.
  3. Run adb install-multiple base.apk config.arm64_v8a.apk config.en.apk config.mdpi.apk, using the actual filenames in the archive.
  4. If the app needs an OBB, copy that file to Android/obb/[package name]/ on the phone's internal storage before launching.

The manual route fails in a specific way if you get it wrong: installing the base alone gives you an app that opens and then crashes or shows blank text, because the language split is missing. That's not a broken download. It's an incomplete install.

Why XAPK installs fail

Five causes cover almost every case.

Unknown sources is off. Since Android 8, this is a per-app permission, not a global switch. The prompt names the app doing the installing, and you grant it in Settings → Apps → Special app access → Install unknown apps. On Android 13 and later there's a second gate: apps installed outside a store have sensitive permissions locked, and some installers need Allow restricted settings in Settings → Apps → [installer] → More before they can finish.

There isn't enough space. An XAPK needs room for the archive plus the unpacked APKs plus the installed app. A 24.5 MB download can want well over 60 MB free before it finishes. Android reports this as a generic failure, not a storage warning.

The signatures don't match. If the app is already installed from another source, Android compares signing keys and refuses. The message is usually "App not installed". Uninstall the existing copy first, and accept that its data goes with it.

The architecture doesn't match. A 64-bit-only build on a 32-bit device, or an x86 build on an ARM phone, fails with INSTALL_FAILED_NO_MATCHING_ABIS over adb and a plain "App not installed" on the phone. Check the config. splits in the archive against your phone's CPU.

The Android version is too old. Every XAPK manifest declares a minimum SDK. Smart Launcher's says 32, which is Android 12L. On Android 11 the install fails before it starts, and no amount of retrying helps.

Is an XAPK safer than an APK?

No, and it's worth being blunt about why. An XAPK is a zip: no additional signing, no verification step, and no security property that an APK lacks. Whatever safety you get comes from the signature on the APKs inside and from where you downloaded the file, not from the extension.

In one way an XAPK is slightly harder to check, because the thing you downloaded isn't the thing that gets installed. You're trusting the installer to extract it and pass the right files through. A plain APK you can inspect with any zip tool and compare against a published hash.

So treat the extension as a packaging detail, not a trust signal. The source is the trust signal.

FAQs

Can I rename an XAPK to APK and install it?
No. Renaming changes the extension, not the contents. Android would try to read a zip full of APKs as a single package and fail.
Do XAPK files contain malware more often than APKs?
There's no evidence the container itself is riskier. Both formats install whatever is inside them, so the risk sits with the source and the signature, not the extension.
Why is the XAPK bigger than the size shown in the store?
Because it holds the base APK plus every configuration split and sometimes an OBB. The store number usually describes the compressed download for one device configuration.
Can I update an app installed from an XAPK with a normal APK later?
Only if the signing key matches and the version is the same or newer. Mixing sources usually produces a signature conflict, and the fix is to uninstall and reinstall.
Back to top

Sources

We use cookies and other technologies on this website to enhance your user experience.
By clicking any link on this page you are giving your consent to our Privacy Policy and Cookies Policy.
Learn More about Policies