Google Play Developer Account: 2026 Setup Guide

To create a Google Play developer account, sign in to Play Console with a Google Account, accept the Developer Distribution Agreement, pay the one-time US$25 registration fee, choose a personal or organization account, and complete identity and contact verification. If you choose a personal account, plan for one more step before launch: new personal accounts must run a closed test with at least 12 testers for 14 days before they can publish to production.

This guide walks through each step, compares the two account types side by side, and explains what happens after signup so you are not surprised a month later.

What you need before you start

According to Play Console Help, you need the following before you open the signup page:

• A Google Account. Many developers create a dedicated one for publishing rather than using a personal Gmail they share with family devices.
• Age 18 or older. Google states you must be at least 18 to sign up for a Play Console account.
• A payment card for the US$25 fee. It is a one-time fee, not annual. Prepaid cards are not accepted.
• Identity documents. You may be asked for a government ID and a credit card, both under your legal name.
• A working email and phone number you can verify with a one-time code and keep active for as long as the account exists.
• For personal accounts: an Android device, because new personal accounts must verify access to a real Android device through the Play Console mobile app.
• For organization accounts: a D-U-N-S number for your business.

One warning from Google that is worth reading twice: if the identity information you submit is judged invalid, the registration fee is not refunded. Use your real legal name exactly as it appears on your documents and payments profile.

Step-by-step: creating the account

1. Go to Play Console signup and sign in with the Google Account that will own the developer account.

2. Choose your account type: Personal or Organization. This choice matters later (see the comparison below), so decide before you pay.

3. Accept the Google Play Developer Distribution Agreement.

4. Pay the US$25 registration fee.

5. Fill in your developer profile: developer name (shown on Google Play and changeable later), legal name and address (pulled from your linked Google payments profile), contact email, contact phone, and developer email.

6. Verify your email addresses and phone numbers with the one-time codes Google sends.

7. Complete Google Play developer verification of your identity. Depending on your situation, this can involve uploading a government ID.

8. For personal accounts, install the Play Console app on an Android phone and complete device verification.

Google does not publish a fixed verification time, so start early. You can explore Play Console while verification is pending, but you cannot publish until it is complete.

Personal vs organization account

Play Console Help says both account types have the same functionality and both can earn money on Google Play with a payments profile. The differences are in who the account is for, what you must verify, what is shown publicly, and what you must do before your first production release.

When an organization account is expected

Google says you should choose an organization account if you provide financial products or services (banking, loans, stock trading, crypto wallets or exchanges), health apps such as medical apps, apps approved to use the VpnService class, or government apps. If your app falls into one of these categories, a personal account is the wrong choice regardless of convenience.

About D-U-N-S verification

A D-U-N-S number is a nine-digit business identifier from Dun & Bradstreet. Google uses it to verify organization accounts, and without one you cannot create an organization account. Getting a D-U-N-S number from Dun & Bradstreet is free; Google explicitly warns about third-party services that charge a fee for it. The process can take a while, so request it before you plan to register.

Which one should a solo developer pick?

If you are an individual without a registered business, the personal account is the realistic option. It is quicker to set up and has no D-U-N-S step. The trade-off is the testing requirement covered in the next section, plus the fact that your legal name and country are displayed on your developer page.

If you already run a registered company, an organization account avoids the closed-testing gate entirely and shows your business details instead of your personal name. It just takes longer to set up.

What happens next for personal accounts

This is the part many first-time developers miss. If you create a personal account (after November 13, 2023), you cannot go straight from uploading an app to a public release. Play Console Help states that you must:

1. Run a closed test with at least 12 testers who have been opted in continuously for at least 14 days.

2. Apply for production access from the Dashboard, answering questions about your closed test, your app, and your production readiness.

3. Wait for Google's review of that application, which usually takes seven days or less, though it can take longer.

Only then can you publish to the production track. Open testing also becomes available only after you gain production access, so it is not a shortcut.

The details of that rule, including what counts as an opted-in tester and what resets the 14 days, are covered in Google Play 12 testers, 14 days rule explained. For a realistic schedule from signup to launch, see closed testing to production timeline.

Organization accounts are not subject to this testing requirement. If you register as an organization, you can set up your app and submit a production release directly.

Common account setup problems

The fee was charged but verification failed

Google says the fee is not refunded if the information you provided is judged invalid. Double-check that your legal name, address, and ID all match before submitting.

Wrong account type

Pick carefully at signup. If you realize later that you need the other type, check the current Play Console Help guidance on changing account types before creating a second account, since running duplicate accounts can create policy problems of its own.

Phone or email stops working

Google requires your verified contact email and phone to remain operational for the lifetime of the account. If you change numbers, update and re-verify in Play Console instead of letting it lapse.

No Android device for device verification

New personal accounts need a real Android device to complete verification through the Play Console app. An inexpensive Android phone is enough.

Where Doply fits

Doply is only relevant if you chose a personal account and are facing the 12-tester closed test. Doply provides at least 14 testers (usually 16) on real Android devices, keeps the test running for 18 days to leave a buffer beyond the required 14, and drafts answers for the production application, for $6.99 per app plus tax. It cannot guarantee Google's approval. Setup requirements are in the Doply docs.

FAQ

How much does a Google Play developer account cost?

US$25, paid once at registration. There is no annual renewal fee for the developer account itself.

What is the difference between a Google Play personal and organization account?

Both have the same Play Console features and can earn money. Organization accounts require a D-U-N-S number and business contact details, and are expected for categories like finance, health, VPN, and government apps. Personal accounts created after November 13, 2023 must complete a 12-tester, 14-day closed test before production; organization accounts do not.

Do I need a D-U-N-S number for a personal account?

No. A D-U-N-S number is required only for organization accounts.

How long does Google Play developer verification take?

Google does not publish a fixed time, and it varies by account. Start it as soon as you register so it does not block your first release.

Can I publish immediately after creating a personal account?

Not to production. You can upload builds and use internal and closed testing, but production access requires the 12-tester, 14-day closed test and an approved application first.