How to Publish an App on Google Play: 2026 Steps

To publish an app on Google Play, you create a developer account, create the app in Play Console, complete the app content and store listing, upload a signed Android App Bundle to a testing track, and then release it to production for Google's review. If you have a personal developer account created after November 13, 2023, there is an extra gate in the middle: a closed test with at least 12 testers for 14 days, followed by an application for production access.

Below is the full sequence in the order you will actually do it, with realistic timing for each stage.

The publishing path at a glance

Organization accounts skip stages 5 and 6.

Step 1: Create your developer account

Sign up for Play Console, pay the one-time US$25 fee, choose a personal or organization account, and verify your identity and contact details. New personal accounts must also verify access to an Android device through the Play Console mobile app. Our Google Play developer account guide compares both account types in detail.

Step 2: Create the app in Play Console

In Play Console, choose Create app and fill in:

• App name (you can change it later)
• Default language
• Whether it is an app or a game
• Whether it is free or paid
• Declarations accepting the Developer Program Policies and US export laws

Think carefully about free vs paid. Google does not let you switch a free app to paid later, although a paid app can become free.

Step 3: Complete app content and the store listing

Play Console's Dashboard shows a checklist of setup tasks. Most of them live under App content and the main store listing.

App content declarations

• Privacy policy: a public URL describing how your app handles user data.
• App access: if parts of the app require login, give reviewers credentials or instructions.
• Ads: declare whether the app contains ads.
• Content rating: answer the rating questionnaire so your app receives age ratings for different regions.
• Target audience and content: choose the age groups your app targets. Targeting children brings additional policy requirements.
• Data safety: describe what user data your app collects and shares, and how it is protected. This appears publicly on your store listing, so it must match what your app and its SDKs actually do.
• Other declarations that apply to your app, such as news apps, government apps, or financial features.

Store listing

Write a short description and full description, then upload graphics: an app icon, a feature graphic, and phone screenshots. Choose a category and contact details. A clear listing also helps reviewers understand what the app is supposed to do.

Technical requirements to check now

Your upload must be an Android App Bundle (AAB) signed for release. Google Play also enforces a target API level: starting August 31, 2026, new apps and app updates must target Android 16 (API level 36) or higher (Wear OS, Automotive, TV, and XR have lower minimums). Checking this before you build saves a rejected upload later.

Step 4: Internal testing (optional but useful)

Internal testing lets you share a build with up to 100 testers you add by email. Builds are usually available to testers within minutes, which makes it ideal for checking that your release build installs, signs in, and processes purchases correctly. Internal testing does not count toward the 12-tester requirement for personal accounts. See our Google Play internal testing guide for how it compares with closed and open testing.

Step 5: Closed testing (personal accounts)

If your personal account was created after November 13, 2023, Play Console Help requires you to run a closed test with at least 12 testers who have been opted in continuously for at least 14 days before you can apply for production.

The practical steps:

1. Create a release on the closed testing track and upload your AAB.

2. Choose the countries where the closed test is available.

3. Add testers by email list or Google Group.

4. Send the release for review. Once the track is published, copy the opt-in link and share it.

5. Make sure each tester opens the link with the same Google account you added, accepts the invitation, and installs the app.

6. Keep testers engaged and ship updates during the test. Google lists insufficient tester engagement as a reason it may ask you to keep testing.

The most common failure is testers who never actually opt in, or who opt out partway through. Why closed testing testers are not counted covers the usual causes.

Step 6: Apply for production access

After 14 days with 12 or more continuously opted-in testers, Apply for production appears on the Dashboard. The application has three parts:

1. Your closed test: how easy recruiting was, how engaged testers were, and a summary of feedback and how you collected it.

2. Your app or game: target audience, value proposition, and an estimated install range for the first year.

3. Production readiness: what you changed based on testing and how you decided the app was ready.

Google reviews the application and emails the account owner. Play Console Help says this usually takes seven days or less, but can take longer. Keep your closed test running while you wait. If you are refused, read what to do when production access is rejected.

Step 7: Release to production

With production access granted (or immediately, for organization accounts), create a release on the Production track:

1. Upload your AAB or promote the build you tested.

2. Write release notes.

3. Choose countries and regions.

4. Optionally use a staged rollout to release to a percentage of users first.

5. Send the changes for review from the Publishing overview page.

If you want to control the exact moment your app goes live after approval, turn on managed publishing so approved changes wait until you publish them.

Google Play app review time

Google does not publish a single guaranteed review time. Play Console Help says that for certain developer accounts Google will take more time to review apps thoroughly, which may result in review times of up to seven days or longer in exceptional cases. Updates to existing apps are processed as soon as possible, but some apps may be subject to extended reviews.

Practical takeaways:

• Budget a week for a brand-new app's first review, even if it often comes back faster.
• Do not schedule a marketing launch for the same day you submit.
• Remember the production access review (Step 6) is a separate review from the app review (Step 7).

From account creation to a live listing, a personal account developer should realistically plan for about four to five weeks. Our production release checklist helps you avoid last-minute surprises.

Getting through the closed test

Recruiting and keeping 12 active testers is where most personal-account developers lose time. If you want to hand that part off, Doply provides at least 14 testers (usually 16) on 36 real Android devices, launches your app daily, picks up your updates automatically, and keeps the test running for 18 days. It costs $6.99 per app plus tax, includes a draft of the production application answers, and does not guarantee Google's approval. Requirements such as including South Korea in your closed track countries are listed in the docs.

FAQ

How long does it take to publish an app on Google Play?

For organization accounts, mostly the time for app setup plus the review, which can be up to seven days or longer in exceptional cases. For personal accounts created after November 13, 2023, add at least 14 days of closed testing and the production access review, so about four to five weeks in total.

Do I need to do internal testing before closed testing?

No. Internal testing is optional, though Google recommends it as a starting point. It does not count toward the 12-tester requirement.

Can I use open testing instead of closed testing?

Not for new personal accounts. Open testing becomes available only after you gain production access.

What file format do I upload to Google Play?

New apps are published as Android App Bundles (AAB), signed for release, and must meet the current target API level requirement.

Why is my app still in review after several days?

Google says some accounts and apps get more thorough reviews that can take up to seven days or longer. New developer accounts are more likely to see longer reviews.