APK, XAPK, APKS and OBB: what the difference actually is
Download an app outside the Play Store and you will meet four extensions. They are not competing formats and none of them is a worse version of another: each one exists because Android splits large apps into pieces, and each solves a different part of putting those pieces back together.
At a glance
| Extension | What is inside | Installs directly? |
|---|---|---|
| APK | One complete app | Yes, Android opens it natively |
| XAPK | An APK plus its split APKs or OBB data, zipped together | No, needs an installer app |
| APKS | A bundle of split APKs for one device configuration | No, needs an installer app |
| OBB | Extra game data, no code | No, it is copied into place |
Publicité
APK: the original single file
An APK is a complete Android app in one file: code, resources, icons and the developer's signature. Tap it, approve the install, done. Every app was distributed this way until app sizes made it wasteful, because a single APK has to carry resources for every screen density, every CPU architecture and every language, even though your phone uses one of each.
Small apps are still shipped as plain APKs, and that is why a browser or a messenger downloads as a single file while a big game does not.
Why apps got split up
Google's answer to that waste was the Android App Bundle. The developer uploads one bundle, and Google generates a tailored set of files per device: a base APK plus split APKs for your architecture, your screen density and your language. You download only what your phone needs, which is why the same game can be 40 % smaller from the Play Store than from a single-file APK.
XAPK and APKS: the two ways to package a split app
APKS is the format Google's own tooling produces: a zip of the base APK and the split APKs for one device configuration, and nothing else.
XAPK is the wider community format. It holds the same splits, and it can also carry OBB data and a manifest describing what belongs where. That makes it the format you usually see for large games, since it can package the whole install in one download.
Neither can be installed by tapping it, because Android has no built-in handler for a zip of APKs. That is the job of an installer app.
The step that makes XAPK and APKS files installable. It unpacks the archive, installs the base and its splits in a single session, and copies any OBB data to the right folder.
OBB: the data half of a big game
An OBB file is pure data, usually textures, audio and video for a game. It holds no code and cannot be installed, only copied to Android/obb/<package name>/. Put it in the wrong folder and the game will launch and then ask you to download several gigabytes again.
How to install each one
- Allow installs from your browser or file manager Settings, Apps, Special access, Install unknown apps, then grant it to the app you download with. This is a per-app permission, not a global switch.
- For an APK, just open it Your file manager or browser downloads screen will hand it to the system installer.
- For an XAPK or APKS, open it with an installer APKCombo Installer detects the type, unpacks it and installs every part in one go.
- For a separate OBB, let the installer place it Do not copy it by hand unless the installer failed and you know the package name.
- Check the signature if you are unsure of the source A file that came from the developer keeps their signature; a repackaged one does not, and Android will refuse to update it over the original.
Which one should you download?
Take whichever the download page offers first, and only go looking if that fails.
- You want to tap and install with nothing else on the device
- The app is small, like a browser or a messenger
- You need to keep the file for another phone
- It is a large game with extra data
- The APK-only version refuses to install or crashes on launch
- You want the exact splits your device needs, and nothing more
In short: APK is one file, XAPK and APKS are several files in a wrapper, OBB is the data half of a game. Pick the one the page offers, use an installer for anything that is not a plain APK, and check the signature when the source is new to you.
Frequently asked questions
Is an XAPK file safe?
As safe as the APK inside it. What matters is the signature: a file that keeps the developer's original signature is the same app the Play Store would give you. A repackaged one is not, and Android will refuse to install it over the original.
Can I convert an XAPK to an APK?
Not meaningfully. You can unzip it, but the base APK on its own is incomplete and will crash once it looks for a resource that lives in one of the splits.
Why does my install fail with "App not installed"?
Usually one of three things: a different signature from an existing copy, so uninstall the old app first; a missing split, so use an installer instead of the bare APK; or not enough free storage, since Android needs room for the archive and the unpacked app at the same time.
Do I need root to install these?
No. Every format here installs on a stock, unrooted phone. You only need to allow installs from unknown sources for the app you are installing from.
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.
