Publishing your first Android app on Google Play takes more than uploading a file. You need a verified developer account, a complete store listing, accurate policy answers, and a correctly built release. New personal accounts also need a mandatory closed test before Google gives production access.
This guide walks you through the whole journey in order, from creating your developer account to going live. Each step links to a deeper guide when you need more detail. The rules below come from Google Play Console Help and were current in September 2026. Google changes them often, so double-check anything important in Play Console.
Quick Answer: How to Publish an App on Google Play
The short version
Create a developer account ($25). Create your app. Fill in the store listing and App content answers. Build an app bundle that targets Android 16 (API 36). Release it to a closed testing track. Keep at least 12 testers opted in for 14 days in a row. Then apply for production access. Google usually reviews within seven days.
Who needs the closed test
Personal developer accounts created after 13 November 2023 must run a closed test with at least 12 testers for 14 days in a row before they can apply for production access. Organization accounts have different rules.
The 9 Steps to Publish Your App
Create your Google Play developer account
You need a developer account before you can publish anything. Skip this step if you already have one.
- Register at play.google.com/apps/publish/signup with a Google Account. You must be at least 18.
- Accept the Developer Distribution Agreement and pay the one-time US$25 registration fee. Prepaid cards are not accepted.
- Choose a Personal or Organization account, then finish identity verification. Google may ask for a government ID and a card in your legal name. The fee isn't refunded if verification fails.
- Personal accounts may also need to check an Android device using the Play Console mobile app.
Create your app in Play Console
This creates the record that every later step attaches to.
- In Play Console, go to Home → Create app.
- Enter the app name (up to 30 characters), the default language, whether it's an app or a game, whether it's free or paid, and a contact email.
- Accept the declarations and select Create app.
- Your package name is unique and permanent, so settle it before your first upload.
Complete your store listing
Google won't publish a listing that's missing required items. Good visuals and text also help people decide to install. ASO and listing optimization can help with this.
- A short description of up to 80 characters and a full description of up to 4,000 characters.
- An app icon: 512 × 512 px, 32-bit PNG with alpha, up to 1024 KB.
- A feature graphic: 1024 × 500 px, JPEG or 24-bit PNG without alpha.
- At least two screenshots (JPEG or 24-bit PNG, 320 to 3840 px per side). To be eligible for featured sections, Google recommends at least four at 1080 px or larger.
Complete the App content declarations
Open App content in Play Console. Missing or wrong answers are a common reason for rejection. That's why many developers run a Play Console audit first.
- Privacy policy: add a public link that explains how you handle user and device data.
- Ads: declare whether the app contains ads, including third-party ad SDKs.
- App access: if any part of the app needs a login, give reviewers working test credentials.
- Content rating: complete the questionnaire. Unrated apps can be removed from Google Play.
- Target audience and content and the Data safety form, which must match what your app actually collects.
- Clear everything listed under Needs attention.
Build your app bundle
Google Play accepts Android App Bundles (.aab).
- Build a signed release bundle in Android Studio or your build tool.
- Target the required API level. New apps and updates must target Android 16 (API level 36) or higher. Google updates this every year, so check the current target API requirement.
- Give every upload a version code higher than the last (the maximum is 2,100,000,000).
- On your first release, Play Console asks you to set up Play App Signing. Changing the signing key later forces testers to reinstall the app.
Create your closed testing track and release
New personal accounts must test in a closed track. Internal and open testing do not count toward the requirement. Menu names can differ slightly between console versions.
- Go to Test and release → Testing → Closed testing, create a track (or use Manage track), then choose Create new release.
- Upload your bundle, name the release (visible only to you) and add release notes of up to 500 characters per language.
- Save, choose Next, fix any errors on the review screen, then select Start rollout.
- The opt-in link appears once the track shows as Published. Google may review the release first.
Add your testers
Google requires at least 12 testers to stay opted in to your closed track. The most reliable ways to reach that number are in how to get 12 testers. Or you can let our closed testing service supply verified testers on real devices.
- In Closed testing → Manage track → Testers, choose Create email list. A list holds up to 2,000 addresses.
- Import or enter the testers’ email addresses, save the list and select it for your track.
- Copy the opt-in URL from the Testers tab and share it so each tester can join on their own Android device.
- Testers need a Google Account to join.
Keep the test running for 14 consecutive days
Google counts testers who stay opted in for 14 consecutive days. The detail of what this means is in how to pass the 14-day test.
- Keep the closed track published and the tester list in place.
- Testers who opt out before 14 days do not count, and a tester who leaves and returns starts their 14 days again.
- Use real testers on real devices. Emulators and device farms put your account at risk, as explained in why Google bans emulator testers.
Apply for production access
Once at least 12 testers have been opted in for 14 consecutive days, you can apply.
- In Play Console, open Dashboard and select Apply for production.
- Complete three sections: about your closed test, about your app or game, and about your production readiness. See what to write in the production access form.
- Google says review usually takes seven days or less, though it can take longer. The account owner is notified by email.
- After approval, create your first production release and roll it out. If you are rejected, read what to do when closed testing is rejected.
Pre-Launch Checklist
Before you start your closed test, confirm each of these. Anything missing now can cost you days later.
- Developer account verified and in good standing
- Store listing complete: descriptions, icon, feature graphic and at least two screenshots
- Privacy policy URL is public and works
- Content rating, target audience, ads, and data safety answers are complete and accurate
- Login credentials provided for reviewers if your app needs a sign-in
- Bundle targets Android 16 (API level 36) or higher and uses a new version code
- Closed track published, with the tester list selected and the opt-in link ready
Common Mistakes That Delay Publishing
- Using the wrong track: Internal and open testing do not satisfy the closed test requirement. Only a closed track counts.
- Testers dropping out: Only testers who stay opted in for 14 days in a row count. A tester who leaves and comes back starts over.
- Old target API level: You can't submit new apps or updates that don't meet the current requirement.
- Wrong answers: A data safety form or content rating that doesn't match the app is a common reason for rejection.
- Skipping the audit: Checking your whole Play Console setup before the test helps you avoid failing for a reason that has nothing to do with testing.
Want help with the testing step?
Hire App Testers gives you 12 to 25 verified testers on real Android devices and keeps them active for the full 14 days. If you follow our process and are rejected because of tester activity, we re-test for free or refund you. Compare the plans or read customer reviews.
Frequently Asked Questions
How long does it take to publish an app on Google Play?
Setting up your account, listing, and first release usually takes a few days of work. For new personal accounts, the closed test adds 14 days in a row. Google says its review of a production access application usually takes seven days or less. Plan for about three to four weeks from your first upload to a live app.
How much does it cost to publish an app on Google Play?
Google charges a one-time US$25 registration fee for a developer account. Publishing apps after that carries no further fee from Google, though you may pay for testers, design or other services.
Do I need 12 testers to publish my app?
If you created a personal developer account after 13 November 2023, yes. Google requires at least 12 testers to stay opted in to a closed test for 14 days in a row before you can apply for production access. Organization accounts have different rules.
What Android API level must my app target in 2026?
Google requires new apps and app updates to target Android 16 (API level 36) or higher. The requirement changes every year, so check Google's current target API level page before you build.
Can I skip the closed test?
Not on a personal developer account created after 13 November 2023. The closed test with at least 12 testers for 14 days in a row is required before you can apply for production access.
What happens after Google approves production access?
You can create your first production release in Play Console and roll it out. After that, each update goes through review as usual, and you should keep your store listing, privacy policy and data safety form accurate.