Testing & Testers11 min read

How Much Does Google Play Closed Testing Cost in 2026?

Closed testing is free from Google; only the $25 account fee applies. Here is what 12 testers really cost: free routes, prices we checked, and a failed run.

Ahmed Akash
Ahmed Akash
How Much Does Google Play Closed Testing Cost in 2026?

Need testers who stay active for all 14 days?

TesterBee matches you with 12 real Android testers in under 24 hours. Refund if Google rejects you over tester engagement.

Get 12 testers
On this page
  1. 01What does Google charge for closed testing?
  2. 02What does it cost to get 12 testers? Every route compared
  3. 03Closed testing service prices we checked
  4. 04The cost nobody quotes: a run that fails
  5. 05How to keep the total cost down
  6. 06Free or paid: which costs less for your launch?
  7. 07Frequently Asked Questions
  8. 08Sources

Short answer: Google charges nothing for closed testing. The only fee Google takes on the way to production is the one-time US$25 Play Console registration. What costs money, or time, is keeping 12 testers opted in for 14 days in a row: $0 if you recruit them yourself, and from US$14.99 to US$99 per app if you pay a service, going by the prices we read on each provider's own website on 22 November 2026. The cost that never appears on a price list is a run that fails and has to be repeated.

TesterBee sells closed testing, so read this with that in mind. Our own prices sit in the same table as everyone else's, and the outcome figures below come from the 1,500+ closed testing campaigns TesterBee has analyzed, not from Google. The page splits the cost into three parts: what Google charges, what testers cost on each route, and what a second 14-day window adds.

What does Google charge for closed testing?

Nothing. Running an internal, closed or open test in Play Console carries no Google fee, and neither does the production access application you submit once the 14 days are done. The one charge is the registration fee you pay when you create the developer account. Google's Play Console Help puts it in one line: "There is a US$25 one-time registration fee." You pay it once per developer account, not per app, so it costs the same whether you publish one app or twenty.

The testing requirement itself is policy, not a paid step. Google's help page on app testing requirements says personal developer accounts created after November 13, 2023 must run a closed test with at least 12 testers who have been opted in continuously for at least 14 days before they can apply for production access. Organization accounts are not bound by the 12-tester rule, which is why some teams register as an organization instead; that route needs a verified organization and comes with its own paperwork.

One later cost gets mixed up with testing. Google's service fee applies to apps and in-app products sold through Google Play's billing system, so a free app with no in-app purchases pays nothing beyond the registration. If you have already paid the US$25 and want the full picture of that step, including verification times, see our Play Console registration fee guide.

What does it cost to get 12 testers? Every route compared

The money you spend depends on how you find the 12 people. The requirement is the same on every route: each tester opts in to your closed track and stays opted in for 14 consecutive days. Google's help page adds that a tester who opts out and back in must have 14 consecutive days to count, so a single dropout late in the window can push your application date back.

RouteMoneyTime you spendMain risk
Friends, family and colleagues$0Asking, then reminding people for two weeksThey install once and stop opening the app
Developer communities and tester swaps$0Testing other developers' apps in return, often every dayPartners uninstall once their own test is done
Freelance gigsSet by each sellerVetting sellers and checking every opt-in yourselfEmulators, shared accounts, no replacement for dropouts
Managed testing servicesUS$14.99 to US$99 per appMinutes of setupWhat is included varies by provider

The free routes cost time instead of money, and the time is easy to underestimate. Recruiting is the quick part; keeping 12 people opted in and opening your app for a fortnight is the slow part, and it is where most do-it-yourself tests come apart.

Freelance gigs sit in between: cheap per head, but you carry the vetting. Our guide on hiring Android app testers safely covers how to spot emulator farms and shared accounts before you pay.

Closed testing service prices we checked

These are each provider's own published prices, read from their websites on 22 November 2026. Prices change often and several providers showed limited-time discounts, so confirm the amount at checkout.

ServicePublished priceWhat the provider says the price covers
TesterBeeUS$14.99 (12 testers), US$18.74 (15), US$24.98 (20), US$31.23 (25)One-time per app, 14 days, free retest or full refund if rejected for tester engagement
Testers CommunityFrom US$15Starting price stated in its page title
onTestUS$19.99 one-time12 testers for 14+1 days, 3-day money-back guarantee
PrimeTestLabStarting at US$19.99Starting price shown on its homepage
AppTesterHubUS$29.99, US$49.99 and US$79.99 plansShown as discounted from US$45, US$75 and US$120
TestFiUS$39.99 flatA closed test sized for Google's 12-tester rule
Android Closed TestingUS$80 (Basic) or US$99 (Premium) per appShown as discounted from US$100 and US$150

Why does the same requirement cost US$15 in one place and US$99 in another? Because the requirement is fixed and the extras are not. The higher prices usually buy more testers, written reports, broader functional testing or app-building help, not a different deal with Google, which treats every closed test the same way.

TesterBee's larger tiers are the 12-tester price scaled by headcount, so a buffer of three extra testers costs US$3.75 more. The full list of what each tier includes is on the TesterBee pricing page. Whoever you pick, check five things before paying:

  • Whether testers who drop out are replaced during the 14 days, and how fast.
  • Whether testers use physical phones rather than emulators, which cannot show the real-device usage the application asks you to describe.
  • What the refund or retest terms say, in writing, if Google asks for more testing.
  • That the service never asks testers to post public reviews.
  • Whether the price is one-time per app or a recurring subscription.

The cost nobody quotes: a run that fails

The most expensive closed test is the one you run twice. Google's help page says it can require continued testing when there were fewer than 12 opted-in testers or insufficient tester engagement during the testing period. Either way you keep testing, and a second window means waiting at least another 14 days before you can reapply.

