How to Publish an App on Google Play in 2026: Steps, Cost and Timeline

Publishing an app on Google Play costs a one-time $25 and takes anywhere from a few days to a few weeks, depending mostly on your account type. The work itself is predictable: create and verify a developer account, prepare a store listing, answer Google's app content questions, upload a signed Android App Bundle, and pass review. This guide covers every step in the order Play Console asks for it, with the exact asset sizes and the rules that catch first-time publishers out.

What you need before you start

• A signed Android App Bundle (AAB). Google Play requires the AAB format for new apps; an APK alone can only be installed directly on a phone.
• A Google account to own the developer account, ideally one your business controls rather than a personal inbox.
• A government-issued ID and proof of address for identity verification, or a D-U-N-S number if you register as an organization.
• An Android phone, which Google uses to verify you have access to a real device.
• A privacy policy hosted at a public URL.
• Store assets: a 512×512 icon, a 1024×500 feature graphic and at least two screenshots.

Don't have an app yet? If you have a website, you can turn it into a signed Android app with an AAB in minutes. See how to convert a website to an Android app.

How much it costs to publish on Google Play

The only other cost is building the app itself, which ranges from free to thousands of dollars depending on the tool or developer. Our website to app pricing guide compares the options.

Step 1: Create and verify your developer account

Sign up at the Google Play Console, choose an account type, pay the $25 fee, and complete verification. The account type matters more than it looks:

Google also asks you to verify a contact email and phone number and to confirm you have access to an Android device. Verification can take a few days, so start it before your app is finished.

Step 2: Create your app in Play Console

Click Create app and enter your app's name, default language, whether it's an app or a game, and whether it's free or paid. Choose carefully: a free app can never be changed to paid later. You'll also accept the Developer Program Policies and US export laws declarations.

Step 3: Prepare your store listing

For the best chance of being featured, Google recommends at least four screenshots at 1080px or more (1080×1920 for portrait). Write the short description as a clear benefit, and use the words people would search for in the first lines of the full description. Avoid keyword lists, fake reviews and mentions of other apps' names, which break Play's metadata policy.

Step 4: Complete the App content section

Under Policy and programs, then App content, Google asks a series of questions. Every one must be answered before you can release:

• Privacy policy: a public URL. Required for every app.
• App access: if any part of your app needs a login, give reviewers reusable test credentials and instructions. If your app uses one-time codes or two-step verification, provide a login that bypasses it. Missing credentials are one of the most common reasons for rejection.
• Ads: declare whether the app shows ads.
• Content rating: a short questionnaire that produces age ratings for each region.
• Target audience and content: the age groups your app is designed for. Choosing under-13 audiences brings extra Families policy requirements.
• Data safety: what user data the app collects and shares, why, and whether it's encrypted. For an app that loads your website, this should match what the website collects: account details, analytics, payment information and so on.
• Government apps, financial features, health and news declarations if they apply to you.

Step 5: Upload your AAB and understand app signing

Create a release on a testing or production track and upload your signed AAB. New apps use Play App Signing: you sign the bundle with your upload key, and Google re-signs the final APKs with an app signing key it manages. Two things follow from that:

1. 1Every future update must be signed with the same upload key. Lose it and you'll need to contact Google to reset it, so use a tool that stores it safely. Capsule keeps your key and signs every rebuild with it automatically.
2. 2If your app uses Android App Links (links to your website that open in the app), your assetlinks.json file must include the SHA-256 fingerprint of Google's app signing key, found in Play Console under App integrity, not just your upload key.

Your app must also meet Google Play's target API level requirement. Since August 31, 2026, new apps and app updates must target Android 16 (API level 36). If you're using a builder or converter, check that its builds meet the current requirement before you submit.

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

If you have a personal account created after November 13, 2023, you can't release to production yet. You need at least 12 testers opted in to a closed test for 14 consecutive days, then an approved application for production access. It's the step that surprises most first-time publishers, so we wrote a full guide: Google Play closed testing: the 12 testers, 14 days rule.

Step 7: Release to production and pass review

Once you have production access (or immediately, for organization and older accounts), create a production release, choose the countries you want to launch in, and send it for review. Google says reviews can take up to seven days or longer, especially for new developers. Later updates are usually reviewed faster.

Common reasons apps are rejected

• No sign-in details for reviewers when the app needs a login.
• A Data safety form that doesn't match what the app actually collects.
• Requesting permissions the app doesn't use, such as location or microphone.
• Minimum functionality: apps that offer too little, or that simply display a website the developer doesn't own. A website app is fine if it's your own site and it behaves like an app, with a proper icon, splash screen, navigation and features like push notifications.
• Misleading metadata: keyword stuffing, other brands' names or screenshots that don't show the real app.
• A broken or missing privacy policy link.

If you're rejected, Play Console tells you which policy was involved. Fix the issue, submit a new release or update the relevant form, and resubmit. For apps built from websites, see the Play Store section of PWA vs WebView app as well.

After you launch

• Updates to your app go through review again, but usually faster than the first release.
• If your app loads your website, content changes appear instantly without a new release.
• Keep up with the target API level requirement each year, or your app becomes unavailable to new users on newer Android versions.
• Reply to reviews and watch Android vitals (crashes and ANRs) in Play Console.