Publishing for Unitys
Unity publishing is the step of turning a project into a build players can install and distributing it. You pick a build target in Build Settings, set player options such as icon, version and scripting backend, produce a build, and upload it to a store like Google Play, the App Store, Steam or itch.io.
Stage: Optimise and Release · Part of the Unity roadmap · Last reviewed 19 November 2026
What to learn in Publishing
- Configure Build Settings, scenes in build and player settings for a target
- Produce an Android build and sign it with a keystore
- Understand IL2CPP versus Mono scripting backends and their trade-offs
- Test a release build for bugs that only appear outside the editor
- Prepare store listing assets and follow a store's submission checklist
Publishing interview questions
What is the difference between a development build and a release build in Unity?
A development build enables debugging, the Profiler connection and script logging, and it is larger and slower. A release build strips these and applies optimisations. Always test a release build before shipping because some bugs appear only there.
Why does an Android build need a keystore?
Android requires apps to be signed with a key so the store and devices can verify the developer and accept updates. The keystore holds that key. If you lose it, you cannot publish updates to the same app listing, so back it up safely.
Where Publishing fits in the Unity roadmap
Publishing belongs to the Optimise and Release stage (intermediate level). Ship the game.
Other units in this stage
Back to the full Unity roadmap