← Back to Guides

Google Play Closed Testing: Complete Step-by-Step Guide

Last updated: November 7, 2026

Google Play closed testing is a required stage for personal developer accounts created on or after November 13, 2023. Before these accounts can publish apps publicly on the Play Store, Google requires them to run a closed testing track with at least 12 opted-in testers for a minimum of 14 continuous days. This guide walks through every stage of the process from setting up your testing track in Google Play Console to submitting your app for production access.

Note: Requirements and policy details may change. Always verify the current requirements in your own Google Play Console dashboard and in Google's official Play Console Help documentation.

Who Must Complete Closed Testing?

Google's closed testing requirement applies to personal developer accounts created on or after November 13, 2023. These accounts must complete a qualifying closed testing track before they are eligible to apply for production access. Organization accounts and personal developer accounts created before November 13, 2023 are not subject to this mandatory closed testing gate.

If you are unsure whether your account is subject to this requirement, sign in to Google Play Console and check whether the production track is available to you. If your account requires closed testing before production access, Google Play Console will indicate this.

Overview of the Closed Testing Requirement

The core requirement has two components:

Both conditions must be met simultaneously — running for 14 days with fewer than 12 opted-in testers does not satisfy the requirement, and having 12 testers for fewer than 14 days does not satisfy it either.

Step 1: Prepare Your App and Store Listing

Before setting up closed testing, your app needs to be in a state that Google can review and testers can install. Prepare the following:

Having a complete and accurate store listing reduces the likelihood of issues during the subsequent production access review.

Step 2: Create a Closed Testing Track

To set up a closed testing track in Google Play Console:

  1. Sign in to Google Play Console and select your app.
  2. In the left navigation, expand Testing and select Closed testing.
  3. Click Create track (or use the default Alpha track if you have not created one yet).
  4. Give the track a name if prompted, or keep the default.
  5. Click Create track to confirm.

After creating the track, you will be taken to the track's management page, where you will upload your app release and manage testers.

Step 3: Upload a Release to the Closed Testing Track

  1. On the closed testing track page, click Create new release.
  2. Upload your signed APK or AAB file.
  3. Add release notes (optional for closed testing, but helpful for testers).
  4. Click Save, then Review release.
  5. Resolve any warnings or errors that appear. Some warnings can be dismissed; errors must be fixed before proceeding.
  6. Click Start rollout to closed testing (or the equivalent button for your track).

Once the rollout is initiated, Google typically reviews the release before making it available to testers. This initial review can take a few hours to a few days. The 14-day testing clock does not start until the release is active and testers can install it.

Step 4: Set Up Your Tester List

Testers must be added to the closed testing track using a Google Group or by uploading a list of email addresses. Each approach has the same result: invited testers receive an opt-in link they must use to join the testing track.

Option A: Create a Google Group

  1. Go to groups.google.com and sign in with your developer Google account.
  2. Click Create group.
  3. Name the group (e.g., "My App Testers") and set the group email address.
  4. Set Group visibility to restrict access as appropriate. Under Who can join the group, select Anyone can ask or Only invited users.
  5. Add your testers' email addresses as group members.
  6. In Google Play Console, navigate to your closed testing track, then to Testers tab, and add the Google Group email address.

Option B: Upload an Email List Directly

  1. In Google Play Console, navigate to your closed testing track and select the Testers tab.
  2. Click Add email addresses.
  3. Upload a CSV file containing one tester email address per line, or type the addresses directly.
  4. Click Save changes.

After adding testers via either method, Google Play Console generates a tester opt-in link. This link is what you share with your testers — they must click the link and opt in through the Google Play Store before they will appear as active testers in your Console.

Step 5: Share the Opt-In Link with Testers

Sending the right link is critical. Find the opt-in link in Google Play Console:

  1. Navigate to your closed testing track's Testers tab.
  2. Locate the Feedback URL or Opt-in URL field. This is the link you share with testers.
  3. Copy the link and send it to all testers via email, messaging, or any other channel.

Each tester must:

