Skip to content

How to Publish a Unity Game on Google Play

Unity settings for Google Play: IL2CPP and ARM64, Build App Bundle, keystore, target API level, and running your game’s 14-day closed test.

Updated 3 min readBy the TestersZone team

Short answer

Switch the platform to Android, set Scripting Backend to IL2CPP with ARM64 enabled, choose a recent Target API Level, create a keystore under Publishing Settings, tick Build App Bundle (Google Play) and build. Upload the .aab to a closed testing track.

1. Player Settings that matter

Open Edit → Project Settings → Player → Android:

  • Package Name: your permanent application ID.
  • Version (versionName) and Bundle Version Code (versionCode, increase every upload).
  • Minimum API Level: as low as your game supports.
  • Target API Level: at least API 36 since August 31, 2026 (install the SDK via the Unity Hub or Android Studio). See target API 36.
  • Scripting Backend: IL2CPP and Target Architectures: ARM64. Google Play requires 64-bit support for apps with native code, and Mono builds don’t support ARM64.

2. Keystore

Under Publishing Settings use the Keystore Manager to create a new keystore and key. Keep it outside the project and back it up. With Play App Signing, this is your upload key.

3. Build the bundle

File → Build Settings → Android, tick Build App Bundle (Google Play), then Build. If your game is large, read about Play Asset Delivery: the base download has size limits, and asset packs handle the rest.

4. Game-specific checks before testers

CheckWhy
Test on a low-end phoneGPU and memory limits show up there first
Frame rate and thermal throttlingTesters notice heat and battery drain
Ads SDK in test modeTesters clicking live ads can get your ad account flagged
IAP via license testersSo testers aren’t charged. See license testers
Families policyIf kids are in your audience, see target audience

5. Run a game-style closed test

Games need different tester tasks: tutorial, a level target, the store. See closed testing for games.

After the bundle is built: same path for every app

  1. Create the app in Play Console and complete the store listing and App content. See does a closed test need a store listing.
  2. Upload the .aab to a closed testing track (internal first is optional). See upload your first AAB.
  3. Attach a tester list and publish. Share the opt-in link.
  4. On a new personal account: keep 12+ testers opted in for 14 days, then apply for production access.

Frequently asked questions

Why is my Unity build missing ARM64?

ARM64 needs the IL2CPP scripting backend. Switch from Mono to IL2CPP in Player Settings, then tick ARM64.

How do I reduce my Unity game’s download size?

Compress textures for mobile, strip unused engine code, and consider Play Asset Delivery for large content.

Do I need Unity Gaming Services for Google Play?

No. Analytics, ads and cloud services are optional. Whatever you add must be declared in your Data safety form.

Sources and how we keep this accurate

Policy facts are checked against Google's own documentation on the date shown above. Google can change requirements at any time, so confirm in your Play Console. Where we give advice or estimates rather than Google's rules, we say so. TestersZone is independent and not affiliated with Google. Drafts are AI-assisted and reviewed by our team.

Need 12 testers? Get them free.

Test 3 apps, earn 60 credits, and list your app for up to 20 real testers with verified daily check-ins.

Start free

Keep reading

Closed Testing for Mobile Games: A 14-Day Playbook

Do Games Need the 12-Tester Closed Test Too?

How to Publish a Godot Game on Google Play

How to Publish a Capacitor or Ionic App on Google Play

How to Publish an Expo App on Google Play With EAS

How to Publish a PWA on Google Play With a Trusted Web Activity

Browse all guides, or see the quick answers, guides and comparisons.