Can You Publish an Android App for Free in 2026?

Ask an AI assistant whether you can publish an Android app for free and you will usually get the 2023 answer: pay $25, upload, done. That answer is now wrong in both directions. There is a genuinely free Android developer account in 2026, and it genuinely cannot put your app on Google Play. This post maps the two consoles and the three distribution paths Google now offers, what each one costs, what each one unlocks, and the traps between them. Where Google's own pages currently contradict each other, and on two points they do, we show you both sides instead of picking the convenient one.

What are the three Android publishing paths in 2026?

The comparison, row by row

Read this once and most of the confusion on this topic disappears. The filter hides the two rows where all three paths behave identically, so you can see only the decisions that actually matter.

Two consoles, one verification story

If you already have a Play Console account you do not need a second console just because you also ship your app somewhere else. Google's verification FAQ points existing Play developers at Play Console as the single place to manage their verification requirements. The Android Developer Console exists for developers who are only ever distributing outside Play, which is why its help pages never mention store listings, reviews or production tracks. That silence is not an oversight. It is the product boundary.

One more thing worth pinning down before the detail: the closed-testing rule people are trying to escape belongs to Google Play, not to any of these accounts. It applies to personal Play accounts created after November 13, 2023, and no amount of account shopping in the other console removes it.

What does the free account actually get you?

The number everyone quotes is 20. The number almost everyone misreads is also 20. It is not 20 installs, not 20 users per app, and not 20 downloads before the account locks. It is 20 device slots that exist at the same moment, and every one of them is filled by hand. Fill them, empty them, refill them: try it.

Included, and not included

Google's own words

Short quotations, each with the help page it came from, so you can check every one of them yourself rather than trusting a summary. We have deliberately not stitched these into a single sentence Google never wrote.

Short quotations from Google's current help pages, retrieved August 9, 2026. Full links are at the end of this post.

Does the free account require your ID?

This is the row of the story that gets flattened fastest. A forum post says "no ID", a summary turns that into "no verification", and by the third retelling it has become "an anonymous developer account". Here is the actual ledger, in the order the signup asks for it.

• 01 A Google Account The account that will own the Android Developer Console account. Choose it deliberately, because it becomes the identity behind everything you register. Required
• 02 2-Step Verification Turned on for that Google Account before you start the signup. Required
• 03 A linked Google payments profile It has to carry your current legal name and address. Nothing is charged, but the identity information is still collected. Required
• 04 Contact details The Limited Distribution page lists a contact email. Google's general Android Developer Console page says every ADC account needs a verified email address and a verified phone number, so plan for both. Required, wording varies
• 05 A government-issued ID This is the change. Google states that Limited Distribution developers do not need to provide a government ID, which is exactly what the paid tiers do ask for. Not required

For the two paid accounts the picture is heavier, not lighter. A Play Console account can be asked for a government ID and a credit card in your legal name. Full Distribution on the Android Developer Console asks for identity verification with official documents, and an organization going that route needs a D-U-N-S number, which Google says can take up to 30 days to obtain. That is a planning number, not a formality: start it before you need it.

How do you create a Limited Distribution account?

Register the package name

Authorize each device

Authorization is deliberately manual. The flow Google documents authorizes devices one at a time, and every one of them needs the device itself to produce a code, so there is no "anyone with the link" mode and no way to pre-authorize a device nobody is holding.

1. 01 Name the device A friendly name so you can tell slot 7 from slot 14 later.
2. 02 QR code or shared link Scan it on the device, or send the link to the person holding it. Link expires in 7 days
3. 03 The device returns a code Unique to that device. The user is asked to confirm they know and trust you.
4. 04 Select Add device Enter the code in the console and the slot is filled.

Remove a device and it can no longer install or receive updates until you authorize it again. That is the trade for a free 20-slot account: the slot is reusable, the access is not automatic. It also means the free tier is a poor fit for a fleet you do not control, because every replacement phone is a fresh round of this exchange.

Has the free account launched everywhere yet?

That gap is worth naming plainly rather than resolving for you. The product-specific page is the more precise source and it says the accounts are open to everyone; the sibling page that helps you choose between plans has not been updated to match. Both were live on August 9, 2026. Neither one publishes a launch date, so any article that gives you a specific day in August is filling in a blank Google left empty.

Check it yourself in about a minute

• Open the Android Developer Console signup.
• Choose the Personal account type.
• Look for Limited Distribution in the distribution choice. If it is not offered, the rollout has not reached your account yet.

That is a better test than any article, including this one. Staged rollouts are normal, and Google's help pages have historically been updated after the product rather than before it. If the option is missing today, nothing is wrong with your account.

