How to publish an app on Google Play, step by step (2026)

What are the steps to publish an app on Google Play?

Publishing on Google Play is eight steps, and only two of them involve waiting on Google: the production access review (new personal accounts) and the release review. Here is the whole path at a glance.

Step	Where in Play Console	Typical blocker
1. Developer account	Sign-up page	ID and card name must match your legal name
2. Create the app	Home, Create app	Wrong app or game choice, wrong default language
3. App content forms	Monitor and improve, Policy and programs, App content	Missing privacy policy, sign-in details for review
4. Store listing	Grow users, Store presence, Store listings	Feature graphic and screenshots missing
5. Build	Test and release, App bundle upload	Old target API, APK instead of App Bundle
6. Testing	Test and release, Testing	12 testers for 14 days (new personal accounts)
7. Production access	Dashboard, Apply for production	Thin answers about the closed test
8. Production release	Test and release, Production	Review time, countries not selected

Step 1: How do you open a developer account?

You sign up with a Google Account, accept the Developer Distribution Agreement, pay the one-time 25 USD fee and choose a personal or organization account. You must be at least 18. Google then verifies your identity with a government ID and a card under your legal name; organization accounts also need a D-U-N-S Number. Personal accounts additionally verify access to a real Android device through the Play Console mobile app.

The decision between personal and organization matters more than it looks: it decides whether the 12-tester rule applies. The full walkthrough is in Google Play developer account.

Step 2: How do you create the app in Play Console?

From the Play Console home page, click Create app and fill in:

App name: as it will appear on Google Play (up to 30 characters; you can change it later).
Default language: the language of your main store listing.
App or game: you can change this later.
Free or paid: decide carefully. Plan for a free app with in-app purchases or subscriptions if there is any chance you will charge later.
Contact email and the declarations: Developer Program Policies, US export laws, and the Play App Signing terms.

The package name (applicationId in your build) is set by your first upload and identifies the app permanently. Pick it before you upload anything.

Step 3: Which App content forms must you complete?

Google will not review a release until the App content page is complete. Open Monitor and improve, Policy and programs, App content and work through each card:

Privacy policy: a public URL. Required for nearly every app, and always when you handle personal or sensitive data.
App access: if any part of the app is behind a login, give reviewers working credentials and instructions.
Ads: declare whether the app shows ads, including through third-party SDKs.
Content rating: fill in the questionnaire to receive age ratings from the official rating authorities.
Target audience and content: the age groups your app is designed for. Choosing children's ages brings extra policy requirements.
Data safety: what user data the app collects and shares, and why. Every published app completes it, including apps that collect nothing.
Permissions declarations: only when you request high-risk permissions such as SMS or call log.
Category-specific declarations: for example financial features, health, news or government apps, when they apply.

The most common review delay at this stage is App access: a login screen with no test account.

Step 4: What goes into the store listing?

Open Grow users, Store presence, Store listings. These are the fields and files Google requires to publish:

Asset	Requirement
App name	Up to 30 characters
Short description	Up to 80 characters
Full description	Up to 4,000 characters
App icon	512 x 512 px, 32-bit PNG with alpha, up to 1,024 KB
Feature graphic	1,024 x 500 px, JPEG or 24-bit PNG, no alpha; required
Screenshots	At least 2 in total across device types, up to 8 per device type; JPEG or 24-bit PNG; each side 320 to 3,840 px; the long side at most twice the short side
Contact email	Required; a website is recommended
Category and tags	Set in Store settings; up to 5 tags

Your text is also policy-checked. Google's metadata policy bans emoji and repeated special characters in the title, all-caps unless it is your brand, and ranking or price claims such as "#1", "best app of the year" or "50% off" in text and graphics. Repetitive or unrelated keywords in the name or descriptions can get the app suspended. Write for people first; what ASO is explains how the store reads these fields.

Step 5: What build does Google Play accept?

Upload an Android App Bundle (.aab). Since August 2021 new apps must use App Bundles, and Google Play generates and signs device-specific APKs under Play App Signing.

The build must also meet the target API level rule. From August 31, 2026, new apps and app updates must target Android 16 (API level 36). Existing apps must target at least API 35 to stay available to new users; Wear OS, Android Auto and Android TV have their own thresholds. Check targetSdk before the upload, not after a rejection.

Step 6: How does testing work before production?

Play Console has three testing tracks under Test and release, Testing:

