Google Play closed testing: the complete guide for new developer accounts

If your personal Play Console account was created after November 13, 2023, you can't publish to production right away. You first run a closed test with at least 12 testers who stay opted in for 14 days in a row. Then you apply for production access and Google decides (Play Console Help).

This guide covers the whole path in order, with a detailed page for each step. Every statement about Google's rule comes from Google's own help pages, checked on November 8, 2026.

Who has to run a closed test

The requirement applies to personal developer accounts created after November 13, 2023 (Play Console Help). Until you meet it, Production (Test and release > Production) and Pre-registration stay disabled. Open testing only unlocks after you get production access.

The rule does not name two groups:

• Personal accounts created before November 13, 2023.
• Organization accounts. Some apps must use one anyway: financial products and services, health apps, apps approved to use VpnService, and government apps (Play Console Help).

Not sure which account you have? See new developer account requirements.

The rule in Google's words

"Developers with personal accounts created after November 13, 2023, must run a closed test for their app with a minimum of 12 testers who have been opted in continuously for at least 14 days."

Three details trip people up:

1. It has to be a closed test. Internal testing does not satisfy it.
2. Opted in, continuously. A tester who opts out and opts back in later needs a new run of 14 consecutive days.
3. It's checked when you apply. Google says at least 12 testers must be opted in "when you apply for production access, and they must have been opted in continuously for the preceding 14 days."

Google lowered the number from 20 to 12 on December 11, 2024 (Android Developers Blog). The details and history are in the 12 testers, 14 days rule explained. How the days are counted is in how the 14 days are counted.

The full path, step by step

1. Set up and verify your developer account

Google Play charges a one-time $25 registration fee (Android Developers). You verify your identity and your contact details. New personal accounts must also prove they have a real Android device: the Play Console mobile app on a non-rooted phone running Android 10 or later (Play Console Help). It takes under a minute.

Details: new developer account requirements.

2. Build an app bundle Play will accept

Since August 31, 2026, new apps and app updates must target Android 16 (API level 36) or higher. Wear OS and Android Automotive OS apps need API 35, Android TV and Android XR apps need API 34 (Play Console Help). Details: target API 36.

Keep your signing key safe. Under Android developer verification, if you lose your signing key you can't register your package names (Android Developers). Details: developer verification in 2026.

3. Create the app and complete app setup

In Play Console, create the app, then work through the setup tasks on its Dashboard. Google lists what it needs to review your app: privacy policy, ads declaration, access instructions for any login, target audience and content, content rating, and data safety (Play Console Help). Closed testing becomes available once app setup is complete.

If your app needs a login, give Google working test credentials now. Without them, Google says it can't review your app and it may be rejected (Play Console Help).

4. Optional: run an internal test first

Internal testing takes up to 100 testers and builds reach them within minutes (Play Console Help). It's handy for a quick sanity check with your own devices.

One warning: "A user who opts into your app's internal test is no longer eligible to receive an open or closed test." Keep your 12 closed testers out of the internal track. The full comparison is in closed vs internal vs open testing.

5. Create the closed test

Go to Test and release > Testing > Closed testing and click Manage track. On the Testers tab, add testers by email list or by Google Group. Then create a release, upload your app bundle and send the changes for review. Every click is in how to set up closed testing.

6. Wait for "Published", then copy the opt-in link

Play Console only shows the opt-in link when the app status is "Published". Not in "Draft", not in "Pending publication". After the first publish, the link can take several hours to work for testers (Play Console Help).

The link looks like https://play.google.com/apps/testing/your.package.name (Play Console Help).

7. Get testers to opt in and install

Testers open the link, read the tester terms, opt in, then install the app from Google Play. If you use a Google Group, testers must join the group before they opt in. The tester side is explained in how testers join a closed test.

No testers yet? How to get 12 testers compares every option, free and paid.

8. Keep at least 12 opted in for 14 days in a row

Recruit more than 12. Anyone who opts out breaks their own streak, and you need 12 unbroken streaks on the day you apply.

Google's own advice for this phase: give testers clear instructions, tell them which feedback you want, provide a feedback channel, and remind them to stay opted in for 14 days. Respond to feedback and fix the bugs they find. Updating the app in closed testing before production is listed as a best practice (Play Console Help).

Testers can also send private feedback through Google Play. You read it in Play Console under Monitor and improve > "Ratings and reviews" > Testing feedback. Keep notes: you'll have to summarize this feedback when you apply.

9. Apply for production access

Once the 14 days are complete, open the Dashboard and click Apply for production. The form has three parts: about your closed test, about your app or game, and about your production readiness. Each question, with example answers, is in how to apply for production access.

10. Wait for Google's answer

"Review usually takes seven days or less, but can occasionally take longer." Google emails the account owner. If you're approved, Production and Open testing unlock. If Google asks for more testing, read production access rejected: what to do.

Timeline at a glance

Add it up and the fastest realistic path is a little over two weeks. Three to four weeks from first closed release to production is a safer plan.

One more timing trap: Google counts the review clock from your last submitted change. Sending new changes while others are in review can push you to the back of the queue (Play Console Help).

What Google looks at when you apply

The application form tells you what matters. Google asks:

• how easy it was to recruit testers;
• whether testers used all the features;
• whether their usage matched how you expect real users to behave, and how it differed;
• a summary of the feedback and how you collected it;
• your target audience and your app's value;
• an estimated "install range" for the first year;
• what you changed because of the test, and how you decided the app was ready.

When Google asks for more testing, it names two reasons: "fewer than 12 opted-in testers or insufficient tester engagement during the testing period" (Play Console Help).

Policy is a separate check. Google warns that its review "is not a troubleshooting step". Check content, target age, stability and test credentials before you apply.

Common problems and their fixes

• Testers see "App not available": closed testing app not available.
• The Play Store says "Item not found": item not found in closed testing.
• The opt-in link fails: closed testing link not working.
• Your tester count is lower than expected: testers not counted.
• "Your device isn't compatible with this version": device not compatible.
• Your track sits "In review": closed testing review time.
• You want to stop a test: remove a closed testing track.

Android developer verification in 2026

This is a different program, and it concerns all developers, not only new accounts. Since September 30, 2026, apps installed from participating stores in Brazil, Indonesia, Singapore and Thailand must come from registered, verified developers. Google plans the global rollout for 2027 (Android Developers). Creating an app in Play Console registers its package name for you. What else to check is in developer verification in 2026.

Checklist

• Personal account created after November 13, 2023? Then the rule applies to you.
• Device verification done in the Play Console mobile app.
• App bundle targets API 36 or higher.
• Dashboard setup tasks complete, including login credentials if needed.
• Closed track has testers (list or Google Group) and a feedback channel.
• Status is "Published" and you copied the opt-in link.
• More than 12 testers opted in, none of them in your internal test.
• Testers know they must stay opted in for 14 days.
• Feedback collected and at least one update shipped from it.
• 14 full days passed, then apply.