What Is Godot Docs (docs.godotengine.org)?

docs.godotengine.org is the official documentation site for Godot Engine, a free and open source, community-driven 2D and 3D game engine. The site currently presents the 4.7 branch as the stable documentation in English. Use it when you need authoritative, version-matched guidance on installing the editor, learning GDScript, configuring renderers, exporting projects, or looking up engine behavior — rather than relying on third-party tutorials that may target older releases.

What the site covers

The documentation is organized as a structured reference plus a learning path. From the homepage you can reach:

• Introduction and orientation — "Before you start," "About Godot Engine," "Organization of the documentation," and "About this documentation."
• Feature and platform lists — a "List of features" page and a "Platforms" page describing supported targets.
• Core systems — Editor, Rendering, 2D and 3D graphics, 2D and 3D physics, Shaders, Scripting, Audio, Import, Input, Navigation, Networking, Internationalization, Windowing and OS integration, Mobile, XR support (AR and VR), GUI system, Animation, and File formats.
• System requirements — separate minimum and recommended specs for the Godot editor and for exported Godot projects, each split between desktop/laptop PC and mobile devices.
• FAQ — licensing and cost, supported platforms and languages, GDScript rationale, 3D model formats, renderer choice, release timing, and upgrade questions.
• Get involved and Offline documentation sections.

How to use it for a concrete task

A typical workflow, for example preparing a new project:

1. Open the "Which Godot version should I use for a new project?" FAQ entry to confirm the recommended branch for new work.
2. Check System requirements for your target platform before downloading the editor.
3. Read the Introduction section for editor basics, then move to Scripting for GDScript.
4. When you reach rendering decisions, consult "Should I use the Forward+, Mobile, or Compatibility renderer?" to match the renderer to your target hardware.
5. Before shipping, review Exporting and the Complying with licenses pages, which cover the credits screen, licenses screen, output log, accompanying file, printed manual, and license link requirements.

Each step has a verifiable outcome: a chosen version, a confirmed hardware fit, a working script, a selected renderer, and a license-compliant export.

Common sticking points

• Version mismatch. The site labels its branch (currently 4.7). Tutorials and answers written for 3.x can describe menus and APIs that no longer exist, so confirm the branch shown at the top of the page.
• Upgrade decisions. The FAQ includes "Should I upgrade my project to use new Godot versions?" — treat this as a per-project judgment, not a default, since upgrading can require code and asset changes.
• Renderer choice. Forward+, Mobile, and Compatibility are not interchangeable; the FAQ entry exists precisely because the right pick depends on your target devices and features.
• Offline use. If you need the docs without a connection, the Offline documentation section explains the available options.

What it is not

The site is documentation, not a marketplace, asset store, or support contract. It documents an engine whose license terms and cost are addressed in the FAQ, and it points to community channels for contribution and contact. For anything beyond what the pages state — pricing specifics, commercial support arrangements, or platform certification details — check the linked official sources rather than assuming.