How much does it cost to publish on Google Play?

The Google Play developer account is a one-time $25 fee. That's the only mandatory cost — everything else (store assets, testing devices, marketing) is up to you.

How long does Google Play review take?

For new apps, typically a few days up to about a week. Updates to existing apps are usually faster. Policy-sensitive categories and Families-targeted games can take longer.

Why do games get rejected on Google Play?

The most common causes are inaccurate data safety declarations, content rating mismatches, targeting an outdated API level, broken or placeholder store listings, and crashes found by the pre-launch report.

How to Publish a Game on Google Play: Step-by-Step (2026)

Step 1 — Create your developer account

Head to the Google Play Console and register as a developer. It's a one-time $25 fee. You'll choose between a personal and an organization account — if you're a company, register as an organization (it looks more credible on your store listing and avoids some of the extra verification steps personal accounts face). Have identity documents ready; Google verifies new developers before you can publish.

Step 2 — Prepare the build

Google Play requires an Android App Bundle (AAB), not an APK, signed with a release key. Enroll in Play App Signing (the default) so Google manages your signing key — it protects you if your local key is ever lost. Target the current API level Google requires for new apps; builds targeting old Android versions are rejected automatically. Test the release build on real devices, not just the emulator — crashes in the first session are the fastest route to bad reviews.

Step 3 — Build a store listing that converts

Your listing is a landing page, not a formality. You'll need a 512×512 icon, a 1024×500 feature graphic, at least two screenshots per device type, a short description (80 characters — treat it like ad copy), and a full description. Put your strongest hook and keywords in the first lines of both descriptions: they carry the most weight for Play Store search, and most visitors never tap "read more."

Step 4 — The compliance forms everyone underestimates

Three questionnaires block more launches than anything technical: the content rating questionnaire (answer honestly — misrating gets apps pulled), the data safety form (declare every SDK that collects data, including your ads and analytics SDKs — Google cross-checks), and the ads declaration. If your game targets children or has mixed audiences, the Families policy adds more requirements. Budget an afternoon to do these carefully; a rejection here costs you a review cycle of several days.

Step 5 — Test, then launch

Run a closed test with real testers before production — Google requires it for new personal accounts and it's good practice for everyone. Use the pre-launch report: Google runs your game on real devices and flags crashes, performance issues, and accessibility problems for free. When the test looks clean, promote to production. Reviews for new apps typically take from a few days up to a week — plan your marketing dates around that, not around the day you press the button.

After launch — the part that decides your downloads

Publishing is the start line. The store algorithm watches early signals: crash rate, retention, ratings velocity, and conversion from listing views to installs. Respond to reviews, ship fixes fast, and iterate your screenshots and descriptions — App Store Optimization is an ongoing process, not a launch task. We cover the revenue side in our guide to earning from games.

How to publish a game on Google Play