MWM
Contact salesBuild your app
App Store Optimization

Android App Bundle (AAB)

Also known asAAB.aab

Google's modern Android distribution format that lets the Play Store generate device-optimized APKs from a single uploaded bundle — reducing average install size by 15-50%.

Key takeaways

  1. 01AAB replaced APK as Google Play's required upload format for new apps in August 2021. Existing apps had until 2023 to migrate.
  2. 02Google Play generates device-optimized APKs per install from the AAB — only the resources / code that device actually needs.
  3. 03Typical install size reduction: 15-50% vs equivalent universal APK. Larger benefit for apps with many language assets / device variants.

Android App Bundle (.aab) is Google's modern Android distribution format, introduced in 2018 and made mandatory for new Google Play uploads in August 2021. Replaces the older APK format for store distribution. The key benefit: Google Play uses the AAB to generate device-optimized APKs per install — each user only downloads the resources, code, and language assets their specific device needs, dramatically reducing install size.

Why AAB matters

  • Smaller install sizes: 15-50% reduction vs universal APK. Apps with many languages or many device-variant assets see the largest benefit.
  • Faster downloads on weak connections: emerging-market install completion rates increase materially when install sizes drop below carrier-network friction thresholds.
  • Modular delivery: apps can split features into modules that download on demand rather than upfront. Reduces initial install size further.
  • Asset packs: large assets (HD textures, video content, ML models) can ship separately, downloaded only when actually used.

Migration: existing apps on the Play Store had until late-2023 to migrate to AAB. New apps must use AAB from August 2021. APKs are still used internally — Google Play generates them dynamically from your uploaded AAB — but you no longer build or upload them yourself.

Outside Google Play: AABs aren't directly installable. For direct distribution (enterprise apps, alternative app stores, sideloading), developers still need APKs — generate them from the AAB using `bundletool`. F-Droid, Amazon Appstore, Huawei AppGallery, Samsung Galaxy Store all still accept APK (some are starting to accept AAB).

AAB vs APK

AAB (.aab)APK (.apk)
Google Play uploadRequired (new apps since Aug 2021)No longer accepted
Install size15-50% smaller (device-optimized)Universal — larger
Direct install / sideloadNot directly installableYes
Alt stores (Amazon, F-Droid)Some now acceptStandard

Google Play generates device-optimized APKs from your AAB at install time. For sideloading or alternative stores you still produce APKs via bundletool.

Quick answers

What is an Android App Bundle (AAB)?

Google's modern Android distribution format — replaces APK as the Google Play upload format. The .aab file contains all app resources + code; Google Play uses it to generate device-optimized APKs per install. Each user downloads only the resources their specific device needs. Reduces typical install size by 15-50%.

Is APK still relevant in 2026?

Yes for direct distribution. Google Play requires AAB for new app uploads since August 2021, but APKs are still used for sideloading, enterprise distribution, alternative app stores (Amazon Appstore, F-Droid, Huawei AppGallery), and internal testing. Generate APKs from your AAB using Google's `bundletool`. APKs are also what Google Play dynamically generates from your AAB at install time.

How much does AAB reduce my install size?

15-50% vs equivalent universal APK. Apps with many language assets, multiple device variants (different screen densities, CPU architectures), or large texture / model assets see the largest reduction. Apps with minimal assets see modest reduction. Either way, the benefit compounds at scale — material impact on install-completion rates in emerging markets where weak carrier networks make large downloads friction-heavy.

Next reads

Back to glossary