Fyrox is an MIT-licensed, general-purpose 2D and 3D game engine written in Rust, distributed as a crate with an integrated scene editor, and it is aimed at developers who want to build games in Rust with a single engine and a matching authoring tool.

What it is

Fyrox is a feature-rich, production-ready 2D and 3D game engine written in the Rust programming language. It lives in the Rust ecosystem and is published through the standard Rust channels: the fyrox crate on crates.io, with API documentation hosted on docs.rs, a dedicated project site at fyrox.rs, and official documentation in the Fyrox book at fyrox-book.github.io. It is a general-purpose engine rather than a genre-specific framework, and it carries a scene editor as part of the package, so rendering, GUI and scene authoring are shipped together rather than assembled from separate libraries. The project was formerly known as rg3d, which means older material referring to that name points to the same engine.

The concrete problem it addresses is the plumbing that a Rust game project would otherwise need to build or assemble itself. Instead of wiring a renderer, a GUI layer, asset handling and an editing tool into a working whole, a team adopts one engine whose runtime and editor share the same scene representation and the same code base. The repository topics — 3d, 3d-engine, game-development, game-engine, gamedev, gui, rendering, rust and rust-lang — describe exactly that scope, and the README's own framing of Fyrox as "feature-rich, production-ready, general purpose" positions it as a replacement for that hand-assembled stack rather than as a thin bindings layer.

Key capabilities

• A combined 2D and 3D engine with an integrated scene editor, covering the 3d, 3d-engine, gui and rendering topics listed for the repository.
• Distribution as the fyrox crate, published on crates.io, with generated documentation available on docs.rs.
• Demonstrable output: the full list of demo projects is published at fyrox.rs/examples.html, and each demo's source code lives in the separate FyroxEngine/Fyrox-demo-projects repository.
• Examples that can be run directly in a web browser, allowing the engine to be tried without building anything locally first.
• Comprehensive written documentation through the official Fyrox book at fyrox-book.github.io, which covers everything from how to build the engine to full tutorials.
• Community support through a Discord server and GitHub Discussions, both linked from the README.
• An explicit contribution path: CONTRIBUTING.md guidelines, continuous integration through the repository's ci.yml GitHub Actions workflow, and a good first issue label for newcomers.

Who uses it and how

• Individual developers and small teams building 2D or 3D games in Rust, using the bundled scene editor as the authoring surface for levels and scenes.
• Prospective adopters who evaluate the engine by running the published demo projects in a browser, then reading the Fyrox book before committing to a build.
• Newcomers to the engine who follow the book's sequence from "how to build" through the tutorials, which is the path the README recommends first.
• First-time open-source contributors, who are directed specifically to issues carrying the good first issue label.
• Donation-funded development: the README names a long list of sponsors whose contributions through Boosty and Patreon sustain the project's ongoing work.

Getting started

Fyrox is consumed as the fyrox crate from crates.io, so a project begins by adding that dependency and following the build instructions in the Fyrox book. Before installing anything, the demo projects at fyrox.rs/examples.html can be run directly in a web browser.

How it compares

The facts provided do not name any competing engines or paid products, so Fyrox stands alone in this registry as a Rust-native 2D and 3D engine with an integrated scene editor. Anyone arriving from older material should note that the engine was formerly known as rg3d and now ships under the Fyrox name.

When to use it — and when not to

The licence is unambiguous at MIT, and the last push in September 2026 shows an actively maintained repository, so the usual licensing and staleness risks do not apply here. What a self-hoster must operate is the Rust toolchain and build workflow: Fyrox is a library rather than a hosted service, and the README excerpt describes no database, object storage or SMTP dependency, because there is no server component to run. The main weakness visible in the facts is documentation placement: the excerpt is largely badges, community links, sponsor lists and funding instructions, with the substantive technical guidance living in the external Fyrox book instead of the repository README, so anyone who expects to learn the engine from the README alone will be disappointed. Teams that are not prepared to work in Rust, or that want a managed editor with commercial support behind it, should look elsewhere.