Google Play Console Setup: A Step-by-Step Guide (2026)

Before a single Android user can download your app, you need a Google Play Console account — and the setup has more moving parts than most first-timers expect. Between the $25 fee, identity verification, and Google's rules for new personal accounts, it's easy to lose a day to false starts. This guide walks the complete Google Play Console setup in the order you'll actually do it, so you can get from "no account" to "ready to upload your first app" without backtracking.

The short version: create a Google account, register as a developer, pay the one-time $25 fee, verify your identity, and create your app record. Verification is the part that can stall you, so start it first. This post is the Google Play half of the broader flow in our pillar on how to publish an app without code.

What you need before you start

Gather these before you open the console. Missing one is the most common reason setup stalls partway.

Requirement	Detail
A Google account	Personal Gmail works; use one you'll keep long-term
$25 registration fee	One-time, paid by card during signup
Legal name & address	Must match a government ID for verification
Phone number	For account verification
Account type	Personal or Organization (choose carefully — see below)
Privacy policy URL	Required before you publish, not to create the account
D-U-N-S number	Organization accounts only

Decide personal vs. organization up front, because changing it later is painful. Personal is fine for indie makers publishing under their own name. Choose organization if you're a registered business — it displays a company name as the developer and requires a free D-U-N-S number, which can take a couple of weeks to obtain.

Step 1: Create your Google Play developer account

Go to the Google Play Console and sign in with the Google account you want to own the app. On the sign-up screen, select your account type (personal or organization) and country. Country determines your payments profile and can't be changed later, so pick the one you actually operate in.

You'll then enter your developer details:

Developer name — this is the public name shown under your app on the Play Store (e.g., "Jane Doe" or "Acme Apps"). You can change it later, but pick something you're happy shipping with.
Contact email and phone — Google uses these for account and security notices. Use an address you monitor.
Contact details for users — a support email that appears on your store listing.

Step 2: Pay the $25 registration fee

Google charges a one-time $25 registration fee to open a developer account. Unlike Apple's Developer Program — which is $99 per year — the Play Console fee never renews, and it covers unlimited apps under that account. You pay it by card during signup, and the account isn't active until the payment clears.

Step 3: Verify your identity

This is the step that catches people off guard, so do it early. Google requires every developer to verify their identity before publishing to production.

Personal accounts verify a legal name and address, and you may be asked to upload a government-issued photo ID.
Organization accounts additionally verify a D-U-N-S number and business details.

Verification often clears in minutes, but it can take a day or two — and occasionally longer if Google asks for more documents. Your account can exist and let you build out an app while verification is pending, but you cannot go live until it's complete. Treat it as a background task you kick off on day one.

Step 4: Set up your payments profile (if you'll charge money)

If your app will be free with no in-app purchases, you can skip this for now. If you plan to sell the app, offer subscriptions, or use in-app purchases, create a payments profile under Setup → Payments profile. This is where Google sends your payouts and collects tax information. Getting it done before launch means your first sales don't sit in limbo.

Step 5: Create your first app in Play Console

With the account live, click Create app on the console dashboard. Google asks for a handful of basics:

Field	What to enter
App name	Up to 30 characters — the title shown on the store
Default language	Your primary listing language
App or game	Category type
Free or paid	You can switch free → paid restrictions later, but not paid → free easily
Declarations	Confirm you meet developer policies and US export laws

This creates the app record — an empty shell you'll now fill with a build and a store listing. Naming matters for discovery, so if you haven't locked yours in, see how to choose an app name before you commit.

Step 6: Understand the closed-testing requirement for new accounts

Here's the single biggest surprise for indie makers in 2026, so plan for it now.

New personal developer accounts — those created after November 13, 2023 — must run a closed test with at least 12 testers opted in for 14 continuous days before you can apply for production access. Organization accounts and older personal accounts are exempt.

That means even after your app is finished, verified, and uploaded, a brand-new personal account faces a mandatory two-week testing window before it can reach the public Play Store. Line up your 12 testers early. For the full walkthrough, see our guide to Google Play closed testing.

Step 7: Prepare your store listing assets

While testing runs (or verification clears), build the assets Google's listing requires. You'll need these before you can publish:

App icon — 512×512 PNG
Feature graphic — 1024×500
Phone screenshots — at least two, at 1080×1920
Short description — up to 80 characters
Full description — up to 4,000 characters
Privacy policy URL — publicly reachable
Content rating — via Google's questionnaire
Data Safety answers — a structured declaration of what data you collect

You can produce most of these without a designer or lawyer. Adalo Studio's screenshot generator exports Play-ready images at exactly 1080×1920 so the console never rejects them for being off-spec — the screenshot sizes reference has the full spec table. Its store-listing generator drafts your short and full descriptions and your Data Safety answers, and the privacy policy generator gives you a hosted URL to paste straight into the listing. Everything is free to design; you only pay a one-time unlock (or use an included paid Adalo plan) to export — the details are on the pricing page.

Step 8: Upload your build and roll out

When your app produces a signed Android App Bundle (.AAB) — the format Google Play requires — upload it to a release track under Release → Production (or a testing track first). Complete the content rating questionnaire, fill in Data Safety, add your privacy policy URL, and finish the store listing. Once everything shows a green check and (for new accounts) your closed test is satisfied, promote the release to production and submit for review.

Google Play Console setup checklist

[ ] Google account chosen (long-term)
[ ] Account type decided: personal vs. organization
[ ] $25 registration fee paid
[ ] Identity verification submitted (do this first)
[ ] Developer name and contact details set
[ ] Payments profile created (if charging)
[ ] App record created in Play Console
[ ] 12 testers lined up (new personal accounts)
[ ] Icon 512×512, feature graphic 1024×500, screenshots 1080×1920 ready
[ ] Privacy policy URL live
[ ] Content rating + Data Safety completed
[ ] Signed .AAB uploaded to a release track

Get the account and verification handled first, prep assets in parallel, and the rest of the setup is mostly filling in forms. If you're weighing the whole publishing journey across both stores, the app store submission checklist keeps every step in one place.

Frequently asked questions

How much does a Google Play Console account cost?

A Google Play developer account costs a one-time $25 registration fee, paid when you sign up. There is no annual renewal, unlike Apple's $99/year Developer Program. The fee covers unlimited apps under that one account.

How long does Google Play identity verification take?

Verification usually clears within a few minutes to a couple of days, but it can occasionally take longer if Google requests additional documents. Start it early, because you cannot publish to production until your account is fully verified. Personal accounts must verify a legal name and address; organization accounts also verify a D-U-N-S number.

Do I need a website to set up Google Play Console?

No, a full website is not required to create the account, but you do need a valid contact email and, before you publish, a publicly reachable privacy policy URL. Many indie makers host a one-page privacy policy instead of a full site. You can generate a hosted policy in minutes rather than building a website first.

Tools mentioned in this guide: App Store Screenshot Generator, App Privacy Policy Generator.