Making games with Godot

Godot is a free, open-source engine that has quietly become the default recommendation for new developers — not because it's the most powerful, but because nothing stands between you and making something. You download a file under 150 MB, run it, and you're in the editor. No account, no launcher, no licence key.

Who it's for

Anyone starting out, and a growing number of people who aren't. It's strongest for 2D — its 2D renderer is genuinely first-class rather than 3D with the depth turned off, which is what several competitors offer. 3D is capable and improving quickly, but it's still where Godot is youngest.

If you're making a pixel-art platformer, a top-down RPG, a puzzle game or a visual-novel hybrid, Godot is probably the right answer and you can stop reading comparisons.

What it's good at

• **Starting.** The gap between downloading it and having something on screen is smaller than any other general-purpose engine.
• **2D.** Real 2D pipeline, pixel-perfect rendering, tilemaps that work properly.
• **GDScript.** A Python-like language built for the engine. Experienced programmers sometimes look down on it; beginners get moving in it far faster than in C#, and that matters more than elegance.
• **Scenes as building blocks.** Everything is a scene, and scenes nest inside each other. Once this clicks it's a genuinely good way to think about a game.
• **Size.** The whole editor is smaller than some engines' launchers.
• **It can't be taken away.** Open source under a permissive licence, so no company decision can change your terms retroactively. After 2023, developers take this seriously.

Where it fights you

An honest list, because a guide that only lists strengths isn't useful.

• **3D is behind.** Improving fast, but if you're making something visually ambitious in 3D, Unreal will get you further.
• **Console export isn't built in.** Godot can't ship to Switch, PlayStation or Xbox directly — those platforms require closed SDKs that an open-source project can't distribute. You go through a third-party porting house. Plan for it early if consoles matter.
• **Fewer ready-made assets.** The asset library is smaller than Unity's, so you'll write more yourself.
• **Documentation gaps in newer features.** The core is well documented; the newest additions sometimes aren't.
• **Tutorials go stale.** Godot 3 and Godot 4 differ enough that an old tutorial will not work. Check the version before following anything.

Your first hour

• Download from **godotengine.org** — the current stable line is 4.6. Take the standard version unless you specifically want C#.
• Make a new project, 2D.
• Add a `Sprite2D`, drop any image on it, press play. That's the loop.
• Then follow the official *Your first 2D game* tutorial in the documentation — it's about two hours and it's better than most paid courses.
• Don't start with your dream project. Make something small and finish it. Finishing is a separate skill from building, and it's the one that's scarce.

Shipping it here

Project → Export. Add a preset for the platforms you want, export, and you'll get an executable plus its data files.

• **Desktop:** put the exported files in a `.zip` and upload that. Don't upload a bare `.exe` — browsers warn on it and we require archives anyway.
• **Web:** export to HTML5 and you get a folder with an `index.html`. Zip the folder contents so `index.html` is at the top level.
• Tick **Embed PCK** in the export preset if you'd rather ship one file than several.

Where to learn more

• Official documentation — unusually good, start here
• Godot Asset Library
• GDQuest — the most reliable free tutorials