Skip to content

Google Play requirements for games: a 2026 checklist

To publish and keep updating an Android game on Google Play in late 2026, a small studio needs a verified developer account (a one-time US$25), an Android App Bundle that targets API level 36, native libraries that support 16 KB memory pages, and a complete set of declarations: privacy policy, Data safety, ads, target audience and content rating. New personal accounts must also run a closed test with 12 testers for 14 days before production. The next hard date is 1 February 2027, when updates without 16 KB support can no longer be released.

By Futigo · Updated · 11 min read

Key points

  • A Play Console account costs a one-time US$25, and personal accounts created after 13 November 2023 must run a closed test with 12 testers for 14 days before applying for production.
  • Since 31 August 2026, new apps and updates must target Android 16 (API level 36); the extension Google offered ran to 1 November 2026.
  • From 1 February 2027, updates that do not support 16 KB memory pages cannot be released.
  • Games that sell digital items must use a supported Play Billing Library: version 8 is accepted until 31 August 2027, and version 9 until 31 August 2028.
  • Android vitals lowers a game's visibility above a 1.09% user-perceived crash rate or a 0.47% user-perceived ANR rate.

The checklist

Each row is a rule Google states on its own pages. The source column names the page; the links are in the sections below and in the source list.

Google Play requirements for publishing an Android game, November 2026
RequirementWhat it isCurrent threshold or deadlineOfficial source
Developer accountA Play Console account, personal or organisation. You must be at least 18.US$25, one-timePlay Console Help: Get started with Play Console
Identity verificationLegal name and address from a Google payments profile, verified with a government identity document. Organisations also need a D-U-N-S number. Contact email and phone are verified by one-time password.Before you can publishPlay Console Help: Required information; Verify your developer identity information
Device verificationPersonal account owners verify access to a physical, non-rooted Android device (Android 10 or later) with the Play Console mobile app.Before publishingPlay Console Help: Device verification requirements
Closed testPersonal accounts created after 13 November 2023 must run a closed test before applying for production access.At least 12 testers opted in continuously for 14 daysPlay Console Help: App testing requirements for new personal developer accounts
Android developer verificationApps must be registered by a verified developer to install on certified Android devices. Play Console developers use their Play account, and apps using Play App Signing are part of automatic registration.In force since 30 September 2026 in Brazil, Indonesia, Singapore and Thailand; global in 2027developer.android.com/developer-verification
Android App BundleNew apps must be uploaded as an .aab, not an APK.Since August 2021developer.android.com: About Android App Bundles
Play App SigningGoogle holds the app signing key; you sign uploads with an upload key (RSA, 2048 bits or more). A lost upload key can be reset.Terms accepted when you create the appPlay Console Help: Use Play App Signing
Download sizeLimits apply to the compressed download size.Base module 500 MB; install-time total 4 GB (see below)Play Console Help: Google Play app size limits
Target API levelThe Android version your build declares it targets.New apps and updates: Android 16 (API level 36) since 31 August 2026. Existing apps: API level 35 to stay available to new users on newer Android versions.developer.android.com: Meet Google Play's target API level requirement
16 KB page sizeApps targeting Android 15 or higher must support 16 KB memory pages on 64-bit devices. This concerns native code, which every game engine ships.Updates without support cannot be released from 1 February 2027developer.android.com: Support 16 KB page sizes
Privacy policyA link on the store listing and inside the app, even if the game collects no personal data.Required to complete the Data safety formPlay Console Help: Prepare your app for review
Data safety formA declaration of what data the game and its SDKs collect and share.Required for closed, open and production tracks; internal testing is exemptPlay Console Help: Provide information for Google Play's Data safety section
Ads declarationSay whether the game contains ads, including house ads for your other games. A plain "More Games" menu entry does not count.Must be accurate; misrepresenting it can lead to suspensionPlay Console Help: Prepare your app for review
Target audience and Families policyDeclare the target age groups. If children are included, the Families policy applies.Before publishingPlay Console Help: Google Play Families Policies
Content ratingThe IARC questionnaire, for new apps, unrated apps and any update that changes the answers.Unrated apps may be removedPlay Console Help: Content rating requirements
Play BillingIn-game digital items such as virtual currency, extra lives and characters must be sold through Google Play's billing system, unless a listed exception or regional programme applies.Library version 8 or 9 for new apps and updatesPlay Console Help: Payments; developer.android.com: Billing Library deprecation FAQ
Account deletionIf players can create an account in the game: an in-app path and a web link to delete the account and its data.Enforcement possible since 31 May 2024Play Console Help: Understanding Google Play's app account deletion requirements
Android vitalsStability measured on real devices, averaged over 28 days.Crash rate under 1.09% and ANR rate under 0.47% overall; under 8% on any one phone modeldeveloper.android.com: Android vitals

