Limited Distribution Accounts on Android: What They Replace

Google now offers a free Android developer account that needs no government ID and lets you install your app on up to 20 devices. It is called a limited distribution account, and since it launched globally in August 2026 it has been circulating among developers as a rumored way around Google Play's closed testing requirement. It is not that. A limited distribution account distributes apps outside Google Play, to devices you personally authorize one at a time. It has no store listing, no closed testing track, and no production access, so nothing about it counts toward the 12-tester, 14-day rule. If your goal is a Google Play listing, the closed test still stands. What the account is genuinely good for is putting a finished app on a small, fixed group of real phones while you decide, or while you prepare the Play Console side properly.

What a limited distribution account actually is

Google's own definition, from the Android Developer Console Help page, is short: "A limited distribution account in Android Developer Console is designed for students and hobbyists who want to distribute their apps to a small number of users. This account type is completely free. With this account, you can distribute your apps on up to 20 authorized devices" (support.google.com, checked 22 October 2026).

Three details in that paragraph do the real work. It lives in the Android Developer Console, a separate product from Play Console that exists for "developers who only distribute outside of Google Play" (get started guide). It is free, with no US$25 registration fee. And the unit of distribution is the authorized device, not the install, which we come back to below.

To sign up you need a Google Account with 2-Step Verification turned on, a linked Google payments profile (used for your legal name and address), and a contact email. Google states plainly that "there are no additional verification requirements for limited distribution accounts. For example, you do not need to provide a government ID." The account type reached early access in July 2026 and launched globally in August 2026, on the schedule Google published on 18 June 2026 (Android Developers Blog).

What it does not replace

Here is the requirement it gets confused with, in Google's words: personal developer accounts created after 13 November 2023 "must run a closed test for their app with a minimum of 12 testers who have been opted in continuously for at least 14 days", and until that is done, "Production and Pre-registration remain disabled" (App testing requirements for new personal developer accounts).

That requirement attaches to your Play Console account and to the app's closed testing track. A limited distribution account has neither. Google publishes no rule giving credit for devices authorized in the Android Developer Console, because the two systems measure different things: one tracks whether an app may be installed from participating stores, the other tracks whether a specific cohort of testers has stayed opted in to a specific test.

So a limited distribution account does not give you a store listing, ratings, reviews, production access, or any way to apply for it. It also cannot be the origin of a 14-day clock. In the 1,500-plus closed-testing campaigns OnTesters has analyzed, every clock that ever reached a production access application ran on a Play Console closed testing track. That is our own record of how these systems behave in practice, not a Google statistic, but it matches what Google's documentation describes: the requirement is written about Play Console testing tools only.

None of this makes the account useless. It makes it a different tool. If you have already accepted that the closed test is coming, a limited distribution account is a clean way to put the build on real devices now instead of waiting for the Play Console side to be ready.

Play Console and limited distribution, side by side

One row in that table decides most of the conversations we have about this. Developers read "up to 20 authorized devices" and mentally convert it into 20 testers, then ask whether day one of a limited distribution pilot is day one of their 14 days. It is not, and the reason sits in the closed testing row rather than the reach row. Based on the questions developers bring to OnTesters' 1,500-plus closed-testing campaigns, the pattern is a consistent one: limited distribution gets discovered while someone is still avoiding the Play Console paperwork, and it stops being relevant the moment a store listing becomes the goal. The other thing our records keep showing is the arithmetic that causes the most avoidable restarts. A cohort recruited to exactly 12 that loses one person on day 9 costs the whole window, which is why the honest version of this table ends with the same advice every time: use the free account for the smoke test, then run the real clock on a closed testing track with a buffer above 12.

Why this question got loud in 2026

Limited distribution accounts did not appear in isolation. They are one piece of Android developer verification, which Google started rolling out to all developers on 30 March 2026 and which produced a user-facing deadline on 30 September 2026. From that date, app installations are checked against developer registration in four countries first (Brazil, Indonesia, Singapore and Thailand) across seven stores, including Google Play, Galaxy Store and GetApps, with the protections planned to expand to all certified Android devices globally in 2027 (Android Developers Blog, 30 March 2026, updated 29 September 2026).

