Godot guide · · 6 min read
Godot 4.5 export to Android AAB: SDK, keystore and Play fixes
Export a signed AAB from Godot 4.5.1: tool versions from the docs, keystore commands with placeholders, the target API Google Play needs and four real errors.

What do you need installed to export a Godot 4.5 game to Android?
You need a JDK, the Android SDK with a few packages, and the Godot export templates. As of November 2026 the Godot 4.5 docs list these versions, and the first two are the ones that cause most failed first exports.
After installing, open Editor Settings, section Export > Android, and set the Java SDK path and the Android SDK path. The SDK path must contain platform-tools/adb. On macOS the default SDK location is ~/Library/Android/sdk.
The Gradle build that makes an AAB comes from the template inside Godot, so you do not install Gradle yourself. In Godot 4.5.1 that template uses Gradle 8.11.1 with Android Gradle Plugin 8.6.1, minSdk 24, compile and target SDK 35. I read those from the config.gradle file of the 4.5.1 source, not from the docs, because the docs do not give a Gradle version.
- OpenJDK 17 (the docs say newer versions also work).
- Android SDK Platform-Tools 35.0.0 or later.
- Android SDK Build-Tools 35.0.0 and Platform API 35.
- Android SDK Command-line Tools, latest.
- CMake 3.10.2.4988404 and NDK r28b (28.1.13356709) are in the same list.
How do you export an AAB from Godot 4.5?
Install the export templates (Editor > Manage Export Templates), then in your project choose Project > Install Android Build Template. Open Project > Export, add an Android preset, and turn on Use Gradle Build. Set Export Format to AAB, keep only the architectures you ship (arm64-v8a is the 64-bit ARM one), and put your release keystore in the Release fields. Untick Export With Debug when you export.
I did exactly that on a Mac with Godot 4.5.1, Corretto 17 and SDK platform 35, using an empty project and a key made for the test that was deleted afterwards. It produced a 25.5 MB bundle in 43 seconds, then 14 seconds on the second run, with the Gradle download already cached. On a machine that has never built, expect Gradle and its libraries to download first. My SDK folder had no CMake and no NDK, and the Gradle export worked anyway, so treat those two as needed for compiling Godot or plugins, not for this export.
The same export from a terminal is below. Keep the three variables out of the repo and out of your shell history on shared machines.
# Release AAB from the command line, Godot 4.5.1. Nothing secret is in the project.
export GODOT_ANDROID_KEYSTORE_RELEASE_PATH="/path/to/your-upload.keystore"
export GODOT_ANDROID_KEYSTORE_RELEASE_USER="<your key alias>"
export GODOT_ANDROID_KEYSTORE_RELEASE_PASSWORD="<your password>"
godot --headless --path . --export-release "Android" build/mygame.aab
How do you make an Android keystore, and which key do you upload with?
Make one keystore with keytool, which ships with the JDK, and use it as your upload key. Godot uses the same password for the keystore and the key, and its docs warn that special characters in it can cause errors, so pick a long one made of letters and digits. Do not commit the file or the password. Back the file up somewhere that is not the project folder.
With Play App Signing, which new apps use, you sign the bundle with the upload key and Google signs what players download with a second key it holds. If you lose the upload key you can ask Play for a reset. If you instead manage a signing key yourself and lose it, there is no reset, so let Google generate it unless you need the same key on other stores.
One consequence: services that check your app's signature, such as sign-in or ad SDK settings that ask for a fingerprint, need the fingerprint of the Play app signing key from Play Console, not the one from your upload keystore.
# One time. Pick your own alias and password when it asks. Back the file up outside the repo.
keytool -v -genkey -keystore your-upload.keystore -alias <your key alias> -keyalg RSA -keysize 2048 -validity 10000
# Check what is inside, and read the SHA-256 fingerprint:
keytool -list -v -keystore your-upload.keystore -alias <your key alias>
# Check which key signed a bundle you built:
keytool -printcert -jarfile build/mygame.aab
Which target API level does Google Play ask for now?
Google's page says that from August 31, 2026, new apps and app updates must target Android 16, API level 36. Wear OS and Android Automotive have lower bars. The page offered an extension to November 1, 2026, which has passed as I write this.
Godot 4.5.1 targets API 35 by default. I checked the Gradle config in the 4.5.1 and 4.6.3 sources: 4.6.3 defaults to 36. On 4.5.1 you can type 36 into Target Sdk in the export preset. I built an APK both ways and read the manifest with aapt2 dump badging: 35 by default, 36 after the change. Godot says in the editor that a target above its default is untested, so run the game on a real phone before you upload. The Android target API article tracks the other store rules.

Why does the Android export fail with an empty error?
Four failures are worth knowing, all reproduced with Godot 4.5.1. The first is the nastiest. A headless export printed Cannot export project with preset "Android" due to configuration errors: and then nothing. The cause was Project Settings > Rendering > Textures > VRAM Compression > Import ETC2 ASTC, which was off. Android needs it, and the message that should name it did not appear.
The second is a missing build template: the message tells you to install it from the Project menu. The third is a release export with no keystore, and the fourth is a wrong password, where Gradle fails at the signing task and says the keystore password was incorrect. Read the last lines of the Gradle output, not the first.
Related reading: how we fixed ITMS-91064 on iOS is the same kind of store problem, and the web export guide covers the other target most Godot games ship to.

What was not tested, and when is the AAB not needed?
Not tested here: uploading to Play Console, installing the bundle on a phone (it needs bundletool, which I did not use), a real production key, and Windows or Linux. The export above is a plain empty project with no plugins such as ads, which add their own Gradle dependencies.
You also do not need an AAB while developing. A debug APK from the one-click deploy button is faster, and works with the standard export templates without the Gradle build. Turn on Use Gradle Build when you need an AAB, a custom manifest or an Android plugin. The Godot docs say uploads to Google Play must be signed with a non-debug keystore, so sign the release build with your own key.
When you do upload, expect the store forms next: the closed test rule for new personal accounts and the Data safety form for games with ads.
Questions people ask
- Do I need Android Studio to export from Godot?
- No. The Godot docs say you can install the SDK packages through Android Studio or with the sdkmanager command line tool. Godot only needs the JDK and SDK folders set in Editor Settings.
- Does Google Play still accept APK files?
- Godot's docs say that new apps uploaded after August 2021 must be AAB files. Use an APK only for your own testing or for other stores.
- What happens if I lose my keystore?
- If you use Play App Signing and the lost file was only the upload key, you can request an upload key reset in Play Console. Without Play App Signing, losing the signing key means you can no longer update that app.