How to Create a Google Play Developer Account in 2026

Creating a Google Play developer account in 2026 takes six steps: sign up with a Google Account you are at least 18 to use, accept the Developer Distribution Agreement, pay a US$25 one-time registration fee, choose between a Personal and an Organization account, verify your contact details and identity, and, on a Personal account, clear the Android device check and the closed-testing requirement before your app can appear on Google Play.

Google publishes that sequence in its Get started with Play Console article, and the order matters more than any individual step. Each verification has prerequisites, and the account type you choose in step four decides what you are asked to prove in step five. This guide follows Google's sequence step by step, states what each stage asks for, and flags the two places where developers lose days rather than minutes.

What to have ready before you start

Almost everything that slows a signup down is a missing document, not a broken form. Google collects the items below during registration or in the verification tasks that follow it, and it links every legal detail back to one record: the Google Payments profile you create or select while signing up.

Two of those rows cannot be rushed. If you are registering an Organization and do not yet have a D-U-N-S number, Google says the application through Dun & Bradstreet is free but "can take up to 30 days", and that you will not be able to create the account without one. If your payments profile needs a bank account verified, Google publishes that part at up to 5 days. Everything else in the sequence is in your hands on the day you start.

The six steps of Play Console signup, in Google's order

Step 1: Sign in with the Google Account that will own the developer account

Google's first step is a single instruction: using your Google Account, sign up for a Play Console developer account. The signup flow opens from the link in Google's own article, and the page behind it asks you to sign in before anything else. Two rules attach to this moment. You must be at least 18 years of age to sign up for a Play Console account, and the Google Account you sign in with is the one that owns the developer account afterwards.

There is no separate developer login. The Google Account you already use is the credential, and it becomes the account that owns the developer account, so sign in deliberately: in the browser profile you intend to publish from, not in whichever session happened to be open. The account-type decision that follows is the harder one to reverse, and it is covered in the FAQ below.

Step 2: Accept the Developer Distribution Agreement

During the signup process you review and accept the Google Play Developer Distribution Agreement. This is the contract that governs how you distribute apps and games through Google Play, including payments, takedowns, and termination. It is a legal document rather than a settings screen, and accepting it is a precondition of the account, not an optional acknowledgement you can skip and return to.

In practice this step costs a few minutes. Read it once with two questions in mind: what obligations you are accepting about the apps you publish, and what happens to your account and your apps if those obligations are breached. Everything later in the console, including the right to distribute at all, sits downstream of this agreement.

Step 3: Pay the US$25 one-time registration fee

Google charges a US$25 one-time registration fee. Its article lists the accepted cards as MasterCard, Visa, American Express, Discover in the United States, and Visa Electron outside the United States, and states plainly that prepaid cards are not accepted, with accepted types varying by location.

Two lines on the same page are worth reading before you enter anything. Google says that to process your request you may be asked for a valid government ID and a credit card, both under your legal name, and that if this information is determined to be invalid, your registration fee will not be refunded. The card and the ID are being compared against each other, so the name on the payment must be the name on the document.

The fee itself raises its own questions: what it covers, what it does not, and how it compares with the cost of the testing that follows. Our breakdown of what the $25 actually covers handles that separately, because on a new account the fee is the only charge Google makes and the expensive outcome is a restarted 14-day clock, not a price rise.

Step 4: Choose between a Personal and an Organization account

Google Play offers two developer account types, Personal and Organization, and states that both have access to the same functionality and both can monetize using a payments profile. Personal suits a student, hobbyist or amateur developer. Organization is for an organization or business, for example where you are engaged in commercial, industrial, professional, or governmental activities.

Four categories make the decision for you. Google says you should choose an organization account if you provide financial products and services, health apps such as medical and human subjects research apps, apps approved to use the VpnService class, or government apps developed by or on behalf of a government agency. Its Play Console Requirements policy repeats the same four as mandatory, so this is not a preference you can override at signup.

Organization accounts also need a D-U-N-S number before you can complete the account information step. Google calls it a mandatory requirement for verifying your organization, applies for free through Dun & Bradstreet, and warns about third-party services that charge for that free registration.

The account type does more than set your paperwork. It decides whether the 12-tester, 14-day closed test applies to your apps at all, which is the single largest difference between the two routes. We cover that trade-off in does an organization account skip the 12-tester rule.

Step 5: Verify your contact details and identity

Google collects two different sets of information from new developers, and confusing them is the most common reason the console looks confusing. The first set is a private contact email address and phone number that Google uses to contact you about your developer account; these are not shown to users. The second is the developer information that appears as your public profile on Google Play. Your legal name and legal address come from the Google Payments profile you linked during account creation, and all of it is verified with a one-time password.

What you are asked for depends on the type you chose in step four. For a Personal account whose payments profile has not been verified, Google asks for an official government identity document. For an Organization account, it asks for a D-U-N-S number unless the account is for a known government organization or agency, an official government identity document, and an official organization document.

