Android developer verification for Godot games
From 2027, Android phones will only install apps from registered developers, unless the end user turns on a setting that takes a day to enable. Installing from the Godot editor and from Google Play is not affected. What changes is APKs you share yourself, on itch.io, for game jams or with playtesters.
- Since 30 September 2026: Brazil, Indonesia, Singapore and Thailand, for installs from Google Play and six other big app stores.
- 2027: everywhere, for "all apps on certified Android devices".
Certified devices are phones and tablets with Google Play services, on Android 7 or newer. The check runs when an app is installed or updated. Checked against Google's Android developer verification pages in November 2026.
Testing your own game
Nothing changes. The Android button in the Godot editor installs the game with adb install, and so does running adb install your-game.apk yourself. Google's FAQ says adb installs don't need verification.
Sharing an APK
From 2027, there are three ways end users can install an APK you share outside Google Play.
1. Register as a developer
Sign up for the Android Developer Console, verify your identity and register your game's package name. End users then install your APK as they do today.
- It costs $25. If you have a Google Play developer account, you can register from the Play Console instead.
- You need government photo ID and proof of address. Organisations also need a D-U-N-S number, which can take up to 28 days.
- For each package name you give the SHA-256 fingerprint of your signing key - the key in the release keystore you set in Godot's Android export preset.
If you have already shared APKs with that package name, the console also asks you to prove you have the key, by uploading a signed APK with a file it gives you. Google's console guide explains how.
Google's FAQ says that if you lose your signing key, you can't register the package.
2. Use a limited distribution account
This is free and doesn't need ID - a Google account with 2-step verification and a Google payments profile is enough. You invite devices with a QR code or link, and your APK installs normally on them.
Google's FAQ says up to 20 devices, and its limited distribution page now says 50. It is meant for apps with "no commercial intent", so it fits playtesters and friends rather than a public itch.io page.
3. The end user enables the advanced flow
If the developer isn't registered, the end user can still allow unverified apps with a one-time setup.
- Turn on Developer options (tap Build number 7 times in Settings → About phone).
- In Settings → Developer options → Apps from unverified developers, turn on Allow apps from unverified developers.
- Confirm nobody is guiding you through it.
- Restart the phone.
- After 24 hours, go back to the same setting and confirm with fingerprint, face or PIN.
- Allow it for 7 days or indefinitely.
After that, unverified APKs install after a warning with an Install anyway button.
Games on Google Play
Play registered almost every app automatically, and a developer verified on Play doesn't need to verify again. The Play Console's Android developer verification page shows whether any of your apps still need registering.
With Play App Signing, Google signs the Play version with its own key, and the APK you build is signed with your upload key. Check the upload key is listed for the package before you share the APK.
FAQ
Will games people already installed stop working?
No, the check runs at install and update. But an update to an unregistered app fails unless the end user has enabled the advanced flow, or installs it with adb.
I build with ShipThis. Does anything change?
Builds uploaded to Google Play are covered by Play's automatic registration. APKs from shipthis game build download are signed with your game's keystore, so if you share them outside Play, Sharing an APK applies.