Google doesn't charge anything for closed testing itself. The only fixed cost of publishing is the one-time developer registration fee; the 12 testers can cost you nothing if you recruit them yourself. The real cost is time and effort: finding at least 12 people, getting them opted in, and keeping them engaged for 14 continuous days. Paying a testing service is one option, but it's not required.
What Google charges
- Developer account: "a US$25 one-time registration fee" (Get started with Play Console).
- Closed testing: no fee. Creating a track, adding testers and running the test are part of Play Console.
- Pre-launch report: free automated testing generated when you upload a bundle.
The requirement itself applies to personal developer accounts created after November 13, 2023: run a closed test with at least 12 testers opted in continuously for at least 14 days. If you're not sure whether it applies to you, see personal vs organization accounts.
Option 1: People you know (free)
Google's own advice is to "reach out to friends, family, colleagues, or classmates." For many developers, this is the cheapest and fastest route.
What it costs: your time, and some goodwill.
What helps:
- Ask people who already use Android. A tester needs a Google account and an Android device that can install your app.
- Collect the exact Gmail address each person uses on their phone. Wrong accounts are a common reason testers don't count.
- Explain the commitment up front: opt in, install, keep it for at least 14 days, use it now and then.
- Recruit more than 12. Someone always forgets or switches phones.
Downsides: friends may be polite rather than honest in feedback, and keeping a dozen busy people engaged for two weeks takes reminders.
Option 2: Communities (free)
Google also suggests you "connect with communities where potential users exist" and "post about your app on social media." That includes interest groups related to your app's topic, developer forums, and tester-exchange groups where developers test each other's apps.
What it costs: time, and often your time testing other people's apps in return.
Upsides: community testers can be closer to your real audience, which Google values: it recommends testers who "represent your app's intended future audience."
Downsides:
- Exchange groups depend on reciprocity. If people drop out after a few days, they don't count, and you may not notice in time.
- Coordination is on you: tracking who opted in, when, and with which account.
- Quality varies. Some people opt in and never open the app, which doesn't help with engagement.
Option 3: Your own users or waitlist (free)
If you already have a website, a newsletter, or users of a previous app, invite them. These are often the most useful testers you can get, because they actually want what you're building.
Downsides: most first-time developers don't have an audience yet.
Option 4: A paid testing service
Several companies, GoPlayTester among them, provide testers for a fee. Google's official documentation doesn't mention paid testing services at all. A Product Expert's community guide says reaching out to third-party testing companies "does not violate the policy", but that's a community view, not official Google policy.
What it costs: a fee that varies by provider, plus your time to set up the track and keep improving the app.
What you're paying for: mainly convenience and reliability. Recruiting, reminding and replacing testers becomes someone else's job.
What you're not paying for: approval, a shorter test, or reviews. Google makes the production access decision and may still ask for more testing, nobody can make the 14 days shorter, and testers can't leave public reviews on test versions. Before you pay, check that the testers are real people on real Android devices who stay opted in for the full 14 days, and be wary of anyone promising guaranteed approval or offering bots, emulators or fake accounts.
Comparing the options
| Option | Money | Your time | Main risk |
|---|---|---|---|
| Friends and family | Free | Medium | Dropouts, polite feedback |
| Communities and exchanges | Free | High | Reciprocity drops, uneven engagement |
| Your own users | Free | Medium | Not available to everyone |
| Paid service | A fee | Low to medium | Choosing a provider you can trust |
Many developers mix them: a core of people they know plus a few community testers, or a service plus their own users for richer feedback.
Costs people forget
- Delays. If your track isn't properly published, or testers use the wrong account, days are lost. See how testers join a closed test.
- A second round. If Google asks for more testing, you continue the test. What to do if production access is rejected covers that.
- Engagement work. Whatever route you choose, you still need feedback to summarize and improvements to describe when you apply. Keeping testers engaged has practical ideas.
Key takeaways
- Closed testing has no Google fee; the account itself costs a one-time US$25.
- Free options work: people you know, communities and your own users, as Google itself suggests.
- A paid service saves time and coordination, but can't guarantee approval or shorten 14 days.
- Whatever you choose, real people using the app for 14 continuous days is the goal.
If you decide a service fits your situation, current GoPlayTester pricing is on the order page, and the setup guide shows what you'd do in Play Console.