The rule that catches people is exactness. Google states that all submitted documents must exactly match the information in your payments profile, and that if it detects mismatches you will receive an email and a Play Console banner telling you to fix them by a deadline. Correct the payments profile rather than submitting a differently-spelled document again. Google's own organization verification guide puts it bluntly: providing unsupported documents is the main reason for verification issues, and providing modified or fake documents can lead to the immediate removal of your account and apps.

What ends up public differs by type. For a Personal account Google displays your legal name, your country as per your legal address, and your developer email address; if you monetize, it displays your full address. For an Organization account it displays your legal name, legal address, developer email address and developer phone number, which is why Google asks organizations to use an official address rather than a generic or personal one.

Step 6: Device verification and testing requirements (Personal accounts only)

Google's own sequence labels this "(Personal accounts only) Step 6", and it has two halves. The first is device verification: new Personal accounts must verify that they have access to a real Android mobile device using the Play Console mobile app before they can make an app available on Google Play. Google requires any non-rooted physical Android mobile device running at least Android 10, and says the verification itself should take less than a minute. You find the task on the Play Console Home page, scan the QR code to open the Play Console mobile app, sign in as the account owner, select the account and tap Verify. One eligible device can verify multiple developer accounts, and the phone number of the device you use is not collected as part of the check.

The second half is the testing requirement. Developers with personal accounts created after November 13, 2023 must run a closed test with a minimum of 12 testers who have been opted in for at least the last 14 days continuously before the app is eligible for distribution. Until that is met, Play Console disables Production and Pre-registration for the account. We look at what that date decides in the next section.

From our side of this step: OnTesters runs closed tests on physical Samsung, Pixel, Xiaomi and OnePlus devices, on Android 11 through Android 15, across more than 80 countries, and our own records cover over 1,500 closed-testing campaigns. The device question shows up twice on Google Play. Once at signup, when a Personal account has to prove it controls real hardware, and again when your testers have to install your build on their own phones. One current non-rooted Android handset settles the first. It does nothing for the second, which is where most launch timelines actually slip.

Why phone verification will not move until identity and device verification clear

The phone number step looks like one of the first things you would do in a signup form, and on a Play Console developer account it is one of the last. Google's verification article states the dependency directly: before you can verify your developer phone number you must complete identity verification, website verification for organization accounts, and device verification for individual accounts. Phone number verification cannot proceed until those prerequisites are met, and Google tells you to check the Play Console home page to see any pending verifications.

So a stuck phone field is not a signal that your number is wrong. It means an upstream task is still open. The practical order is: clear identity verification first, clear the device task if you are on a Personal account or the website task if you are on an Organization account, then return to the phone number.

What your account's creation date decides

Google introduced the testing requirement in November 2023, and it applies to developers with personal accounts created after November 13, 2023. The date is attached to the account, not to the app. A new app added to an existing qualifying account inherits the same obligation, and the account's creation date is fixed from the moment you complete signup.

For anyone creating an account now, the consequence is straightforward: a Personal account created today was created after November 13, 2023, so the requirement applies to it by default. The question is not whether you fall inside the rule but how you plan the two weeks it takes to clear it. Google's article states that a minimum of 12 testers must have been opted in for at least the last 14 days continuously, and that when you meet the criteria you can apply for production access on the Dashboard in Play Console. When you apply, you must answer questions about your app, its testing process, and its production readiness.

Two Play Console features tell you where you stand before you go looking: Production and Pre-registration are disabled until the requirements are met. Organization accounts are outside the scope of Google's article, which frames the rule as applying to personal developer accounts, so if you registered an Organization account for one of the four categories that require it, this particular gate does not appear. The full detail sits in the 12-tester requirement, and the wider list of obligations a new account picks up is in Google Play publishing requirements for new accounts.

What comes after the account exists

An account on its own publishes nothing. Google's next article, Create and set up your app, describes the following stage: from Play Console, select Home then Create app, choose a default language and the app name, say whether it is an app or a game and whether it is free or paid, add an email address that Play Store users can use to contact you, acknowledge the Developer Program Policies and US export laws declarations, accept the Play App Signing terms of service, then select Create app. The dashboard then walks you through store listing details, policy declarations such as your privacy policy and content rating, and the release you will push to a testing track.

Only after that does the clock become relevant. You create the closed test, invite 12 testers who opt in through the link, and the 14 continuous days start counting from the point where at least 12 are opted in. The setup work for that is described in how to set up closed testing in Play Console, including the two prerequisites that most often delay the opt-in link appearing.

Our recommendation, drawn from our own campaign records, is to line up the testers before you create the account rather than after. Signup and verification are single-day work on a good day and a few days on a bad one; recruitment is the step that decides your calendar. OnTesters matches a closed-testing campaign in under 24 hours once a client has a track ready, and the variable is never the console. It is whether twelve people are waiting when the link goes live.

Where Play Console signup goes wrong

Most signup failures are a disagreement between two records rather than a fault in the form. Correct the record Google is comparing against, then resubmit once. Submitting the same mismatched document repeatedly does not change the comparison.

