Convert AAB to APK Online: What This Tool Actually Does
The Android App Bundle (.aab) is the format Google Play asks developers to upload, but it is not something you can install on a phone. If you have an .aab file from a build server, a CI pipeline, or a colleague, you first need to turn it into an installable .apk. This page gives you two things for that job: an interactive AAB to APK command builder that writes the exact bundletool command for your operating system, and an AAB file explorer that opens the bundle in your browser so you can see what is inside before you convert it.
The conversion itself runs through Google's official bundletool, which is a Java program. Because bundletool needs the Java runtime and access to your keystore, the actual build step happens on your own machine, not on our servers. Your .aab file is never uploaded anywhere. The builder simply removes the guesswork so you can copy a correct, ready-to-run command instead of memorising flag names.
AAB vs APK: Why You Cannot Just Rename the File
A lot of people search for how to change AAB to APK by renaming the extension, and it never works. An .apk is a single, self-contained package that Android can install directly. An .aab is a publishing container: it holds your compiled code and resources split into modules, and it expects Google Play or bundletool to generate the final, device-optimized APKs from it. Renaming the file does not unpack those modules or sign anything, so Android refuses to install it. The only reliable way to convert an Android App Bundle to APK is to let bundletool build the APK set for you.
How to Convert AAB to APK on Windows, Mac, and Linux
The steps are the same on every platform, and only the file-path style changes, which is why the command builder above has a Windows, macOS, and Linux switch. Here is the full flow from start to finish:
- Install Java JDK 8 or newer. Run
java -versionin a terminal to confirm Java is on your PATH. - Download bundletool. Get the latest
bundletool-all.jarfrom Google's official GitHub releases page. - Build the APK set. Point bundletool at your bundle and let it produce a .apks archive:
java -jar bundletool-all.jar build-apks --bundle=app.aab --output=app.apks --mode=universal - Open the .apks archive. It is just a ZIP file, so extract it and you will find
universal.apkinside. - Install on your device. Copy the APK to your phone and sideload it, or use
bundletool install-apkswith a device connected over USB.
Universal APK vs Split APKs: Which One Should You Build?
If you want one file that installs on any phone, use --mode=universal. This builds a single universal APK from your AAB that bundles every CPU architecture, screen density, and language into one package. It is larger, but it is the simplest option for testing, archiving, or sharing a build outside the Play Store. If you leave the mode out, bundletool instead produces split APKs that are trimmed for one specific device, so they download smaller but you have to install the matching set together. For most people who just need to convert an .aab for a quick install, the universal APK is the right choice.
Signing the APK You Get From an AAB
Android will not install an APK unless it is signed. For testing, bundletool can sign with a debug key automatically, which is exactly what the "Use debug keystore" option in the builder does. If you are preparing a release build, for example to distribute on your own website, sign it with your own keystore by filling in the keystore path, keystore password, key alias, and key password fields. The builder then adds the --ks, --ks-pass, --ks-key-alias, and --key-pass flags so the APK you get carries your real production signature instead of a throwaway debug one.
Common bundletool Errors and How to Fix Them
Two problems come up again and again. The message "bundletool: command not found" means you tried to run bundletool as if it were a built-in command. It is a JAR file, so you always call it with java -jar bundletool-all.jar. The "No key/certificate" error means signing details are missing: either add --mode=universal for an unsigned test build, or supply your keystore flags as described above. The Troubleshooting tab higher up the page covers more of these, and the AAB Explorer lets you confirm your bundle really contains the modules you expect before you spend time debugging a command.
When Would You Actually Need to Convert an AAB?
The usual reasons are testing a release build on a real device before you publish, handing a build to a tester who does not use Google Play, keeping an installable copy of your own app for your records, or running QA on hardware that Play Store internal testing does not reach. Whatever the reason, only convert app bundles that you have the right to use, such as your own builds or bundles you have clear permission to work with.