How Much Does Google Play Closed Testing Cost in 2026?

Short answer: Google charges nothing for closed testing itself. The only fee on Google's side is the $25 one-time developer account registration, which you pay once and never again. The variable cost is the testers: doing it yourself costs $0 in cash, managed testing services in 2026 run from $10 to $47 per app, and the cheap end of that range is cheap for a reason.

Below is the price list as each provider publishes it, checked 30 September 2026, followed by the cost nobody puts on a pricing page: what a failed run actually costs you in days, and how to tell a flat fee from a fee that grows at checkout.

Does Google Play charge for closed testing?

No. Testing tracks — internal, closed and open — are part of Play Console and are not billed. Google publishes one fee on the road to production: a $25 one-time registration fee for a Play Console developer account, charged once rather than annually. There is no per-tester charge, no per-track charge, and no fee to apply for production access.

That means the entire cost of clearing the 12-tester requirement is either your own time or whatever you pay someone else to remove that time from your calendar. Google's requirement itself is unchanged from what it has been since December 2024: a closed test with at least 12 testers "who have been opted in for at least the last 14 days continuously" for personal accounts created after 13 November 2023.

"If you have a newly created personal developer account, you must run a closed test for your app with a minimum of 12 testers who have been opted-in for at least the last 14 days continuously."

Google Play Console Help, App testing requirements for new personal developer accounts. Nothing in that sentence mentions payment — and nothing in Google's documentation approves a paid service either. That distinction matters, and the section on paying for testers covers it honestly.

What do paid tester services charge in 2026?

Every service sells the same unit: twelve people who stay opted in for fourteen days. The prices below are the ones each provider publishes on its own site or pricing page. Nothing here is a quote, a coupon or a negotiated rate — open the link and you should see the same number.

• OnTesters — $14.99 per app. 12 testers with a built-in buffer of 2–3, bug reports, priority support and free retesting included at the same price. One-time, no subscription.
• GetClosedTesting — from $14.99 per app. Flat fee for a 12-tester, 14-day campaign, tiered by tester count.
• Testers Community — $15 for 15 testers, $25 for 25 testers. Flat per app, with a stated approval-or-money-back term.
• testmyapps — $10 for one app, $19 for two. 14 testers across a 16-day managed window (two days of operational buffer).
• PrimeTestLab — $19.99 for 12 testers, $29.99 for 20, $27.99 for 25, plus a 5% service fee added at checkout. Retesting until approved is included on the higher tiers.
• TestFi — $39.99 flat for 16 testers, with a free re-run if twelve are not still opted in on day 14.
• 12TesterHive — $47 per app for 15 verified testers.
• Fiverr and Kwork gigs — listings from about $5. Cheapest entry price in the market, and the one with no retention term behind it.

Two things are worth noticing in that list. First, the spread is narrow at the top: four services sit within a dollar of each other at $14.99–$15, so the sticker price is not where they compete. Second, the ranking by price is close to the reverse of the ranking by risk. A $5 gig buys twelve opt-ins; a $47 campaign buys fifteen people plus a retention guarantee. Those are different products with the same headline number.

Why is there a $5 tier and a $47 tier?

Because you are not buying the same thing at each end. At $5 on a marketplace you are buying twelve installs. Whether those twelve people are still opted in on day 8, still have the app installed on day 11, and ever open it again after the first session is not part of the deal — and there is no replacement clause when one of them disappears.

At the other end, the extra money buys the three things that decide whether your 14-day window survives:

1. Buffer seats. Google's floor is 12. Start with exactly 12 and the first dropout puts you at 11. Services sell 14, 15, 16 or 25 precisely so a single opt-out costs you nothing.
2. Replacement. A tester who goes quiet mid-window is replaced the same day in a managed campaign, and left to rot in a marketplace order.
3. A term you can point at. "Approved or your money back", "free retest until approved", "campaign re-runs free" — these convert an unknown outcome into a bounded cost. A price with no term behind it is a bet, not a fee.

This is the question the closed testing service buyer checklist exists to answer: eleven questions, and the answers that should end the call. The short version is that if a provider cannot tell you what happens when a tester drops on day 9, you are not buying a 14-day test — you are buying 14 days of hope.

What does the free route actually cost?

Cash: nothing. Reddit swap threads, Discord tester exchanges, friends, family and classmates will all get you to twelve opt-ins without opening your wallet. The cost is paid somewhere else, and it is paid in three currencies.