Google justified the change with a security number: "over 90 times more malware from sideloaded sources than on Google Play". For the overwhelming majority of users nothing changed. The consequence lands on unregistered apps: they can no longer be installed normally and require ADB or the new advanced flow, which is Google's name for the hardened sideloading path aimed at power users.

For Play developers the deadline also had a Play-side bite. Google's Play Console Help states that "Effective September 30, 2026, all Play packages must be registered to meet Android developer verification requirements. Apps not registered by Sep 30, 2026 will be removed from Play pursuant to the Play Console Requirements policy" (Registering Play package names). Google auto-registered about 99% of Play apps using signing information developers had already provided.

The result is three similar-sounding things that developers keep collapsing into one. Identity verification is about who you are. Package registration is about which package name belongs to which signing key. Limited distribution is an account type for people who distribute only outside Play. If you publish on Google Play, Google's developer guide is explicit that "you must use the Play Console to manage your Play package names" (developer.android.com, updated 30 September 2026), and Google's guidance to Play developers is to handle registration inside Play Console, including for apps you also distribute outside Play, rather than opening an Android Developer Console account. Our explainer on device verification versus closed testing covers the identity half of this in more detail.

The package-name rules that catch people out

Two restrictions decide whether limited distribution is even available to you, and both are easy to miss.

First, the package name must be new. "You can only register new package names that have never been seen before on Android. If you attempt to register a package name that already exists on Android, you will receive an error and will not be able to register it" (same Google help page). If your app already has installs anywhere, this route is closed to you.

Second, the plan is permanent. "You can't change your plan once your Android Developer Console account has been created. If you need to change plans in the future, you'll need to create a new account and transfer your package names" (Choose a distribution). A student who later turns a project into a business does not upgrade; they start over with a new account.

What about the reverse direction, starting under limited distribution and then going to Google Play? Google's Play Console guide says a name used outside Play is not lost: "If you have been using the name outside of Google Play, you can still use it on Google Play" (developer.android.com). That sentence sits in the Play Console registration documentation rather than in the limited distribution documentation, and Google publishes no step-by-step for transferring a limited distribution registration itself. Our reading is that the portable thing is the package name and the signing key, not the account: when you create the app in Play Console, Play registers the package name against your signing key as it does for any new app. Treat that as an interpretation to confirm in your own Play Console, not as a documented migration path.

How device authorization works

Because this account type has no store, every install is an explicit handshake. On the Devices page of the Android Developer Console you add a friendly name for the device, then generate an authorization code. If you hold the phone, you scan a QR code. If you do not, you send a link, and the person on the other end generates the code themselves. Google notes that the request "will include your developer name, and the user will be asked to confirm that they personally know and trust you as a developer before the code is generated", and that shared authorization links expire after 7 days.

Three practical consequences follow. The 20-device ceiling is 20 devices at any one time, not 20 installs in total: removing a device frees a slot, but that device "will no longer be able to install or receive updates" until it is authorized again. Unauthorized devices cannot install or update the app at all, which means you cannot simply hand a download link to a 21st person. And someone has to be physically holding each device at the moment the code is generated, which is the step that generates the most back-and-forth if you are coordinating a pilot remotely.

On the hardware side nothing exotic is required, but the gap between devices matters more than it looks. Our own closed-testing campaigns run on physical Samsung, Pixel, Xiaomi and OnePlus hardware across Android 11 to 15 in more than 80 countries, and the device-to-device differences that surface in the first hour of a real install are exactly what a two-phone smoke test will not show you.

Who it is for, and who should take the Play path instead

Google's stated audience is students and hobbyists, and the account fits three honest use cases. A class project or portfolio app shared with a supervisor and a handful of classmates. An internal tool for a small team that will never be published. A private pilot with people you know personally, while you decide whether the app is worth taking through the full Play process.

