Knowing how to create a Google Play developer account is the first step for anyone preparing to publish an Android app. The process looks simple, but in recent years Google has tightened identity verification and added testing requirements for new accounts. This guide walks through choosing an account type, verification, the closed testing rule and preparing your first release.
Google Play policies change often. Everything below reflects the situation at the time of writing, so always confirm the current requirements in the Play Console Help Center before you apply.
Personal or Organization Account?
| Criteria | Personal account | Organization account |
|---|---|---|
| Best for | Individual developers and side projects | Companies, agencies, institutions |
| Verification | Government ID of the account owner | Company details and a D-U-N-S number |
| Name shown on the store | Developer name; some contact details may be public | Company name |
| New account testing rule | Closed testing required before production access | At the time of writing, not applied to organization accounts |
If you are publishing on behalf of a business, an organization account is almost always the right choice. Transferring apps from a personal account later is possible but adds work.
What You Need Before You Start
- A Google account controlled by the company, with two-step verification enabled.
- A one-time $25 registration fee; there is no annual renewal.
- A card that supports international payments.
- A government ID (personal accounts) or a D-U-N-S number (organization accounts), which Dun & Bradstreet issues free of charge.
- A verifiable phone number, email address and, for organizations, a website.
The same D-U-N-S number is also used for an Apple organization account; see our guide on how to open an App Store developer account.
Steps to Create a Google Play Developer Account
- Go to play.google.com/console and sign in with the Google account you will use.
- Choose whether the account is for yourself or for an organization.
- Enter your public developer name, contact email and phone number.
- For organizations, enter the D-U-N-S number, address and website exactly as they appear in the D-U-N-S record.
- Accept the Developer Distribution Agreement and pay the $25 fee.
- Complete identity and contact verification. Review can take several days.
The most common cause of delay is a mismatch between the company name or address entered and the D-U-N-S record.
The Closed Testing Requirement for New Personal Accounts
Google restricts new personal developer accounts from publishing directly to production. At the time of writing the rule was:
- Publish your app to a closed testing track first.
- Have at least 12 testers (reduced from an earlier 20) opted in for at least 14 consecutive days.
- Then apply for production access in Play Console and answer questions about your test.
These numbers have changed before and may change again, so rely on what Play Console shows for your account. Recruit testers who will genuinely use the app, ship at least one update based on their feedback, and include this two-week window in your launch plan.
Preparing Your First Release
- Store listing: name, short and full description, icon, feature graphic and screenshots.
- Content rating: complete the questionnaire.
- Data safety form: declare what data you collect and why, with a privacy policy link.
- Target audience and ads declaration.
- Target API level: new apps and updates must target a recent Android API level.
- Android App Bundle: new apps are uploaded as AAB with Play App Signing.
Your data safety answers must match the app's real behavior, including third-party SDKs. Planning this early in mobile app development avoids last-minute surprises.
Common Mistakes
- Registering a company app under an employee's personal Google account.
- Setting a launch date without accounting for closed testing.
- Starting the release process without a privacy policy page.
- Not storing signing keys securely.
Account security and team access
Your developer account is the key to every app you publish. Invite team members with their own Google accounts and only the permissions they need, enforce two-step verification, and if you work with an agency, keep the company as account owner and give the agency user access. Back up your upload key securely and keep contact emails current, since Google sends time-sensitive policy warnings by email.
We handle Google Play and App Store releases for our own products too; see them on our apps page. If you need help with account setup, closed testing or building and launching your app end to end, contact BernSoftware.
Frequently asked questions
How much does a Google Play developer account cost?
There is a one-time registration fee of 25 US dollars. Unlike Apple's program, there is no annual renewal.
How long does Google Play account verification take?
Verification usually takes a few days but can take longer if documents do not match. Organization accounts should also allow time to obtain a D-U-N-S number.
Do organization accounts need closed testing too?
At the time of writing, the closed testing requirement applied to newly created personal accounts. Rules can change, so follow the requirements Play Console shows for your account.
Planning a project like this?
Plan it in 10 steps