Android App Bundle vs APK: what your app team is publishing
Understand Android App Bundles, device-specific APK delivery and the publishing questions to settle with your app team.
If a developer tells you the build is an "AAB" or an "APK", they mean two different file formats. This article summarises Google's "About Android App Bundles" page as read on 15 November 2026 (the page says it was last updated 2026-06-24). It is a short page, so this is a short article. Google changes these requirements, so read the page before you act.
What the page says
- An Android App Bundle is a publishing format that includes all of the app's compiled code and resources and leaves APK generation and signing to Google Play.
- Google Play uses the bundle to generate and serve optimized APKs for each device configuration, so a device downloads only the code and resources it needs. The page says you no longer have to build, sign and manage multiple APKs for different devices.
- The page opens with a notice that from August 2021 new apps are required to publish with the Android App Bundle on Google Play, that new apps larger than 200 MB are supported through Play Feature Delivery or Play Asset Delivery, and that from June 2023 new and existing TV apps must be published as App Bundles.
- Play Feature Delivery lets a project add feature modules that are included only under conditions you set, or downloaded later on demand. Play Asset Delivery is Google's route for large game assets.
- The page says most projects need little effort to build bundles if code and resources already follow conventions.
The size limit
The total compressed size of the APKs needed to install the app (the base APK plus configuration APKs) must be no more than 4 GB, and any later download such as an on-demand feature module must also fit. Asset packs do not count toward this limit but have their own limits. The page says Play Console gives an error if any possible download exceeds the maximum. App bundles do not support APK expansion (.obb) files. For size problems it suggests enabling all configuration APKs, shrinking unused code and resources, following app size best practices, and moving features used by only some users into on-demand modules, which may need refactoring.
Known issues the page lists
- Partial installs of sideloaded apps (installed outside Google Play and missing required split APKs) fail on all Google-certified devices and on Android 10 (API level 29) or higher. Installs through Google Play include all required components.
- Tools that dynamically modify resource tables can make APKs generated from bundles behave unexpectedly, so the page recommends disabling them when building a bundle.
- A feature module can set build properties that conflict with the base module's (the page's example is a debuggable flag), which can cause build and runtime problems.
Omnistu advice for an app project (not from the source)
- Ask the developer which format they upload to Play and which they hand to testers. If you share APKs for testing outside Play, ask how they are produced, because the page warns about incomplete sideloaded installs.
- Bundles go with Play App Signing, which holds the app signing key; see our article on upload keys and signing keys for who should hold what.
- If the app is large or game-heavy, ask early whether Play Feature Delivery or Play Asset Delivery is planned, since the page says size limits apply.
- Ask for the bundle's release build to be the one tested before launch, not only a debug build.
Limits
One short Android Developers page, read in full on 15 November 2026. We did not read the linked pages on Play Feature Delivery, Play Asset Delivery, app size practices or building bundles, and we tested nothing. The page's video content was not viewed. Android and Google Play only. Requirements and limits change; check the page on the day.
By Omnistu.