You cannot open an AAB file on your phone by tapping it, because a phone does not install AAB files. An AAB is the file you upload to Google Play. Play turns it into the APK your phone actually installs.
To try your app on a phone, send it through Google Play’s internal app sharing. Or convert it on your computer with Google’s bundletool. Both take a few minutes.
Once your app works on your phone, the next step before launch is the closed test. You run that step with Testers Community.
Updated November 2026
Why your phone will not open it
Google describes an Android App Bundle as a publishing format. It holds all of your app’s code and resources, and leaves the final step to Google Play.
That final step is building APKs. Google Play uses your bundle to make an APK suited to each kind of phone. That APK is what gets installed.
So the AAB is the recipe, not the meal. Your phone has nothing to do with it until something turns it into an APK.
For the longer version, see our page on what an AAB file is.
The easiest way: internal app sharing
This is Google’s own way to get a build onto a phone fast. You upload the AAB, and Play Console gives you a link.
You open that link on the phone. No cables, no command line.
On your computer
- Open Play Console and go to the internal app sharing upload page.
- Upload your AAB. It can be signed with any key, even a debug key. Google re-signs it for sharing.
- Copy the link Play Console gives you, and send it to your phone.
You need the “Release apps to testing tracks” permission, which account owners have by default.
The app also needs to exist in your Play Console. Whoever installs it needs access to its store listing.
On your phone, once
The Play Store hides this switch, so you turn it on one time per phone.
- Open the Google Play Store app.
- Tap Menu, then Settings.
- In the About section, tap the Play Store version seven times.
- When the Internal app sharing setting appears, switch it on.
- Tap Turn on.
Now open the link on that phone. It opens in the Play Store, and you install your app from there like any other.
Two limits are worth knowing. Up to 100 people can install from one link. Links expire 60 days after you upload.
Need more people or more time? Upload the same file again for a fresh link.
The offline way: bundletool
bundletool is Google’s free command-line tool for app bundles. It runs on your computer and turns the AAB into APKs.
It then installs them on a phone plugged in by USB. Download it from Google’s bundletool releases page.
Get the phone ready
- Open Settings, then About phone, and tap Build number seven times. You will see “You are now a developer!”
- Find Developer options in Settings and turn on USB debugging. The exact menu path varies by phone.
- Plug the phone into your computer and accept the prompt to allow debugging from it.
Run two commands
First, build the APKs from your bundle.
bundletool build-apks --bundle=my_app.aab --output=my_app.apksThen install them on the connected phone.
bundletool install-apks --apks=my_app.apksIf you do not give it a signing key, bundletool signs the APKs with a debug key. That is fine for trying the app on your own phone.
Want one single file you can send to someone instead? Add --mode=universal to the first command.
You get one universal APK that installs on any phone. It is bigger than a normal APK, because it carries everything for every kind of device.
Which way should you use?
| Internal app sharing | bundletool | |
|---|---|---|
| Needs a computer | Only to upload | Yes, and a USB cable |
| Needs Play Console | Yes | No |
| Good for | You and up to 100 people | Your own phone, offline |
| Link or file lasts | 60 days | As long as you keep it |
If you already have a Play Console account, use internal app sharing. It is quicker, and it installs your app the same way your users will get it.
Someone sent me an AAB. How do I install it?
You do not, at least not from the file alone. Ask whoever sent it for an internal app sharing link or a Google Play link.
That is the safe way to install a build that is not in the Play Store yet.
Be careful with apps that claim to open AAB files for you. Installing apps from outside Google Play skips its checks, so only do it for builds you trust.
From an AAB to a live app
Getting the app onto your phone is step two. This is the full route.
- Build your AAB and sign it with your upload key.
- Try it on your phone with internal app sharing or bundletool, as above.
- Upload it to a closed testing track in Play Console. Our closed testing walkthrough shows each screen.
- Test with Testers Community. Go to testerscommunity.com/submit-app, submit your app, and opt for Starter, $15. That is all.
- Apply for production access once 12 testers have tested for 14 days in a row.
Internal app sharing does not count toward step four. Google’s requirement for new personal developer accounts is 12 testers in a closed test for 14 days.
Builds shared through internal app sharing cannot be part of a testing track release.
How does the testing step work with Testers Community?
Production access, or your money back.
- Go to testerscommunity.com/submit-app and submit your app.
- Opt for Starter, $15, paid once for that app.
- That is all.
We assign verified testers on real Android devices, usually within 6 hours. They already know the opt-in step.
They stay for the full 14 days. Anyone who goes quiet is replaced before it costs you the count.
At the end you get a feedback report, and we help you write the production access answers. You submit the application, and Google makes the decision.
We have run Google Play closed tests since March 2024, and more than 20,000 apps have reached production through the paid service.
Frequently asked questions
Can I install an AAB file directly on Android?
No. A phone installs APK files. An AAB is the publishing format you upload to Google Play, and Play builds the APKs. Use internal app sharing or bundletool.
What is the easiest way to test my AAB on my phone?
Internal app sharing. Upload the AAB in Play Console and copy the link. Turn on internal app sharing in the Play Store settings by tapping the Play Store version seven times. Then open the link on your phone.
How do I convert an AAB to an APK?
Use Google’s bundletool on your computer. Run build-apks to make APKs from the bundle. Add –mode=universal if you want one single APK that installs on any phone.
Do I need a computer to open an AAB file?
Yes, at some point. Internal app sharing needs a computer only to upload the file to Play Console. bundletool needs a computer and a USB cable the whole time.
How many people can use an internal app sharing link?
Up to 100 people can install from one link, and each link expires 60 days after you upload. Upload the same file again to get a new link.
Does internal app sharing count toward the 12 testers?
No. Google’s requirement is 12 testers in a closed test for 14 days. Internal app sharing builds cannot be included in a testing track release. Run the closed test with Testers Community as its own step.
Someone sent me an AAB file. How do I install it?
Ask them for an internal app sharing link or a Google Play link instead. Only install builds from outside Google Play if you trust where they came from.
Run your testing step with Testers Community
- Production access, or your money back.
- Starter, $15 gives you 15 verified Android testers for the full 14 days. Paid once per app.
- Pro, $25 gives you 25 testers, plus a detailed ASO report and priority support. Also paid once per app.
- Testers opt in within 6 hours, on real Android devices, never emulators.
Submit your app and opt for Starter when your build is ready.
Short on budget? The free Pack of 16 in the Testers Community app has developers test each other’s apps for 16 days.
