Google Play Console is where developers publish Android apps on Google Play and run them after launch: releases and testing tracks, the store listing, the policy declarations, ratings, reviews and statistics. A developer account costs a one-time registration fee of 25 US dollars. A new personal account must also verify an Android phone and run a closed test with at least 12 testers, opted in for 14 days in a row, before it can publish to everyone; an organization account proves who it is with a D-U-N-S number instead. Then every app follows the same path: create it, fill in its store listing and its policy declarations, upload an Android App Bundle, test it, send it for review, and publish.
This guide follows Google’s own help pages, quoted and linked, as read on 1 November 2026: what the account costs, which type to choose, how the closed test works, what the store listing needs, and what happens at review. Google’s menus move from time to time; the paths below are the ones its help gives today.
What is the Google Play Console?
Play Console is a website, at play.google.com/console, with a companion Play Console app for Android. One developer account holds all your apps, and each app has its own pages, grouped in a few sections of the menu:
- Dashboard: the setup tasks for a new app, and the button to apply for production access.
- Test and release: the Production track, the Testing tracks (internal, closed, open) and the Latest releases and bundles page.
- Grow users › Store presence › Store listings: your app’s name, descriptions, graphics, translations, category and contact details.
- Monitor and improve: ratings and reviews, testers’ feedback, and Policy and programs › App content, where the policy declarations live.
How much does a Google Play developer account cost?
Google charges once, when you sign up:
There is a US$25 one-time registration fee.
You pay it with a Mastercard, Visa or American Express card, a Discover card in the United States, or a Visa Electron card outside the United States. Google adds that it does not accept prepaid cards, and that card acceptance varies by location. Keep the card and an ID under your legal name: Google may ask for both to check your identity, and it warns that “if this information is determined to be invalid, your registration fee will not be refunded.”
Apple charges every year instead. Its Apple Developer Program, which you need to publish on the App Store, is “99 USD per membership year, or in local currency where available”, and eligible nonprofits, accredited schools and government entities can ask for a fee waiver. Our guide to the Apple Developer account covers Apple’s side.
| Account | Price | Paid |
|---|---|---|
| Google Play Console | US$25 | Once |
| Apple Developer Program | 99 USD | Yearly |
Then there is the fee on what you sell. Apps and in-app products sold through Google Play’s billing pay a service fee. Its rate depends on the kind of sale, and Google is rolling out updated rates region by region: from 30 June 2026 in the European Economic Area, the United Kingdom and the United States, and from 30 September 2026 in Australia and Japan. Most developers never pay it, because they sell nothing through Google Play:
97% of developers distribute their apps and take advantage of all Google Play has to offer at no charge.
If you do sell, read Google’s service fees page for your country before you set your prices.
Personal or organization account?
Google offers two types of developer account, and the choice changes what it asks of you.
Choose a personal account if your account is for personal use—for example, if you’re a student, hobbyist, or amateur developer.
A personal account can still earn money on Google Play, invite other people to the account and manage several apps. An organization account is for a business or another organization, and Google requires one for four kinds of apps: financial products and services (banking, loans, trading, investment funds, cryptocurrency wallets and exchanges), health apps, apps approved to use Android’s VpnService class, and government apps.
- Personal account: for students, hobbyists and amateur developers. Google may ask for an ID and a card in your legal name. Before the first public release, you verify an Android device, then run a closed test of 12 testers for 14 days.
- Organization account: for businesses and other organizations, and required for financial, health, VPN and government apps. Google may ask for the same ID and card, plus a D-U-N-S number for the organization. There is no closed-test requirement.
The D-U-N-S number comes from Dun & Bradstreet, and Google warns about paying for it:
Applying for a D-U-N-S number through Dun & Bradstreet is a completely free process.
How to sign up for Google Play Console
Google’s sign-up has six steps, the last one for personal accounts only:
- Use a Google Account, and be at least 18. You sign up from the Play Console sign-up page with that account.
- Accept the Google Play Developer Distribution Agreement.
- Pay the US$25 registration fee.
- Choose personal or organization.
- Verify your identity. What Google asks for depends on the account type, and you can add more account information later.
- Personal accounts: verify an Android device, then meet the testing requirement. You verify the phone from the Home page of Play Console, by scanning a QR code that opens the Play Console app, signed in as the account owner. Any non-rooted Android phone running Android 10 or later works, it can be one you already used for another account, and Google says it “should take less than a minute.”
The closed test: 12 testers for 14 days
This is the step that surprises most first-time Android developers. Since November 2023, a new personal account cannot publish an app to everyone until it has tested it:
Developers with personal accounts created after November 13, 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.
Until then, the Production track and pre-registration stay disabled. The four tracks open one after the other:
- Internal testing: up to 100 testers you list by email, who get new builds within minutes. You can use it any time, even before the app is set up.
- Closed testing: a group of testers you control, and the required test. It opens once the app’s setup is complete.
- Open testing: a test anyone can join from Google Play. It opens after you get production access.
- Production: your app, on Google Play, for everyone. It opens after a closed test that meets the rule, and Google’s approval.
“Continuously” is literal. A tester who opts out and comes back later starts their 14 days again, and testers who leave before 14 days do not count. Google suggests recruiting through friends, family, colleagues and classmates, and in the communities where your future users are, and telling every tester to stay opted in for the whole two weeks.
When 12 testers have stayed 14 days, you open the Dashboard, click Apply for production, and answer three groups of questions: about your closed test (how hard testers were to find, how they used the app, what they reported), about your app (its audience, what it offers, the installs you expect in its first year), and about your production readiness (what you changed after the test, and how you knew the app was ready). Then Google reviews the application:
Review usually takes seven days or less, but can occasionally take longer.
Google may ask you to keep testing, for example with fewer than 12 opted-in testers or testers who barely used the app. So count at least three weeks between the start of your closed test and a public release: 14 days of testing, then a review that usually takes up to seven. Accounts created before 13 November 2023 do not have this requirement.
Create your app in Play Console
In Play Console, Create app asks for:
- The app’s name, as it will appear on Google Play. You can change it later.
- A package name, the app’s permanent identifier. Choose it carefully: “Package names can’t be deleted or re-used.”
- A default language, whether it is an app or a game, and whether it is free or paid.
- A contact email that Google Play users can write to.
- Three declarations: the Developer Program Policies, US export laws, and the Play App Signing Terms of Service.
Then you upload builds as Android App Bundles, from which Google Play makes the APKs for each device. Every bundle carries a versionCode that must grow with each update and stay at or below 2,100,000,000, and must meet Google Play’s target API level requirements.
Your store listing: what people see, and what search reads
The store listing is shared by every track, testing tracks included. You fill it in under Grow users › Store presence › Store listings:
| Field or asset | Google’s limit |
|---|---|
| App name | 30 characters |
| Short description | 80 characters |
| Full description | 4,000 characters |
| App icon | 512 × 512 px, 32-bit PNG with alpha, up to 1,024 KB |
| Feature graphic | 1,024 × 500 px, JPEG or 24-bit PNG |
| Screenshots | Up to 8 per device type; 320 to 3,840 px, the long side at most twice the short one |
To show up in the large recommendation formats of Google Play, an app needs at least four screenshots of 1,080 px or more, in 16:9 or 9:16 (every size for both stores is in App Store screenshot sizes). If you don’t translate your listing, Google Play shows people an automated translation, with a note saying so, or your default language.
These fields are also what Google Play search reads, since Play has no keyword field. Google’s advice for the title is short:
Your title should be unique and accessible, avoid common terms, and reinforce what your app is about.
Its warning about stuffing keywords is just as clear: “Repetitive or irrelevant keyword usage in your app name, short description, or full description can create an unpleasant user experience and result in app suspension.” How search uses each field, and what Google keeps secret, is in our guide to Google Play search ranking.
App content: the declarations before review
Under Policy and programs › App content, Play Console lists the declarations your app needs before Google reviews it. The main ones:
- A privacy policy, for every app. Google is explicit: “You must link to a privacy policy on your store listing and within your app, even if your app doesn’t access personal or sensitive user data or target children.”
- Ads: whether your app shows ads, including through third-party SDKs. If it does, your listing shows a “Contains ads” label to every user.
- Content rating: a questionnaire that gets your app its ratings from the official rating authorities.
- Target audience and content: the age groups your app is for. If they include children, Google Play’s Families policy applies.
- App access: if part of the app needs a login, working credentials for the reviewers.
The App content page sorts them into what needs your attention and what you have already declared, and Google asks you to keep them up to date as your app changes.
Send for review, then publish
Changes that Google must review, a new release, a listing change or a declaration, wait on the Publishing overview page until you click Send for review. By default, they go live as soon as Google approves them:
The changes will be published automatically as soon as they’re reviewed and approved by Google unless managed publishing is turned on.
With managed publishing on, approved changes wait until you publish them, which helps when a release must go out with a launch or a campaign. After publishing, Google says it can take a few hours for the changes to show on Google Play. And publishing is close to permanent: an app that people have installed can’t be deleted, only unpublished, because they keep the right to reinstall it.
After launch: experiments, and your ranks
Play Console can test your listing on real visitors. For each app, you can run one default graphics experiment, on the icon, feature graphic and screenshots in your default language, or up to five localized experiments at the same time, which can also test your descriptions, and Play Console compares the variants on installs. Play Console also shows which searches brought people to your listing, as our guide to ASO keyword research explains.
What it does not give is where your app ranks for each search, in each country, from one day to the next. Ranks move with the country, the language and the day, so read them over several days, as our guide to checking a keyword ranking shows, and compare the weeks before and after any change to your listing before you decide it worked.
What to do
- Pick the account type first: personal if you are on your own and your app isn’t financial, health, VPN or government; organization otherwise, with a free D-U-N-S number.
- Pay the US$25 fee with a card in your legal name, never a prepaid one.
- Personal account: verify an Android phone, and line up at least 12 testers before you need them.
- Choose your package name once. It can never change.
- Start an internal test as soon as you have a build, then a closed test as soon as the app setup is complete, and keep your 12 testers in it for 14 days without a break.
- Write the listing for people and for search: 30, 80 and 4,000 characters, no keyword stuffing, translated where you sell.
- Complete App content, privacy policy included, before you send anything for review.
- After launch, test the listing with experiments, and measure your ranks per country before and after each change.
Sources
- Google, Play Console Help, Get started with Play Console: age, the Developer Distribution Agreement, the US$25 fee and the cards accepted, identity checks.
- Google, Play Console Help, Choose a developer account type: personal and organization accounts, the apps that need an organization, the D-U-N-S number.
- Google, Play Console Help, Device verification requirements for new developer accounts: the Android phone, Android 10 or later.
- Google, Play Console Help, App testing requirements for new personal developer accounts: 12 testers, 14 days, the tracks, applying for production, the review time.
- Google, Play Console Help, Set up an open, closed, or internal test: internal tests of up to 100 testers.
- Google, Play Console Help, Create and set up your app: creating an app, package names, versionCode, the store listing’s character limits, automated translations.
- Google, Play Console Help, Add preview assets to showcase your app: icon, feature graphic and screenshots.
- Google, Play Console Help, Get discovered on Google Play search: the title.
- Google, Play Console Help, Prepare your app for review: the App content page, privacy policy, ads, content rating, target audience.
- Google, Play Console Help, Control when app changes are reviewed and published: Publishing overview and managed publishing.
- Google, Play Console Help, Publishing issues: the hours before changes show, unpublishing instead of deleting.
- Google, Play Console Help, Run A/B tests on your store listing: default graphics and localized experiments.
- Google, Play Console Help, Service fees: the service fee and the 97%.
- Apple, Apple Developer, Membership Details: the Apple Developer Program’s yearly fee and fee waivers.
Checked on 1 November 2026.