Game engine
Also known as: games engine, video game engine
A game engine is a software framework that provides the core systems needed to build games: rendering graphics, simulating physics, playing audio, handling controls, managing networking, and packaging the game for different platforms.
Unreal Engine, Unity, and Godot are the best-known engines. While engines are named after games, they now power films, architecture visualization, car configurators, and training simulations too.
Game engine, explained at three levels
At home
Building a game from nothing is like building a car by first inventing the wheel, engine, and steering. A game engine is a ready-made chassis. It already knows how to draw 3D graphics, make objects fall and collide, play sounds, and read your controller. Developers place their own characters and rules on top, then the engine runs everything together dozens of times per second.
At work
A game engine is a software platform that supplies the core systems every game needs: rendering, physics, audio, input, networking, and tools to package builds for each platform. Teams build their content and logic on top instead of rewriting those systems. That cuts development time and cost, and lets one codebase ship on phones, PCs, and consoles. Engines are also used for films, architecture, and training simulators.
At home
Under the hood, an engine runs a loop many times per second: read input, update the game world, simulate physics, then draw the frame and play sounds. On top of that loop sits an editor where developers place objects in levels and attach scripts that define behaviour, such as what happens when a player opens a door. Asset stores sell ready-made models, sounds, and tools that plug into the editor.
At work
An engine bundles subsystems that share one game loop: a renderer, a physics engine such as Havok or Jolt, animation, audio, input, networking, and a scripting layer in C++, C#, or a visual system like Unreal's Blueprints. An asset pipeline converts source files into optimized formats for each platform, and build tools package everything for certification. Licensing ranges from revenue royalties (Unreal) to subscriptions (Unity) to free open source (Godot).
At home
Most engines organize the game world as entities with components attached, such as a model, a collider, and a script, so behaviour comes from combining parts rather than deep code hierarchies. Big studios often build their own engines, like EA's Frostbite or Guerrilla's Decima, to shape those systems around one kind of game. While that control is tempting, in my opinion it only pays off at huge scale; for most teams, a commercial engine's tools and community are worth more.
At work
Engine choice locks in architecture, staffing, and costs for years. Evaluate source code access, which affects how deeply you can fix problems, platform support and console certification, performance on the weakest target device, the hiring pool, and licensing at success-case revenue. Migration is expensive because assets, scripts, and tools are engine-specific. Unity's 2023 runtime fee showed terms can change, so negotiate contracts that lock licensing for a project's lifetime where possible.
Real-world examples
At home
Carlos taught himself to make games in his spare time. Using a free game engine, he built a small puzzle game in three months and published it on a PC store without writing any graphics code himself.
At work
Lena is a product manager at a Canadian automaker. Her team used a game engine to build an online car configurator that renders paint colours and wheels in real time, reusing the same 3D models for showroom displays.
How it compares
| feature | Unreal Engine | Unity | Godot Engine |
|---|---|---|---|
| Pricing model | Royalty after revenue threshold | Subscription tiers | Free, open source |
| Main language | C++ and Blueprints | C# | GDScript, C# |
| Strength | High-end 3D graphics | Mobile and cross-platform | Lightweight and open |
| Typical users | Large studios, film | Indie and mobile studios | Indie developers, hobbyists |
Engines differ in cost, language, and the kinds of projects they suit best.
For analysts
Choosing an engine is a multi-year commitment. I'd model licensing costs at success-case revenue and check how terms have changed historically, since a pricing change can upend a studio's finances.
History & origin
Early games were built from scratch, but id Software's engines for Doom (1993) and Quake (1996) were licensed to other studios, popularizing the idea of reusable engines. Epic Games released Unreal in 1998 and licensed its engine widely. Unity launched in 2005 and made engines affordable for small studios, helping fuel the indie and mobile game boom. Epic made Unreal Engine 4 free to download in 2015, with royalties on revenue, and the open-source Godot engine gained traction in the 2010s. In 2023, Unity's proposed 'runtime fee' charging per install caused a developer revolt; Unity cancelled it in 2024. In my view, that episode showed that choosing an engine is also choosing a business partner.