Google Play Closed Testing: Can Your 12 Testers Be in Different Countries?

Last reviewed against Google Play Console Help: October 2026.

Short answer: yes — your 12 testers can be in different countries. Google publishes no rule that testers share your country, and no rule that they must live in one country between them. But there is a catch that trips up a lot of developers: whether a tester can actually open your closed test is not decided by where they are standing. It is decided by country targeting — and by the country registered to that tester's Google Play account.

So the honest full answer is: international testers are usually possible, and the failure mode is almost never "Google forbids it". It is usually one of two things — your closed-testing track is not available in that tester's Google Play country, or the tester's Google Play country is not what you assumed it was.

This article separates those two ideas properly, shows the exact Play Console settings involved, and explains the one place where Google does document a country exception — and why it does not apply to closed testing. Where Google has published something, it is quoted and linked. Where a fix is practical troubleshooting rather than documented policy, it is labelled that way.

Quick answer

Can your 12 Google Play testers be in different countries?

Yes. There is no published requirement about where testers live, whose country they share, or how many countries they are spread across. If you recruit twelve people across five countries and each of them can install your app and complete the opt-in, then you have twelve testers.

What Google does publish is mechanical: a release can be targeted to users in specific countries, and that targeting decides who can see and install the release. Google's documentation puts it plainly — "When you roll out your app release to production, open testing, or a closed testing track, you can target your release in each track to users in specific countries." Closed testing is named in that sentence, so country targeting genuinely applies to it.

That produces the rule of thumb worth remembering: testers can be anywhere; your release has to be available where their Google Play account is registered. Those are two different conditions, and only one of them is about people.

Two things are worth being precise about here, because this is a topic where confident articles get sloppy. First, Google never publishes a sentence saying "closed-test testers may be in different countries". What it publishes is a country-targeting mechanism that names closed testing, plus the absence of any same-country rule — so the cross-country conclusion follows from the documented mechanics rather than being a policy statement you can point at. Second, Google does tell developers to "recruit a diverse group of testers" — but its own explanation of that phrase is about user groups and device types: it says a diverse group helps "identify bugs and usability issues that might affect specific user groups or device types". Country is not mentioned. Any article that turns that sentence into a geographic-diversity requirement has invented the geography.

Two practical consequences follow, and both are the kind of thing that wastes a testing cycle:

• An invitation is not access. Adding someone to a tester list does not make your app available in their country. If the closed-testing track does not cover their Google Play country, they will not be able to install it, and they cannot count toward your 12 if they cannot opt in.
• A tester's country is probably not what you think. People move, study abroad, keep an old payment method and a Google Play account registered elsewhere. This is common enough that it is the single most useful thing to check before inviting anyone from a new country.

If you are still assembling your group, the mechanics of adding testers to a closed test matter more than where they live, and what counts as an eligible tester covers the states that quietly break a count.

Physical location vs. Google Play country

This is the distinction that resolves most confusion about international testers, so it is worth stating in Google's own words. From Google's documentation on distributing releases to specific countries:

Read that sentence twice, because it answers both halves of the question. Your target is the account's Play country. A tester's GPS position, SIM card, current time zone and physical address are not what the store checks when deciding whether to show them your app.

The four concepts involved are often used interchangeably, and that is where the trouble starts:

Example. A tester lives in Germany but their Google Play account is registered to the United States, because that is where they set it up and their payment method is still American. For country targeting, that tester is a US user. If your closed-testing track covers the US, they will see the app — even though they are in Berlin. If your track covers only Germany, they may not.

The same example, reversed. A tester with a UK Google Play account spends three weeks in Japan. They are still a UK user. Their holiday does not move them into your Japan-only test, and it does not take them out of a UK test.

There is one place where physical location genuinely does matter, and it is easy to confuse with the above. Setting up a Google Play country is location-bound: Google requires that to set up a new country you must be in that location and have a payment method from the new country. Google also applies a wait of at least 90 days after you initially set your Play country, and at least 90 days between subsequent changes, and it notes that the change can take up to 48 hours to take effect. So location determines whether someone can establish a Play country — it does not determine which country they are treated as for availability at download time.

