Free online XAPK to APKS converter

What the XAPK format is

XAPK is an Android distribution archive, usually a ZIP file containing a base APK, optional split APKs, and sometimes an .obb expansion file. APKPure and some third-party Android app stores commonly distribute applications as XAPK files, especially large games that cannot fit their additional data into the base APK.

An XAPK does not have one universal internal specification. A package may contain one APK plus an OBB, several APK splits, or a manifest describing the package name and version. You can inspect one with unzip -l app.xapk after making a copy and, if necessary, rename it to app.zip.

What the APKS format is

APKS is an archive of Android APK files, normally produced by Google's bundletool from an Android App Bundle. It can contain a base APK and configuration or feature splits selected for a device, along with bundletool metadata such as toc.pb.

Installers such as Split APKs Installer (SAI) use APKS to install several mutually dependent APKs as one package. APKS avoids manually installing incompatible split files separately, but it does not replace an OBB expansion file and cannot create missing APK splits from a single universal APK.

How to actually convert XAPK to APKS

Best method when the XAPK contains split APKs

1. Copy the original XAPK and inspect its contents. Confirm that it contains the base APK and any files with names such as config.arm64_v8a.apk, config.xxhdpi.apk, or feature APKs.
2. Install Split APKs Installer (SAI) on an Android device. Use SAI's install function to open the XAPK, or extract the archive and select all APK files together if direct XAPK support is unavailable.
3. After the package is installed, open SAI's backup function, select the installed application, and export or back it up as an .apks file. SAI generates a package archive from the APK set rather than merely changing the extension.
4. Test the resulting APKS on the target device with SAI. Keep the original XAPK and its OBB file until the application has been tested.

Manual extraction for inspection

On a computer, extract the archive with unzip app.xapk -d xapk_contents. Do not assume that renaming .xapk to .apks, or putting every extracted file into a new ZIP, creates a valid APKS package. Some APKS installers require bundletool metadata and a compatible split set, so a manually repacked archive may be rejected.

When the original AAB is available

If the XAPK came from your own Android project and the original Android App Bundle is available, generate APKS from the AAB instead of converting the downloaded archive:

java -jar bundletool.jar build-apks --bundle=app.aab --output=app.apks --mode=universal

For device-specific splits, use --connected-device with a connected Android device, or provide a device specification. bundletool cannot reconstruct an AAB or its split-selection metadata from an arbitrary XAPK.

Online repackaging

For a simple archive conversion, you can submit the file to 101convert.com and convert it for free without installing software. Online repackaging cannot repair missing splits, generate an OBB, or guarantee that an installer will accept a nonstandard XAPK.

Compatibility and limitations

APK files are signed, and repackaging the files into an APKS archive does not change those signatures. Installation still requires every split to have the same package name, version code, signing certificate, and compatible split configuration.

If the XAPK contains an OBB, copy the OBB to Android/obb/<package.name>/ on devices and Android versions that permit that location. An APKS export does not automatically include or install this external data, and newer Android releases may restrict direct access to the OBB directory.

Architecture and screen-density splits can make an archive device-specific. Preserve the original APK files without modifying, recompressing internally, or re-signing them; otherwise Android may reject the installation or an existing installation may fail signature verification.