Requirements
How to publish an app on Google Play and what it costs: the full process for personal developers
From the US$25 developer registration fee and identity verification to app setup and the store listing, closed testing with 12 testers for 14 days, applying for production access, and launch — the whole process, costs, and timeline for personal developers publishing on Google Play, in one place.
Last checked Oct 14, 2026.
At a glance
For an individual developer, publishing an app on the Play Store takes six steps. The only payment to Google is the one-time US$25 developer account registration fee, and the step that takes longest is the 14 days of closed testing. If you have testers lined up in advance, plan on about 3–4 weeks from creating your account to launch.
| Step | Time |
|---|---|
| 1. Create a developer account | A day to a few days |
| 2. Create your app and set it up | Half a day |
| 3. Prepare your store listing | Half a day |
| 4. Closed testing: 12 testers, 14 days | A few days of review + 14 days |
| 5. Apply for production access | Usually within 7 days |
| 6. Release to production | Review takes hours to days |
Step by step
1) Create a developer account
Create a Play Console developer account with your Google account, accept the Developer Distribution Agreement, and pay the one-time registration fee of US$25. Choose an account type (personal or organization) and complete identity verification. You may need an ID and a card in your own name. Personal accounts also go through device verification, which uses the Play Console mobile app to confirm you have access to an Android device (Creating a developer account).
2) Create your app and set it up
Create your app in Play Console and complete the app setup items on the dashboard (privacy policy, app access, ads, content ratings, target audience, data safety, and so on). You can only use closed testing once this setup is done.
3) Prepare your store listing
Add your app name and description, an app icon (512×512 PNG), a feature graphic (1024×500), and at least 2 screenshots.
4) Closed testing: 12 testers, 14 days
This only applies to personal accounts created after November 13, 2023. Upload an App Bundle to the closed testing track, add testers, get it reviewed, and then keep at least 12 testers opted in for 14 consecutive days. The steps are in Closed testing requirements explained and How to add testers.
5) Apply for production access
Apply from your dashboard and answer the questionnaire. Google's documentation says reviews usually finish within 7 days but can take longer (How to apply for production access, and how long it takes).
6) Release to production
Once approved, create a release on the production track and send it for review. When the review is done, your app goes live on the Play Store.
What it costs
- Developer account registration fee — US$25, once. Paid by credit or debit card. Prepaid cards aren't accepted.
- Google Play service fee — only when you earn money. It applies to revenue from paid apps and in-app purchases. In the 15% tier, it's 15% on the first US$1M each year, 30% above that, and 15% for auto-renewing subscriptions (Service fees).
- Cost of finding testers — optional. Free if you recruit friends or communities; if you use a testing service, you pay its fee (ways to find testers compared).
Accounts that don't need closed testing
The 12-tester, 14-day closed testing requirement only applies to personal accounts created after November 13, 2023. Organization accounts and personal accounts created before then can skip steps 4–5 and release to production right after completing app setup and the store listing. To check whether your account is subject to it, see When you don't need closed testing.
Where the timeline stretches
- The first review. For a first-time app, the review of your closed testing release can take several days. Start by checking that you actually sent it for review (When your closed test is stuck in review).
- Testers dropping out. If testers leave during the 14 days and you fall below 12, you have to wait again until new testers complete 14 days.
- Production access denied. If you're sent back to test more, the timeline grows by that much. Shipping updates during testing and writing specific questionnaire answers are the surest way to prepare.
Frequently asked questions
- How much does it cost to publish an app on the Play Store?
- The only payment to Google is the one-time US$25 developer account registration fee. For a free app, there's nothing else to pay Google after that. If you earn money through a paid app or in-app purchases, a Google Play service fee applies to that revenue.
- What percentage is the Google Play service fee?
- According to Google's documentation, developers in the 15% service fee tier pay 15% on the first US$1M of earnings each year and 30% on anything above that, while auto-renewing subscriptions are 15% regardless of earnings. Check the Help Center for the full conditions.
- How long does it take to launch?
- For personal accounts subject to the requirement, the 14 days of closed testing plus review time at each step usually add up to 3–4 weeks if you have testers lined up in advance. Organization accounts and accounts created before November 13, 2023 can go straight to production without closed testing, so it's much shorter.
- Should I create a personal or an organization account?
- If you operate as a business, you can consider an organization account. It requires more verification and documents, but the 12-tester, 14-day requirement doesn't apply. Choose the type that matches how you actually operate, not as a way to avoid the requirement.
- Can I get the registration fee refunded?
- Google's documentation says the registration fee won't be refunded if you provide incorrect information when registering. Enter the name and details you'll use for identity verification accurately from the start.
Meet the requirement without recruiting testers
DUIRE joins your closed test with real Android devices and opens your app every day for 14 days. Registering your app and checking installability are free.