How to Submit an App to Google Play: Complete 2026 Step-by-Step Guide

Key Takeaways

• New apps and updates must target Android 16 (API level 36) or higher since August 31, 2026.
• Play Console requires identity verification and a one time registration fee of USD 25.
• New personal accounts must run a closed test with 12 testers for 14 days before production access.
• Upload a signed Android App Bundle (AAB) and enroll in Play App Signing.
• Complete the Data safety, content rating, ads, and app access forms before you send the release for review.
• Crashes, privacy policy gaps, and invalid demo credentials cause most rejections.

Google Play reaches billions of Android users. However, one missing form, a wrong API level, or an expired demo login can block your release. Reviewers check your build, your listing, your privacy policy, and your declarations. Most rejections come from basic gaps, and you can prevent every one of them. This guide shows how to submit an app to Google Play in nine steps, from account setup to production rollout.

Android’s larger download share makes Google Play a key distribution channel for businesses targeting a broad global mobile audience. In 2025, Google Play accounted for 104.6 billion app and game downloads, or 73.5% of the 142.2 billion downloads recorded across Google Play and Apple’s App Store. Apple’s App Store generated 36.6 billion downloads, representing the remaining 26.5%.Android powers most smartphones, so Google Play app publishing gives you direct access to this demand. If you are still choosing a platform, read our comparison of Android vs iOS first.

If you prefer professional support throughout the process, an experienced Android application development company can help prepare your app, meet Google Play requirements, and manage the submission process.

What You Need Before Uploading an App to Google Play Store

Before anything else, gather these items. They cover the core Google Play app requirements, and they show how to publish an app on Google Play without stopping halfway to find a missing asset.

1. Google Play Developer Account

You need a developer account in Play Console. Choose one of two types:

• Personal: For individuals. It requires government ID verification and a closed test before production access.
• Organization: For companies. It requires a D-U-N-S number and skips the closed testing rule.

Both types pay a one-time registration fee of USD 25.

2. Android App Bundle (AAB) File

Google Play requires the AAB format for new apps. Google builds smaller APKs for each device from your bundle, so users download less data. Build it in Android Studio with Build, then Generate Signed App Bundle. You can also run ./gradlew bundleRelease from the command line.

3. App Signing and Release-Ready Build

Your upload must be a release build, not a debug build. Therefore, check these items before you build:

• Remove test code, debug logs, and placeholder text.
• Turn on code shrinking and obfuscation with R8.
• Enroll in Play App Signing. Google stores your app signing key, and you keep only an upload key.

4. Privacy Policy URL

Host your privacy policy on a public HTTPS page that loads without a login. Next, make sure the policy states what data you collect, why you collect it, and how users request deletion. It must also match your Data safety form.

5. App Store Listing Assets

Next, prepare these assets before you open the listing page.

App Icon

Use a 512 x 512 px, 32-bit PNG file. The file can be up to 1 MB.

Screenshots

Upload at least 2 and up to 8 screenshots per device type. Each file can be PNG or JPEG up to 8 MB. Show real app screens only.

Feature Graphic

Create a 1024 x 500 px image in JPEG or 24-bit PNG format without transparency.

App Description and Contact Details

Then write these fields before you start:

• App name: up to 30 characters
• Short description: up to 80 characters
• Full description: up to 4,000 characters
• Support email: required
• Website: optional

6. Test Device and Test Accounts

Test the release build on at least one physical Android device. Cover different Android versions and screen sizes. In addition, collect Gmail addresses for your testers, because closed testing needs them.

7. Demo Login Credentials for Reviewers

If your app needs a login, create a permanent demo account. Give reviewers the username, password, and any extra steps. Expired or locked accounts cause rejection.

Step-by-Step Guide: How to Submit an App to Google Play

Step 1: Create a Google Play Developer Account

The Google Play publishing process starts with a verified developer account. Expect this step to take a few business days.

Sign In to Google Play Console

Open play.google.com/console and sign in with a Google account. First, turn on 2-Step Verification. Then choose a personal or organization account.

Complete Developer Verification

Google requires identity verification for new developer accounts. Personal accounts submit a government ID. Organization accounts submit a D-U-N-S number and business details. This check matters because Google banned more than 80,000 developer accounts that attempted to publish harmful apps in 2025.

Pay the Google Play Console Registration Fee

Pay the USD 25 fee by card. The fee is one time, has no annual renewal, and is not refundable.

Accept the Developer Distribution Agreement

Read the agreement and accept it. Otherwise, Google blocks your uploads.

Step 2: Prepare Your Android App for Google Play

Your build must meet the Google Play publishing requirements before the console accepts it.

Use Android App Bundle Format

Export an AAB, not an APK. The console rejects APK uploads for new apps, so check your build settings.

