Which Platforms and Programming Languages Does Godot Support?

Godot supports desktop (Windows, macOS, Linux), mobile (Android, iOS), and web export, and its primary scripting language is GDScript, a language built specifically for the engine. C# is also supported for those who prefer it, and the engine can be extended with C++ through GDExtension. The exact set of platforms you can target depends on the renderer and export templates you choose, so the sections below separate what the engine supports from what you need to configure.

Platforms Godot supports

The documentation lists platforms across two categories: the editor itself and exported projects.

Where the editor runs

• Desktop or laptop PC (Windows, macOS, Linux)
• Mobile device (smartphone/tablet)

The docs give minimum and recommended system requirements for each, and the same split applies to exported projects.

Where exported projects run

• Desktop or laptop PC
• Mobile device (smartphone/tablet)
• Web (browser)

This means you can develop on a desktop machine and ship to desktop, mobile, and web from the same project, subject to renderer and export template choices.

Renderer choice affects platform reach

Godot offers three renderers, and the docs frame the choice as a question: "Should I use the Forward+, Mobile, or Compatibility renderer?" The renderer you pick constrains which platforms and features are practical, so treat platform support and renderer selection as one decision rather than two. If you need broad low-end and web coverage, the Compatibility renderer is the relevant option; if you need advanced 3D features, Forward+ is the relevant option. Check the renderer comparison in the docs before committing, because switching later can require reworking visuals.

Programming languages Godot supports

GDScript

GDScript is a language created specifically for Godot. The docs address it directly with the question "What is GDScript and why should I use it?" and also explain "What were the motivations behind creating GDScript?" The short version: it is tightly integrated with the engine, so it is the default and best-documented path for scripting gameplay.

C#

C# is supported as an alternative to GDScript. If your team already writes C#, this lets you reuse that knowledge, but you should confirm the current .NET setup requirements in the docs for your Godot version before starting a project.

C++ and engine extension

Godot can be extended with C++ rather than scripted with it. The docs cover this under "How can I extend Godot?" and the GDExtension system. Use this when you need native performance or want to bind an external library, not as a general gameplay scripting language.

Visual scripting

The input notes that Godot supports visual scripting. This is a node-based approach for users who prefer connecting logic visually rather than writing code. It is a complement to GDScript and C#, not a replacement for the engine's core scripting.

Which language is fastest?

The docs answer "Which programming language is fastest?" directly. Read that entry rather than assuming, because the answer depends on what the code is doing and how it interacts with the engine, not on a single benchmark ranking.

How to decide

Common sticking points

• Platform support is not automatic. Exporting to Android, iOS, or web requires the corresponding export templates and, for mobile, the relevant SDK setup. The docs' platform list tells you what is possible, not what works out of the box.
• Renderer and platform are linked. Choosing a renderer for visual quality can exclude platforms you intended to ship to. Decide both together.
• Language choice is not permanent but is costly to reverse. GDScript and C# can coexist in a project, but rewriting gameplay logic later is real work. Pick based on your team's existing skills and the docs' guidance for your target platforms.

For the authoritative, version-specific details, start from the "List of features," "Platforms," and "Frequently asked questions" sections of the Godot documentation for the branch you are using.