Two related traps worth knowing, both from Google's own page on changing your Google Play country: a profile change can take up to 48 hours to update, and members of a Google Family group cannot change their Google Play country at all. If a tester tells you their country is "wrong", those two facts explain a large share of the cases.

How country targeting works for closed testing

Google separates app availability from country targeting, and the difference decides what you are allowed to customise for a closed test.

App availability is your app's availability in the production track. Google's wording: "When you select a country as available, any current and future production releases include that country." That makes it a broad setting with consequences beyond testing.

Country targeting is the per-release adjustment, and Google describes the default behaviour clearly:

That default is the trap. If your closed test has never been unsynced from production, then your closed test covers exactly the countries your production release covers — no more, no less. Inviting a tester whose Google Play country is outside that list cannot work, no matter how genuine they are.

Google also warns that distribution changes are not track-local: "Changes to distributed countries and regions apply across all tracks." Combined with the sync default, that means an edit you make in one place can move your closed test, your open test and your production release together.

Customising it is possible, but it is conditional. Google documents a prerequisite with two acceptable cases:

• Your app doesn't have an app bundle uploaded to production; or
• Your app has an app bundle uploaded to production and at least one country is available in the production track.

Google also documents when the sync itself remains enabled — so before you plan an international test around a custom country list, check which of these applies to your app:

• Your track has no release rolled out; or
• Your production track targets at least one country/region; or
• Pre-registration has started and targets at least one non-"Rest of World" country.

None of this is exotic. It is simply the difference between "I invited twelve people" and "twelve people can install my app" — and for international testers, it is the whole game. If you want the background on how the tracks differ, internal vs closed vs open testing covers it in more detail.

When the internal-testing exception gets misquoted

Google documents one genuine country exception, and it is the sentence most often borrowed to answer a question it does not address. Here it is in full:

Note precisely what that covers: internal testing only. It says nothing about closed testing, and it cannot be extended to closed testing — closed testing is the track the country-targeting article names when it describes releases you can target to specific countries. Google's testing documentation repeats the exception in the same narrow terms, listing country distribution as an internal-testing property: "You can add users from any location to your internal test."

That distinction has a real consequence. Internal testing is a separate track for a small team, and the published production-access requirement refers to running a closed test with at least 12 testers opted in continuously for at least 14 days. So "just use internal testing, country targeting doesn't apply there" is not a workaround for international testers who need to count toward your 12 — it is a different track answering a different question.

There is a related gotcha worth knowing if you use both tracks with the same people. Google documents that a user who opts into your internal test is no longer eligible to receive an open or closed test, and must first opt out of the internal test before opting in to the closed test. A tester who is "already installed on the internal build" is not automatically a closed-test tester.

Why does a tester see "This app isn't available in your country"?

This message means the store has decided your app is not available to that account — so the useful question is why, and there are several distinct causes. Some are directly documented by Google; others are practical troubleshooting. The table marks which is which.

Work down that list in order, and change only one thing at a time. The most common mistake is widening production availability to fix a problem that was actually a synced track or an unjoined Google Group — which is a large, consequential change made for the wrong reason. On that last point Google is explicit: "Only members of the specified Google Groups can join your test." Being invited to a group is not the same as having joined it.

How to check country availability in Play Console

There are two different places to look, and knowing which one you need saves a lot of guessing. Both paths below use the current labels from Google's documentation.

1. Your app's overall availability (the production track).

1. Open Play Console and select the app.
2. Go to the Production page.
3. Select the Countries/regions tab.
4. Click Add countries/regions or Remove countries/regions and select the countries or regions you want to change.
5. Confirm your selection.

2. Country availability for your closed-testing release.

1. Open Play Console and select the app.
2. Go to Testing > Closed testing.
3. Click Manage track next to the track you want to update.
4. Select the Countries/regions tab.
5. If the track is synced with production, click Unsync countries/regions. Once it is no longer synced, click Edit countries and select the countries or regions to add or remove.
6. Confirm your selection.

Do all 12 testers need to be in the same country?

No. Google publishes no requirement that testers share a country — not with you, and not with each other. There is no documented minimum number of testers per country either, and nothing that says a test group must be concentrated in one market.

