What You Can Do with Godot Engine

Godot Engine is a free, open-source, community-driven 2D and 3D game engine. You can use it to build games and interactive applications across desktop, mobile, web, and XR targets, write gameplay logic in GDScript or other supported languages, and ship projects without engine licensing fees. It fits best when you want a lightweight editor, a permissive license, and a code-first workflow rather than a large prebuilt asset ecosystem.

Core things you can build

The official documentation organizes features into these areas, which map directly to what you can make:

• 2D games — sprites, tilemaps, 2D physics, 2D tools, and a dedicated 2D renderer.
• 3D games — 3D graphics, 3D physics, 3D tools, and shaders.
• GUI-driven applications — a built-in GUI system for menus, HUDs, and tool-like interfaces.
• Interactive experiences with audio, animation, and input — audio playback, animation systems, and configurable input handling.
• Networked games — high-level and low-level networking APIs.
• XR / AR / VR experiences — the docs list XR support as a feature area.
• Mobile games — mobile platform support and OS integration.

The FAQ also confirms you can use Godot for non-game applications and even as a library, so it is not strictly limited to games.

Platforms you can target

Godot is cross-platform by design. The documentation lists platform support and separates editor requirements from exported project requirements, with minimum and recommended specs for:

• Desktop or laptop PC
• Mobile devices (smartphone/tablet)

This means the machine you develop on and the machine you ship to are treated as separate concerns, which matters when you plan a build pipeline.

Scripting and languages

Godot supports multiple programming languages. The documentation specifically covers:

• GDScript — Godot's own scripting language, designed for the engine and recommended for most gameplay code.
• Other supported languages, which the docs address in the scripting section.

The FAQ answers "Which programming languages are supported in Godot?" and "Which programming language is fastest?" — useful when you are choosing a language for performance-sensitive parts of a project.

Rendering options

Godot offers three renderers, and the FAQ asks directly: "Should I use the Forward+, Mobile, or Compatibility renderer?" The right choice depends on your target hardware and the visual features you need. The documentation treats this as a decision point rather than a single default, so check the renderer comparison before committing to one for a project.

Cost and licensing

Godot is free and open source. The FAQ explicitly covers "How much does it cost?" and "What are the license terms?", and there is a dedicated section on complying with licenses that explains requirements, inclusion, credits screens, licenses screens, output logs, accompanying files, printed manuals, and linking to the license.

If you ship a commercial project, the license-compliance section is the part to read before release — it tells you what attribution and file inclusion your build needs.

Getting started

1. Read the introduction — the docs recommend new users start with the introduction before anything else.
2. Check system requirements — confirm your development machine meets the editor's minimum or recommended specs.
3. Install the editor — the FAQ covers installation and desktop integration for Windows, macOS, and Linux, and explains whether the editor is portable.
4. Pick a version — the FAQ answers "Which Godot version should I use for a new project?" and "Should I upgrade my project to use new Godot versions?"
5. Choose a renderer — decide between Forward+, Mobile, and Compatibility based on your target.
6. Start with 2D or 3D — follow the corresponding graphics, tools, and physics sections.

When Godot is a good fit

Choose Godot when:

• You want a free, open-source engine with no licensing cost.
• You need 2D and 3D in the same tool.
• You want to target desktop, mobile, web, and XR from one project.
• You prefer GDScript or want flexibility in programming language.
• You want to read and modify the engine source, or use it as a library.

Consider alternatives when your project depends on a large marketplace of prebuilt assets, or on closed SDKs — the FAQ addresses whether specific closed SDKs will be supported, and the answer is not a blanket yes.

Offline and community resources

The documentation includes an Offline documentation section if you need to work without internet access, and a Get involved section covering how to contribute, share ideas, and support development. The FAQ also explains how to contact the team and who is working on Godot.