HTML to AAB for Google Play
Google Play needs an Android App Bundle (AAB). Build a signed AAB from HTML, a ZIP or a website for free, targeting the latest Android version Play requires.
How it works
- Build your app as usual.
- In Output, choose APK + AAB.
- Use the same signing key for every update.
- Upload the AAB in Play Console.
HTML to AAB: what you get
Google Play only accepts Android App Bundles for new apps. Choose APK + AAB in the Output step and you get both: the APK to test on your phone, and the AAB to upload to Play Console.
Bundles target the Android version Google Play currently requires, include 16 KB page alignment for newer devices, and are signed with your upload key for Play App Signing.
- Signed APK and Google Play AAB
- Your own signing key
- Icon, splash screen, toolbar, tabs and drawer
- Native JavaScript bridge (FreeApp)
- AdMob ads with optional mediation
- No sign-up, no watermark, no limits
Questions about hTML to AAB
What is the difference between APK and AAB?
An APK installs directly on a phone. An AAB is uploaded to Google Play, which creates optimised APKs for each device.
Which key signs the AAB?
Your upload key. Google Play re-signs the final app with its app signing key.
What target SDK do bundles use?
The latest Android version Google Play requires (API 36), with older versions selectable.