Game Engines and Frameworks

Resources · Game Development · Directory ·

Choosing an engine is easy to turn into a month-long research project. Do not give it a month.

Pick two tools suited to your game. Build the same tiny scene in both. Add movement, one interaction, one sound, a saved value, and an export. You will learn more in two evenings than you will from twenty comparison videos.

This directory covers engines, frameworks, and focused creation tools. An engine gives you an editor and a production workflow. A framework gives you code and leaves more decisions in your hands.

Search every engine and asset source

Start with bash.tv

bash.tv puts the editor, game, and publishing flow in the browser. I like it for quick experiments, game jams, and projects meant to reach players through a link.

Yibbly used bash.tv to build and publish Space Arena, a multiplayer arcade shooter.

Match the tool to the game

  • For a first browser project, try bash.tv, GDevelop, or Construct 3.
  • For general 2D work, start with Godot, GameMaker, or Defold.
  • For detailed 3D worlds, compare Unreal Engine, Unity, and Godot.
  • For games inside a large player platform, review Roblox Studio and Unreal Editor for Fortnite.
  • For direct programming work, look at LÖVE, raylib, MonoGame, libGDX, or Bevy.
  • For browser games written in JavaScript or TypeScript, review Phaser, PlayCanvas, Babylon.js, and Excalibur.js.
  • For visual novels and branching stories, compare Ren’Py, Twine, and Adventure Game Studio.
  • For retro limits, try GB Studio, PICO-8, or TIC-80.

Give each choice one evening. Notice how long setup takes. Check whether the documentation answers your first problem. Export before you grow attached to the editor. Daily friction matters more than a feature you might need next year.

General and platform engines

  • Godot. Strong for 2D, small-team 3D, and open development. Its editor uses scenes and nodes, with GDScript, C#, C++, and extensions. It exports to desktop, mobile, and web. Cost and license: Free under MIT.
  • Unity. Suits cross-platform 2D, 3D, mobile, XR, and teams using a large asset ecosystem. The editor centers on C# scripts and components. Targets include desktop, mobile, web, consoles, and XR. Cost and license: Free and paid plans under Unity terms.
  • Unreal Engine. Built for detailed 3D, high-end rendering, multiplayer, film work, and larger productions. Blueprints supports visual logic, and C++ supports lower-level systems. It targets desktop, mobile, consoles, and XR. Cost and license: Epic terms include seat and royalty rules.
  • GameMaker. Focused on 2D games, quick prototypes, and small teams. It offers visual actions and GameMaker Language. Exports cover desktop, mobile, web, and consoles by plan. Cost and license: Free and paid proprietary plans.
  • GDevelop. A good match for beginners, jams, and 2D projects built with event sheets. JavaScript extends its visual workflow. It exports to web, desktop, and mobile. Cost and license: Open-source editor with free and paid services.
  • Construct 3. Designed for 2D games made through browser-based event sheets. JavaScript handles custom behavior. Web export sits at its core, with desktop and mobile packaging options. Cost and license: Free trial and paid subscriptions.
  • Defold. Fits lightweight 2D games, mobile releases, and small web builds. Its editor uses Lua scripts, collections, and game objects. It supports desktop, mobile, web, and console workflows. Cost and license: Free with source available under the Defold license.
  • Cocos Creator. Suits 2D, mobile, web, and mini-game platforms. Its component editor works with TypeScript and JavaScript. Targets include web, desktop, and mobile. Cost and license: Free and open source.
  • Roblox Studio. Built for multiplayer games published inside Roblox. Creators use a scene editor, platform services, and Luau scripts. The target is the Roblox ecosystem across its supported devices. Cost and license: Free under Roblox platform terms.
  • Unreal Editor for Fortnite. Made for islands and games published inside Fortnite. The workflow combines Unreal editing tools, Fortnite devices, and Verse. Players join through Fortnite. Cost and license: Free under Epic and Fortnite creator terms.
  • CryEngine. A 3D engine for detailed environments, rendering, physics, and C++ projects. It includes a full editor and visual scripting. Desktop remains its main public target, with other platform access tied to program terms. Cost and license: Royalty-based proprietary terms with source access.

Code-first engines and frameworks