Read on 15 November 2026 from the Play Console Help and developer.android.com pages named in each row. This is a summary of published rules, not legal advice; the Developer Program Policies take precedence.

Before you create the account

Choose the account type with care, because the paperwork differs. Get started with Play Console gives the fee as a one-time US$25 and says prepaid cards are not accepted. A personal account needs your legal name, legal address and a government identity document. An organisation account also needs a D-U-N-S number, which is free from Dun & Bradstreet but, by Google's account requirements page, can take up to 30 days to arrive.

Know what becomes public. For a personal account Google Play shows your legal name, country and developer email address, and your full address if you monetise. For an organisation it shows the legal name, D-U-N-S number, legal address, developer email and developer phone number.

A new personal account then has to pass the closed testing requirement: at least 12 testers opted in continuously for 14 days. A tester who leaves and rejoins starts the 14 days again. Google says the production access review usually takes seven days or less, and that it may ask for more testing if tester engagement was too low. The rule as written applies to personal accounts only.

Separately, Android developer verification began on 30 September 2026 for installs from participating stores, Google Play included, in Brazil, Indonesia, Singapore and Thailand, with a global rollout stated for 2027. Play developers handle it inside Play Console, and Google's FAQ says apps using Play App Signing are part of automatic registration.

Before the first upload

The build has to be an Android App Bundle signed with your upload key. Keep that key safe, but losing it is not fatal: Play App Signing lets you request a reset. The size limits are generous for a small game: 500 MB for the base module, 1.5 GB for a single asset pack, 4 GB in total for modules and install-time asset packs, and 30 GB for packs delivered fast-follow or on demand. Above 200 MB, players on mobile data see a size warning before installing. Larger games move art and audio into asset packs with Play Asset Delivery.

Then fill in the App content page, as set out in Prepare your app for review: privacy policy, ads, sign-in details if any part of the game is behind a login, target audience, content rating and Data safety. The privacy policy must be a public web page, not a PDF. Ad and analytics SDKs count as your data collection, so check what they send before answering.

Games draw children, so read the Families policy before choosing age groups. Google may judge the audience from your imagery, whatever you declare. If children are in the target audience, ads shown to them must come from Families Self-Certified Ads SDKs, must not be personalised, and must be closeable after 5 seconds when they interrupt play. A game for both children and adults needs a neutral age screen.

Google Play store listing asset sizes for a phone game
AssetSizeFormatNotes
App icon512 x 512 px32-bit PNG with alphaMaximum file size 1024 KB
Feature graphic1024 x 500 pxJPEG or 24-bit PNG, no alphaShown behind the preview video's play button and in large game recommendations
ScreenshotsEach side between 320 px and 3840 px; the long side no more than twice the short sideJPEG or 24-bit PNG, no alphaAt least 2 to publish, up to 8 per device type
Screenshots for game recommendations16:9 landscape, at least 1920 x 1080 px, or 9:16 portrait, at least 1080 x 1920 pxAs aboveAt least 3, showing the game being played
Tablet and Chromebook screenshotsBetween 1,080 px and 7,680 px, 16:9 or 9:16As aboveA minimum of 4
Preview videoA YouTube URLPublic or unlisted, ads off, not age-restrictedOnly the first 30 seconds autoplay
Short description80 charactersTextGoogle advises against emoji, special characters and repeated punctuation

From Play Console Help, "Add preview assets to showcase your app", read on 15 November 2026.

Before each update

  • Target API level. The target API page requires API level 36 for new apps and updates. The extension it offered ended on 1 November 2026, and the page gives no 2027 date yet.
  • 16 KB pages. Google's page size guide says NDK r28 and higher build 16 KB aligned libraries by default, with Android Gradle Plugin 8.5.1 or higher for packaging. Every prebuilt SDK in the game has to comply as well.
  • Billing Library. The deprecation table stopped accepting version 7 on 31 August 2026, with an extension to 1 November 2026. Version 8 runs to 31 August 2027 and version 9 to 31 August 2028. The latest release in Google's notes is 9.1.0, dated 18 June 2026.
  • Declarations. A new ad SDK, a new login or new content can change your Data safety, ads and content rating answers. Update them with the build.
  • Pre-launch report and pre-review checks. Play Console crawls an uploaded bundle on lab devices for several minutes when capacity allows, and reports stability, compatibility, performance and accessibility issues. The crawler works with standard Android widgets, so a game that draws its own interface needs a game loop to be tested in any depth.
  • Android vitals. The thresholds are judged on the last 28 days of data. Above them, Play may reduce the game's visibility and show a warning on its listing.