Set the Correct Target API Level

Since August 31, 2026, new apps and updates must target Android 16 (API level 36) or higher. Wear OS and Android Automotive OS apps must target API level 35. Android TV and Android XR apps must target API level 34. Set both values in your Gradle file, as shown here:

android {

compileSdk = 36

defaultConfig {

targetSdk = 36

}

}

Android 16 turns on predictive back navigation by default for apps that target API level 36. As a result, you must test every back gesture before you upload.

Configure App Version Code and Version Name

Version code is an integer that must increase with every upload. Version name is the label users see, such as 1.0.0. Google Play rejects a bundle that reuses a version code.

Enable Play App Signing

Play App Signing is the default for new apps. Because Google holds the signing key, a lost upload key does not end your app. You can reset the upload key through Play Console support.

Test Core Features Before Submission

Run your full QA pass on the release build. For example, check login, payments, push notifications, and offline behavior. Our guide to Android App Development and the Android Dev Process article explain how to structure builds and QA before release.

Step 3: Create a New App in Google Play Console

The next part of how to submit an app to Google Play happens inside the console. You create the app record first, then attach your build later.

Go to All Apps and Select Create App

First, open Play Console, click All apps, then click Create app.

Add the App Name and Default Language

Enter the name users will see on Google Play. Next, pick your default language. You can add translations later.

Choose App or Game

Select the type that matches your product. This choice sets the categories you can pick.

Select Free or Paid

You can change a paid app to free later. However, you cannot change a free app to a paid. Choose carefully.

Complete Required Declarations

Confirm that your app follows the Developer Program Policies and US export laws. Then click Create app.

Step 4: Complete Your Google Play Store Listing

Your listing drives installs, so write it for users first. Follow the Google Play Store guidelines on metadata. Do not add price claims, ranking claims such as “best” or “#1”, or emoji to your app name.

Add Your App Name

Use the real name of the app in 30 characters or fewer. Put the main keyword in the name only if it describes the app accurately.

Write a Short Description

You have 80 characters. State the main benefit in plain words. Example: “Track expenses, set budgets, and export reports in one app.”

Write an SEO-Friendly Full Description

Put your main keyword and core benefit in the first two lines. Use short paragraphs and bullet points for features. Do not repeat keywords or list unrelated terms. For more ranking tactics, read our guide to App Store Optimization.

Select an App Category and Tags

Pick the one category that fits best. Add up to 5 tags that describe your app. Accurate tags improve search relevance.

Upload Your App Icon

Upload the 512 x 512 px PNG. Match it to the launcher icon inside the app.

Upload Screenshots and Promotional Graphics

Add at least 2 phone screenshots, plus the 1024 x 500 px feature graphic. Add tablet screenshots if your app supports tablets. Each screenshot must show a real feature.

Add Support Email, Website, and Privacy Policy

Enter a monitored support email. Add your website and the public privacy policy URL. Google checks that the link loads.

Step 5: Complete the App Content and Policy Declarations

Google compares these forms with your app’s real behavior. Missing or wrong answers violate Google Play policies, so finish each form before you upload.

Fill Out the Data Safety Form

List every data type your app collects or shares. Include data handled by third party SDKs such as analytics and ad libraries. State whether you encrypt data in transit and whether users can request deletion. Your answers must match your privacy policy. Review our App Security Best Practices before you answer.

Complete the Content Rating Questionnaire

Answer the IARC questionnaire honestly. Questions cover violence, sexual content, language, gambling, and user generated content. The system assigns ratings for each region.

Declare Ads in Your App

Tell Google if your app shows ads. The declaration adds an “Contains ads” label to your listing.

Add App Access Instructions

If any feature sits behind a login, paywall, or location restriction, add instructions. Provide working demo credentials. Reviewers cannot test what they cannot open.

Set Your Target Audience and Content for Children

Select the age groups you target. If children under 13 are in your audience, your app must comply with the Families Policy. Do not select child age groups unless your app is built for them.

Complete Sensitive Permissions Declaration, If Required

Some permissions need a written declaration. Examples include SMS, call log, background location, and all files access. Some declarations also need a short video that shows the feature in use. Request only the permissions your features need.

Step 6: Set App Pricing and Distribution

Pricing and distribution settings control who can install your app and what they pay.

Choose Free or Paid

Confirm the pricing model you selected in Step 3. However, paid apps also need a payment profile.

Select Countries and Regions

Choose the countries where you want to publish. Check local rules for each market, such as age limits and payment rules.

Configure In-App Purchases and Subscriptions

First, create products in the Monetize section of the Play Console. Then integrate the Google Play Billing Library in your app. Test purchases with license testers before launch.

Choose Device Availability