It is the wrong tool in four situations. If you want a Play listing, nothing here substitutes for it. If you need more than 20 users, the ceiling is hard. If your package name already exists on Android, registration will fail. And if the reason you are looking at limited distribution is to skip the 12-tester requirement, the plan does not survive contact with Play Console: the 14 days run on a closed testing track or they do not run.

For developers building with AI tools, there is a sensible sequence here. Putting the app on a few real phones through a limited distribution account is a legitimate way to find the embarrassing first-run problems before the store listing exists, and it costs nothing but the package name decision. Then open the Play Console account, complete device verification, and start the 14 days with a proper cohort. We covered why the requirement does not care who wrote your app in do I still need 12 testers if my app was built with AI, and the same logic applies here: the common questions around hitting 12 testers include the ways people hope to get around the rule.

If Play is the destination, the path is the same one it has been since the rule changed. A US$25 personal or organization account (see how to create a developer account in 2026 and whether personal or organization accounts suit you), identity and device verification, a closed test with at least 12 testers opted in continuously for 14 days, then a production access application. Recruit more than 12. The posts above and the new-developer requirements guide walk the gates in the order they bite, and where to find Android app testers covers the cohort problem. Google does not prohibit paying testers, but the application asks about engagement, so a bought list that installs once is a worse outcome than a smaller group that actually uses the app.

Frequently asked questions

Is a limited distribution account really free?

Yes. Google describes it as "completely free" with no registration fee, no US$25 charge and no government ID requirement. You still need a Google Account, 2-Step Verification and a linked Google payments profile, which is used for your legal name and address rather than for billing.

Can I publish to Google Play with a limited distribution account?

No. It is an Android Developer Console account for distribution outside Google Play. There is no store listing, no closed testing track and no production access to apply for. Google Play publishing requires a Play Console account.

Does limited distribution count toward the 12-tester requirement?

No. The requirement is written about Play Console testing tools: at least 12 testers opted in continuously for at least 14 days on your closed test. Google documents no credit for devices authorized in the Android Developer Console, and the two systems track different things.

How many devices can I authorize?

Up to 20 at any one time. Reaching the limit means removing a device before adding another, and a removed device can no longer install or update the app until it is authorized again.

Can I use limited distribution for an app I have already published?

Only if its package name has never been seen before on Android. Google states that registering an existing package name in a limited distribution account will fail with an error. Existing apps belong on the full distribution or Play Console side, where signing-key ownership is what proves the package is yours.

Can I upgrade a limited distribution account later?

Not in place. Google says the plan cannot be changed after the account is created, and that changing plans means creating a new account and transferring your package names. If growth is even plausible, start where you intend to end up.

Do my testers need to install anything special?

They need to authorize their device first, by scanning a QR code or generating a code from a link you send, and confirm that they know and trust you as the developer. Authorization links expire after 7 days, so an unused link means starting that step again.

Sources

All links checked live on 22 October 2026. These are the pages we would re-check first if anything here has moved: the limited distribution account page for what the free account gives you, the app testing requirements page for what Google Play still asks for, and the verification rollout post for the enforcement timeline. Google edits these pages in place rather than renaming the URLs, so if a sentence quoted above disagrees with the live page, the live page wins. We re-open every link and re-check the quotes against what is actually published that day whenever this article is updated.

• Limited distribution accounts in Android Developer Console, Android Developer Console Help
• Choose a distribution, Android Developer Console Help
• Get started with an Android Developer Console account, Android Developer Console Help
• Registering Android package names, Android Developer Console Help
• Register for limited distribution on Android devices, Android Developers
• Register on Google Play Console, Android Developers
• Android developer verification: Building a safer ecosystem together, Android Developers Blog, 18 June 2026
• Android developer verification: Rolling out to all developers, Android Developers Blog, 30 March 2026
• App testing requirements for new personal developer accounts, Play Console Help
• Registering Play package names, Play Console Help