How to Convert an APK to an Android App Bundle (AAB) – 2025 Guide

📦 Introduction

Since 2021, Google Play has required all new apps to be published in the AAB (Android App Bundle) format instead of APK.
But thousands of developers and testers still use APKs — for sideloading, debugging, or distribution outside the Play Store.

If you’ve got an APK file and want to convert it into an AAB (for uploading to Play Console or sharing as a modern bundle), this guide walks you through the safe, AdSense-compliant way to do it — without shady converters or illegal tools.

🧠 APK vs AAB: What’s the Difference?

Feature APK (Android Package) AAB (Android App Bundle)
Purpose Final app installation file Publishing format for Play Store
Structure Single package (includes all device assets) Modular: splits assets per device type
Size Larger (includes all configs) Smaller per-user install size
Play Store Support Deprecated (upload not allowed for new apps) Required for new uploads
Signing Developer-signed Signed by Google Play (Play App Signing)

In short:

  • APK = installable app file
  • AAB = smarter packaging system used by Play Store

🧰 What You’ll Need

Before starting the conversion, make sure you have:

  • A Windows / macOS / Linux PC
  • Java JDK 11+ installed
  • Android Studio (latest version)
  • The original APK file
  • Optionally: key.keystore (your signing key if you plan to re-sign the AAB)

⚙️ Method 1: Convert APK to AAB Using Android Studio

Step 1. Create a New Project

  1. Open Android Studio → File → New Project.
  2. Choose “No Activity” template and set the same package name as your APK (important for signing consistency).

Step 2. Import the APK Assets

  1. Open your project folder.
  2. Extract your APK (use 7-Zip or WinRAR).
  3. Copy the classes.dex, lib/, res/, and AndroidManifest.xml files into the new project’s app/src/main/ directory.

⚠️ Note: APK → AAB conversion isn’t a “true reverse build” — it’s about repackaging an existing app with bundle metadata.

Step 3. Sync Gradle & Dependencies

Update your build.gradle file to include:

android {
    compileSdkVersion 34
    defaultConfig {
        applicationId "your.package.name"
        minSdkVersion 21
        targetSdkVersion 34
        versionCode 1
        versionName "1.0"
    }
    buildTypes {
        release {
            minifyEnabled false
            debuggable false
        }
    }
    bundle {
        storeArchive {
            enable true
        }
    }
}

Step 4. Build the AAB File

  1. Go to Build → Build Bundle(s) / APK(s) → Build Bundle(s)
  2. Wait for Gradle to finish.
  3. Your new .aab file will appear under:
    app/build/outputs/bundle/release/app-release.aab

🧰 Method 2: Convert APK to AAB Using Command Line

If you prefer a direct approach, you can use bundletool, the same official tool Google uses.

Step 1. Download Bundletool

Step 2. Run the Conversion Command

java -jar bundletool-all.jar build-bundle \
--modules=base.zip \
--output=app-release.aab

Note: You’ll need to manually re-package your APK’s contents into a base.zip before running the command.

Step 3. Sign the AAB (Optional)

If you need to upload to Play Store:

jarsigner -keystore my-release-key.jks app-release.aab alias_name

🔐 Signing & Verification

Google Play requires all AABs to be digitally signed.
If you don’t sign it yourself, Play Console will use Play App Signing to manage your keys securely.

You can verify your bundle’s signature with:

jarsigner -verify app-release.aab

📉 Why Developers Are Switching to AAB

✅ Smaller app size (20–40% less than APKs)
✅ Dynamic delivery — only downloads assets needed for your device
✅ Better security (Google-managed signing keys)
✅ Faster updates and modular downloads

However, for testing, sideloading, or offline installs, APKs remain useful — which is why conversion between the two formats is still popular in 2025.

⚠️ Important Notes (AdSense Safe Practices)

  • ❌ Don’t promote illegal or modified APK conversions.
  • ✅ Only use official tools like Android Studio or Bundletool.
  • ✅ Never host copyrighted apps or modified builds.
  • ✅ Educate users — do not distribute converted apps unless you own or have permission to do so.

This keeps your content fully AdSense-compliant and developer-friendly.

🏁 Final Thoughts

Converting an APK to an AAB isn’t always one-click simple, but using Android Studio or Bundletool, you can safely re-package and modernize your apps for 2025’s publishing standards.

As Google continues to refine Play App Signing and dynamic delivery, understanding the APK ↔ AAB relationship will help developers stay compatible, secure, and efficient.