Part of: Upload APK Online
Convert an .aab to an APK you can install
Phones install APKs, not bundles. Drop your .aab here and this page turns it into one universal APK, with every CPU type, screen density and language from the bundle, signed so Android will install it. It all happens in this tab: the bundle is never uploaded.
What you get
One APK that installs on any phone the app supports, the same kind of file bundletool builds with --mode=universal. It holds the base module and any install-time asset packs. It is bigger than what Play would send one device, because it carries every split at once, which is what you want for testing on more than one phone.
To see what is inside the bundle first, or what Play would actually send a device, open it in the AAB inspector.
Why the APK is signed with a test key
Android refuses to install an unsigned APK. Your release key should never be typed into a web page, so this one has no keystore field. Instead, the first conversion makes a key in this browser and keeps it in the browser's own storage, where page scripts can use it to sign but cannot read it out. Every conversion after that uses the same key, so a newer build installs over an older one.
The certificate is named Test build. It is not your Play signing key, so the APK will not install over a copy from Google Play, and APIs that check the SHA-1 (Google Sign-In, Maps) need the fingerprint shown after converting added in their console.
What this converter can't do yet
Bundles with feature modules, or with asset packs Play delivers after install, are refused with a message, never turned into an APK with parts missing. So are a few rare resource features and bundles over 250 MB. bundletool handles all of those on your own machine.
Convert with bundletool instead
To sign with your own key, or for a bundle this page refuses, run bundletool locally. Pick your system and key and copy the commands. In Android Studio you can also skip the bundle entirely: Build, then Generate Bundle(s) / APK(s), then Generate APK(s).
java -jar bundletool-all.jar build-apks --bundle=app-release.aab --output=app.apks --mode=universal tar -xf app.apks universal.apk adb install universal.apk
Without --ks, bundletool signs with the Android Studio debug key in ~/.android/debug.keystore. Install bundletool with brew install bundletool, then run bundletool in place of java -jar bundletool-all.jar.
Send the APK to testers
After converting, Get an install link uploads the APK, not the .aab, and gives you a link and QR code testers open on their phones. Or upload any APK you already have.
AAB or APK: which one goes where
The .aab goes to Google Play, which requires it for new apps. The APK goes everywhere else: testers, clients, a device on your desk, a bug report. The IPA vs APK explainer covers how the formats compare across platforms.
Frequently Asked Questions
Can you install an .aab file on an Android phone?
No, Android installs APKs, not bundles. An .aab is the format Google Play takes in: Play splits it into the APKs each device needs, and a phone has no way to open the bundle itself. To try a build outside Play you need an APK, which is what this page makes: one universal APK that holds every CPU type, screen density and language from the bundle.
Is my .aab uploaded anywhere?
No, the conversion runs in this browser tab. The bundle is read and rebuilt on your device and is never sent to BetaDrop or anyone else. The only thing that can leave your device is the converted APK, and only if you click Get an install link after converting.
Is the converted APK signed?
Yes, with a test key created in this browser. Android will not install an unsigned APK, so the page makes an RSA key the first time you convert, keeps it in this browser's storage where page scripts cannot read it out, and signs with it every time after. The certificate says CN=Test build, so nobody mistakes it for your release key. The SHA-1 and SHA-256 fingerprints are shown after each conversion.
Will it install over the Play Store version of my app?
No, Android refuses an update signed with a different key. The Play copy is signed with your app signing key and the converted APK with this browser's test key, so uninstall the Play copy first. Later conversions in the same browser use the same test key, so a tester can install a newer converted build over an older one.
Why does Google Sign-In or Maps fail in the converted APK?
Those APIs check the signing certificate's SHA-1. They only accept fingerprints you registered in the Google Cloud or Firebase console, and the test key's is not one of them yet. Add the SHA-1 shown after converting to the matching Android API key or OAuth client, or build the APK with your own key using the bundletool command on this page.
Can I convert with my own keystore?
Not on this page; your key stays on your machine. The page has no keystore or password field on purpose. The bundletool section builds the command for you: pick your keystore path and alias, run it locally, and bundletool signs the universal APK with your key. Passwords stay as placeholders you fill in on your own machine.
What about feature modules and asset packs?
Install-time asset packs are included; feature modules aren't yet. A bundle with feature modules, or with asset packs Play delivers after install (fast-follow or on-demand), is refused with a message rather than turned into an APK that would be missing parts. bundletool with --mode=universal handles those bundles, and the command is on this page.
How do I send the APK to testers?
Click Get an install link after converting. The APK uploads to BetaDrop and you get a link and a QR code that testers open on their phones to install it. Without an account the link lasts 24 hours; a free account keeps builds for up to 7 days. Your .aab is never uploaded, only the APK.
Will this still work when Google's developer verification reaches every country?
Google says it will expand verification to all certified devices in 2027. As of 18 Oct 2026, its developer verification page (developer.android.com/developer-verification) says protections began on 30 Sep 2026 for people installing apps from participating stores in Brazil, Indonesia, Singapore and Thailand on certified devices running Android 7 or newer, and that verification will be expanded globally for all apps on certified devices in 2027. Google has not yet published how that will treat test builds signed with a test key. We will update this page when it does.