Internal testing: up to 100 testers, builds available within minutes. Best for your own team.
Closed testing: invited testers by email list (up to 2,000 per list) or Google Group. This is the track the 12-tester rule counts.
Open testing: anyone can join from your store listing; you can cap the number at 1,000 or more.

Testers cannot leave public reviews for test versions; they send private feedback instead. Details and the "item not found" fixes are in internal vs closed vs open testing.

If your personal account was created after November 13, 2023, you must run a closed test with at least 12 testers opted in for 14 consecutive days before you can apply for production. If someone opts out and back in, their days restart. Organization accounts skip this. The full playbook is in the 12 testers for 14 days rule.

Step 7: How do you apply for production access?

When the closed test has run its 14 days, open the Dashboard and click Apply for production. The form has three parts:

About your closed test: how easy recruiting was, whether testers used all features, whether their use matched real users, and what feedback you got and how.
About your app: target audience, what makes the app valuable, and your estimated installs in the first year.
Production readiness: what you changed because of the test, and how you decided the app is ready.

Google says this review usually takes seven days or less and emails the account owner with the result.

Step 8: How do you roll out the production release?

Open Test and release, Production, choose the countries and regions, then Create new release, add the App Bundle (or promote one from testing), write the release notes and click Review release, then Start rollout to production. For a first release the app goes to everyone in the chosen countries; staged rollouts are only for updates (see phased release and staged rollout).

Google reviews the release. Its help pages say review can take up to 7 days, or longer in exceptional cases, and some accounts get extended reviews. Track it on the Publishing overview page. If you want to control the exact moment it goes live, turn on managed publishing there: approved changes then wait until you click publish, and go live within minutes. Timing details are in Google Play review time.

Checklist before you click "Start rollout"

Account verified; payments profile set up if you sell anything.
Every App content card complete, with a working test login if needed.
Privacy policy URL loads and matches the Data safety answers.
Icon, feature graphic and at least 2 screenshots uploaded.
Title, short and full description free of emoji, caps, rankings and price claims.
App Bundle signed, targetSdk at the required level, versionCode higher than any previous upload.
Closed test passed and production access granted (new personal accounts).
Countries selected; managed publishing on if launch timing matters.

Common mistakes that cost weeks

Choosing a personal account for a company, then hitting the 12-tester rule.
Testers who join but never install, or uninstall on day 3. Google counts opted-in testers continuously; plan for more than 12.
Buying testers from strangers. Policy bans fake or incentivized engagement, and a test that real users never touched makes the production application weak.
Writing marketing claims ("the #1 app") in the title. That is a policy problem, not a style choice.
Forgetting that review can take a week: do not announce a launch date before the release is approved.

Publishing on iOS too?

The Apple side has different costs (99 USD a year) and a different test system. Follow How to publish an app on the App Store for the parallel path, and use Play Console basics if the panel itself is new to you.

What should you track after launch?

The day your app is live, its search position starts to matter. Uptika's Keyword radar reads your Google Play rank for each keyword every day, in each country you choose. When you submit new store text, Uptika watches the public page and marks the day it goes live, so you can compare ranks before and after. From the Starter plan, the Rival log also shows when competitors change their title, icon or screenshots. Start on the free plan: one app, one storefront, 10 keywords. To check your listing text before you submit, the free Metadata Linter flags limits, repeats and claims in your browser.

Questions

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

A Google Play developer account is a one-time 25 USD registration fee. There is no yearly fee and no per-app fee. Google takes a service fee only when you sell something through Google Play billing.

Can I publish an app on Google Play for free?

Not entirely: the 25 USD registration is required once. After that, publishing any number of free or paid apps costs nothing extra.

How long does it take to publish an app on Google Play?

Plan for the account verification, then 14 days of closed testing if you have a new personal account, up to 7 days for the production access review, and a review of the first release that Google says can take up to 7 days or longer in exceptional cases.

Do I need 12 testers to publish on Google Play?

Only if your account is a personal account created after November 13, 2023. Those accounts must run a closed test with at least 12 testers opted in for 14 days in a row before applying for production. Organization accounts are not subject to this rule.

Can I upload an APK instead of an App Bundle?

Not for a new app. Since August 2021, new apps on Google Play must be published as Android App Bundles (.aab), and Google Play generates and signs the APKs for each device.

Which target API level does Google Play require in 2026?

From August 31, 2026, new apps and updates must target Android 16 (API level 36). Existing apps must target at least API 35 to stay visible to new users, with exceptions for Wear OS, Android Auto and Android TV.