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.
Updated 2026-11-22 · 9 min read · apktools editorial
What “install XAPK” really means
People search for how to install XAPK on Android because the file extension looks official. Android still expects APK packages or split APKs. An XAPK is almost always a zip-style container. The real install flow is extract, install, place expansion data, then launch.
You can do this with a computer and browser tools, or with a careful on-device workflow. The safest mindset is the same in both cases: trust the source, understand the files inside, and avoid random “XAPK installer” APKs from unknown websites.
Before you start
Confirm you have enough free storage for the extracted APKs and OBB files. Large games can need several hundred megabytes or more beyond the archive size. Also note your Android version and whether the device allows installs from your chosen installer source.
- Keep the original XAPK until the app launches successfully
- Know whether the archive contains one APK or multiple splits
- Check whether OBB files are included
- Prefer official or trusted package sources only
- Back up important data if you will overwrite an existing app
Method 1: Extract on a computer, then install on the phone
This is the clearest method for most people who already use a PC or Mac. Open the XAPK in a local extractor such as the apktools XAPK to APK page. Download the base APK, any split APKs, and any OBB files. Transfer them to the phone with USB, cloud storage you trust, or another private channel.
If you only have one APK
Copy the APK to the device and open it with the system package installer or a trusted file manager. Allow installation from that source if Android asks. After install, copy OBB files into Android/obb/<package.name>/ if the archive included them.
If you have split APKs
Do not install only one config split and expect the app to work. Use a split-aware path. The most reliable developer path is USB debugging with adb install-multiple, listing every APK from the set. apktools can generate those commands after it parses the XAPK.
On-device split installers exist, but quality varies. If you use one, stick to well-known tools and still verify package identity. Random installers bundled with ads or unknown permissions are a common malware vector.
Place OBB files correctly
Missing OBB placement is one of the top reasons an XAPK “install” looks successful and then fails at runtime. After the APK is installed, create or open Android/obb/<package.name>/ on shared storage and copy the main or patch OBB files there with the exact names from the archive.
If you are unsure of the package name, inspect the extracted base APK with an APK info tool or read package_name from the XAPK manifest. A mismatched folder name means the app cannot find its expansion data.
Method 2: Install with ADB
ADB is ideal when you have multiple splits or need repeatable QA installs. Enable developer options and USB debugging, connect the device, extract the XAPK locally, then run adb install-multiple with every APK path. Push OBB files with adb push into the package OBB directory.
Example pattern after extraction into a folder named extracted:
- adb install-multiple "extracted/base.apk" "extracted/split_config.arm64_v8a.apk"
- adb push "extracted/main.123.com.example.app.obb" "/sdcard/Android/obb/com.example.app/main.123.com.example.app.obb"
Verify the install
Launch the app once and confirm it passes the first-run asset check. If it crashes immediately, revisit OBB paths and architecture splits. If Android rejects the install, read the failure carefully. Signature conflicts with an existing app, minSdk mismatches, and corrupted downloads are frequent causes.
When a publisher provides a hash, compare your XAPK or extracted APK with the hash checker before you spend time on install troubleshooting.
What not to do
Do not assume every XAPK installer app on the internet is safe. Do not ignore split APKs. Do not delete the OBB files because the APK “already installed.” Do not use apktools or any similar utility as a place to hunt pirated games. These guides exist to help you handle packages you already have permission to use.
Frequently asked questions
Why does Android say the XAPK file is invalid?
Because Android is not installing the wrapper archive. Extract the APKs first, then install those packages.
Do I always need a special XAPK installer app?
No. Many people extract on a computer and install with the system installer or ADB. Special installer apps are optional and should be chosen carefully.
The app installed but assets are missing. Why?
Usually the OBB files are missing, renamed, or sitting in the wrong Android/obb/<package>/ folder.
Can I install XAPK without a computer?
Yes, if you extract on the device with a trusted zip workflow and use a split-aware install method when needed. A computer-based extract is often easier to verify.
Related tools
Related guides
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.
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.
Fix “App not installed” error
When Android refuses an APK or split set, the cause is usually signatures, version codes, architecture, or a bad package file.