APK vs AAB: Which Format to Submit to Google Play?
Google now requires Android App Bundle (AAB) for new apps, but APKs are still essential for testing and sideloading. Here is when to use each and how to generate both.
The short answer
For Google Play → AAB
Required for new apps since August 2021. Smaller download size. Google generates optimised APKs per device.
For testing → APK
Required for direct device installation (sideloading), human testing services, and beta distribution outside Play Store.
What is an APK?
An APK (Android Package Kit) is the traditional Android app format. It contains everything needed to run the app: code, resources, assets, and manifest: packaged into a single file. APKs can be installed directly on any Android device without going through the Play Store.
When to use APK: Direct device testing, human testing services like AppTester.co, distributing to internal testers outside Play Store, sideloading on Fire OS or other Android forks, and beta distribution via platforms like Firebase App Distribution.
What is an AAB?
An AAB (Android App Bundle) is a publishing format that includes all your app's code and resources but defers APK generation to Google Play. When a user downloads your app, Google Play generates a streamlined APK containing only the code and resources needed for that specific device.
The result: App downloads are typically 15–20% smaller. Users get a faster install. Google Play handles device fragmentation for you. You cannot install an AAB directly on a device.
How to generate both from Android Studio
Generate a release APK
Build → Generate Signed Bundle/APK → APK → Select keystore → Release
Or via Gradle: ./gradlew assembleRelease
Generate a release AAB
Build → Generate Signed Bundle/APK → Android App Bundle → Select keystore → Release
Or via Gradle: ./gradlew bundleRelease
The testing workflow we recommend
Build a signed release APK for pre-submission testing: use AppTester.co to get it tested on real devices.
Fix bugs found during testing. Increment the version code.
Build a signed AAB for Google Play submission.
Upload the AAB to Play Console. Never upload a debug build.
Test your APK before it becomes an AAB
Upload your signed release APK to AppTester.co. Real testers on real Android devices will find the bugs before your users do: within 48 hours.
Submit APK for Testing: from $19