Hours. Reciprocal exchange platforms and manual outreach are typically estimated at 10–20 hours of coordination per app — posting, chasing, verifying screenshots, following up when someone goes quiet. That estimate comes from third-party write-ups of the market rather than from us; treat it as an order of magnitude, not a measurement. Your own number depends on how organised your first message is.

Dropout risk, unpriced. The failure mode of every free route is the same: reciprocity expires. Someone tests your app for six days, loses the incentive, opts out, and your count falls below 12 with a week left on the clock. Nothing in a swap thread guarantees otherwise, because there is nothing to guarantee it with.

Delay. This is the one that never appears on a pricing page, and it is the largest number in the article. See the next section.

There is also a fourth cost that free routes cannot charge for at all: replacement speed. The single thing that decides whether a dropout ruins your window is how fast the empty seat refills. In our own campaigns a new tester is matched to a campaign in under 24 hours, because sourcing is the job. On a swap thread, sourcing is your job, and the only people who can refill your seat are the ones who already owe you nothing — which is why free routes fail at the end of the window rather than the start. They get you to 12 quickly; the question is whether they can get you back to 12 on day 9 when someone uninstalls, and our campaign record suggests that is exactly where engagement-heavy routes separate from count-only ones: 97% approval where testers stayed active 10 or more days, against 41% where activity ran 5–7 days.

What does a failed run cost?

A failed run costs 14 more days. Not 14 more dollars — 14 more days, plus the re-recruitment, plus the re-application, and for most solo developers that means a launch date that slips by a month.

We can put numbers on this because the campaign record behind OnTesters now covers more than 1,500 closed tests on physical devices. First-attempt approval across all campaigns is 72%. Split by what happened inside the window and the pattern is blunt:

• 97% approval where testers stayed active for 10 or more days each.
• 89% approval where the app was updated two or more times during testing.
• 53% approval where there were no updates during the window.
• 41% approval where testers were active only 5–7 days.
• 91% approval on the second attempt after a rejection was fixed properly.

Now run the arithmetic on the cheap option. A $5 run that ends with testers active 5–7 days lands in the 41% group. You have saved $10 against a $14.99 managed campaign and bought a roughly six-in-ten chance of repeating the entire fortnight. At that point the cheapest price in the market has become the most expensive outcome in it.

The useful number is not price per tester — it is price per approval. A service that gets you through on the first attempt at $14.99 costs less than a $5 service that takes two attempts, whatever the checkout says.

Which costs appear at checkout instead of on the pricing page?

Four, in order of how often developers are surprised by them:

Service fees. Some plans advertise a struck-through price and add a percentage at payment — PrimeTestLab, for example, lists $19.99 for 12 testers plus a 5% service fee. Five percent on $19.99 is a dollar; it is not the point. The point is that a "from $X" headline and the amount you actually pay are different numbers, so compare totals, not banners.

À la carte add-ons. Bug reports, session evidence and priority support are standard inclusions at some price points and paid upgrades at others. If your production access application needs evidence of what testers did and found, a plan that charges extra for the report is more expensive than the plan that includes it.

Retest charges. Some providers include retesting until approval; others charge again for a second run. Since 28% of campaigns in our record did not pass on the first attempt, a retest charge is not an edge case — it is a coin flip you are paying for twice.

Recurring billing. A closed test is a one-time event. Any plan that renews monthly is charging you for a second app you have not built yet. OnTesters is a flat one-time fee per app with no subscription and no renewal, and that should be the shape of every quote in this market.

Is paying for testers allowed by Google?

Google neither sells testers nor publishes a rule forbidding you from paying for recruitment. What it publishes is a warning, and it is worth reading in full rather than paraphrasing away. From Google's community guide on the 12-tester requirement:

"Please be aware of a scam that people offering access to groups in return for a fee are not recognized testing companies."

The same guide is blunt about the limits of any third party: "Google does not have control over the third-party testing company."

Read that as a statement about what you are buying, not a ban. Paying a service is paying for recruitment, scheduling, device coverage and the logistics of keeping twelve people opted in — all legitimate work. What Google actually evaluates at review is the record: whether at least 12 testers were opted in continuously for the preceding 14 days, and whether they engaged with your app. Google's stated examples of why it asks for continued testing are exactly those two: "not having 12 testers opted-in to your closed test, or your testers not being engaged with your app during your closed test."

