XAPK is APKPure's bundle format designed to solve a fundamental Android installation challenge: large games and applications require both an APK installer file and additional expansion data (OBB files) that must be placed in a specific filesystem location. Without the OBB data in the correct path, the game crashes, shows "downloading additional data" errors, or displays missing textures and audio.
XAPK packages everything together — the APK installer and all required OBB expansion files — into a single downloadable container. AnExplorer handles XAPK installation end-to-end: it installs the APK through Android's package manager and automatically copies OBB files to the exact required directory path. No manual file copying, no separate steps.
Quick Answer
Open AnExplorer → navigate to the .xapk file → tap it → tap Install. AnExplorer installs the APK and places OBB data files in the correct /Android/obb/ directory automatically.
What Is an XAPK File?
XAPK is a ZIP-based container format created by APKPure that bundles:
- The APK file — the main application installer (typically 30-100 MB)
- OBB expansion files — additional game data like maps, textures, audio, and video (can be 500 MB to 4 GB)
- manifest.json — metadata describing the package name, version, and file placement instructions
The format exists because Android historically limited APK files to 100 MB (later increased to 150 MB). Games exceeding this limit must store extra assets in OBB (Opaque Binary Blob) expansion files placed at a very specific path: /Android/obb/[package.name]/. If this file is missing or in the wrong location, the app cannot find its assets and fails.
The Play Store handles OBB delivery automatically during installation. But when sideloading (installing outside the Play Store), you need a tool that understands OBB placement — which is exactly what AnExplorer provides.
Where You Encounter XAPK Files
XAPK files appear primarily from these sources:
- APKPure downloads — APKPure's default download format for large games
- Game archive sites — preserved game versions with data included
- Region-restricted games — large games not available in your Play Store country
- Older game versions — specific builds for compatibility or nostalgia
- Offline game installers — complete packages for installing without internet
- Shared game files — received from friends who want to share a game they have
Games that commonly come as XAPK include: large RPGs, racing games with high-quality tracks, shooters with detailed maps, and any game with substantial audio/video content.
Step-by-Step: Install an XAPK File
Prerequisites
Grant AnExplorer permission to install apps:
- Go to Settings → Apps → Special app access → Install unknown apps
- Find AnExplorer → toggle Allow from this source
Installation Process
- Download the
.xapkfile from APKPure or your source - Open AnExplorer → navigate to Internal Storage → Download/
- Tap the
.xapkfile - AnExplorer displays the app information: name, version, package name, and total size
- Tap Install
- AnExplorer performs two actions automatically:
- Step 1: Installs the APK via Android's package manager
- Step 2: Copies OBB files to
/Android/obb/[package.name]/
- Tap Open to launch the game — no "downloading additional data" prompt needed
The process takes longer than a standard APK install because OBB files can be several gigabytes. A 2 GB XAPK might take 30-60 seconds to fully install.
Technical Details
XAPK Internal Structure
An XAPK file is a standard ZIP archive with this layout:
GameName_v1.2.3.xapk (ZIP container)
├── com.developer.game.apk (main installer)
├── Android/obb/com.developer.game/
│ └── main.1234.com.developer.game.obb (expansion data)
└── manifest.json (placement metadata)
Some XAPK files contain multiple OBB files:
main.[version].[package].obb— primary expansion (required)patch.[version].[package].obb— patch expansion (updates to main data)
OBB File Naming Convention
Android requires OBB files to follow a strict naming pattern:
[main|patch].[versionCode].[package.name].obb
Example: main.12345.com.gameloft.android.ANMP.GloftA9HM.obb
mainorpatch— identifies the file type12345— the app's versionCode from AndroidManifest.xmlcom.gameloft.android.ANMP.GloftA9HM— the exact package name
The OBB must be in /Android/obb/[package.name]/ for the app to find it. AnExplorer places it exactly there during XAPK installation.
Size Limits and Reality
| Component | Historical Limit | Typical Size |
|---|---|---|
| APK file | 100-150 MB | 30-100 MB |
| Main OBB | 2 GB max | 500 MB - 2 GB |
| Patch OBB | 2 GB max | 100 MB - 1 GB |
| Total XAPK | ~4.15 GB theoretical | 500 MB - 3 GB |
Note: Starting with Android 11, Google recommends Play Asset Delivery (PAD) instead of OBB files. However, many existing games still use OBB, and XAPK remains relevant for sideloading these games.
Modern XAPK with Split APKs
Newer XAPK files from APKPure may contain split APKs in addition to OBB data:
GameName_v2.0.xapk (ZIP container)
├── base.apk (core app)
├── split_config.arm64_v8a.apk (native libs)
├── split_config.xxhdpi.apk (density resources)
├── Android/obb/com.developer.game/
│ └── main.2000.com.developer.game.obb (expansion data)
└── manifest.json (metadata)
AnExplorer handles this hybrid format as well — installing all APK splits via session installer and placing OBB data in the correct location.
XAPK vs APK vs APKM vs APKS
| Feature | XAPK | APK | APKM | APKS |
|---|---|---|---|---|
| Source | APKPure | Anywhere | APKMirror | SAI/backup tools |
| Contains OBB | ✅ | ❌ | ❌ | ❌ |
| Contains split APKs | Optional | ❌ | ✅ | ✅ |
| Size range | 500 MB - 3 GB | 1-150 MB | 10-200 MB | 10-200 MB |
| Best for | Large games | Small apps | Modern apps | App backups |
| Auto-OBB placement | ✅ | N/A | N/A | N/A |
| AnExplorer support | ✅ | ✅ | ✅ | ✅ |
XAPK is the only format that bundles game expansion data. If you are downloading a large game for sideloading, XAPK is typically the format you need.
Why OBB Files Matter
Understanding OBB placement helps when troubleshooting game installation issues:
Android's expansion file system requires OBB files at exactly:
/storage/emulated/0/Android/obb/[package.name]/[filename].obb
If this file is missing, misnamed, or in the wrong directory, the game will:
- Crash immediately on launch with no error message
- Show "Downloading additional data" and then fail (no internet or server offline)
- Open but display placeholder textures, silent audio, or missing levels
- Show "Storage permission required" even when permissions are granted
AnExplorer eliminates all these issues by placing OBB files precisely where they need to be during XAPK installation.
Manual OBB Installation
If you have a standalone .obb file separate from an XAPK (perhaps extracted manually or received separately):
- Open AnExplorer → navigate to
Internal Storage/Android/obb/ - Create a folder named exactly matching the app's package name (e.g.,
com.gameloft.android.ANMP.GloftA9HM) - Copy the
.obbfile into that folder - Verify the OBB filename matches the expected pattern
- Launch the game — it should find the data without downloading
Storage Considerations
XAPK files are large. Plan your storage:
- You need free space for: the XAPK file itself + the installed APK + the OBB files in their final location
- A 2 GB XAPK typically needs ~4 GB free (the XAPK file + 2 GB OBB placed in obb folder)
- After successful installation, you can delete the original
.xapkfile to reclaim space - OBB files in
/Android/obb/are automatically deleted when you uninstall the game
Use AnExplorer's storage analysis to check available space before installing large XAPK files.
Troubleshooting
Game crashes immediately after XAPK install
- The OBB file may not have been placed correctly
- Check
Internal Storage/Android/obb/[package.name]/— it should contain the OBB file - Verify the OBB filename matches the expected naming pattern
- If the folder is empty or missing, try installing again via AnExplorer
- On Android 11+, accessing
/Android/obb/may require special permissions for manual verification
"Download additional data" prompt after installation
- The OBB version may not match the APK version (version mismatch)
- The XAPK may be for a different version than what was installed
- Re-download the XAPK ensuring APK and OBB versions align
XAPK install fails at the APK step
- Check that AnExplorer has permission to install unknown apps
- Uninstall any existing version of the game first (different signatures block upgrades)
- Ensure sufficient storage for both APK installation and OBB copying
Installation is extremely slow
- XAPK files are large (often 1-3 GB). Copying gigabytes of OBB data takes time.
- On devices with slower internal storage (eMMC vs UFS), expect 30-90 seconds for large games.
- Do not interrupt the process — let it complete fully before launching the game.
"Insufficient storage" error
- You need space for the XAPK file + extracted OBB + installed APK
- For a 2 GB XAPK, free at least 5 GB before installation
- Use Memory Cleaner to clear unnecessary files
- Consider installing on an SD card if your device supports adoptable storage
Related Guides
- Install APK Files — basic APK installation
- Install APKM Files — APKMirror split bundle
- Install APKS Files — SAI bundle format
- Backup Apps as APK — create APK backups
- App Manager
