How to Publish an App on Google Play Store (2026 Guide)

To publish an app on the Play Store, you register a Google Play Console developer account (a one-time US$25 fee), create the app in Play Console, fill in the store listing and the App content declarations, upload a signed Android App Bundle (.aab), and send the release for review. If you opened a personal account after 13 November 2023, Google also requires a closed test with at least 12 testers for 14 days in a row before you can apply for production access.

This guide walks through every step in the order Play Console asks for it, with the 2026 rules checked against Google's own help pages on 7 October 2026. It covers the choice between a personal and an organization account, the testing rule that catches many first-time developers, realistic review times, the reasons apps get rejected, and a launch checklist you can work through before you press publish.

What you need before you start

Have these ready before you open Play Console. Missing any one of them stops you partway through.

Sources: fee and payment methods from Play Console Help: get started; account details and D-U-N-S from Play Console Help: required information.

Personal or organization account: which to choose

This is the first real decision, and it is hard to undo later. If the app belongs to a business, register it as an organization.

For Indian businesses, the D-U-N-S number is the step to start early. Google says applying is free and can take up to 30 days, while the testing rule for a personal account takes at least 14 days plus a review. An organization account avoids the testing rule and keeps the app in the company's name, which matters if a developer or staff member leaves.

How to publish an app on the Play Store, step by step

Step 1: Create your Play Console developer account

1. Go to Google Play Console and sign in with the Google account you will use for the business. You must be at least 18.

2. Accept the Developer Distribution Agreement.

3. Pay the US$25 registration fee.

4. Choose personal or organization, then enter the details Google asks for.

5. Complete identity verification and verify your email and phone with the one-time passwords.

6. On a new personal account, complete device verification through the Play Console mobile app.

The steps follow Google's registration guide. Keep the contact email and phone working for as long as you have the account, because Google requires both to stay operational.

Step 2: Create the app in Play Console

From the Play Console home screen, select Create app and fill in:

• Default language and app name (the store shows up to 30 characters)

• App or game

• Free or paid. Google lets you change a paid app to free, but once an app has been offered free it cannot be changed to paid, so decide now.

• A contact email users can write to

• The declarations: Developer Program Policies, US export laws and the Play App Signing Terms of Service

Source: Play Console Help: create and set up your app.

Step 3: Complete the App content declarations

Your app's dashboard lists the setup tasks. Read each question properly, because a wrong answer here can hold up the review or cause trouble after launch.

• Privacy policy. A public URL that explains what data the app collects, how it is used and who it is shared with. It must be linked in the store listing and inside the app if you handle sensitive data or target children.

• App access. If any part of the app sits behind a login, give Google working test credentials and instructions. You can add up to five sets.

• Ads. Declare whether the app shows ads, including ads from third-party SDKs.

• Content rating. Answer the rating questionnaire. Unrated apps can be removed from Google Play.

• Target audience and content. Declare the age groups the app is for. Apps aimed at children must meet the Families policy.

• Data safety. Every developer must complete this form, including apps that collect no user data. What you declare appears on your store listing.

• Other declarations where they apply, such as news apps, health apps and financial features.

Sources: App content declarations and Data safety section in Play Console Help.

An India note: the Data safety form is Google's rule, and Indian law adds its own. The Digital Personal Data Protection Rules were notified on 14 November 2025 with an 18-month phased timeline. If your app collects names, phone numbers or locations from Indian users, write your privacy policy and consent screens with both in mind, and make sure your Data safety answers match what the app does. Google says it may take enforcement action, including blocked updates or removal, when the declaration and the app's behaviour do not match.

Step 4: Build the store listing

The store listing is what people see before they install. These are Google's current limits:

Sources: Play Console Help: preview assets and create and set up your app. Google recommends at least four screenshots at 1080 px or more for apps.

Write the description for people first. Google's own policy guidance names keyword stuffing in descriptions as a common violation. Say what the app does, who it is for, and what a user can do in the first minute.

Step 5: Prepare a release build that meets the 2026 technical rules

Your developer exports this from Android Studio, Flutter or React Native. As a business owner, ask them to confirm each of these:

• Android App Bundle. New apps have had to publish as .aab files since August 2021. The compressed download needed to install the app must be 4 GB or less.

• Target API level. Since 31 August 2026, new apps and updates must target Android 16 (API level 36) or higher. Wear OS and Android Automotive apps need API 35, and Android TV and XR apps need API 34. Google allows extension requests until 1 November 2026.

• 16 KB memory pages. Apps targeting Android 15 or higher must support 16 KB page sizes on 64-bit devices. From 1 February 2027, updates that do not support them cannot be released. This mostly affects apps with native (NDK) code.

• App signing. You accept Play App Signing when you create the app. Your developer still keeps an upload key; store it somewhere safe and in the company's control.

Step 6: Run a closed test (required for new personal accounts)

Many tutorials skip this step. Google's testing requirements page says personal accounts created after 13 November 2023 must run a closed test with at least 12 testers who have been opted in continuously for at least 14 days. Until you meet it, the Production track and pre-registration stay locked.

The 14 days must be continuous for each tester. Someone who opts in, tests for a week and opts out does not count. If they come back later, their clock starts again. In practice:

1. Create a closed testing track and upload your .aab to it.

2. Add testers by email list and share the opt-in link with them.

