APKS is the split APK bundle format popularized by SAI (Split APKs Installer) and commonly used in app backup tools. Unlike a traditional single .apk file, an .apks file is a ZIP container holding multiple APK splits — the base application, architecture-specific native libraries, screen density resources, and language packs. These splits must be installed together in a single session for the app to function correctly.
AnExplorer handles APKS installation natively. Tap the file, confirm the installation, and all splits are installed together using Android's session installer API — no separate tools or multi-step processes required.
Quick Answer
Open AnExplorer → navigate to the .apks file → tap it → tap Install. AnExplorer automatically expands the bundle and installs all splits in a single session.
What Is an APKS File?
APKS is a ZIP-based container format that bundles multiple Android split APK files into a single downloadable or transferable file. The format was established by the SAI (Split APKs Installer) project and has since become a de facto standard for app backup and transfer tools.
Inside a typical APKS file you will find:
- base.apk — the core application code, primary resources, and manifest
- split_config.arm64_v8a.apk — native library code for ARM64 processors
- split_config.xxhdpi.apk — image resources scaled for high-density screens
- split_config.en.apk — English language strings and locale resources
- Additional split APKs — feature modules, other languages, other architectures
All these components together form the complete application. Installing just the base.apk alone would result in a broken app missing native libraries, appropriately-sized graphics, or language resources.
Where APKS Files Come From
You encounter APKS files in several scenarios:
- App backups — SAI and similar tools export installed apps as APKS to preserve all splits
- Device-to-device transfer — moving apps between phones without re-downloading from Play Store
- ADB backups — Android Debug Bridge can export app bundles
- Custom ROM setup — pre-packaged system apps in APKS format
- Enterprise distribution — IT departments sharing internal apps
- Archiving — saving specific app versions for testing or rollback
- Alternative app stores — some stores provide downloads in APKS format
The key difference from downloading a fresh APK: APKS files capture the exact configuration that was installed on a particular device, including only the splits relevant to that device's architecture and screen density.
Step-by-Step: Install an APKS File
Prerequisites
Enable AnExplorer to install apps from unknown sources:
- Go to Settings → Apps → Special app access → Install unknown apps
- Find AnExplorer → toggle Allow from this source to ON
Installation Process
- Transfer the
.apksfile to your phone (download, USB transfer, cloud storage, or receive via Bluetooth) - Open AnExplorer → navigate to the file location (usually Downloads/)
- Tap the
.apksfile — AnExplorer recognizes it as a split APK bundle - Review the app information displayed: package name, version, permissions
- Tap Install
- Android installs all splits together in one atomic session
- Tap Open to launch the app or Done to return to AnExplorer
The installation typically takes 3-10 seconds depending on the app size.
Technical Details
APKS Internal Structure
An APKS file is a standard ZIP archive containing APK files:
AppName_v2.1.0.apks (ZIP container)
├── base.apk (core application ~20-50 MB)
├── split_config.arm64_v8a.apk (ARM64 native libraries ~5-30 MB)
├── split_config.xxhdpi.apk (high-density resources ~2-10 MB)
├── split_config.en.apk (English strings ~0.1-1 MB)
└── split_config.es.apk (Spanish strings ~0.1-1 MB)
Installation Mechanism
AnExplorer uses Android's PackageInstaller Session API for APKS installation:
- Session creation — opens a new installation session with the package manager
- Split streaming — reads each APK from the APKS container and streams it into the session
- Validation — Android verifies all splits share the same package name and signing certificate
- Atomic commit — all splits are installed simultaneously (all succeed or all fail)
- Registration — the app appears in the launcher and app drawer
This is identical to how the Play Store installs apps from App Bundles, ensuring full compatibility.
Split APK Types Explained
| Split Type | Example Filename | Purpose | Size Impact |
|---|---|---|---|
| Base | base.apk | Core code and resources | Required, largest |
| ABI (CPU) | split_config.arm64_v8a.apk | Native libraries | 5-100 MB for games |
| Density | split_config.xxhdpi.apk | Screen-appropriate images | 2-20 MB |
| Language | split_config.en.apk | Locale strings | 0.1-2 MB each |
| Feature | split_dynamic_feature.apk | On-demand modules | Varies |
Why Split APKs Exist
Google introduced split APKs with Android App Bundles to solve the "universal APK" bloat problem:
- A universal APK includes native libraries for ARM, ARM64, x86, and x86_64 — only one is used
- It includes drawable resources for ldpi through xxxhdpi — only one density matches your screen
- It includes strings for 40+ languages — you use only one or two
With splits, your device gets only what it needs. A 200 MB universal APK might become 60 MB of device-specific splits. The APKS format preserves these splits for redistribution.
APKS vs APKM vs XAPK vs APK
| Feature | APKS | APKM | XAPK | APK |
|---|---|---|---|---|
| Source | SAI, backup tools | APKMirror | APKPure | Anywhere |
| Container | ZIP | ZIP | ZIP | Single file |
| Contains splits | ✅ | ✅ | Optional | ❌ |
| Contains OBB data | ❌ | ❌ | ✅ | ❌ |
| Metadata format | None (just APKs) | manifest.json | manifest.json | N/A |
| Best for | Backups, transfers | APKMirror downloads | Large games | Simple apps |
| AnExplorer support | ✅ | ✅ | ✅ | ✅ |
All four formats are supported by AnExplorer with identical ease of use — tap and install.
Creating APKS Backups
You can export installed apps as APKS files for backup or transfer:
- Open AnExplorer's App Manager
- Find the app you want to back up
- Long-press → Backup or Export as APK
- The exported file preserves all splits for the app as installed on your device
- Transfer the APKS to another device or cloud storage for safekeeping
Note: Apps with DRM or license verification may not work when transferred to a different device or Google account.
Inspecting APKS Contents
You can examine what is inside an APKS bundle without installing:
- Long-press the
.apksfile in AnExplorer - Tap Open as archive — the file opens like a ZIP
- You see all the split APK files listed with their sizes
- This lets you verify the correct architecture and configuration splits are included
Useful checks:
- Confirm
split_config.arm64_v8a.apkexists for modern phones - Verify the base.apk version matches what you expect
- Check total extracted size to ensure you have enough storage
Compatibility Considerations
APKS files exported from one device may not work on another if:
- Architecture mismatch — an APKS exported from an ARM64 phone will not work on an x86 tablet because it lacks x86 native libraries
- Density mismatch — not critical, Android scales resources. The app works but may use slightly more memory.
- Android version — the app's minimum SDK version must be met by the target device
- Signature conflicts — if a different version of the app (with different signing key) is already installed
For maximum compatibility when backing up apps, ensure all architecture splits are included or use a tool that exports universal bundles.
Troubleshooting
"Package conflicts with existing package"
The target device already has a version of the app installed with a different signing certificate. This commonly happens when:
- The installed version came from a different source (modified APK)
- You are trying to install an older version over a newer one
Solution: Uninstall the existing app first, then install the APKS.
APKS installs but app crashes or features are missing
The bundle may be missing device-specific splits needed for the target device:
- Open the APKS as a ZIP and check for your device's architecture split
- If you exported from an ARM64 device and are installing on x86, it will fail
- Download the Universal variant or export from a matching device
"Session failed" or installation times out
- Close background apps to free RAM — the session installer needs memory for processing
- Ensure sufficient storage space (2x the APKS file size recommended)
- On some devices, very large bundles (500+ MB) may time out. Try again after a fresh reboot.
Cannot open APKS file — "unknown format"
- Ensure you are using AnExplorer to open the file, not the default file manager
- Long-press → Open with → AnExplorer if another app is handling the file association
- The file may be corrupted. Re-download or re-transfer the APKS file.
Related Guides
- Install APK Files — standard single APK installation
- Install APKM Files — APKMirror bundle format
- Install XAPK Files — APKPure bundle with OBB data
- Backup Apps as APK — export installed apps
- App Manager