That is why outcome data matters more than the sticker price. Across the 1,500+ campaigns TesterBee has analyzed, 72% got production access on the first attempt across all campaigns, a figure that includes teams who recruited their own testers and cut corners. Of the apps refused once, 91% were approved on the second attempt after addressing the reason Google gave, and the total success rate, meaning production access after one or more attempts, is 98.4%.

The same data shows why the cheapest testers can end up costing the most. In TesterBee's campaigns, apps whose testers were active on 10 or more days were approved at the first attempt 97% of the time, against 41% when testers were active on only 5 to 7 days. Shipping two or more updates during the window went with 89% first-attempt approval, against 53% with none. Google's own guidance points the same way: it says acting on tester feedback during the test increases the likelihood of a successful production access application.

A tester who installs once and disappears still counts toward the 12. What they cost you shows up later, as the thin engagement record behind a request for more testing, and that request costs two weeks, not dollars.

How to keep the total cost down

Most of the savings come from avoiding a second window, not from finding the lowest price. These six habits cost little or nothing:

  1. Recruit above 12. Two to four spare testers absorb a dropout without pushing your application date back. On a free route that means inviting 15 or 16 people; on TesterBee it is the 15-tester tier.
  2. Check the opted-in count every day. Play Console shows it on the closed track. Catching a drop on day 3 costs a replacement; catching it on day 13 costs a new window.
  3. Ship at least two updates during the 14 days. Each update gives testers a reason to reopen the app and gives you something concrete to describe when the application asks how you used feedback.
  4. Read the retest and refund terms before you pay. A free retest turns a failed window into a delay instead of a second invoice.
  5. Never pay for reviews. Google's User Ratings, Reviews, and Installs policy prohibits manipulating ratings, reviews or install counts, including paying for fake reviews. Closed-test feedback reaches you privately in Play Console and needs no public review.
  6. Finish your store listing while the test runs. The listing, content rating and data safety form do not depend on the 14 days, so doing them in parallel removes waiting time from your launch.

For the full sequence from account setup to production, see our complete guide to Google Play's 12 testers rule.

Free or paid: which costs less for your launch?

Free is cheaper when you already have people who will use your app for two weeks: an existing community, a waitlist, colleagues who are your real target users. It also suits a launch with no fixed date, because a slower start costs you nothing but patience. The free route is weakest when you need a guaranteed start, since nobody is obliged to stay for 14 days.

Paid is cheaper when your time or your launch date is worth more than the fee. A quick way to compare is to put a number on your time. Say coordinating a free group takes five hours across the fortnight and you value your time at US$20 an hour: the free route costs US$100 of your time, about the price of the most expensive plan in the table above and more than six times the cheapest. Your numbers will differ; the point is to compare money with money.

Then add the risk of repeating. Whichever route you pick, the real cost is the price plus the chance of a second window multiplied by what two more weeks cost you. A route with weak engagement can be the expensive one even at $0. If you are weighing specific providers, our side-by-side comparison of TesterBee, Testers Community and PrimeTestLab goes through features beyond price.

Frequently Asked Questions

Is Google Play closed testing free?

Yes. Google charges no fee for internal, closed or open testing, or for the production access application. The only Google fee on the path to publishing is the one-time US$25 developer registration.

Do I have to pay for 12 testers?

No. You can recruit friends, colleagues and developer communities yourself. You pay only if you want a service to supply the testers and keep them opted in for the full 14 days.

How much do closed testing services charge?

The published prices we checked on 22 November 2026 ran from US$14.99 to US$99 per app for a one-time 12-tester run. Higher prices usually add more testers, reports or broader testing, not a different Google requirement.

What does it cost if Google asks for more testing?

No fee from Google, but at least another 14-day window before you can reapply. If you paid a service, check whether it includes a free retest; TesterBee offers a free retest or a full refund when a rejection is due to tester engagement.

Can I pay testers to leave reviews?

No. Google's User Ratings, Reviews, and Installs policy prohibits manipulating ratings, reviews or install counts, including paying for fake reviews. Closed-test feedback goes privately to you, and a testing service should never ask testers for public reviews.

Is TesterBee priced per tester or per app?

Per app, one-time: US$14.99 for 12 testers, US$18.74 for 15, US$24.98 for 20 and US$31.23 for 25, each for a full 14-day window.

Sources

  • Get started with Play Console, Play Console Help: the US$25 one-time registration fee.
  • App testing requirements for new personal developer accounts, Play Console Help: 12 testers, 14 consecutive days, the reasons Google requires continued testing, and acting on tester feedback.
  • User Ratings, Reviews, and Installs, Play Console Help: the policy against manipulated ratings, reviews and installs.
  • Service fees, Play Console Help: which sales carry a Google service fee.
  • Provider prices: each service's own website, checked on 22 November 2026 (testerscommunity.com, ontest.app, primetestlab.com, apptesterhub.com, testfi.app, androidclosedtesting.com).
  • TesterBee campaign data: outcomes from the 1,500+ closed testing campaigns TesterBee has analyzed. These describe those campaigns and are not a Google statistic.
Ahmed Akash
Ahmed Akash·Senior Full Stack Developer & Founder of TesterBee

Senior full stack developer specializing in Laravel, React, and Firebase. Helped 1,300+ Android developers pass Google Play Closed Testing and publish apps. Expert in Play Console, production access, and Android app publishing.

November 22, 2026 · 11 min readLinkedInGitHub

Get 12 testers into your closed test in 24 hours

Matched Android testers who open your app every day of the 14-day window, so your production access review has real engagement to look at.

Start your closed test