Closed testing for games on Google Play: a guide for Unity, Unreal and Godot
Updated November 2026
Games go through the same closed testing requirement as any other app: if your personal developer account was created after 13 November 2023, you need at least 12 testers opted in for 14 days in a row before you can apply for production. Games have their own pitfalls, though: big downloads, devices that can't run the build, and testers who open the game once and never come back. This guide covers what game developers should set up and what to ask testers to do.
The same rule, with game-specific risks
Google treats games and apps alike here. Run a closed test with at least 12 testers who stay opted in continuously for 14 days, then apply for production. The production form asks about tester engagement, feedback and what you changed, so a test where nobody played past the tutorial makes for weak answers.
The risks that hit games more than other apps:
- Device compatibility: testers see "your device isn't compatible" and can't install.
- Download size: a large first download on mobile data puts testers off.
- Session length: people won't play a 20-minute level every day for two weeks.
- Content gaps: a vertical slice with one level runs out of things to do by day three.
Build settings to check first
- Unity: build an Android App Bundle (.aab), use IL2CPP with ARM64 enabled (Google Play requires 64-bit support), and set a minimum API level that doesn't exclude more phones than you need to. If your build is large, use Play Asset Delivery rather than one huge download.
- Unreal Engine: package for Android as an App Bundle with arm64, check the target and minimum SDK levels in Project Settings, and keep the first download small by moving optional content into asset packs.
- Godot: use the Android export template with Gradle build enabled and export as AAB. Make sure arm64-v8a is included, and test the renderer on a low-end phone, because some devices handle the Compatibility renderer better than Forward+ or Mobile.
- All engines: target the API level Google Play currently requires for new apps, and sign with Play App Signing.
After uploading, open the Device catalog in Play Console to see how many devices your build supports. If a big share is excluded, fix it before testers arrive.
Set up the test
- Create or open the closed track: Test and release, then Testing, then Closed testing.
- Add countries where your testers live.
- Add testers with an email list or a Google Group. With Tester Exchange, add testerexchange-testers@googlegroups.com.
- Upload the .aab, send the release for review and wait until it shows Published.
- Share the opt-in link. The first time, it can take several hours to start working.
If testers report "app not available", see the guide on fixing that. It covers wrong accounts, countries and unpublished tracks.
What to ask testers to play
Give testers small daily goals that fit into a couple of minutes. Real, varied play is what helps you, and it's what you'll describe later in the production form.
- Days 1 to 3: finish the tutorial and the first level. Report anything confusing.
- Days 4 to 7: play one short session a day; try settings, sound, controls and pausing.
- Days 8 to 11: try a new build with fixes; replay a level to see if it feels better.
- Days 12 to 14: play the hardest content available and report crashes, lag or battery drain.
If your game has daily rewards, a short daily challenge or a quick mode, point testers at it. It fits the daily rhythm naturally.
Show engagement
- Ship at least one update during the test, ideally two. Fixing a reported crash is the best story for the production form.
- Use Android vitals and the pre-launch report in Play Console to find crashes and ANRs on real devices.
- Collect written feedback in a simple form: device model, what they did, what happened.
- Keep a log of daily active testers, sessions, bugs found and builds shipped.
Multiplayer and online games
If your game needs a server, keep it running for all 14 days, and make sure the game is still playable when testers are alone. A lobby that never fills looks like an empty test. Add bots or a solo mode for the test period if you can.
If you need sign-in, give testers a working guest mode or clear instructions. Sign-in walls lose testers on day one.
Getting enough players
Ask for 15 testers rather than 12, because some players drop out of games quickly. Tester Exchange sends real people who play on their own Android phones and shows daily use for each tester: $12.99 for 12, $14.99 for 15 or $22.99 for 25, paid once. You can also earn testers free by testing other developers' apps and games at https://testerexchange.com/earn.
Frequently asked questions
Do games need closed testing too?
Yes. The requirement applies to all apps from personal accounts created after 13 November 2023, including games.
Can my game still be unfinished during closed testing?
Yes, a closed test is for a work in progress. But testers need enough content to play for two weeks, and you should keep improving it during the test.
Why can't some testers install my game?
Usually device compatibility: a high minimum Android version, missing 64-bit support, or required hardware features. Check the Device catalog in Play Console.
How long should testers play each day?
Google doesn't set a number. A short real session every day is better than one long session and then nothing.
Should I use Play Asset Delivery for the test?
If your game is large, yes. Smaller first downloads mean more testers actually install and start playing.