How to Publish an App on Google Play: Step-by-Step Guide (2026)

Quick answer: To publish an app on Google Play, register a Play Console account (a one-time US$25 fee plus identity verification), create the app, complete the App content declarations, build the store listing, and upload a signed Android App Bundle to a testing track. New personal accounts need a 14-day closed test with at least 12 testers before production access. Then send the release for review.

Google Play offers two developer account types, and the choice changes your path to production.

If you're shipping for a company, set up an organization account from the start. Moving apps between accounts later is possible but adds paperwork.

Your app also needs to meet Google Play's target API level requirement. From August 31, 2026, new apps and updates must target Android 16 (API level 36) or higher, with exceptions for Wear OS, Android TV, Android XR and Automotive apps.

In Play Console, choose Create app and fill in:

1. App name as it should appear on Google Play (30 characters max; you can change it later).
2. Default language for your store listing.
3. App or game (changeable later).
4. Free or paid. Choose carefully: you can switch a paid app to free, but once an app has been offered for free, it can't become paid. You'd need a new app with a new package name.
5. Declarations: accept the Developer Program Policies, US export laws and the Play App Signing terms.

Your package name (for example com.yourcompany.yourapp) comes from your first upload and is permanent.

The app dashboard lists the setup tasks Google needs before release. Expect these:

Answer these from what the app actually does, including third-party SDKs. The privacy labels and Data safety guide covers the common mistakes.

Your main store listing is what converts visitors into installs. Requirements to have ready:

• Text: app name (30 characters), short description (80) and full description (4,000).
• App icon: 512 × 512, 32-bit PNG, up to 1 MB, a full square that Google Play masks itself. See Google Play icon requirements.
• Feature graphic: 1024 × 500, JPEG or 24-bit PNG with no alpha.
• Phone screenshots: 2 to 8, JPEG or 24-bit PNG with no alpha, each side 320 to 3,840 px, the long side no more than twice the short side. For eligibility in recommendations, provide at least four with a short side of 1,080 px or more.
• Tablet and other form factors if you support them.
• Promo video: optional, as a YouTube URL.

The Google Play screenshot sizes guide has the exact pixel options, and the store listing guide walks through every field.

New apps are published as Android App Bundles (.aab). Google Play generates optimized APKs for each device configuration from the bundle and signs them with Play App Signing; you sign uploads with your own upload key.

1. In Android Studio, choose Build > Generate Signed App Bundle or APK, select Android App Bundle, and sign with your upload key.
2. Increase versionCode for every upload; Play rejects a bundle that reuses one.
3. In Play Console, open the Internal testing page, create a release, and upload the bundle.
4. Add testers by email list and share the opt-in link.

Internal testing is the fastest way to check that the bundle installs and that sign-in, purchases and deep links work on real devices. Store listing graphics don't need to be final for this stage.

If you have a personal account created after November 13, 2023, Google currently requires a closed test before production. You need at least 12 testers who have been opted in continuously for at least 14 days.

1. Open the Closed testing page, create a release, and upload your bundle.
2. Add testers by email list or Google Group, and share the opt-in link.
3. Keep at least 12 testers opted in for 14 straight days. People who opt out reset your count.
4. Ship real fixes during the test; Google asks about your testing when you apply.
5. When you qualify, click Apply for production on the Dashboard and answer the questions about your test.

Google says reviewing a production access application usually takes seven days or less, but can take longer. Google Play closed testing has tips for recruiting testers who actually stay opted in.

Create a production release, add release notes, and review the warnings Play Console shows. Then go to Publishing overview: your changes aren't sent for review automatically, so click Send changes for review.

• Review time: Google says that for certain developer accounts, reviews can take up to seven days or longer in exceptional cases. Updates to existing apps are usually published as soon as possible.
• Managed publishing: turn it on if you want approved changes to wait until you click Publish, which helps you line up a launch date.
• Staged rollout: release to a percentage of users first, watch crashes and ratings, then increase.
• Pre-review checks: Play Console runs automated checks on some issues before review, which can catch problems early.

After the first review passes, your app appears on Google Play in the countries you selected. Updates follow the same path: upload a new bundle with a higher versionCode, add release notes, and send for review.