3. Recruit more than 12 people. If a few drop out, you still clear the bar.

4. Ask testers to use the app properly and send feedback. Google also looks at engagement, and low engagement can mean you are asked to keep testing.

5. Fix what testers find and push updated builds to the same track.

6. After 14 days, open the Dashboard and select Apply for production. You answer questions about your closed test, your app and your production readiness.

Google says this production access review usually takes seven days or less but can take longer. Organization accounts skip this step, which is one more reason to register a business app as an organization.

Step 7: Create the production release and send it for review

1. Choose the countries and regions where the app will be available.

2. Go to Production, select Create new release, and upload the .aab (or promote the build you tested).

3. Add release notes that say what is in this version.

4. Review any warnings, then save and send the changes for review.

If you want to control the exact launch moment, turn on managed publishing. Google still reviews the release, but once it is approved, you decide when it goes live. That is useful when a launch is timed with a campaign or a press note.

How long Play Store review takes

Many tutorials promise 24 to 48 hours. Google does not promise a fixed time. Its publishing status page says some developer accounts and apps get extended reviews, which "may result in review times of up to seven days or longer in exceptional cases".

Here is a planning timeline for a brand-new personal account, built from Google's stated figures. Treat it as an estimate, not a promise.

For an organization account the testing stage drops out, though a first review can still take several days. Organizations should instead allow up to 30 days for a D-U-N-S number if they do not already have one. Build these weeks into your launch date before you announce it.

Common reasons apps get rejected (and how to avoid them)

Sources: Google Play functionality and user experience policy, Android Developers Blog on common policy violations and the Play Console Help pages linked above.

The website-wrapper point matters for Indian small businesses in particular. A quick app that loads your website in a WebView is cheap to build and is exactly the kind of app Google's guidance flags. If budget is tight, a mobile-friendly website may serve you better until you can fund a proper app. Our guide on choosing between a website and a mobile app covers that decision.

What publishing on Google Play costs

Publishing itself is cheap. Building and running the app is where the money goes.

• Play Console registration: US$25, paid once.

• Publishing a free app with no in-app sales: no further Google fee.

• Selling digital goods or subscriptions in the app: Google's service fee in markets that include India is 15% on a developer's first US$1 million of earnings each year, 30% above that, and 15% on auto-renewing subscriptions. If you also offer users in India an alternative billing system, the fee on those transactions is reduced by 4 percentage points.

• Selling physical goods or real-world services (food, salon bookings, deliveries): Google's payments policy says these must not use Google Play billing, so they go through a payment gateway such as Razorpay, which charges its own fee.

For the cost of building the app in the first place, see our breakdown of mobile app development cost in India.

Play Store launch checklist

1. Developer account is in the company's name, with a shared company email and a phone number that will not change.

2. Account type chosen (organization for a business), and D-U-N-S number applied for if needed.

3. Privacy policy is live at a public URL and covers DPDP consent and deletion requests.

4. App name, short description and full description are written and within limits.

5. Icon, feature graphic and at least four screenshots are exported at the right sizes.

6. Content rating, target audience, ads, app access and Data safety are all complete.

7. Release .aab targets API 36, supports 16 KB pages, and is signed with an upload key you control.

8. Release build tested on at least one older, low-RAM Android phone.

9. For new personal accounts: 12+ testers opted in for 14 continuous days, then Apply for production.

10. Managed publishing turned on if the launch date matters.

11. Launch date set at least 3 to 5 weeks out for a new personal account.

12. Someone is responsible for replying to Play Console emails and policy notices after launch.

Choosing who builds and publishes the app matters as much as the checklist. Our older guide on how to choose a mobile app developer lists what to check before you hire.

Frequently asked questions

How much does it cost to publish an app on the Play Store?

Google charges a one-time US$25 registration fee for a Play Console developer account. There is no further fee to publish free apps. If you sell digital goods or subscriptions inside the app, Google takes a service fee, which is 15% on the first US$1 million of yearly earnings in markets including India.

Can I publish an app on the Play Store for free?

No. Every developer account needs the US$25 one-time fee, and Google does not accept prepaid cards for it. After that one payment you can publish free apps on the same account without further Google fees.

Is it hard to publish an app on the Play Store?

The steps are well documented, but there are more of them than most people expect. The parts that cause trouble are the App content declarations, the Data safety form and, for new personal accounts, the 14-day closed test with 12 testers. Plan for three to five weeks from a new personal account to a live app.

How long does Google take to review an app?

Google gives no fixed time. It says some accounts and apps get extended reviews of up to seven days, or longer in exceptional cases. New personal accounts also wait for a production access review after the closed test, which usually takes seven days or less.

Do I need 12 testers to publish my app?

Only if you have a personal developer account created after 13 November 2023. Those accounts must run a closed test with at least 12 testers who stay opted in for 14 continuous days before they can apply for production. Organization accounts do not have this requirement.

Does Google take 30% of in-app purchases?

Only on earnings above US$1 million a year. In markets that include India, the fee is 15% on a developer's first US$1 million each year and 15% on auto-renewing subscriptions. Payments for physical goods and real-world services go through other payment methods and are not charged this fee.

Planning an app launch?

Webhorse Studio designs and builds Android, iPhone and cross-platform apps for businesses in Mumbai and across India. See our mobile app development services, or tell us about your app and we will help you plan the build and the Play Store launch.