How to Choose a Godot Renderer: Forward+, Mobile, and Compatibility Compared

Fri, 19 Jun 2026 21:52:48 +0800

When you create a Godot 4.x project, Godot asks you to choose a renderer: Forward+, Mobile, or Compatibility.

This is not just a question of visual quality. The choice affects which rendering features you can use, which hardware your game can support, whether you can export to the Web, and how the game performs on different devices.

If you just want a quick starting point, choose by target platform: desktop 3D usually means Forward+, mobile 3D usually means Mobile, and Web, older devices, and most 2D projects usually mean Compatibility.

Quick answer

Use this table as a starting point:

Target	Recommended renderer
Desktop 3D game with advanced rendering features	`Forward+`
Newer mobile 3D, desktop XR, or mobile-aware 3D	`Mobile`
Web/HTML5 export	`Compatibility`
Older desktops, older phones, or standalone XR devices	`Compatibility`
2D games, or 3D games that do not need advanced rendering	`Compatibility`
Widest hardware coverage	`Compatibility`
2D game that needs advanced features such as compute shaders	Consider `Forward+`

This is only a starting point. Every game is different, and you still need to test on your target devices.

When Forward+ makes sense

If you mainly target desktop platforms and relatively new hardware, Forward+ is a good first choice.

Choose Forward+ when:

You are developing for desktop.
Your target hardware is fairly new and supports Vulkan, Direct3D 12, or Metal.
The project is a 3D game.
You want to use Godot’s most complete and advanced rendering features.

Forward+ is better suited to 3D projects with higher visual requirements. It gives access to more advanced rendering features and fits newer GPUs, newer operating systems, and desktop platforms.

But it is not the best default for every project. If your game must run on older devices, browsers, or low-end phones, Forward+ may bring compatibility or performance problems.

When Mobile makes sense

The Mobile renderer targets newer mobile devices and can also suit some desktop XR or desktop projects. It still depends on modern graphics APIs such as Vulkan, Direct3D 12, or Metal, but it accounts for mobile hardware limits.

Choose Mobile when:

You target newer mobile devices.
You target desktop XR or desktop platforms.
Your target hardware supports Vulkan, Direct3D 12, or Metal.
The project is a 3D game.
You want advanced rendering features while accepting mobile hardware limits.

In short, Mobile is the more natural choice for 3D projects on newer mobile devices. It is not meant for every phone; it is better for newer devices.

If you need to support very old Android devices, low-end phones, or as much mobile hardware as possible, Compatibility is usually safer.

When Compatibility makes sense

Compatibility has the widest hardware support. It is suitable for older devices, Web, standalone XR, and projects that do not need advanced rendering features.

Choose Compatibility when:

You target older mobile devices.
You target older desktop devices.
You target standalone XR devices.
The target hardware does not support Vulkan.
You need Web/HTML5 export.
The project is a 2D game.
The project is a 3D game that does not need advanced rendering features.
You want stable performance across as many devices as possible.

If you are making a Web game, Compatibility is the only choice. Godot documentation clearly states that Web projects must use Compatibility.

For many 2D projects, Compatibility is also the simpler default. It supports more devices, performs steadily, and reduces the chance of device compatibility issues during testing and release.

Web projects should use Compatibility

If your target includes Web/HTML5, do not overthink it: choose Compatibility.

The reason is direct. In Godot 4.x, Web export can only use the Compatibility renderer. Even if your development machine has a modern GPU, this conclusion does not change.

Web cases that should choose Compatibility include:

Browser mini-games
Itch.io Web builds
Website demos
Teaching demos
Small interactive projects embedded in web pages

If you plan to export the game to Web later, test with Compatibility early. Do not wait until the end of the project to switch renderers.

2D games usually fit Compatibility

For a normal 2D game, Compatibility is usually the better choice.

Most 2D games do not need the advanced 3D rendering capabilities of Forward+. You care more about fast startup, broad compatibility, stable performance, and more publishing options.

These projects can usually start with Compatibility:

Platformers
Top-down shooters
2D puzzle games
Card games
Visual novels
Pixel art games
Web playable demos

There are exceptions. Godot documentation notes that you might choose Forward+ for a 2D game if you need advanced features such as compute shaders. But that is for cases where you clearly know you need those features. It is not the beginner default.

How to decide for 3D games

For 3D games, target platform matters more.

If the target is newer desktop hardware and you want advanced rendering effects, choose Forward+.

If the target is newer mobile devices or desktop XR, choose Mobile.

If the target is older devices, Web, standalone XR, or broad hardware coverage, choose Compatibility.

A simple rule:

1
2
3

New desktop 3D: Forward+
New mobile 3D: Mobile
Web / old devices / broad compatibility: Compatibility

Do not choose only by “highest visual quality.” The game ultimately runs on player devices, and compatibility plus stable frame rate often matter more than the visuals on your development machine.

Older and low-end devices: prefer Compatibility

If your users’ devices are uncertain, or you want to support as much hardware as possible, Compatibility is safer.

Typical cases include:

School lab computers
Old office PCs
Older laptops
Older Android phones
Player devices with unknown specs
Browser or lightweight distribution channels

Forward+ and Mobile both assume relatively modern graphics API support. If the device does not support Vulkan, Compatibility is the only choice.

Can you switch renderers later?

You can switch, but you should not treat it as a harmless toggle.

Different renderers do not support exactly the same features. Some advanced rendering features used under Forward+ may be unavailable or behave differently after switching to Compatibility.

If the project is still early and has few rendering dependencies, switching is usually not too expensive. The later the project gets, the more materials, lights, post-processing, shaders, and particles you may have, and the higher the risk becomes.

Recommendations:

Choose based on your target platform early.
Test on target devices as soon as possible.
Do not wait until the game is almost finished to switch renderers.
If you plan to support Web, validate with Compatibility from the beginning.

My recommendation

If you are new to Godot, use this order:

Making 2D or Web: choose Compatibility.
Making desktop 3D for newer hardware: choose Forward+.
Making 3D for newer mobile devices: choose Mobile.
Want the widest device coverage: choose Compatibility.

For a first Godot project, I recommend Compatibility. It has fewer surprises, wider support, and a steadier publishing path, especially for 2D, Web, teaching demos, and small indie games.

When you clearly need advanced 3D rendering, compute shaders, or more complex desktop graphics, consider Forward+. If your project truly targets newer mobile 3D hardware, consider Mobile.

The most advanced renderer is not always the best renderer. The best renderer is the one that runs reliably on your target players’ devices.

Compatibility on KnightLi Blog