To create a Google Play developer account, sign up on the Play Console sign-up page with a Google account, accept the Developer Distribution Agreement, pay the one-time US$25 registration fee, choose a personal or an organization account, and verify your identity. You must be at least 18.
Most of it takes an evening. The parts that take longer are identity verification, a D-U-N-S number if you register a business, and, for new personal accounts, the closed test before your first public release. Here is each step, based on Google's Play Console Help pages as of November 2026.
Step 1: get ready before you start
Use a Google account you'll keep for years, ideally one created just for your developer work. Play Console, payments and every app you publish will hang off it.
Have two things in your legal name: an official government ID and a credit or debit card. Google says it doesn't accept prepaid cards, and warns that if the information turns out to be invalid, the registration fee isn't refunded.
Step 2: personal or organization account
A personal account is meant for individuals: students, hobbyists and solo developers. An organization account is for companies and other organizations. Both have the same core features once they are set up.
An organization account needs a D-U-N-S number from Dun & Bradstreet. Google describes getting one as free but says it can take up to 30 days. You'll also give the organization's name, address, phone number and website, and verify the website.
Some apps must come from an organization account, according to Google: financial products, health apps, apps using VpnService and government apps. If yours is one of them, choose organization from the start.
Step 3: pay and fill in your details
The registration fee is US$25, paid once. After that, there is no yearly fee for the developer account itself.
For a personal account, Google asks for a developer name, which is shown on Google Play, your legal name and address, a contact email and phone number, and a developer email that users can see. Your legal name and address come from the payments profile linked to the account.
Step 4: verify identity, contacts and device
You upload an official government ID. Organizations also upload an official organization document. Google says you must verify the account before you can submit apps.
Contact details are confirmed with one-time codes: a 6-digit code for the developer email, and a text or voice call for the phone number.
New personal accounts also have to prove they have a real Android phone by signing in to the Play Console mobile app on it before they can make an app available on Google Play. If you only have an iPhone, borrow an Android phone for this step.
Mistakes that slow sign-up down
A name that doesn't match. The legal name on your ID, your payments profile and your card should be the same. A nickname in one place and a full name in another is a common reason verification asks for more documents.
A prepaid or virtual card that isn't accepted. Use a regular card in your own name, because Google says prepaid cards aren't accepted and the fee isn't refunded if the details are invalid.
The wrong account type. Switching later is not a simple toggle, so if you plan to publish as a company or build one of the app types that need an organization, set it up that way from the start.
Using a Google account someone else controls, such as an old work or school account. If you lose access to it, you lose access to your apps.
Waiting to plan testers. Verification can take days, and the 14-day closed test only starts counting once 12 testers are opted in. Line them up while the account is being verified.
Step 5: what happens after the account is ready
If you created a personal account, Google requires a closed test before production. According to Google's help page, personal accounts created after November 13, 2023 must run a closed test with at least 12 testers who stay opted in for at least 14 days in a row. Production and pre-registration stay disabled until then.
When the 14 days are done, you apply for production from the Dashboard. Google says the review usually takes seven days or less. Organization accounts don't have this testing requirement and can publish to production directly.
Plan the closed test while you wait for verification. If you don't have 12 people who will stay for 14 days, PeerPlay is a free way to find them: Android developers test each other's apps every day through your real closed track.
Top comments (0)