The requirements that do exist are about access and participation rather than geography. For eligible personal developer accounts created after 13 November 2023, the published requirement is a closed test with at least 12 testers opted in continuously for at least 14 days, after which you can apply for production access on the Dashboard. Google's own definition of continuity is strict about the clock, not about the map: testers who opt in, test for fewer than 14 days and opt out do not count, and if a tester opts out and back in later, the 14 days must be consecutive.

Notice what that sentence never mentions: location. The count is a count of opted-in testers, wherever they are. If the number is not behaving the way you expect, 12 testers not counting walks through the states that break a count.

So the practical test for any international tester is simply: can this person install my app and stay opted in for the period? If yes, they belong in your group. If no, the fix is either the track's country availability or a different tester — not a change of plan.

International testers: what should developers check before starting?

This is the pre-flight list. Everything here is either documented by Google or a direct consequence of it, and working through it before you invite people is far cheaper than discovering a problem on day three.

• Each tester's Google Play country — ask, or have them confirm it in their own account. Do not infer it from where they live.
• The closed-testing track's country availability — and specifically whether it is still synced to production.
• The right tester list — the exact Google account you added, or confirmed membership of the Google Group you use, since group members must join the group before opting in.
• A working opt-in link — and confirmation that the app status is "Published", because the link only displays when it is.
• Successful opt-in by each tester — not "they said they installed it". Twelve invitations are not twelve testers.
• Access to the correct app and version — the tester is receiving the testing release, not an older production build.
• Clear testing instructions — what to install, what to try, which features matter, and how to report problems.
• A record of participation and feedback — opt-in dates, what each tester exercised, what they reported, and what you changed.

Two of those deserve emphasis for international groups. First, the instructions: a tester in another country, possibly in another language, is more likely to complete the opt-in correctly if you send a short, explicit series of steps rather than a bare link. Second, the record: if you end up describing tester engagement when you apply, "twelve testers across four countries, here is what each of them did" is a much stronger story than a list of names.

For keeping people in the test for the full period — which is where international groups most often lose members to time zones and slow replies — see how to keep 12 testers opted in for 14 days. If a tester simply cannot see your app, the troubleshooting patterns in closed testing not working overlap heavily with the country cases above.

Does using testers from different countries help with production access?

Not in the way developers usually hope. Google publishes no geographic-diversity requirement and no advantage for spreading testers across countries. There is no box on the production access application that rewards a wider map, and no documented credit for international testers.

What Google's documentation actually cares about is whether the testing was real. Its guidance asks developers to give testers clear instructions, tell them what feedback you want, encourage them to use as many features as possible, provide a clear feedback channel, and keep testers informed so they remain opted in across the period. The application then asks about how easy it was to recruit testers, how engaged they were, whether they used all available features, whether their usage matched what you would expect from production users, the feedback you received, how you collected it, what you changed, and how you determined the app was ready. Answering the closed-testing questionnaire covers those questions one by one.

So the value of an international group is practical, not promotional — and it is real, as long as you do not mistake it for a shortcut:

• You can reach twelve genuine Android users when your own network is too small.
• Different locales, devices, carriers and languages can surface problems your own environment never will.
• Feedback from outside your assumptions is often more useful than polite agreement from friends.

But a tester in another country who installs the app and disappears is worth exactly as much as a tester next door who does the same: nothing. The evidence has to come from what you record during the test, and the requirement itself is still the one described in the complete 14-day guide for 12 testers. Meeting it makes you eligible to apply; it has never guaranteed approval, and no arrangement of tester countries changes that.

How 12 Testers Community helps

Most international-testing problems are logistics problems: someone cannot see the app, someone's Play country is not what you assumed, someone drifts away in week two. That is the part we handle.

12 Testers Community organises Google Play closed testing for indie Android developers:

• 12+ testers, so the published tester requirement is covered with a buffer for dropouts.
• 14-day closed-testing support, with testers kept opted in across the period.
• Real Android device testing — genuine hardware rather than emulators.
• Tester coordination — onboarding, instructions, reminders and continuity checks, which is exactly where international groups are most fragile.
• Practical testing and feedback support, so testers exercise real features and report things you can act on.
• Assistance with the closed-testing process end to end, including what to record and how to describe it when you apply.
• Pricing that starts at $14.99 for a full 14-day test.