A tester who has only received the email invitation but has not completed the opt-in process does not count toward the 12-tester requirement. The tester count in Google Play Console shows only testers who have completed the opt-in.

Step 6: Monitor Opted-In Testers in Google Play Console

After inviting testers, monitor the opted-in count in Google Play Console:

  1. Navigate to your closed testing track.
  2. Select the Testers tab.
  3. Check the number of testers shown as opted in.

You need at least 12 testers showing as opted in. If the count is below 12, invite more people or follow up with testers who have not yet completed the opt-in process. Do not proceed to the next step until you have at least 12 opted-in testers and the testing period has run for 14 days.

Step 7: Maintain the Testing Period for 14 Days

The testing track must remain active for at least 14 continuous days with 12 or more opted-in testers. During this period:

Google Play Console shows whether the closed testing requirement has been met in the production access application section. Once both the 14-day period and the 12-tester count have been fulfilled, the closed testing requirement status should update accordingly.

Step 8: Apply for Production Access

Once the closed testing requirements are met, you can apply for production access through Google Play Console:

  1. In Google Play Console, navigate to Production (under the Testing section or the main release section).
  2. If your account is eligible to apply for production access, you will see an option to Apply for production access or a prompt to submit your app for a production review.
  3. Follow the prompts to submit your app. Google may ask you to review and confirm your store listing, content rating, and other settings.
  4. Submit the application.

After submission, Google's team reviews the app. This review can take anywhere from a few days to several weeks. During this time, do not make significant changes to the app or store listing unless Google requests them.

What Google Evaluates During the Production Access Review

Completing closed testing makes you eligible to apply for production access, but Google evaluates several additional factors before approving it:

See our guide on common reasons Google Play may review or not immediately approve a production access application for more detail on this.

How SAMFA Digital Helps With Closed Testing

Sourcing 12 real, cooperative testers who will complete the opt-in process and remain active for 14 days is one of the most common challenges developers face. SAMFA Digital provides cohorts of real human testers for Google Play closed testing:

The process is straightforward: select your package on the website and reach out via WhatsApp. The SAMFA Digital team will guide you through setting up the testing track correctly so the opt-in link works and testers can join without issues.

Important: SAMFA Digital provides testers to help you meet the closed testing requirements. The service does not and cannot guarantee that Google will approve your production access application. That decision is made by Google based on a review of your app and account.

View available packages and pricing →

Frequently Asked Questions

Does the 14-day clock start from when I create the testing track?

No. The clock starts from when the testing track is active and testers can install the app — not from when you first create the track. The release must pass Google's initial review and be available on the closed testing track before the qualifying period begins.

What happens if a tester opts out before the 14 days are over?

If the opted-in tester count drops below 12 before the 14-day period ends, the requirement may not be considered met. This is why it is recommended to invite more than 12 testers — having 15 to 20 testers provides a buffer so that a few opt-outs do not disqualify the testing period.

Can I use my own friends and family as testers?

Yes, testers can be anyone with a Google account. However, they must each individually complete the opt-in process from the shared link on an Android device — the opt-in cannot be done on their behalf. If you do not know enough people willing to participate, SAMFA Digital provides a tester cohort as a service.

Does organization (business) accounts need to do closed testing?

Based on Google's current policy, the mandatory closed testing requirement applies specifically to personal developer accounts created on or after November 13, 2023. Organization accounts are not subject to this requirement. Always verify your specific account requirements in your own Google Play Console.

Can I upload app updates during the 14-day closed testing period?

Uploading a new release to the closed testing track during the testing period is generally possible, but check your Play Console dashboard for the effect on your testing progress. Google Play Console indicates whether the closed testing requirement has been met.

How long does Google's production access review take?

Google does not publish a fixed timeline for production access reviews. Reviews can take anywhere from a few days to several weeks. The timeline varies and cannot be predicted. Plan accordingly and do not make significant changes to the app or listing while the review is in progress.

Related Resources

Need testers for closed testing? Chat on WhatsApp →