These choices expect more programming and less editor-driven work.

  • Bevy. A data-driven Rust engine built around an entity component system. It suits developers who want a code-first, open-source stack. Desktop is the strongest target, with mobile and web support still developing. Cost and license: Free under MIT or Apache 2.0.
  • MonoGame. A C# framework for teams who want direct control over their game loop and content pipeline. It targets desktop, mobile, and supported consoles. Cost and license: Free under the Microsoft Public License.
  • libGDX. A Java framework with Kotlin support for cross-platform 2D and 3D games. Developers work in code and choose separate tools for scenes or maps. Targets include desktop, Android, iOS, and web. Cost and license: Free under Apache 2.0.
  • LÖVE. A small Lua framework for 2D games and prototypes. Its simple loop works well for learning through code. Community tools support desktop, mobile, and web workflows. Cost and license: Free under the zlib license.
  • raylib. A compact C library for learning graphics programming and building small games. Bindings support many other languages. It runs across desktop, web, and several community-supported targets. Cost and license: Free under zlib/libpng.
  • Stride. An open-source C# engine with a scene editor, rendering tools, and a code-first workflow. It suits .NET developers building 2D or 3D projects. Targets focus on desktop, with additional platform support documented by the project. Cost and license: Free under MIT.

Browser engines and libraries

  • Phaser. A JavaScript and TypeScript framework for 2D browser games. It handles scenes, input, animation, cameras, and common game systems. The main target is HTML5, with wrappers available for stores. Cost and license: Free under MIT, with paid tools available.
  • PlayCanvas. A browser-based 3D editor paired with a JavaScript engine. It fits shared web projects, product experiences, and WebXR. Projects publish to the web. Cost and license: Free and paid editor plans, with the engine under MIT.
  • Babylon.js. A JavaScript and TypeScript engine for 3D web games, visualizations, and XR. It includes rendering, physics connections, loaders, and browser tooling. Web browsers form its main target. Cost and license: Free under Apache 2.0.
  • Three.js. A JavaScript 3D rendering library for custom browser experiences. It supplies scene, camera, material, loader, and WebXR building blocks rather than a full game editor. Target: Web. Cost and license: Free under MIT.
  • PixiJS. A fast 2D rendering library for JavaScript and TypeScript. Teams bring their own scene, physics, audio, and game structure. It targets modern web browsers. Cost and license: Free under MIT.
  • Excalibur.js. A TypeScript engine for 2D browser games with scenes, actors, input, collisions, and audio. It offers more game structure than a renderer alone. Target: Web. Cost and license: Free under the BSD 2-Clause license.

Narrative, retro, and beginner tools

  • Ren’Py. Built for visual novels and dialogue-heavy games. Its script language handles scenes and choices, with Python available for custom systems. It exports to desktop, mobile, and web targets listed by the project. Cost and license: Free and open source under MIT.
  • RPG Maker. Focused on tile-based role-playing games, events, dialogue, battles, and inventory systems. Recent editions support JavaScript plugins. Export targets depend on the edition. Cost and license: Paid proprietary software.
  • GB Studio. A visual tool for Game Boy games with scenes, events, actors, and music tools. It exports playable ROMs and web builds. Cost and license: Free under MIT.
  • Adventure Game Studio. Made for point-and-click adventures with rooms, inventory, dialogue, and scripts. Its editor and runtime support classic adventure workflows. Desktop is the primary target. Cost and license: Free and open source, with component licenses documented by the project.
  • Twine. A visual editor for branching interactive stories. Story formats provide logic, variables, layout, and scripting. It exports a standalone HTML file. Cost and license: Free and open source, with separate terms for story formats.
  • PICO-8. A paid fantasy console with fixed limits, Lua code, sprites, maps, sound, and music in one editor. It exports cartridges and web players. Cost and license: Paid proprietary software.
  • TIC-80. An open fantasy computer with code, sprites, maps, sound, and music tools. It supports Lua and several other languages. Targets include desktop and web. Cost and license: Free and paid editions, with the core project under MIT.
  • Scratch. A block-based learning platform for interactive stories, animation, and simple games. Projects run and share through the Scratch website. Cost and license: Free under Scratch platform and project-sharing terms.

Test before you settle in

Check five practical details before choosing:

  • Your target platform appears in the current export documentation.
  • The pricing and royalty terms fit a successful release, not only a prototype.
  • Your team understands the main language or visual workflow.
  • The engine handles your input, accessibility, networking, and save-data needs.
  • A current tutorial reaches the same type of game you plan to build.

Keep the test small and export it early. If basic work feels slow or unclear, move to the next choice before your project depends on it.

Reviewed September 2026.