How to Open an XAPK File on Android

Android has no built-in way to open a file that ends in .xapk. That is not a bug in your phone, and it is not a broken download. An XAPK is not an Android format at all: it is a packaging convention, and the operating system was never taught to read it.

The format exists because of a real constraint. Google Play historically capped a compressed APK at 100MB, which pushed developers with large games or media-heavy apps toward separate expansion files for graphics, audio, and video long before Android App Bundles existed. APKPure built the XAPK container to bundle that extra data with the app in one download for people installing outside Play. One of the more popular tools for the resulting split-APK installs, SAI, has not shipped a real update since build 60 in March 2021, which matters when you are choosing which installer to trust with the job.

That leaves readers hitting the same three walls. Tapping the file in a stock file manager does nothing, because the installer only recognizes .apk. The app they already have on their phone usually is not the one built to read an XAPK. And when a bundle also carries OBB expansion data, dropping those files in the wrong folder leaves the app installed but broken, with missing textures, audio, or levels that never load.

What an XAPK File Actually Is

An XAPK is a ZIP-based archive used to distribute and install Android apps outside of Google Play, built to hold an APK file together with the additional files an app needs, most commonly OBB expansion data. APKPure’s own explanation describes it as a container for apps that would otherwise need separate APK and OBB downloads to stay under Google Play’s 100MB upload limit. Inside, alongside the APK and any data files, sits a manifest.json file that records the package name, version, and where each file belongs, which is what an XAPK-aware installer reads to put everything in place.

Because it is a ZIP container underneath, you can look inside one without installing anything. Copy the file, rename the copy’s extension from .xapk to .zip, and open it with any archive tool on your phone or a computer. You will typically see one or more .apk files, sometimes an OBB folder, and the manifest.json that ties them together. This is also the fastest way to confirm what you are actually about to install before you commit to a method.

Quick Comparison: Ways to Open an XAPK File

Install With the Store’s Own XAPK Installer

1. Install the app the XAPK came from. If the file came from APKPure, install the APKPure app itself; it doubles as an XAPK installer. Open Me > App Management > APK / XAPK Management inside the app, find the file, and tap Install. This is the route APKPure documents as its own recommended install path, and it is the one method here that reads manifest.json and places OBB data for you automatically. Before you lean on it as your default source, read our review of whether APKPure is safe to use, since the convenience of a bundled installer is a separate question from how much you trust the store behind it.

2. Grant the “Install unknown apps” permission when prompted. Android will ask you to allow the specific app you are using to install packages from unknown sources. Grant it to that one app only, not as a blanket device setting, so a compromised app later cannot silently sideload something else through the same permission.

Use a Dedicated Split-APK Installer

3. Know exactly what SAI will and will not do with an XAPK. Split APKs Installer (SAI) by Aefyr is built to install split APK sets, the kind Android App Bundles generate as device-specific APK archives. SAI’s own release notes describe its XAPK handling as partial: it can open a .xapk file and install the APKs inside it, but it does not extract OBB expansion data, and the app itself tells you to move any OBB folder manually. If the bundle is APKs only, SAI can take it directly; if there is an OBB folder, plan on the manual placement step below either way.

4. Weigh its maintenance status before you rely on it. SAI’s own README is direct about where the project stands: “SAI is kinda dead cause I have no motivation for continuing its development.” The last real build, version 4.5 build 60, shipped in March 2021 according to its F-Droid listing. It still installs split APKs correctly for most people, but treat it as a tool nobody is actively hardening against new Android versions, not as a maintained product with a support channel behind it.

Extract and Install the Files Manually

5. Rename a copy of the file to .zip and extract it. Because XAPK is a ZIP container at its core, any archive app can open it once the extension is changed. Extracting reveals the base APK, any split APKs, an OBB folder if the app uses one, and manifest.json. Read the manifest first; it lists the package name and, for OBB-based apps, exactly where each data file needs to go.

6. Install the APK, then move OBB data to the correct folder. Install the base APK the same way you would any sideloaded APK, then copy the OBB files to /Android/obb/<package-name>/ on shared storage, matching the folder name to the package exactly. Do not rename or repack the OBB files; Android’s convention expects them untouched, and a mismatched folder name is the single most common reason a manually installed app launches but shows missing assets.

Verify the Install Before You Trust It

An XAPK is still a sideloaded file, so the same checks that apply to any APK apply here, with one addition: because a bundle can carry more than one package and a folder of data files, there is more surface for something unexpected to ride along than in a single APK. Run the file through a malware scan before you open it, the same way you would any other download. If the extracted APK carries a signature you can check, remember that any modification made after an APK is signed invalidates its signature, which is exactly what a tampered repack would trigger. For the full routine, from picking a source to reviewing permissions after install, our complete guide to installing APKs safely covers the steps that sit around this one.

Challenges With Opening XAPK Files

A few problems come up often enough that they are worth knowing before you start, not after something breaks.

• Android will never learn to open it natively. XAPK is not a format Google recognizes or plans to support; every install path here routes through a third-party app or a manual extraction step, and that will not change.
• A bundle can contain more than you expect. Unlike a single APK, an XAPK can pack multiple split APKs plus data files, so a quick glance at the file size or name tells you less than it would for a standalone APK.
• Your installer of choice may be unmaintained. SAI is the clearest example: it still functions, but nobody is patching it against new Android restrictions, which is a real trade-off against the convenience of a storefront app that ships regular updates.
• OBB path mistakes fail silently. Android does not warn you when expansion data lands in the wrong folder. The app simply opens with missing content, and the fix is almost always a folder-name typo against the package name.
• Modded and cracked games travel in XAPK form too. The container format makes it easy to bundle a modified APK with its expected data files and pass the whole thing off as a normal download. If the source is a mod or crack site rather than the game’s actual publisher, our breakdown of why we don’t recommend mod APK sites explains what that repackaging typically strips out.

How to Decide Which Method Fits the File in Front of You

Start with where the file came from. If it is from APKPure, install the APKPure app and use its built-in XAPK installer; it is the only method here that reads the manifest and places OBB data without you doing it by hand. If you would rather not add a storefront app, or the file came from somewhere else entirely, rename it to .zip and extract it yourself, then install the APK and move the OBB folder to its documented path. Reach for SAI only if you are comfortable placing any OBB data yourself and have already accepted that the tool behind it stopped receiving real updates years ago.

Whichever route you pick, do not skip the file itself just because the format is unfamiliar. Scan it, check what you can verify, and confirm the source before you install, the same way you would with any APK you did not get from Google Play.

It belongs with our other Android how-to guides, which handle the practical mechanics rather than the product choice.