One pattern is worth naming separately because it looks like a form bug. If you are registering an Organization and the console keeps asking for a D-U-N-S number you do not have, that is the requirement working as designed. Google says you will not be able to create a developer account for an organization without one, that the application is free, and that it offers no exemptions or extensions beyond the documented exception for known government organizations and agencies.

How long Play Console account verification takes

Google publishes no total duration for identity verification on a new developer account. The clocks it does put in writing are specific ones attached to individual sub-steps, so the honest answer to "how long does verification take" is that the longest documented item sets your schedule, and the identity review itself has no published figure at all.

The only review figure Google publishes anywhere in this area sits in its documentation for accounts created before September 2023, where it says the account owner receives an email when verification is complete and that this "may take a few days". That page covers a different flow, so treat it as the closest available signal rather than a commitment for a new account. Anywhere you see a specific processing time quoted for identity verification on a 2026 signup, it is a claim about Google's internal review that Google itself has not published.

Frequently Asked Questions

How much does it cost to create a Google Play developer account?

Google charges a US$25 one-time registration fee when you register a Play Console account. It is not a subscription, and it is paid during signup by credit or debit card, with prepaid cards not accepted. If your government ID or card details are later judged invalid, Google states the fee is not refunded.

How old do you have to be to create a Google Play developer account?

At least 18. Google's Get started article places the age requirement directly on step one of signup: you must be at least 18 years of age to sign up for a Play Console account. There is no documented route around it, so an under-18 developer needs an adult account owner rather than a different form.

Do I need a company to create a Google Play developer account?

No. Personal accounts exist for exactly this, and Google says both account types have the same functionality and can monetize. You need an Organization account only if you are registering for an organization or business, and Google makes four categories mandatory for it: financial products and services, health apps including medical and human subjects research, apps approved to use the VpnService class, and government apps. The Organization route also requires a D-U-N-S number, which a Personal account does not.

Can I change my account type later if I pick the wrong one?

Google's current Choose a developer account type page does not explain how to change it, and its older verification documentation for accounts created before September 2023 describes the selection as final, saying it determines the verifications you are required to complete and cannot be changed later. Answers in Google's Play Developer Community have gone in both directions over the years. Treat the type as fixed for planning purposes, and read the answer as an analysis of Google's inconsistent documentation rather than a published rule.

Do I need an Android phone just to create the account?

No, but you need one before your app can go public. Device verification is a requirement for new Personal accounts before they can make an app available on Google Play, not a condition of opening the developer account itself. In practice that means you can pay the fee and complete identity verification today, and still be blocked at the point of distribution if no eligible device is available: non-rooted, physical, Android 10 or later.

Why is the phone number verification step unavailable?

Because it has prerequisites. Google requires identity verification, website verification for organization accounts, and device verification for individual accounts to be completed before phone number verification can proceed, and it points you to the Play Console home page to see pending verifications. Clear the upstream task first and the phone number step becomes available.

Does the 12-tester requirement apply to my new account?

If it is a Personal account created after November 13, 2023, yes. Google requires a closed test with a minimum of 12 testers opted in for at least the last 14 days continuously before the app can be made available on Google Play, and it disables Production and Pre-registration until then. Organization accounts are outside the scope of that article. The full conditions are set out in the 12-tester requirement explainer on this site.

Sources

Get started with Play Console - Google Play Console Help. The primary source for the six signup steps, the 18-year age requirement, the US$25 one-time fee and its accepted card networks, the Developer Distribution Agreement step, the government ID and credit card note, and the November 13, 2023 testing and device verification clauses.

Required information to create a Play Console developer account - Google Play Console Help. What Personal and Organization accounts must supply, where legal name and address come from, the one-time password verification of contact details, what Google displays publicly, the D-U-N-S requirement with its up-to-30-day application window, and the up-to-5-day bank verification figure.

Verify your developer identity information - Google Play Console Help. The documents each account type is asked for, the exact-match rule against the payments profile, the ordering constraint that blocks phone verification until identity and device or website verification are complete, and email verification by six-digit code.

Choose a developer account type - Google Play Console Help. The two account types, the statement that both have the same functionality and can monetize, the four categories that should register as an Organization, and the free D-U-N-S application warning.

Play Console Requirements - Google Play Console Help. The policy version of the account-type rules, repeating the four mandatory Organization categories and the required developer account details.

Device verification requirements for new developer accounts - Google Play Console Help. The physical, non-rooted Android 10 or later device rule, the Play Console mobile app steps, the under-a-minute duration, and the treatment of the device's phone number.

App testing requirements for new personal developer accounts - Google Play Console Help. The November 13, 2023 scope, the 12 testers opted in for at least the last 14 days continuously, the disabled Production and Pre-registration features, and the production access application on the Dashboard.

Create and set up your app - Google Play Console Help. What happens after the account exists: creating the app record, the declarations you acknowledge, and the dashboard setup sequence.

Verifying your Play Console developer account for organizations - Google Play Console, organization verification guide. The statement that unsupported documents are the main reason for verification issues and that modified or fake documents can lead to immediate removal.