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

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

Publishing your first Unity game on Google Play is exciting, but the process has several steps that can trip up new developers. This guide covers everything from building a release-ready Android App Bundle to setting up your store listing and passing review, so you can launch with confidence.

Step 1: Create a Google Play Developer Account

Go to the Google Play Console and register as a developer. There is a one-time registration fee and Google verifies your identity. You can register as an individual or as an organization. Organizations need extra details, such as a D-U-N-S number. Note that new personal developer accounts must run a closed test with a minimum number of testers for a set period before they can publish to production, so plan this into your launch timeline and check the current requirement in the Play Console.

Step 2: Prepare Your Unity Project

  1. Install the Android Build Support module for your Unity version, including the SDK, NDK and OpenJDK.
  2. In File > Build Settings, switch the platform to Android.
  3. In Player Settings, set the company name, product name, package name, version (for example 1.0.0) and bundle version code (an integer that must increase with every upload).
  4. Set the Target API Level to the level Google Play currently requires. Google raises this requirement regularly, and uploads that target an older API are rejected.
  5. Choose IL2CPP as the scripting backend and enable the ARM64 architecture, which Google Play requires for 64-bit support.

Step 3: Create a Keystore

Every Android app must be signed. In Player Settings > Publishing Settings, create a new keystore and key with a strong password. Back up the keystore file and passwords in a safe place. With Play App Signing, Google manages the final app signing key, and your keystore becomes the upload key, but losing it still causes headaches.

Step 4: Build an Android App Bundle (AAB)

Google Play requires new apps to be uploaded as Android App Bundles. In Build Settings, enable Build App Bundle (Google Play) and build. Test an APK version on real devices first to catch crashes, layout issues and ad problems.

Step 5: Create the App in Play Console

Click Create app, enter the app name, 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 changed to paid.

Step 6: Complete the App Content Section

Under Policy and programs > App content, Google asks you to complete several declarations:

  • Privacy policy: a public URL. Create one with our free Privacy Policy Generator.
  • Ads: declare whether the app contains ads.
  • App access: explain how reviewers can access restricted parts of the app, if any.
  • Content rating: complete the IARC questionnaire honestly.
  • Target audience: choose age groups. Selecting children brings additional Families policy requirements.
  • Data safety: describe what data your app and its SDKs collect and share.

Step 7: Build the Store Listing

Add your title (30 characters), short description (80 characters), full description (4,000 characters), app icon (512 x 512 PNG), feature graphic (1024 x 500) and at least two phone screenshots. Use our Game Description Generator to draft the texts and the ASO Keyword Checker to optimize keywords.

Step 8: Test, Then Release

Upload your AAB to an internal or closed testing track first. Invite testers, gather feedback and fix crashes. When everything works and any testing requirements for your account are met, create a production release, add release notes and submit for review. Reviews can take from a few hours to several days.

Common Reasons for Rejection

  • Missing or broken privacy policy link.
  • Data safety answers that do not match the SDKs in the app.
  • Using trademarks, characters or brand names you do not own.
  • Ads that appear unexpectedly or block gameplay.
  • Targeting an outdated API level.
  • Metadata with keyword stuffing or misleading claims.

After Launch

Watch Android vitals for crash and ANR rates, reply to reviews and keep updating. Increase the bundle version code with every update. Small, regular improvements keep your game healthy and help it rank over time.

Frequently Asked Questions

Should I upload an APK or an AAB?

New apps on Google Play must use the Android App Bundle (AAB). Use APKs only for local testing on your own devices.

How long does Google Play review take?

It can range from a few hours to several days, and first submissions often take longer. Plan your launch with extra time.

What if I lose my upload key?

With Play App Signing, you can request an upload key reset through the Play Console. Backing up your keystore avoids this hassle.

About the Author

AA
Abdullah Akasha
Project Manager, QA Lead & Editor at App Source Market

Abdullah is a computer science graduate who works with development teams to plan, test and ship websites and mobile projects. At App Source Market he builds the free developer tools and writes practical guides that help indie developers name, reskin, monetize and publish Unity and Buildbox games.

Our Research & Testing Process

Our guides are based on hands-on work with Unity, Buildbox and the Google Play and App Store consoles, and are checked against the official documentation at the time of writing. Each guide is reviewed for clear, step-by-step instructions and practical examples, and we update it when tools, store policies or requirements change.

Published: November 20, 2026Last Updated: November 20, 2026Meet Our Team →
Comments (0)
Login or create account to leave comments

We use cookies to personalize your experience. By continuing to visit this website you agree to our use of cookies

More