We do not publish or promise where our testers are located, and we would be sceptical of any service that presents a particular geographic mix as a Google requirement — it is not one. We are not affiliated with Google, we are not an official Google service, and we do not promise production access. If your group is going to be spread across countries, we can help you set it up so that access and continuity are handled properly, leaving you to work on the app.

Frequently asked questions

Can Google Play closed testers live in different countries?

Yes. Google publishes no rule that testers must share a country, and nothing requiring geographic diversity either. What matters is whether each tester can access your closed test and complete the opt-in, which depends on your testing track's country availability and on the tester's own Google Play country.

Does a tester's physical location determine Google Play country?

No. Google states that country targeting is based on the user's Play country — where their account is registered — not their current location. A tester travelling abroad keeps their existing Play country. Physical location matters only when someone sets up a new Play country, which Google requires you to do from within that country with a local payment method.

Can a tester join if the app is unavailable in their country?

Not through the standard closed-testing route, because closed-testing releases are subject to country targeting based on the tester's Play country. If your testing track does not cover their Play country, they will not be able to see or install the release. The documented any-location exception applies to internal testing, not closed testing.

How do I change country availability for a closed test?

In Play Console, open your app, go to Testing > Closed testing, click Manage track next to the track, and select the Countries/regions tab. Testing releases match production availability by default, so if the track is synced you may need to click Unsync countries/regions first, then use Edit countries to add or remove countries. Customising this depends on Google's documented prerequisites.

Do all 12 testers need to be from one country?

No. There is no same-country requirement and no published minimum per country. The published requirement is at least 12 testers opted in continuously for at least 14 days for eligible personal accounts created after 13 November 2023 — a count of opted-in testers, with no location condition attached.

Can international testers count toward the 12-tester requirement?

Yes, if they genuinely opt in and stay opted in. What the requirement counts is testers opted in to your closed test continuously for the required period. A tester in another country who opts in and remains opted in for the period counts the same as a local one. A tester who cannot install the app counts for nothing.

Is internal testing different from closed testing for country availability?

Yes, and this is the distinction most often misapplied. Google documents that country targeting does not apply to the internal testing track, and that internal testers receive the build from any location — even where your production, open test or closed test is unavailable. That exception is for internal testing only. Closed testing is the track Google names when describing releases that can be targeted to specific countries.

Does using testers from multiple countries guarantee production access?

No. Google publishes no geographic-diversity requirement and no advantage for international testers, and meeting the tester requirement does not guarantee approval in any case. The application is about the quality of the testing: engagement, feature coverage, feedback, the changes you made, and how you decided the app was ready.

What should I check if a tester cannot open the opt-in link?

In order: that the app status is "Published" so the link exists at all; that the tester was added with the exact Google account they are using, or has joined the relevant Google Group; that the tester has not already opted in or out in a way that removed them; that their Google Play country is covered by the closed-testing track's availability; that the track is not still synced to a production list that excludes that country; and whether the change simply has not propagated yet — Google notes a test link can take several hours to become available to testers, and that additional changes can also take several hours.

International closed-testing checklist

A practical checklist, not a set of Google requirements — and completing it does not guarantee approval.

Back to top ↑

Conclusion

Your 12 testers can absolutely be in different countries. What cannot be ignored is that access runs through country targeting, and country targeting is matched against the tester's Google Play country — where their account is registered — rather than wherever they happen to be standing. Once you hold those two ideas apart, most international testing problems stop looking mysterious: they are either a track that is still synced to a production list, or an account whose Play country is not what you assumed.

Three things are worth carrying away. There is no same-country rule, so build your group around who can genuinely test rather than where they live. The internal-testing country exception is real but belongs to internal testing only, and does not answer the closed-testing question. And country diversity is not a shortcut to production access — the evidence that matters is opt-in, feature coverage and feedback, however far apart your testers are.

If assembling and coordinating that group is the part you would rather not do yourself, we can take it from here.

About this guide. 12 Testers Community organises Google Play closed testing for indie Android developers. This article reflects that experience; it is not affiliated with Google, and nothing here guarantees a production-access decision. Google's country and testing rules, quoted above, are documented in Distribute app releases to specific countries, Set up an open, closed, or internal test and App testing requirements for new personal developer accounts. The rules for a Google Play country itself are described in Change your Google Play country.