Quick Answer
To add testers on Google Play Console, go to Play Console → your app → Testing → Closed testing → Testers. Choose Email list and upload a CSV file with one email address per row (no header), or choose Google Groups and enter your group's email address. Each tester receives an opt-in link — they must accept before the app appears in their Play Store under Testing. For new personal accounts, you need a minimum of 12 testers.
Before you add testers, confirm three things in Google Play Console:
- Your app is uploaded to the Closed testing track (not just saved as a draft)
- You have the Release Lead or Admin role on the app
- Your Google Play Developer account is properly set up with a accepted Developer Distribution Agreement
What "Closed Testing" Means
Closed testing on Google Play means your app is only visible to people you explicitly invite. It will not appear in public Play Store search results. Only opted-in testers can see and install it from their Play Store app under Testing → Closed testing.
Two Ways to Add Testers on Google Play Console
Google Play Console gives you two methods to add testers. Both work — the right choice depends on your situation:
| Feature | Email List (CSV) | Google Groups |
|---|---|---|
| Best for | Individual tester invites | Teams, agencies, large tester pools |
| Add testers | Upload new CSV each time | Add members to Google Group directly |
| Remove testers | Upload CSV without removed emails | Remove from Google Group directly |
| Opt-in required | Yes — each tester accepts invite | Yes — each group member accepts |
| 12-tester minimum | Counts individual opted-in emails | Counts individual opted-in members |
Method 1: Add Testers via CSV Email List
CSV is the most common method. It's simple, repeatable, and works for any number of testers.
Step 1: Create Your CSV File
Open any text editor (Notepad, TextEdit, Google Sheets) and list one email address per row. No header row, no commas, no formatting — just clean email addresses:
CSV Format Rules
Do not include a header row (no "Email" or "Tester" label in the first row). Do not use commas between addresses. Do not use Excel's .xlsx format — Google Play only accepts plain .csv. UTF-8 encoding works. Gmail, Outlook, Yahoo, and corporate email addresses are all fine.
Step 2: Upload the CSV in Play Console
- Open Google Play Console and select your app
- Navigate to Testing → Closed testing
- Click the Testers tab
- Select the Email list option
- Click Upload CSV and select your file
- Click Save changes
Step 3: Copy the Opt-In Link
After saving, Play Console generates a unique opt-in URL for your closed testing track. Copy this link — you'll share it with your testers:
Step 4: Share the Opt-In Link with Testers
Each tester must visit the opt-in link and accept the invitation. Without accepting, the app will not appear in their Play Store under Testing. The opt-in link can be shared via email, WhatsApp, Slack — anywhere.
What Testers See
After clicking the opt-in link, testers see a Play Store page that says "You're now a tester for [App Name]". They tap Become a tester, and the app then appears in their Play Store under Testing → Closed testing. The app has a small " tester " badge next to its name.
Method 2: Add Testers via Google Groups
If you manage a team or want to add/remove testers without re-uploading CSVs, Google Groups is the faster method.
Step 1: Create a Google Group (if you don't have one)
- Go to groups.google.com and sign in with a Google account
- Click Create group
- Set Group type to Email list
- Set Who can join to Invited members only
- Add your testers' email addresses as members
Step 2: Connect the Group in Play Console
- In Play Console, go to Testing → Closed testing → Testers
- Select the Google Groups option
- Enter your group's email address (e.g.,
mytesters@googlegroups.com) - Click Save changes
Each Group Member Must Still Opt In
Adding someone to a Google Group does not automatically make them a Play Console tester. Each individual member must still visit the opt-in URL and accept the testing invitation. This is a common mistake — developers add people to the group and assume they're automatically counted.
Google Groups Advantage: Dynamic Roster
The key benefit of Google Groups is that you can add or remove members from the group at any time without re-uploading a CSV in Play Console. As members accept the opt-in link, they automatically become active testers. When you remove a member from the group, they lose access.
How to Verify Your Testers Are Active
After your testers accept their invites, confirm their status in Play Console:
- Go to Testing → Closed testing → Testers
- Look at the Testers section — it shows the total number of opted-in testers
- Click View tester details to see the full list of who accepted
"For new personal developer accounts, Google requires at least 12 opted-in testers who actively use the app through the 14-day closed testing window. A tester who accepts the invite but never opens the app may not count as sufficiently active."
— 12Testers14Days, based on Google Play Console policy documentation
What Counts as an "Active" Tester?
Google tracks the following signals from closed testing testers:
- Daily active sessions — how often the app is opened
- App crashes and ANRs — stability metrics visible in Play Console Vitals
- Play Integrity API responses — especially relevant for TWA/PWA apps using Bubblewrap
- Testing feedback forms — testers can submit structured feedback in the Play Store testing page
Key Takeaways
- Upload a plain
.csvfile with one email address per row, no header, no commas. - Testers must individually click the opt-in URL and accept before the app appears in their Play Store.
- Google Groups lets you manage a dynamic tester roster without re-uploading CSVs.
- Each group member must still opt in individually — group membership alone does not grant tester access.
- At least 12 testers must be opted-in and active for the full 14 days on new personal developer accounts.
- You can add more testers at any time during the 14-day window — the clock resets only from day one of the first tester joining.
Related Guides
Frequently Asked Questions
Go to Google Play Console > your app > Testing > Closed testing > Testers. Choose Email list to upload a CSV file with one email address per row (no header), or choose Google Groups to add an existing group. Each tester receives an opt-in link and must accept before they can install the app from the Play Store testing track.
For new personal Google Play Developer accounts created after November 13, 2023, you need a minimum of 12 testers. The testers must be real people on physical devices who actively use the app throughout a 14-day continuous window.
Yes. In Play Console > Testing > Closed testing > Testers, select Google Groups and enter your group's email address (e.g., mytesters@googlegroups.com). All members of the group automatically become testers when they accept the opt-in link.
Yes. After you add tester emails or groups, each tester receives an email with an opt-in link to the testing track. Testers must click the link and accept the invitation before the app appears in their Play Store under Testing.
If a tester removes themselves or declines the invitation, they no longer count toward your 12-tester minimum. If your active tester count drops below 12 during the 14-day window, Google may reject your production access application.
Yes, you can add new testers at any time during the 14-day testing window. New testers will receive their own opt-in links and can start testing immediately. However, the 14-day window still needs to complete with at least 12 active testers before production access is granted.
Last updated: August 13, 2026 — Fact-checked against Google Play Console UI and documentation