Unity or Godot? (same game, twice) — source summary
A Creative Bloq feature on a rare like-for-like engine comparison: developer “Thomas”
built the same game in both unity-engine and the godot-engine to compare them.
Delivered via Telegram, ingested 2026-05-29. Text in raw/unity-vs-godot-comparison.md.
The verdict
Both engines were suitable for the target game, and both cleared his 60fps target comfortably — i.e. comparable on raw performance. The differences were in everyday usability / practicalities:
- Footprint: Unity Hub needs ~21 GB; Godot ~164 MB.
- Compile speed: Unity (C#) took ~15.4 s to compile scripts; Godot (GDScript) ~0.31 s.
- Build & startup: Godot significantly faster.
- Caveat: some report Godot performance degrading with many objects, and still find it incomplete for certain needs.
Context
Unity remains the most-used engine, but Godot is rising among indies — notably Mega Crit moved from Unity to Godot for Slay the Spire 2 (see mega-crit). Godot’s free/open-source nature is a recurring draw.
Why it matters here
The wiki’s only hard engine-vs-engine data so far — most other sources are first-party product pages (o3de, unreal-engine, unity-engine). It supplies the concrete numbers behind the synthesis “overhead / iteration loop” axis (roughly equal performance; godot-engine markedly lighter/faster in the dev loop; Unity more mature/complete). Still a single practitioner test on one game — and Godot-vs-Unreal and Godot-vs-O3DE remain uncompared.
Related
godot-engine · unity-engine · o3de · unreal-engine · synthesis