A game engine is a software framework that provides the reusable core systems needed to build a video game, so developers do not write everything from scratch. Typical parts are a renderer, physics simulation, audio, input handling, animation, scripting and tools for assembling scenes.
Why it matters
Choosing an engine shapes a project's platforms, performance, team skills and cost. Engines let small teams ship across PC, consoles and mobile by abstracting graphics APIs and hardware differences. They also affect how games run: how efficiently they use the GPU, how they schedule updates and how they handle networking.
Example
Most engines run a loop like this on every frame:
while (running) {
readInput();
updateGameLogic(deltaTime);
simulatePhysics(deltaTime);
renderFrame();
}
Using deltaTime, the elapsed time since the last frame, keeps movement speed the same whether the game runs at 30 or 144 FPS.
Common mistakes
- Picking an engine by popularity alone, without checking platform support and licensing terms.
- Tying game logic to frame rate instead of elapsed time.
- Assuming the engine handles multiplayer fairness; authoritative game servers still need design.
Related
Get notified when this term updates
Plus occasional practical tips on uptime and monitoring, nothing else. Unsubscribe anytime.
This page is general information written by our editorial team and updated when documentation changes. Servers and providers differ, so test changes safely first. See our editorial policy and disclaimer.