What is an XAPK file?
An XAPK is a zip-style Android package that often bundles a base APK, split APKs, and OBB expansion files into one archive.
Updated 2026-11-22 · 8 min read · apktools editorial
Quick answer
An XAPK file is a compressed Android package archive, usually a zip file with a .xapk extension. It is commonly used to deliver a base APK together with optional split APKs and OBB expansion data in one downloadable package. In practice, an XAPK is a convenient container, not a special Android install format that the system understands by itself.
Android does not install a raw .xapk the way it installs a single .apk. You typically extract the archive first, install the APK or APK splits, then place any OBB files in the correct folder. That is why browser tools that can open an XAPK locally are so useful for developers, QA testers, and careful sideloaders.
Why XAPK files exist
Early Android apps often shipped as one APK. As games and rich apps grew, publishers needed a way to ship large assets without stuffing every texture, level pack, or media file into the main APK. Google introduced expansion files (OBB) and later preferred App Bundles for Play delivery. Outside Play, many communities still share combined archives that include the installable package plus the extra data.
XAPK became a popular packaging convention for that combined delivery. Instead of sending a user five separate downloads, a distributor can wrap the base APK, config splits, and OBB files into one archive with a small manifest that describes package name and expansion paths. The idea is convenience. The risk is that some XAPK sources are untrustworthy, so you should only open files you trust.
What is usually inside an XAPK?
Most XAPK archives follow a predictable layout. You will often find a manifest.json file that stores package metadata, one or more APK files, and zero or more OBB files. The exact mix depends on the app.
- manifest.json: package name, app name, version fields, permissions list, split APK entries, and expansion file paths
- Base APK: the main installable package, sometimes named base.apk or similar
- Split APKs: optional config APKs for ABI, density, or language
- OBB files: large expansion data such as main.<version>.<package>.obb
- Icons or other assets: optional branding files that are not required to install
Why the manifest matters
The manifest is not AndroidManifest.xml inside the APK. It is an XAPK-level JSON helper. Good extractors read it to identify the package name, list split APKs, and map OBB install locations. If the manifest is missing or broken, you can still extract zip contents, but package detection and ADB helpers become less reliable.
XAPK vs a normal APK
A normal APK is the installable Android package format. An XAPK is a delivery wrapper around one or more packages and optional data. Thinking of XAPK as “just another APK” causes install failures. Your phone expects APK or split APKs. It does not magically unpack OBB files from a renamed zip.
If you only need metadata such as package name or permissions, extract the base APK first and open it in an APK info tool. If you need the full game content, keep the OBB files and place them correctly after install. Missing OBBs often look like a successful install that crashes or shows missing assets at launch.
How to open an XAPK safely
Because an XAPK is zip-based, you can inspect it with any trustworthy zip tool. For Android package work, a dedicated XAPK extractor is clearer: it validates the archive, lists APK and OBB entries with sizes, and lets you download each file or a zip of everything. On apktools, that workflow runs in your browser so the file does not need to be uploaded to a server.
Safe handling checklist:
- Only open XAPK files from sources you trust
- Scan the file if your security workflow requires it
- Extract locally instead of using unknown “installer” APKs from random sites
- Verify hashes when a publisher provides MD5, SHA-1, or SHA-256 values
- Keep the original archive until the app launches correctly
What to do after extraction
After extraction you usually have three jobs: install the APK or splits, place OBB files, and confirm the package identity. For a single base APK, a normal package installer may be enough if your device allows unknown sources for that installer app. For multiple splits, prefer adb install-multiple or a split-aware installer.
OBB files typically belong under Android/obb/<package.name>/ on shared storage. The exact folder must match the package name from the manifest or APK. If the package is com.example.game, a main expansion often lands at Android/obb/com.example.game/main.<version>.com.example.game.obb.
If installs fail with “App not installed,” check signature conflicts, Android version requirements, architecture mismatches, and leftover data from an older build. Those issues are covered in our install troubleshooting guide.
When to use apktools for XAPK work
Use the XAPK to APK extractor when you need a clear file list and local downloads. Use the ADB command generator when you will install over USB and want ready-made install-multiple and OBB push commands. Use the hash checker before and after transfers if you care about integrity. Use APK info on the extracted base APK when you need package name, version, SDK levels, or permissions.
apktools does not host or distribute apps. Bring your own XAPK. The goal is private package handling, not an app store mirror.
Frequently asked questions
Is an XAPK the same as an APK?
No. An APK is installable by Android. An XAPK is usually a zip archive that contains APK files and sometimes OBB data. You extract first, then install.
Can I rename .xapk to .zip?
Often yes, because many XAPK files are zip archives. A dedicated extractor is still safer because it understands manifest.json and separates APK and OBB outputs cleanly.
Do all XAPK files include OBB data?
No. Some only wrap a base APK and splits. Others include one or more OBB expansion files. Always inspect the archive contents.
Is it safe to download XAPK files from any site?
No. Treat unknown XAPK sources like unknown APK sources. Prefer official or trusted channels, and never use apktools as a place to find pirated apps.
Related tools
Related guides
How to install XAPK on Android
Android does not install .xapk directly. Extract the archive, install the APK or splits, then place OBB files in the correct folder.
What is an OBB file and where does it go?
OBB files store large Android expansion data. They usually belong in Android/obb/<package.name>/ beside a correctly installed APK.
XAPK vs APK vs AAB vs APKS
APK installs, AAB ships through Play, APKS holds splits, and XAPK wraps packages plus optional OBB data. Here is how they differ.