Key Takeaways
- APK is the traditional Android package format, simple, universal, and easy to distribute.
- AAB is Google's newer format that generates optimized APKs per device, resulting in 15% smaller downloads.
- Google Play requires AAB for all new apps since August 2021.
- Use APK for testing, direct distribution, and third-party stores. Use AAB for Google Play.
What Is an APK File?
APK stands for Android Package Kit. It is the traditional file format used to distribute and install applications on Android devices. Think of an APK as a ZIP file that contains everything needed to run an app: compiled code, resources, manifest, and assets.
When you download an app from outside the Google Play Store, from a website, an email link, or a third-party marketplace, you are almost always downloading an APK file. You tap it, Android asks for permission, and the app installs.
APKs have been the standard since Android launched in 2008. They are simple, universal, and understood by every Android device ever made. If compatibility is your top priority, APK is the safe choice.
What Is an AAB File?
AAB stands for Android App Bundle. Google introduced it in 2018 as a newer, smarter way to package Android apps. Instead of shipping one giant file that contains every possible resource for every device, an AAB lets Google Play generate optimized APKs tailored to each user's specific device.
Here is the key difference: an APK is a finished product ready to install. An AAB is a bundle of ingredients that Google Play uses to cook the perfect APK for each download. The user never sees the AAB, they get a smaller, optimized APK automatically.
APK vs AAB: Key Differences
APK
- Direct installation, tap to install
- Works with sideloading
- Larger file size, all resources included
- One size fits all devices
- Easy third-party distribution
- Simple build process
- Universal compatibility
AAB
- Cannot install directly, needs Play Store
- Smaller downloads per device, 15% avg reduction
- Auto-optimized per device and locale
- Required for new Play Store apps
- Enables Dynamic Delivery
- Slightly more complex build process
- Access to advanced Play Store features
Why Google Prefers AAB
Google's push toward AAB is not just about control. There are genuine benefits for developers and users.
Smaller Downloads
Google generates an APK containing only the resources needed for each device. If your app supports 20 languages but the user only needs English, the other 19 are excluded. Average reduction: 15%, up to 30% for large apps.
Better Device Compatibility
AAB delivers only the native libraries and density-specific images matching the user's hardware. Faster downloads, less storage used, and sometimes better performance.
Dynamic Delivery
AAB enables on-demand feature modules. If your app has a large feature most users never touch, Google can defer that download until the user actually opens that feature.
When to Use APK
Despite Google's preference for AAB, there are several scenarios where APK remains the right choice:
- Internal Testing and Distribution - Distribute to your team, beta testers, or a small group without going through Play Store review. Build the APK, share it via email or Slack, and recipients install it directly.
- Third-Party App Stores - Amazon Appstore, Samsung Galaxy Store, F-Droid, and others still primarily use APK files. If you plan to distribute through these channels, you need an APK.
- Enterprise Deployment - Companies deploying apps to employee devices through MDM solutions typically use APK files. This allows pushing updates without any app store.
- Legacy Device Support - Older Android devices (pre-5.0) may not support AAB-derived APKs properly. A universal APK ensures maximum compatibility.
When to Use AAB
If you are publishing a new app on the Google Play Store, AAB is now mandatory. But beyond the requirement, there are good reasons to prefer it:
- New Google Play Submissions - Since August 2021, Google requires AAB for all new app submissions. This is non-negotiable.
- Optimized User Experience - AAB-based apps give users smaller downloads and better-optimized installs. Matters especially for users with limited storage or slow internet.
- Access to Advanced Features - Play Store features like App Bundles and Dynamic Delivery only work with AAB.
How to Generate Each Format
Generate an APK
Open your project in Android Studio. Go to Build, then Build Bundle(s) / APK(s), then Build APK(s). Wait for the build to complete. Find the APK in app/build/outputs/apk/. For signed APKs, go to Build, then Generate Signed Bundle / APK.
Generate an AAB
Open your project in Android Studio. Go to Build, then Build Bundle(s) / APK(s), then Build Bundle(s). Or use the command line: ./gradlew bundleRelease. Find the AAB in app/build/outputs/bundle/release/.
Using a Converter
If you use WebToAppify, the format is handled for you. The converter generates an APK by default and can produce AAB for Play Store submission. No Android Studio needed.
Testing AAB Locally
You cannot install an AAB directly on a device. To test locally, use the bundletool command-line tool: bundletool build-apks --bundle=app.aab --output=app.apks. This converts your AAB into installable APKs for testing.
Quick Decision Guide
- Publishing to Google Play? Use AAB (required for new apps)
- Distributing outside app stores? Use APK
- Internal testing or beta? Use APK for simplicity
- Enterprise deployment? Use APK
- Third-party stores? Use APK
- Need smallest download size? Use AAB through Play Store
- Converting a website to an app? Most tools generate APK by default; some also support AAB
Ready to Convert Your Website?
WebToAppify generates a ready-to-publish Android app from your website. No coding required. APK and Play Store ready.
Convert FreeFrequently Asked Questions
Can I upload an APK to Google Play instead of AAB?
For new apps submitted after August 2021, no. Google requires AAB. Existing apps can still update with APK. If you have an existing APK-based app on the Play Store, you can continue using APK for updates.
Does AAB work with third-party app stores?
No, most third-party stores like Amazon Appstore, Samsung Galaxy Store, and F-Droid still use APK files. If you plan to distribute through these channels, you will need to build a separate APK in addition to your AAB for Google Play.
How much smaller are AAB-generated APKs?
Google reports an average 15% reduction in download size compared to universal APKs. For large apps with many resources like multiple languages and screen densities, savings can reach 30% or more. The exact savings depend on your app's resource diversity.
Can I convert an existing APK to AAB?
You cannot directly convert an APK to AAB. You need to rebuild from your source code using Android Studio's bundle build process. If you are using a conversion service, most can regenerate your app as AAB from the same website URL.