Back to Blog
google play consoleapp publishingandroidgoogle playindie developers

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

October 27, 2026
3 views

Quick answer: To publish on Google Play in 2026 you create a Play Console developer account (one-time US$25 fee plus identity verification), create the app, upload an Android App Bundle that targets Android 16 (API level 36), fill in the store listing and the App content declarations, and send a release for review. If you have a personal account created after November 13, 2023, you must first run a closed test with at least 12 testers opted in for 14 continuous days before you can apply for production access.

Most "Play Console" guides were written before those two rules existed. This one walks through the whole path in the order you will actually hit it, with links to Google's own help pages for every requirement, so you can check anything that has changed since this was written.

What Google Play Console is (and isn't)

Google Play Console is Google's web dashboard for publishing and managing Android apps on Google Play. You use it to create app records, upload builds, manage testing tracks, edit your store listing, answer policy declarations, read crash and ANR data, and reply to reviews. It does not build your app; Android Studio or your CI does that. It is the Android counterpart of App Store Connect, and if you are shipping on both stores, our launch checklist for App Store Connect and Play Console lines the two up side by side.

Step 1: Create your developer account

Sign up at play.google.com/console with a Google Account. You make two decisions here, and both are hard to undo:

  • Personal or organization account. Organization accounts are for registered businesses and require a D-U-N-S number and a website. Google notes that getting a D-U-N-S number from Dun & Bradstreet is free but can take up to 30 days, so request it early. Personal accounts are for individual developers, students and hobbyists.
  • Payment of the registration fee. Full distribution costs a one-time US$25 fee. It is not annual and not per app.

You will then verify your identity. For organizations that means official organization documents plus ID for the account owner or an authorized representative, and the details must match the linked Google payments profile exactly. Google also verifies your contact email and phone with one-time codes, and some of your contact details are shown on your store listing, so use addresses you are comfortable making public.

Indie tip: if you are a solo developer with a registered company, the organization account route skips the closed-testing requirement below. If you don't have a company, don't create one just for this; the personal route works, it just takes two more weeks.

Step 2: Create the app record

In Play Console, choose Create app, then set the app name (up to 30 characters on the listing), default language, whether it is an app or a game, and whether it is free or paid. Note that a free app cannot later be switched to paid. You will also confirm that the app complies with the Developer Program Policies and US export laws.

The dashboard then shows a setup checklist. Work through it top to bottom; it is the most reliable source of what your account still needs.

Step 3: Build an Android App Bundle that meets the target API level

New apps on Google Play are published as Android App Bundles (.aab), and Google signs the APKs it delivers through Play App Signing. Upload your first bundle to a testing track rather than straight to production.

Check your targetSdkVersion before you upload. According to Google's target API level page, starting August 31, 2026, new apps and app updates must target Android 16 (API level 36) or higher, with lower floors for Wear OS, Android Automotive OS, Android TV and Android XR apps. Existing apps must target at least API level 35 to stay available to new users on newer Android versions. Google says you can request an extension to November 1, 2026 if you need more time. If a library you depend on doesn't support the new target yet, fix that first; it is the most common reason a "simple" upload turns into a week of work.

Step 4: Run the closed test (new personal accounts)

This is the step that surprises most first-time Android developers. Google's rule, as stated in the Play Console Help Center:

  • It applies to personal developer accounts created after November 13, 2023. Organization accounts are not subject to it.
  • You must run a closed test (internal testing doesn't count) with at least 12 testers who have been opted in continuously for at least the last 14 days when you apply.
  • Production and pre-registration stay disabled until you meet it. Then you click Apply for production on the Dashboard and answer questions about your closed test, your app and your production readiness.

Google originally required 20 testers and lowered it to 12 in December 2024. A few practical notes:

  • Recruit more than 12. If a tester opts out, their 14 days restart when they rejoin. Inviting 15 to 20 people gives you a buffer.
  • Ask for real use, not just installs. The production application asks what you learned during testing. Keep a short log of the feedback and fixes from the closed test so you can answer honestly.
  • Use the time. Two weeks is long enough to finish the store listing, the content forms below, and your screenshots.

Step 5: Fill in the store listing

Under Grow users > Store presence > Main store listing you need, at minimum:

Asset Requirement (from Google's help page)
App name Up to 30 characters
Short description Required, up to 80 characters
Full description Up to 4,000 characters
App icon Required: 512 × 512 px, 32-bit PNG with alpha, max 1,024 KB
Feature graphic Required: 1024 × 500 px, JPEG or 24-bit PNG (no alpha)
Screenshots At least 2 across device types, up to 8 per device type; JPEG or 24-bit PNG, 320 to 3,840 px, longest side no more than twice the shortest

To be eligible for the large-format recommendation surfaces, Google asks apps for at least four screenshots at 1080 px or more (9:16 portrait at 1080 × 1920 px minimum, or 16:9 landscape at 1920 × 1080 px minimum). Google's listing guidelines also tell you to avoid "Best", "#1", "Free" or "Sale" style claims and call-to-action text like "Download now" in your short description and graphics.

The short description deserves real effort: it is the first text people see on your listing and it can appear outside your store page. If you need a size-by-size reference for both stores, see our App Store and Google Play screenshot sizes cheat sheet, and for the creative side, the screenshot guide.

Step 6: Complete the App content declarations

Under Policy and programs > App content, Google asks a series of questions before you can publish. The exact list depends on your app, but most apps see:

  • Privacy policy URL (required for most apps, and for any app that handles personal or sensitive data).
  • App access: if parts of the app need a login, give reviewers working credentials or instructions.
  • Ads: whether the app contains ads.
  • Content rating: an IARC questionnaire that produces age ratings for each region.
  • Target audience and content: the age groups you target. Targeting children brings extra Families policy requirements.
  • Data safety: what data you collect and share, and why. This appears on your listing as the Data safety section, so it must match what your app and your SDKs actually do.

Answer these from what the app and its third-party SDKs really do, not from what you hope they do. Analytics and ad SDKs are the usual source of mismatches.

Step 7: Release and review

Create a release on the production track (or promote your tested build), write release notes, choose countries, and send it for review. Google's Help Center says reviews for some developer accounts can take up to 7 days or longer in exceptional cases, so don't promise a launch date that depends on same-day approval. You can follow the status in the Publishing overview.

After launch, use staged rollouts for updates, watch Android vitals for crashes and ANRs, and reply to reviews. Ratings influence how your listing converts, and replying is one of the few levers you control directly.

Common mistakes that delay a first Android launch

  1. Choosing a personal account by accident and then discovering the 14-day closed-test clock.
  2. Starting the closed test with exactly 12 testers; one drop-out resets your wait.
  3. Targeting an old API level because a template or plugin pinned it.
  4. A Data safety form that contradicts an SDK you shipped.
  5. A login wall with no reviewer credentials in App access.
  6. Promotional text in graphics ("#1 app", "Free download"), which Google's asset guidelines ask you to avoid.

Where Forvibe fits

Forvibe is an AI ASO Agent built primarily for the App Store. On Google Play today it handles review replies; you still publish Android builds through Play Console yourself. If you ship on both stores, Forvibe's store listing manager and Play Console API connection keep your listing copy in one place, and the both-stores use case shows how teams split the work. You can start free and see what your App Store listing is missing before your next release.

FAQ

How much does Google Play Console cost?

A one-time US$25 registration fee for a full-distribution developer account. There is no annual fee and no per-app fee.

Do I need 12 testers to publish on Google Play?

Only if you have a personal developer account created after November 13, 2023. You need a closed test with at least 12 testers opted in continuously for 14 days before applying for production access. Organization accounts are exempt.

Does internal testing count toward the 14 days?

No. Google's requirement specifically names a closed test. Internal testing is useful for quick builds but doesn't satisfy it.

What target API level do I need in 2026?

From August 31, 2026, new apps and updates must target Android 16 (API level 36) or higher, with exceptions for Wear OS, Android Automotive OS, Android TV and Android XR. An extension to November 1, 2026 can be requested.

How long does Google Play review take?

It varies. Google says some reviews can take up to 7 days or longer in exceptional cases. Plan your launch with that buffer.

Sources