Skip to publishing tools
    Build & publish toolkit

    From Unity template to released game

    Pick your game below and follow the steps to Google Play. Each tool shares what you enter, so you type every answer once.

    Your answers are saved in this browser as you type

    Each game gets its own project: switching back later resumes it. Your studio details (name, email, website, publisher ID) are shared. No login needed.

    Your studio details are kept. Earlier own projects are listed under “Resume a saved project”.

    Before you start you need a Google Play developer account, an AdMob account and, for app-ads.txt, a website (a free one works). These manual tools work without signing in. Optional provider connections require your own authorization.

    Your Google Play release

    0 of 8 steps done. Console steps (upload, forms, review) stay with you; these tools prepare everything for them.

    1. Game chosenPick the game you bought, or type its name in any tool.Next
    2. Paperwork facts to confirm (11)Some answers about your SDKs, data, ads or sign-in are still unknown; exports are drafts until they are answered.To do
    3. AdMob IDs checkedYour own App ID and at least one ad unit, with the exact Unity edits.To do
    4. app-ads.txtGenerate it, upload it to your website root, then check it live.To do
    5. Privacy policy URLGenerate and host it free, or use your own page.To do
    6. Data safety CSV (draft: facts open)Import it in Play Console; you confirm every answer there.To do
    7. Icon, banner and screenshots: review neededNo app icon artwork yet: the icon is just your app name on a gradient. Add your own icon art. Google Play needs at least 2 screenshots; you have 0.To do
    8. Promo videoOptional. Upload to YouTube and paste the link in the listing.Optional
    9. Play kit downloadedEvery file in one ZIP, with a README of where each goes.To do
    10. ReskinMake it look like your own game.Optional
    11. iOS releaseBuild and upload without a Mac.Optional
    Download my Play kit (ZIP)

    Every file the tools make, from the answers on screen now, with a README of where each goes. Built in your browser.

    Your app bundle (.aab)
    Remaining tasks in Play Console and AdMob

    Only you can do these, in your own accounts. We never log in for you.

    Unity build and Google Play upload

    Local pilot for this machine. A separately configured owner-local runner builds only reviewed, hash-pinned templates using server-side project settings and signing profiles. Hosted builds are not available. Your existing guest downloads and manual Play kit remain available.

    Provider setup and release requirements
    • Install the approved Unity editor, Android modules and license; configure immutable templates and a project package allowlist.
    • Keep the existing upload key and signing certificate. Keys and passwords stay with the runner; this form never requests them.
    • Create the app in Play Console and complete its initial setup, Play App Signing, app content and listing. Enable Google Play Developer API; grant a dedicated service account access to this app and testing releases.
    • Upload stages an internal draft edit. Review and commit are separate actions. A committed draft is not a released game. Personal-account testing and production access requirements still apply.
    Official Google Play API setup

    Runner not connected.

    Free tool

    AdMob: test ads to real ads

    Paste your AdMob IDs, catch the classic mistakes, and get the exact lines to change in your template.

    • ID checker for App ID and every ad unit
    • Exact edits for HyperCodeStore templates
    • app-ads.txt generator and live check
    • Release checklist for the ads side
    Open
    Free tool

    Store upload kit

    Everything Google Play asks for before you can press "Publish", generated from a few answers.

    • Privacy policy generator
    • Data safety CSV, ready to import
    • Icon, feature graphic and screenshots
    • Slideshow promo video
    Open
    Request a quote

    Reskin your game

    New graphics, UI, sounds or levels for your template, priced by what you choose. Tell us what you need.

    • Graphics and backgrounds
    • UI kit and app icon
    • Music and sound effects
    • New level packs
    Open
    Guide

    iOS without a Mac

    Build and upload a Unity game to the App Store from Windows, with a cloud Mac doing the Apple-only steps.

    • What you need and what it costs
    • Cloud build options compared
    • Signing and upload with an API key
    • App Privacy answers for AdMob games
    Open

    How to publish a Unity game on Google Play

    Replace the test ads with your own, add a privacy policy and the Data safety form, make the store graphics, then upload in Play Console. Each step below opens the tool that does it.

    1. 1
      Switch AdMob test ads to real ads

      Check your App ID and ad unit IDs, change them in Unity and publish app-ads.txt with the app-ads.txt checker.

    2. 2
      Create and host a privacy policy

      The privacy policy generator for games writes it from a few answers and hosts it at a public link.

    3. 3
      Fill in Data safety and the declarations

      Import the Data safety CSV for AdMob games and copy the content rating, audience and ads answers.

    4. 4
      Make the store graphics

      Icon, feature graphic and screenshots at Google Play’s sizes, plus an optional promo video.

    5. 5
      Optional, later: release on iOS too, without a Mac

      Build, sign and upload to TestFlight with a cloud Mac.

    Need a game to publish first? Browse Unity game templates.

    Questions

    Do I need to buy something to use these tools?

    No. The AdMob switch, the store upload kit and the iOS guide are free for anyone. They are built around HyperCodeStore templates, and work with any Unity game that uses the Google Mobile Ads plugin.

    Do you log in to my Google Play, AdMob or App Store account?

    You can optionally authorize read-only AdMob inventory access in Google’s own dialog. Local build and Play upload require a separately configured owner-local runner; an internal draft upload and its commit each require your explicit action. Manual guest tools stay available.

    Where is my data kept?

    Project answers stay in your browser. Optional hosting publishes the details you review; live checks and quotes send their requested data. AdMob inventory is fetched from Google after your permission, with access tokens kept only in memory. Local runner requests go to this machine and its configured providers. Store graphics and videos are made on your device.