Compare Unity, Godot and Unreal on licensing, languages, platforms and fit, and pick a tool for a given project.
Why this matters
Hand-written canvas code is perfect for testing one mechanic in an afternoon. Once a prototype needs animation tools, a tile map editor, audio mixing, physics with many bodies, or builds for consoles and phones, an engine saves weeks. Choosing one is a real design decision: it affects what your team can build, how fast you can iterate, what it costs, and which jobs your portfolio points towards. The good news is that the core skills (loops, state, collisions, tuning) transfer between all of them.
What an engine gives you
- An editor for placing objects, building levels and tweaking values while the game runs.
- Rendering, physics, audio, input and animation systems.
- A scripting language for your game logic.
- Export to Windows, macOS, Linux, the web, mobile and (with licences) consoles.
- An asset pipeline: importing images, models and sounds.
The big three for indie and studio work
| Godot | Unity | Unreal Engine | |
|---|---|---|---|
| Licence | Free and open source (MIT), no fees or royalties | Proprietary; free tier with revenue limits, paid plans above | Source-available; free to use, royalty on revenue above a threshold for games |
| Languages | GDScript (Python-like), C#, C++ via GDExtension | C# | C++ and Blueprints (visual scripting) |
| Strengths | Small download, fast to open, great for 2D, readable scene/node system | Huge ecosystem and asset store, strong mobile and 2D/3D, very common in industry job ads | High-end 3D graphics, large worlds, used by many AAA studios |
| Watch out for | Smaller asset ecosystem; console export goes through third parties | Licence terms have changed over the years; check the current ones | Heavy downloads and hardware needs; C++ learning curve |
Licensing and pricing change, so always read the official terms before committing a commercial project: godotengine.org/license, unity.com/products/compare-plans and unrealengine.com/eula. Checked on 2026-10-23. In 2023 Unity announced a per-install "runtime fee", faced strong backlash and cancelled it in 2024; the lesson for designers is to read the terms yourself, not to assume they stay the same.
Other tools worth knowing: GameMaker (2D, very popular with indies), Defold (light 2D and mobile), Phaser (JavaScript, browser games), Bevy (Rust), PICO-8 (tiny fantasy console, superb for practice), and Twine (interactive fiction, no code required). For pure design exploration, a paper prototype or a spreadsheet still beats any engine.
How to choose
Ask questions in this order:
- What is the prototype trying to learn? A card-game economy might need only a spreadsheet. A movement feel test needs a real-time loop.
- 2D or 3D, and how ambitious visually? For 2D, Godot, GameMaker and Unity are all excellent. For photoreal 3D, Unreal leads.
- Target platforms. Web builds are easiest from Godot, Unity and Phaser. Console work needs a licensed developer account and usually a studio.
- Team skills. A team of C# developers will be productive in Unity or Godot with C#; artists who want visual scripting may prefer Unreal Blueprints.
- Licence and cost. Open source and royalty-free removes a risk for small teams.
- Career goals. Look at job ads for the studios you want to work at. Many mid-size studios list Unity; AAA studios often list Unreal; indie and education roles increasingly list Godot.
A worked decision
A two-person team wants to make a 2D pixel-art roguelike for a 48-hour jam, playable in the browser, with one programmer who knows Python. Godot fits: GDScript reads like Python, 2D tools are strong, web export works, and there are no licence questions. If the same team were building a 3D shooter with realistic lighting for a publisher pitch, Unreal would be the stronger choice. A studio porting its mobile line-up would likely stay with Unity because its code, tools and staff already use it.
Engine-agnostic habits
Whatever you choose:
- Keep tuning values in one place (resources, data files, scriptable objects).
- Separate game rules from presentation, as you did with
updateanddraw. - Use version control (Git, with large-file support for big assets) from day one.
- Prototype the riskiest question first, not the menu screen.
Common mistakes
- Engine-hopping instead of finishing anything. Pick one for a project and ship.
- Choosing by graphics demos when your game is 2D and small.
- Ignoring licence terms until a game earns money.
- Learning the engine instead of designing. Use the engine to answer design questions.
Quick recap
- Engines provide editor, rendering, physics, audio, scripting and export.
- Godot: free, open source, great 2D, GDScript. Unity: C#, huge ecosystem, common in jobs. Unreal: C++/Blueprints, top-end 3D.
- Decide by the question you are testing, 2D/3D, platforms, team skills, licence and career goals.
- Always check the current official licence terms.
Try it
This lesson is quiz only. Next, you will build your first scene in Godot.