Free online APKM to APKS converter

Devices and installers that support bundletool archives may require .apks instead of APKMirror’s .apkm package. The formats contain split APKs, but their archive metadata differs, so changing the extension alone does not produce a valid APKS file.

What the APKM format is

APKM is an APKMirror package format for distributing an Android app made of multiple APKs: usually a base APK plus configuration splits for CPU architecture, screen density, language, or Android version. APKMirror generates APKM files when an app cannot be distributed as one standalone APK.

An APKM is normally a ZIP-based archive containing split APK files and APKMirror-specific metadata. You encounter it when downloading split applications from APKMirror and installing them with APKMirror Installer. Android’s built-in package installer does not generally install an APKM archive directly.

What the APKS format is

APKS is the archive format produced by Google’s bundletool. It packages APKs generated from an Android App Bundle, normally including a base APK, configuration splits, and a toc.pb table of contents describing the package.

APKS is useful for local testing, device-specific distribution, and installation through bundletool or split-APK installers. Bundletool can select only the APKs required by a connected device, reducing unnecessary downloads compared with installing every split. An APKS archive can also be built in universal mode when one broadly compatible APK is preferred, although universal mode may be larger.

How to convert APKM to APKS

There is no official, lossless APKM-to-APKS converter that creates bundletool metadata from an arbitrary APKM. The reliable method depends on whether the original Android App Bundle is available.

When the original AAB is available

1. Install the Java runtime and download the matching bundletool.jar.
2. Build the APKS archive from the original App Bundle:

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

For a device-independent archive, use --mode=universal. For an installable signed package, provide the signing key, alias, and passwords:

java -jar bundletool.jar build-apks --bundle=app.aab --output=app.apks --mode=default --ks=release.jks --ks-key-alias=app

Use the same release signing identity as the installed application when replacing an existing version. To install the result on a connected device, run:

java -jar bundletool.jar install-apks --apks=app.apks

When only the APKM is available

Use APKMirror Installer → Install APKs or another split-APK installer and select the APKM file; conversion is unnecessary for installation. Extracting the APKM and renaming the ZIP to .apks is not a valid conversion because the archive may lack toc.pb and the metadata expected by bundletool.

You can also use the free converter on 101convert.com without installing software. Treat the output as a repackaged archive unless the service explicitly confirms that it generates bundletool-compatible metadata; test it with the intended APKS installer before distributing it.

Compatibility and limitations

• All component APKs must belong to the same application, version code, and signing certificate. Mixing splits from different releases normally causes installation failure.
• Removing language, density, or ABI splits can make an application fail to install or run on devices that require them.
• APKM and APKS archives do not convert APK binaries, change their signatures, or remove Android package restrictions; they only package already signed APK components.
• An APKS file is still an archive, not a single APK. Use bundletool or a compatible split installer rather than Android’s ordinary single-APK installation screen.