Last reviewed against Google Play Console Help: October 2026.
Most developers asking what 12 testers cost are asking two things at once: what will this fortnight take out of my budget, and am I allowed to do it for free. Both have short answers, and then the useful part begins.
Google charges nothing for testers, and you can satisfy the requirement with people you already know. Paid services exist because coordinating twelve people for fourteen consecutive days is real work somebody has to absorb. This page prices that work: how it is built, what your money buys, how to compare two quotes that look nothing alike, and which parts of a proposal are worth paying for.
For "is a subscription required?", see whether you need to pay for testers at all, which includes a dated survey of published market prices. That survey is not repeated here. The question here is harder: when several services cost roughly the same, how do you tell which is worth it?
Quick answer
Google does not sell testers, and the requirement cannot be bought from Google.
- Recruiting 12 testers yourself costs $0 in money and several hours of coordination.
- Third-party services are optional. You are buying labour — recruitment, chasing, monitoring, replacement and reporting — not permission and not an outcome.
- Published entry tiers cluster around $15 per app, one-time. The spread between providers reflects deliverables, not any Google rule.
- 12 Testers Community plans start at $14.99 for 12+ testers across the full 14 days.
- No third-party service can guarantee production access. That decision is Google's alone.
The rest of this page is about spending that money well — or deciding, with reasons, to keep it.
What Google actually requires
The requirement is a gate on elapsed time, not a bill, so it is worth stating precisely. Google Play Console Help states that developers with personal accounts created after November 13, 2023 must run a closed test with a minimum of 12 testers opted in continuously for at least 14 days. Until those criteria are met, Production and Pre-registration stay disabled.
At the moment of applying: "At least 12 testers must be opted in to your closed test when you apply for production access, and they must have been opted in continuously for the preceding 14 days." (Play Console Help.)
Four properties of that rule decide what anything should cost you:
- The clock is not buyable. Fourteen consecutive days take fourteen days. No fee shortens them.
- The count is checked at the end. Twelve is a floor measured when you apply, not an average. Losing your twelfth tester on day 12 costs you the window you were about to use.
- "Continuously" is operative. Opted in, not merely invited — what counts as an eligible tester covers the difference.
- Meeting it makes you eligible, not likely to be approved. Google reviews the submission and may require more testing.
Nothing in that documentation mentions a tester fee, a provider, a plan, a renewal, or a minimum number of minutes per day. Google documents a test and a set of criteria. The market is something that grew around it.
Do you have to pay for 12 testers?
No. There is no tester line item in Play Console and no Google-operated marketplace. Google's own guidance points at the free route first: "The most common way to recruit testers is to use personal and professional networks. Reach out to friends, family, colleagues, or classmates to ask them to test your app."
Two payments get confused with a tester fee, and neither is one. The one-time developer registration fee pays for the Play Console account itself, whether you recruit testers yourself or pay somebody to help. An invoice from a testing service is optional: Google does not require that business, endorse it, or receive its fee.
One free asset also gets forgotten. The pre-launch report — Google's automated device-lab test — runs against your build and reports stability, compatibility, performance and accessibility issues. You are not paying anyone for basic crash detection, because Google already does it.
What no Google tooling supplies is people who stay opted in. That gap is the entire third-party market, and the only thing worth pricing.
Why do developers pay for a testing service?
Not because the requirement demands it. Developers pay for one of five honest reasons, and knowing which is yours tells you what to spend.
They cannot find twelve people
The most common reason, and the most legitimate. A solo developer with no Android-using network is genuinely stuck.
Their network is not reliable
Friends say yes, install on day 1, and drift. A dropout on day 6 can break the continuous window.
Coordination has become the bottleneck
Recruitment is a small task repeated many times. When it becomes the critical path, the fee is cheaper than the delay.
They need a written record
Google requires you to summarise your testing feedback when applying, so a bare count leaves you writing that summary from memory. See what to track during the 14 days.
The launch date is not theirs to move
When a deadline is fixed, predictability is worth more than the fee. That is a scheduling purchase, not a compliance one.
A reason that is not honest
"I think paying makes approval more likely." Nobody can act on your application. If this is your reason, keep your money.
Four of those six are reasons to pay. If none describes you, the free route is not a compromise — it is the correct answer.
How much does a 12-tester service cost?
Among services that publish prices openly, a one-time, per-app charge for a 12-tester, 14-day campaign sits roughly in the $10 to $60 band, with entry tiers clustering near $15. Those are providers' own figures, not Google's, and they change — which is why the dated provider-by-provider snapshot lives on the site's free vs paid breakdown rather than being copied here.
The more useful question is why two services at the same headline price are not the same product. Three archetypes explain almost all of it.
| Archetype | What it delivers | Who absorbs the work | Cost shape |
|---|---|---|---|
| Recruitment only | A list of accounts, or testers added to your track. No monitoring, no report. | Still yours: reminders, count checks, replacements. | Lowest one-time fee, or credit-based reciprocity. |
| Managed testing campaign | Recruitment, daily monitoring, dropout replacement, feedback and a written report. | The provider, mostly. You upload builds and read the report. | One-time, per app. The band above. |
| Deep QA engagement | Exploratory testing, test plans, regression passes, a device matrix, structured defect reports. | A QA team you are hiring by the project. | Project or hourly pricing, often an order of magnitude higher. |
Only the middle archetype answers the closed-testing requirement: the first leaves you the work you were buying, the third sells testing you may not need. A quote is comparable only once you know which archetype it is.
What moves the number up or down
- Tester count and buffer. A provider promising exactly twelve has no margin for a dropout. Extra testers are insurance, not compliance.
- Monitoring depth. Checking a count daily is cheap. Noticing a specific tester has gone quiet and replacing them before it matters is not.
- Device spread. A range of brands and Android versions is harder to assemble than twelve similar phones, and it produces better feedback.
- Report depth. Forwarded chat messages and a severity-ranked report are different deliverables at different costs.
- Replacement and retest policy. Promising a free replacement, and a retest if Google asks for more, costs the provider money — which is why it is worth money to you.
- Support and start speed. A shared inbox is cheaper than a named contact. A guaranteed fast start needs a standing pool of testers.
- Disclosed fees. Compare totals, not headlines.
What you are actually paying for
Strip the marketing and a service is selling you small, repetitive tasks that would otherwise be yours. Individually they look trivial. Repeated for fourteen days across a group of people, they are the whole job.
| Task | On the free route | What paying should buy |
|---|---|---|
| Finding testers | Ask your network, communities, social posts | People who already have Google accounts and Android devices |
| Getting them opted in | Walking each person through the Play Store flow | Confirmed opt-ins, not just a list of addresses |
| Keeping them opted in | Daily count checks and polite reminders | Monitoring for the full period |
| Handling a dropout | Yours, and it has to be fast | A stated replacement process with a timeframe |
| Collecting feedback | Whatever you can prompt out of people | Issues and observations you can act on |
| Summarising for the application | Written by you, from memory | A document that answers the questionnaire's three sections |
| Absorbing the restart risk | Entirely yours: another 14 elapsed days | A retest or refund policy, in writing |
The last two rows are where the value concentrates. A service supplying twelve accounts and nothing else has sold you the cheapest rows of this table and none of the ones that decide whether your fortnight survives.
Working out your real cost
Comparing a $14.99 invoice against "free" compares a number against nothing. Free costs no money; it costs hours, and it carries a dated risk.
Real cost of the free route
money (0) + (your hourly rate × coordination hours) + (cost of a restart × probability of a restart)
The middle term is yours to estimate. The last is the one developers forget: if a window breaks on day 10, you lose ten days and start a fresh fortnight.
Two lenses help. Price per tester-day: a $14.99 campaign covering 12 testers for 14 days works out at roughly 9 cents per tester-day, which reframes the question from "is $15 a lot?" to "is half an hour of my own chasing worth more than that?". The buffer as insurance: stepping up from 12 to 15 testers typically costs a quarter to a third more, and buys a real reduction in the chance that one dropout invalidates the window.
Neither lens gives a universal answer, because your hourly rate and your deadline are yours. That is the point: the right price depends on what your time and timeline are worth, not on a market average.
$15 vs. higher-priced testing services: what's the difference?
Almost nothing about the requirement changes with price. The gateway criteria are identical at every tier: twelve testers, fourteen continuous days, a feedback summary, an application. What changes is the bundle of work, evidence and risk transfer around that obligation.
So resist reading price as a quality signal. A higher fee is not evidence that testers are real, and a low fee is not evidence that they are not. The only reliable comparison is the one you would apply to any contractor: what is included in writing, how many times you pay, and what happens when the first thing goes wrong.
Worth the premium
- A written replacement policy with a timeframe
- A retest provision if Google asks for more testing
- Feedback detailed enough to summarise on the application
Worth questioning
- A much larger tester count sold as "necessary" — the minimum is 12
- A price increase whose only explanation is the word "premium"
The one thing genuinely worth more at 15 or 20 testers is device and Android-version coverage — the chance your report surfaces something a small, similar group never would. That is a testing-quality argument, not a compliance one, and you can decline it.
Where price legitimately changes the work: recovery from a rejection is a bigger job than a first campaign, with a fresh fourteen-day cycle and often a rewrite of the application answers. Expect it to be priced differently, or expect a policy saying whether it is included.
Free vs. paid testers: which option is right for you?
Neither is correct in general. One is correct for your fortnight, and the tie-breakers are all about you rather than about the market.
| Your situation | Better route | Why |
|---|---|---|
| Twelve or more Android users you actually know | Free | You can assemble the group faster than you can buy one, and the feedback is often better. |
| An active community where your future users already gather | Free | Google asks whether usage matched expected production behaviour. Your real audience answers that best. |
| A flexible launch date and spare hours | Free | You can absorb a restarted window without a business consequence. |
| You want testers you can reuse on the next release | Free | A network you build compounds; a purchased campaign starts from zero again. |
| You cannot find twelve people | Paid | Recruitment is the constraint, and it is the thing being sold. |
| Your network keeps drifting off | Paid | You are buying monitoring and replacement, not bodies. Check that the policy exists. |
| Finding testers has become the critical path | Paid | When the delay costs more than the fee, the fee is the cheaper option. |
| A fixed launch date | Paid | You are buying a start date that behaves like a start date. |
If you are between the two, one rule resolves it: start the free route today and give it a deadline. Twelve opted-in testers by then means you never needed to pay. If not, you have bought certainty about which purchase you are making. What you should not do is spend three weeks recruiting and then buy anyway — that spends both currencies.
The 14 days only begin once testers are genuinely opted in, so the clock starts later than most expect. Assembling a group is covered in seven legitimate ways to get 12 testers, and retention in keeping 12 testers opted in for 14 days.
What to check before paying for a Google Play testing service
Every row has a factual answer. If a provider replies with a promise instead of a policy, that is your answer.
| Check | What a good answer sounds like |
|---|---|
| Are the testers real people? | A concrete description of who they are and how they are identified — not "thousands of testers" |
| Real Android devices? | Named brands or a device list. Emulators and device farms are not testers |
| How many testers, exactly? | A number per tier, in writing, with any buffer identified separately |
| What if a tester drops out? | A named replacement process with a timeframe, and whether it costs extra |
| How long is the period? | The full 14 days stated plainly, with the start date defined. "About two weeks" is not a commitment |
| Is feedback included? | You must summarise feedback when applying, so raw silence leaves you with nothing to write |
| Can I see a sample report? | An actual sample. If none exists, assume the deliverable is a count |
| One-time or recurring? | One-time and per app, matching the shape of a one-off requirement |
| Is the total the total? | Fee-inclusive pricing before you pay, not a surcharge at checkout |
| What if Google asks for more testing? | A stated retest policy: included, discounted, or clearly priced — Google can require this |
| Are the Google claims accurate? | If the marketing contradicts Play Console Help, the documentation wins |
| Is the outcome language honest? | A clear separation between being eligible to apply and being approved |
Two rows carry most of the money: the replacement policy and the retest provision, where a cheaper headline often ends up costing double. Get both in writing before comparing anything else.
What you should not pay for
Some of what is sold around this requirement cannot be delivered by anyone. Money spent on it suggests the provider is selling confidence rather than labour.
- A guarantee of production access. Meeting the requirement makes you eligible to apply. Nobody outside Google has a vote.
- Daily activity quotas. Google publishes no requirement for opens, sessions or minutes per day. A "daily usage guarantee" sold as compliance is inventing criteria.
- A subscription. This is a one-off requirement, and a recurring plan outlives the thing you are paying it for.
- Far more testers than you can use. Twelve engaged testers beat twenty who installed and forgot — and the application asks about engagement.
- "Google-approved", "official" or "trusted" tester status. No such programme exists and no service is endorsed.
- A faster opt-in link or a shortcut to the 14 days. The window is a property of Google's own tracking.
- Unverifiable ratings and approval percentages. Google publishes no per-service approval statistics; self-reported figures are marketing.
This is not an accusation about any company. It is a list of things to decline — and a provider that takes the refusal well is telling you something useful about how they behave when a tester disappears on day 9.
Can a paid testing service guarantee production access?
No. This is not a matter of opinion.
- Google decides. Meeting the criteria unlocks Apply for production. Google then reviews the submission, and its published guidance is that review "usually takes seven days or less, but can occasionally take longer".
- Google can require continued testing. Its documentation names two reasons: fewer than 12 opted-in testers, or insufficient tester engagement during the testing period.
- A provider has no influence over that decision. Google does not require the service, audit it, or consider whether you used one.
- Some of what Google weighs is not purchasable. The application asks how you recruited testers, whether they used your app's features, whether usage resembled your expected production users, how you collected and summarised feedback, and what you changed. A provider can influence the engagement parts by supplying engaged testers; nobody can influence the rest for you — see why production access is still refused after 14 days.
What a service can legitimately promise is narrower and still worth paying for: real testers genuinely opted in for the full period, monitored, replaced when they drop out, and documented in a report you can use. A refund or free-retest policy prices the risk that remains.
How 12 Testers Community helps developers
If the analysis above lands on "managed", we are one of the services to compare — and we would rather you compared properly than picked us by price.
Plainly: this is not a compliance purchase. You can do this without us, and if the free route fits, take it. What we sell is coordination — real testers on real Android devices, opted in for the full 14 days, with the count watched daily so a quiet tester is noticed while there is still time to act.
| Plan | Testers | Price | Included |
|---|---|---|---|
| Starter | 12+ | $14.99 one-time | Full 14 days, real Android devices, live tracking dashboard, basic bug report |
| Professional | 15+ | $20.00 one-time | A buffer above the minimum, detailed bug report, free retest if not approved |
| Enterprise | 20+ | $25.00 one-time | Wider device coverage, comprehensive report, priority support, free retest, questionnaire answers |
Every plan runs the full 14 days, is charged once per app, and carries a money-back guarantee if the app is not approved after our testing. Testing typically starts within a few hours of your order, and you can watch the count from a dashboard rather than chasing anyone.
Equally clear about the limits: we are not affiliated with Google, Google does not endorse us, and we cannot guarantee production access. If Google asks for more testing, our retest provision exists because that outcome is real — not because anyone can promise it will not happen.
Need help organizing your Google Play closed test?
Plans start at $14.99 for 12+ testers across the full 14 days — one payment per app, no subscription.
Frequently asked questions
How many testers does Google Play require?
A minimum of 12 testers opted in continuously for at least 14 days, for apps on personal developer accounts created after November 13, 2023. Twelve is the documented floor; anything above it is a voluntary buffer.
Do I have to pay for 12 testers?
No. Google charges nothing for testers and sells no tester plan. The only Google payment involved is the one-time developer registration fee for the account itself.
Can I find Google Play testers for free?
Yes. Google's guidance starts with personal and professional networks — friends, family, colleagues, classmates — and with communities where your future users gather. It costs nothing but your time.
How much does a 12-tester service cost?
Published one-time, per-app entry tiers cluster around $15, with the market spanning roughly $10 to $60 depending on what is bundled in. These are third-party prices, not Google's, and they change — see the dated provider survey.
Do testers need to use real Android devices?
The requirement is about genuine people testing your app, and Google's guidance is to recruit testers who represent your intended audience. Emulators, bots and device farms do not behave like users, and fake engagement risks your developer account.
Does paying for testers guarantee production access?
No. Completing the requirement unlocks the application; Google then reviews it and decides, and may ask for continued testing if you have fewer than 12 opted-in testers or insufficient engagement.
Do testers need to stay opted in for 14 days?
Yes — at least 12 testers must be opted in continuously for the preceding 14 days when you apply. A tester who drops out mid-period does not satisfy a continuous window. See what resets your testing period.
What should I look for in a testing service?
A written tester count, real-device confirmation, the full 14 days stated plainly, one-time per-app pricing with no checkout surcharge, feedback you can summarise, a sample report, and stated replacement and retest policies.
Can I use friends and family as testers?
Yes. They are legitimate testers, and Google's guidance explicitly includes them. Two caveats: they produce weaker bug reports, and the application asks whether tester usage matched your expected production users.
Is a third-party testing service required by Google?
No. Google requires a closed test with the criteria met. It does not require a provider, endorse one, or take a share of any fee. Hiring help is allowed because every tester is a genuine person opting in voluntarily.
Final checklist
Before you start a closed test — or pay anyone to help with one — work through this once.
Decide the route
- ☐ Checked that the requirement applies to your account type
- ☐ Given the free route a deadline before spending anything
- ☐ Estimated your own coordination hours against a realistic hourly rate
If you are paying
- ☐ Tester count, buffer and device coverage confirmed in writing
- ☐ Full 14 days and the start date stated plainly
- ☐ Replacement policy and retest provision in writing
- ☐ One-time, per-app total confirmed including any fee
- ☐ Sample report seen
- ☐ No guarantee of approval accepted as a selling point
Either route
- ☐ A feedback channel set up before day 1
- ☐ The opted-in count checked during the period, not on day 14
- ☐ Feedback recorded as it arrives, so the summary is written already
The short version: the requirement itself costs nothing, and the market around it sells time, coordination and risk transfer. Pay for those if you are short of them. Do not pay for permission, and do not pay for an outcome — neither is for sale.
Official Google resources
- App testing requirements for new personal developer accounts — the 12-testers and 14-days criteria, tester recruitment guidance, and the production access application.
- Set up an open, closed, or internal test — testing tracks, opt-in links, and how feedback is collected.
- Use a pre-launch report to identify issues — the automated device-lab test described above.
About this guide. 12 Testers Community organises Google Play closed testing for indie Android developers. Every Google requirement and quotation here was checked against Play Console Help in October 2026; third-party prices are the providers' own figures and should be re-checked before you buy. We are not affiliated with Google and cannot guarantee production access.
Wider reading while you decide: the complete 14-day guide for 12 testers, how long closed testing takes, and 10 reasons your closed test is stuck.