Review the device catalog in Play Console. Exclude devices that your app does not support. List phones, tablets, Wear OS, or TV only if you built for them.

Review Government Apps, News Apps, or Other Special Declarations

Some app types need extra declarations. These include government apps, news apps, health apps, and apps with financial features. Complete the ones that apply to you.

Step 7: Upload Your App Bundle to Google Play Console

This step covers how to upload an app to Google Play as an AAB. For a shorter walkthrough with screens, see our guide to Upload to Play Store.

Open the Testing or Production Track

Go to Testing or Production in the left menu. For a first upload, choose Internal testing. Personal accounts cannot use Production until the closed test is complete.

Create a New Release

Click Create new release. Then confirm that Play App Signing is active.

Upload the AAB File

Drag your signed AAB into the upload box. Play Console reads the package name, version code, and target API level. Wait until the upload finishes.

Add Release Notes

Write clear notes in each language you support. Release notes have a 500 character limit per language. Describe what is new in plain words.

Review Errors and Warnings

Google Play submission errors appear on the release summary page. Common ones include:

• Version code already used
• Target API level too low
• Missing 64-bit libraries for native code
• Missing permission declaration

Errors block the release. Warnings do not. Even so, read them.

Step 8: Test Your App Before Launching

Testing catches crashes and listing problems before reviewers do. Our Mobile App Dev Process guide shows where testing fits in the full lifecycle.

Use Internal Testing

Internal testing supports up to 100 testers. Because builds reach testers within minutes, you can use it for quick smoke tests on real devices.

Set Up Closed Testing

New personal Play Console accounts face a strict rule. Before they can apply for production access, they must run a closed test. At least 12 testers must stay opted in for 14 consecutive days. If a tester opts out, the 14 day count resets. Recruit a few extra testers to stay safe.

Consider Open Testing

Open testing lets anyone on Google Play join your beta. Use it to gather broader feedback and device coverage. Testers see your store listing, so finish the listing first.

Fix Crashes, Bugs, and Store Listing Issues

After you upload to a testing track, Play Console runs a prelaunch report on real devices. It flags crashes, slow screens, and accessibility issues. Fix every crash before you move on.

Collect Feedback Before Production Release

Ask testers to complete core tasks, then report problems. Also, track feedback in one place. Release only after you fix critical bugs.

Step 9: Submit Your App for Google Play Review

The final part of how to submit an app to Google Play is sending the release for review.

Review the Play Console Dashboard

First, open the Dashboard. Play Console lists every setup task that still needs action.

Resolve All Incomplete Tasks

Next, finish each task, including the store listing, Data safety form, content rating, and app access. Open tasks block Google Play app submission.

Send the App for Review

Go to Publishing overview and click Send changes for review. Google then checks your app against its policies. Google runs more than 10,000 safety checks on every published app and continues checks after release. Therefore, keep your declarations accurate after launch too.

Start the Production Rollout

After approval, start a staged rollout. Release to 10% to 20% of users first, then expand as crash rates stay low. Plan your launch campaign with our App Marketing Strategies guide.

Track Your App Review Status

Publishing overview shows whether changes are in review. In addition, Google emails the account owner with the result. Watch your Policy status page for any violation notice.

How Long Does Google Play App Review Take?

The Google Play submission process has two waits: the closed test for personal accounts and the review itself. Google states that reviews can take up to 7 days, and some take longer. The table shows typical timelines.

Therefore, submit at least one week before any launch date. Also, avoid stacking large changes in one release.

Common Reasons Google Play Rejects Apps

Even when you know how to submit an app to Google Play, rejection still happens when the app breaks a policy. Google prevented more than 1.75 million policy-violating apps from being published in 2025. Google Play app rejection notices name the violated policy, so read them closely.

1. App Crashes or Broken Features

Reviewers test on real devices. As a result, a crash on launch, a dead button, or a blank screen fails the review.

• Test on multiple Android versions.
• Fix every crash from the prelaunch report.
• Confirm that all core features work as described.

2. Misleading App Description or Screenshots

Your listing must describe the app as it works today. For example, do not claim features you have not built. Screenshots must show real screens, not mockups.

3. Missing or Incorrect Privacy Policy

A broken link, a policy on a login page, or a policy that ignores your data use causes rejection. Host the policy on a public HTTPS URL and keep it current.

4. Incomplete Data Safety Form

Blank fields and answers that clash with the app’s behavior trigger rejection. For example, an app that uses an analytics SDK but declares no data collection fails the check.

5. Invalid Demo Credentials or Restricted App Access

Reviewers cannot log in with expired passwords, locked accounts, or codes sent to your phone. Instead, provide a permanent demo account and clear access instructions.

6. Policy-Violating Content