Which is why the honest answer to "is it safe to pay?" is: it is safe to pay for logistics and unsafe to pay for numbers. Fake accounts, emulators and install-only testers produce a count that looks right and an engagement record that does not — and the engagement record is the thing being read. A vendor's job is to put real people on real devices; the devices in our own pool are Samsung, Pixel, Xiaomi and OnePlus hardware running Android 11 through 15 across 80+ countries, with testers matched to a campaign in under 24 hours. Any provider who cannot name their device mix is selling the number, not the test.

How much should you budget for a first app?

For a developer with a personal account created after 13 November 2023, publishing one app costs, in total:

• $25 — Google's one-time developer account registration. Paid once, applies to every app you ever publish on that account.
• $0 to $47 — the tester route, once per app. Free if you recruit yourself; $10–$15 buys the competitive end of the managed market; above that you are paying for buffer seats, retest terms and reporting.
• Your hours — near zero with a managed service, 10–20 per app on the free routes.

A realistic first-app budget is therefore about $40: the Google fee plus one managed campaign at the competitive end. The second app on the same account drops to the campaign price alone, because the $25 is already spent — but it needs its own closed test, because the requirement is written per app.

What should not be in that budget is a contingency for failure, if you can avoid buying one. Recruit 15–16 rather than 12, ship at least one update during the window, and target 10+ active days per tester: those three habits map to the 97%, 89% and 97% figures above, and none of them cost anything beyond arranging them at the start instead of day 12.

Frequently asked questions

Is Google Play closed testing free?

Yes. Play Console's testing tracks carry no charge, and applying for production access is free. The only Google fee on this path is the $25 one-time developer account registration, which is charged once per account rather than per app or per test.

How much does a paid closed testing service cost in 2026?

Published prices run from about $5 on freelance marketplaces to $47 per app, with the managed market concentrated between $10 and $30 for a full 14-day campaign. Compare the total at checkout — some plans add a service fee — and compare terms (replacement, retest, refund) rather than headline tester counts.

Is it cheaper to get 12 testers myself?

In cash, yes: free routes cost nothing. In total, rarely. Budget 10–20 hours of coordination per app, expect dropouts you cannot replace under any guarantee, and count the cost of a failed run at another 14 days plus re-recruitment. Price per approval is the number that matters.

What happens if my run fails and I have to test again?

You run another 14-day window. In our record, 91% of campaigns were approved on the second attempt once the rejection reason was actually fixed — so a failure is usually recoverable, but it costs a fortnight. This is why retest terms and buffer testers are worth more than a discount of a few dollars.

Do I pay Google again for my second app?

No. The $25 registration is one-time per developer account. You do pay again for testers, because the same people can cover multiple apps but each app still needs its own opt-in and its own 14 continuous days.

Does paying for testers guarantee production access?

No, and any provider promising that is telling you something Google does not. Google states that review "usually takes 7 days or less" and that you "may be required to continue testing". Finishing the window makes you eligible to apply; the decision stays with Google's review.

Sources

Every policy statement above traces to one of these pages, opened and read on 30 September 2026. Prices were read on each provider's own pricing or product page on the same date and can change without notice.

• App testing requirements for new personal developer accounts — Google Play Console Help — the 12-tester/14-day condition, the three-section production access application, the "7 days or less" review time, and Google's stated reasons for requiring continued testing.
• Get started with Play Console — Google Play Console Help — the $25 one-time developer account registration fee.
• Everything about the 12 testers requirement — Google Play community guide — the warning about fee-based access sellers, and Google's statement that it has no control over third-party testing companies.
• View and analyze your app's ratings and reviews — Google Play Console Help — where closed test feedback lives (Ratings and reviews › Testing feedback) and the advice to keep a record of it for the application.
• OnTesters pricing — our own published rate of $14.99 per app, one-time, with free retesting and priority support included.
• Google Play tester services: what you are buying and the buyer checklist — the rest of our coverage on this market, including the three claims to discount on sight.

Provider prices were checked on 30 September 2026 and are subject to change. Every percentage in this article comes from OnTesters' own record of 1,500+ closed testing campaigns on physical Android devices, and describes past campaign outcomes — not a guarantee for any future app. This article contains no policy claims that are not linked to a source above.