Checked August 9, 2026, during the announced launch month. If you are reading this later, the live console is the authority, not this page.

Does the free account skip the 12-tester closed test?

This is the hope behind a lot of the searches that land here, so it is worth being blunt. The requirement is not attached to the price of your account. It is attached to publishing on Google Play from a qualifying personal developer account, and Google words it like this:

Nothing in that sentence mentions the Android Developer Console, because the two systems do not touch. Google's current Help page scopes the requirement to qualifying personal developer accounts created after November 13, 2023, and Google reduced the count from 20 testers to 12 on December 11, 2024. If an article still tells you 20, it predates the change; the 20 to 12 story is here.

Which tracks count toward production access

Where these live: closed testing is at Play Console › Testing › Closed testing › Manage track, and the application itself is at Play Console › Dashboard › Apply for production. Google says that review usually takes 7 days or less, though it can take longer.

Internal testing does not count

Play internal testing supports up to 100 testers and it is genuinely useful. It is the fastest way to get a build onto real devices and shake out the crashes you would rather not show 12 strangers. It is simply not the track Google names in the production-access requirement. Google specifies a closed test, so a flawless 14 days of internal testing leaves the gate exactly where it was. Every year a batch of developers discovers this on day 15.

Why people expect it to count

Both things look like "a small group of people testing my app", so the confusion is fair. The difference is where the install happens. Play counts testers who opted in through a Play testing track attached to your Play listing. Limited Distribution installs happen outside Play entirely, on devices you authorized by hand. Two systems, two records, no overlap, and no mechanism by which one could report to the other. If you want the full mechanics of the test itself, the 12-tester requirement is covered here.

Can you upgrade from Limited to Full later?

The practical read: Google clearly intends one-way migration to exist, and the FAQ is the newer statement of intent. But intent is not a workflow. Until a migration path is visible in the product, treat a Limited account as a commitment to the 20-device world, and pick Full from the start if you can already see yourself outgrowing it.

What if you later want Google Play?

Then you are not upgrading at all. You are opening a different account in a different console, and the two roads never merge.

An Android Developer Console account does not become a Play Console account at any tier. Package transfers between ADC accounts need both accounts verified and in good standing, plus your signing key and package details. A one-click conversion from a Limited ADC account into a Play Console account is not something Google documents anywhere we could find, so budget for creating the Play account properly, including the $25 and everything that follows it.

Which account do you actually need?

The four questions

Nine situations, and the account each one needs

If you would rather not tap through the questions, find yourself in this list. The logic is identical.

Eight claims about the free account, checked

Twelve symptoms, and the actual fix

If you are already mid-problem rather than mid-decision, find your sentence in the left column.

Which 2026 dates actually affect you?

1. Nov 13, 2023 The Play closed-testing gate starts applying Personal Google Play accounts created after this date. Older accounts and organization accounts are outside the rule as Google words it.
2. Dec 11, 2024 The qualifying tester count drops from 20 to 12 Anyone reading an article that still says 20 is reading something written before this date.
3. July 2026 Limited Distribution early access Selected early-access developers only.
4. August 2026 Limited Distribution documented as available for everyone Students, hobbyists and other eligible personal users. Google announced the month, not a day, and as of August 9, 2026 its own pages are still not synchronized on whether the rollout is finished.
5. Aug 31, 2026 New apps and updates on Google Play must target API 36 Every Play publisher. Wear OS and Android Automotive sit at API 35, Android TV and Android XR at API 34. An extension is available to some developers but it is not automatic.
6. Sept 30, 2026 Developer verification enforcement begins Apps installed through participating stores on certified devices in Brazil, Indonesia, Singapore and Thailand. Not worldwide, despite how it is usually summarized, and Google's FAQ says this first phase does not yet reach direct sideloading or stores outside that list.
7. Oct 28, 2026 The Contacts Permissions policy takes effect Apps targeting Android 17 (API level 37) or higher that request broad contacts access. Narrow scope, frequently misquoted.
8. Nov 1, 2026 End of the extension window for the API 36 requirement Developers who were granted the extension. It is not automatic for every case.
9. 2027 onward Verification protections expand globally The wider certified-device ecosystem, on Google's announced timeline.

Where PrimeTestLab fits in all this

Choosing an account is the easy half of this page. Finding 12 real people who will install your app, opt in, and stay opted in for 14 unbroken days is the part that stalls launches for weeks. That is the gap we fill: verified testers on real devices spanning Android 7 to 17, opted in for the full window, so the calendar stops being the thing standing between you and production access.

Frequently asked questions

Bottom line