Google rejects apps with deceptive behavior, malware, hate speech, or copyright violations. Apps with user generated content need moderation tools and a reporting option. Read the current Google Play policies before each major release.

7. Improper Use of Permissions

Request only the permissions your features need. Explain why you need each one before the system prompt appears. Otherwise, unneeded permissions, especially SMS, call log, and background location, draw the strictest review.

8. Low-Quality or Duplicate App Experience

Apps with few features, repeated content, or copied template code fail the quality checks. Add unique features and real value before you submit.

How to Avoid Google Play Store Rejection

Apply these Google Play best practices before every release. Google’s prereview checks can identify improper credential handling, permissions issues, and broken privacy policy links. Catch the same problems in your own audit first.

1. Test Every Core User Journey

Walk through sign up, login, purchase, and account deletion on a release build. Test on low end and current devices. In addition, test with a slow network.

2. Make Metadata Match the Actual App

Compare your description, screenshots, and Data safety answers with the live build. Then update any field that no longer matches.

3. Remove Placeholder Content

Delete lorem ipsum text, sample images, test banners, and “coming soon” screens. Reviewers treat them as unfinished work, so remove them all.

4. Provide Active Login Credentials

Test your demo account on the day you submit. Turn off two step prompts for that account. Keep the account active while the app is live.

5. Follow Google Play Developer Policies

Read the Developer Policy Center when you start development, not after rejection. Subscribe to policy update emails. Also, recheck your app after each policy change.

6. Review Your Release Before Submission

Open the release summary and read every message. Fix Google Play submission errors in this order: errors first, then warnings, then store listing tasks. Then run the prelaunch report one more time. Finally, ask a teammate to complete the submission checklist.

Publishing an app means handling code, policy forms, and store assets at the same time. A development partner takes on the technical and compliance work, so your release does not stall on a missing form or a wrong API level.

How a Development Partner Supports Google Play Submission

Publishing an app means handling code, policy forms, and store assets at the same time. A development partner takes on the technical and compliance work, so your release does not stall on a missing form or a wrong API level.

Cubix is a custom mobile app development company that handles the full release cycle, from signed builds to Play Console setup and post-launch updates.

What a Development Partner Handles

• Build and signing: The team creates the signed AAB, sets the target API level to 36, and configures Play App Signing and version codes.
• Policy forms: The team audits your SDKs and permissions, then completes the Data safety form so every answer matches real app behavior.
• Store listing: The team prepares screenshots, the feature graphic, and metadata that match the live app.
• Testing: The team runs QA on real devices, sets up internal and closed test tracks, and manages the 12 tester, 14 day requirement.
• Error resolution: The team reads release errors and rejection notices, finds the cause, and ships the fix.
• Post-launch monitoring: The team tracks crash rate and ANR rate in Play Console, releases updates, and keeps your declarations current.

Frequently Asked Questions

1. What are the requirements to publish on Google Play Store?

Before you follow how to submit an app to Google Play, confirm four things. You need a verified Play Console account, a signed AAB that targets API level 36, and a privacy policy URL. You also need complete listing assets and finished policy forms. Personal accounts must pass a closed test too, with 12 testers over 14 days.

2. How long does Google Play Store review take?

Google states that reviews can take up to 7 days, and some take longer. Updates to established apps often clear in 1 to 3 days. However, new accounts and sensitive permissions add time.

3. What is the difference between APK and AAB format?

An APK is a single installable file. An AAB is a publishing format, and Google uses it to build smaller APKs for each device. Google Play requires AAB for new apps.

4. Why was my app rejected from Google Play?

The top app rejection reasons are crashes, privacy policy errors, incomplete Data safety forms, and invalid demo credentials. Your Policy status page names the violated policy. Fix the issue, then resubmit.

5. How do I create a Developer Account on Google Play?

Sign in to Play Console with a Google account and choose personal or organization. Complete identity verification, pay the USD 25 fee, and accept the agreement.

6. What information do I need for app listing?

You need the app name, short and full descriptions, icon, screenshots, and feature graphic. You also need a category, support email, and privacy policy URL.

7. Can I publish a beta version of my app?

Yes. Use an internal, closed, or open testing track. In addition, a closed test satisfies the 12 tester requirement for new personal accounts.

8. How do I update my app after publishing?

Increase the version code and upload a new AAB in a new release. Add release notes, keep the target API level at 36 or higher, and send the changes for review.

9. What payment methods does Google Play accept?

Developers pay the USD 25 registration fee by card. Users pay with cards, carrier billing, gift cards, and PayPal in supported countries. Available methods vary by country.

10. How do I monitor my app performance after launch?

Use the Play Console Dashboard, Statistics, and Ratings and reviews pages. Next, watch Android vitals for crash rate and ANR rate. If a spike appears, fix it quickly with a new release.