Google Play dates to watch, November 2026 to November 2027
DateWhat changesWho it affects
31 December 2026The new service fee model and expanded billing choice reach South Korea, Türkiye and South Africa.Games earning from players in those countries
1 February 2027Updates that do not support 16 KB memory pages cannot be released.Every game targeting Android 15 or higher, so every game that updates
February 2027Apps over the memory usage, bitmap memory usage or code optimisation thresholds may see reduced store visibility.Memory-heavy games; the foreground threshold for games starts at 2.25 GB on 4 GB phones
2027, no day givenAndroid developer verification expands globally for all apps on certified devices.All developers; Play Console accounts manage it in Play Console
31 August 2027Play Billing Library 8 stops being accepted for new apps and updates. Extension to 1 November 2027.Games with in-app purchases
30 September 2027The new service fee model reaches the rest of the world.Games earning outside the regions already launched

Dates as published on developer.android.com and Play Console Help on 15 November 2026. Google describes several of these timelines as subject to change.

Fees and billing options differ by region. The new model launched in the EEA, UK and US on 30 June 2026 and in Australia and Japan on 30 September 2026. Google's service fee page has the rates, and its user choice billing page lists which programmes are open to games in which countries. We compare the fees in how casual mobile games make money.

What most often blocks a release

Google's own publishing tips name the pitfalls it sees most from first-time publishers:

  • A thin or misleading store listing. A one-line description, or one with irrelevant or excessive text, can be rejected under the Metadata policy.
  • A listing that promises more than the game does. Screenshots and text must match what is in the build.
  • No login details for reviewers. If part of the game sits behind an account, give working demo credentials or the review cannot happen.
  • Broken functionality. Builds that crash, fail to load or do not respond are rejected under the Broken Functionality policy.

Inaccurate declarations are the other common route to trouble. Google's help pages say misrepresenting ads can lead to suspension, an inaccurate Data safety form to blocked updates or removal, and a misrepresented content rating to removal or suspension. The enforcement page explains the difference: a rejection leaves the published version live and does not affect the account's standing, while a suspension counts as a strike. Developers are responsible for the third-party SDKs in their builds.

How Godot and Flutter projects meet the technical rules

Godot. The Android build configuration in the 4.7.2-stable tag sets the target SDK to 36, the minimum SDK to 24 and the NDK to r29, which is above the r28 line Google gives for 16 KB alignment by default. Godot's Android export guide says an App Bundle needs the Gradle build switched on. For purchases, GodotGooglePlayBilling 3.3.0 uses Play Billing Library 9.1.0. More in Godot vs Unity for 2D mobile games.

Flutter. In Flutter 3.50.0, the stable release of 11 November 2026, the default Android settings are target SDK 36, minimum SDK 24 and NDK 28.2. The Android deployment guide covers creating an upload keystore and running flutter build appbundle. The in_app_purchase_android package moved to Play Billing Library 9.1.0 in version 0.5.5. See also Flutter vs Godot for 2D mobile games.

In both cases the engine default is only half the answer. An older project may pin an earlier target SDK in its own export preset or Gradle file, and any plugin with native code has to be 16 KB compatible on its own account. Google's guide describes how to check a built APK with APK Analyzer or zipalign.

What we do at Futigo

We are a small studio publishing Android games on Google Play. Most are built in Godot 4.7, such as Claywheel and Power Cut, and a few grid puzzles, such as Parkle, are plain Flutter, so the two engine paths above are the ones this checklist was written around.

Questions

How much does a Google Play developer account cost in 2026?
US$25, paid once at registration. Google's help page says prepaid cards are not accepted and that you must be at least 18 to sign up.
How many testers do I need before publishing on Google Play?
Personal developer accounts created after 13 November 2023 need a closed test with at least 12 testers opted in continuously for 14 days before they can apply for production access. The rule as written applies to personal accounts only.
What target API level does Google Play require in 2026?
Since 31 August 2026, new apps and updates must target Android 16 (API level 36). Existing apps must target at least API level 35 to stay available to new users on newer Android versions.
When is the Google Play 16 KB page size deadline?
Apps targeting Android 15 or higher must support 16 KB memory pages on 64-bit devices, and from 1 February 2027 updates without that support cannot be released. Google says NDK r28 and higher build 16 KB aligned libraries by default.
Which Play Billing Library version is required?
New apps and updates must use version 8 or 9. Version 7 stopped being accepted on 31 August 2026, version 8 runs until 31 August 2027 and version 9 until 31 August 2028.
What crash rate gets a game penalised on Google Play?
Android vitals sets the bad behaviour thresholds at a 1.09% user-perceived crash rate and a 0.47% user-perceived ANR rate across all devices, or 8% on a single phone model. Above them, Play may reduce the game's visibility and show a warning on its store listing.