APK vs AAB: Which Should You Upload to Google Play?

The Short Answer

For a new app on Google Play, use an AAB (Android App Bundle). Google Play requires app bundles for new apps; legacy apps created before August 2021 can still use APKs for updates. For direct installation outside Play, use an APK or an appropriate APK set rather than an AAB.

What Each File Actually Is

An APK (Android Package) is an installable Android package containing compiled code and resources. It may be a universal package or target a particular device configuration. Some apps use a base APK together with configuration-specific split APKs, which must be installed as a compatible set.

An AAB (Android App Bundle) is a publishing format, not a file you install directly. Google Play uses it to generate APKs for supported device configurations. This lets Play select the code and resources a device needs without the developer preparing each distribution variant by hand.

When Google Requires Which

• New app through Play Console: Use an AAB and complete Play App Signing and the other release requirements.
• Updating a legacy app created before August 2021: Google Play allows an app bundle or APK. A specific Play App Signing key-upgrade path may require both an AAB and a legacy APK; that is not a blanket rule for every legacy update.
• Private apps in managed Google Play: Publishing from Play Console requires an AAB. The Managed Play iframe supports APK publishing through that separate route.
• Distributing outside Google Play — a signed APK or suitable APK set can be used for direct installation. Check the destination store, device security and applicable distribution requirements; choosing APK alone does not establish eligibility everywhere.

Why AAB Is Not Just Google Being Difficult

An app bundle lets Play generate installable APKs from the code and resources you upload. Split delivery can select resources for supported device configurations, instead of sending every configuration in a universal APK. Measure the actual download size for your app rather than relying on a fixed percentage saving.

Building Both with Free App Maker

For an eligible website-based app, the separately priced Play Store Pack provides the AAB file, signing material, store graphics and form guidance. You upload the files from your own Play Console; Google decides whether the app is approved.

Free App Maker builds a signed APK after email verification. The free preview shows the app name and icon only; downloading and testing the APK requires a one-time unlock, with the price shown before checkout. The signed AAB is part of the separate Play Store Pack for eligible apps. See our step-by-step conversion guide for the builder flow.

How This Shows Up in Play Console

In Play Console, create a release in the appropriate testing or production track and follow its upload instructions. Use an AAB for a new app; legacy apps created before August 2021 can upload an APK or bundle. AAB publishing and Play App Signing also affect the keys and generated APKs used for distribution. Outside Play, an APK or APK set must be suitable for the target device and installation requirements.

Frequently Asked Questions

Can I test an AAB file directly on my phone?
Not the way you would an APK. An AAB is not installable on its own — you either upload it to Play Console and use internal testing, or use a tool like bundletool to generate an installable APK set from it locally. For quick device testing during development, an APK is simpler.

Does an AAB make my app less secure?
The file format alone does not establish app security. Android requires signed APKs; with Play App Signing, Google signs the APKs it distributes. You still need secure code, dependencies, data handling and protection of your signing credentials.

My app predates AAB. Do I have to switch?
Not solely because you are updating a legacy app created before August 2021. Google Play's release guidance allows app bundles or APKs for those updates. Check any app-specific Play Console requirements and signing changes before releasing.

Is there a downside to AAB?
An AAB is a publishing input, so you need Play or a tool such as bundletool to generate installable APKs. Test the resulting APKs for the devices and distribution route you support; the AAB cannot simply be installed as a file on a phone.

Do I need different signing keys for APK and AAB?
Not because of the file format alone. With Play App Signing, an upload key signs what you send to Play, while the app signing key signs APKs delivered to users. Directly distributed updates need a compatible signing identity. Do not assume an upload key can update a Play-installed app.

Where do I choose the format when publishing?
Create a release in the appropriate Play Console track and follow its upload instructions. New apps use AAB; legacy apps created before August 2021 can use APK or AAB. See our Google Play publishing guide for the broader submission process.

Technical sources checked 2 November 2026: Android App Bundle format, Play release requirements, App Bundle FAQ and app signing and upload keys. Check current Play Console requirements for your own app.

Conclusion

For a new Google Play app, prepare an AAB and complete the account, signing, listing and policy requirements. Keep an APK for direct Android testing or other supported distribution routes. Free App Maker's build is free after email verification, APK downloads need a one-time unlock, and eligible Play Store files are sold separately in the Pack.