I was wondering if console ports for PS4, PS5, XBOX 1, XBOX Series X, and maybe even Nintendo Switch work.
If not, I suggest these features be implemented into the engine.
There is nothing native in the engine that directly ports to console.
There is nothing stopping you from compiling to them, but you would be legally required to have a licensed a SDK for the console, a licensing agreement with the manufacturer, and the knowledge on how to adapt your code to their SDKs AND sign it with your dev signatures for that specific console.
Unfortunately, there is nothing that the GDevelop team could add to accomplish any (or 95%) of the above.
Can the GDevelop games be ported to consoles?
Console ports are possible via a third-party studio. GDevelop does not currently provide support for Xbox/Playstation/Switch consoles for various reasons:
- Third-party studios do it extremely well.
- Legal reasons due to the MIT open-source licence of the game engine.
- High budget costs ($50k+) and NDA agreements with console manufacturers.
Games on consoles are reviewed by the platform holder against an extensive list of requirements. In short, if you think you can create a game and play it on a console within minutes, that’s not possible. Even competing engines have the same limitations mentioned above. What they do is ensure hardware and software compatibility with consoles, which means they don’t need third-party studios. However, if you want to play on a portable console, it is possible with one device: Valve’s Steam Deck.
The only exception is Valve’s Steam Deck console, which requires the game to be available on Steam, so a Windows/Linux export is required.
We have a guide for this: Publish to Steam - GDevelop documentation
it is best you work with a company whos sole job is porting, and release these versions after the game.
From what I’ve seen, the main challenge with console ports is usually certification and platform-specific optimization rather than the game engine itself. If the project already works well with controllers and stable performance, that’s a pretty good starting point at least.
The biggest hurdle is the porting process, which is why a third-party studio is needed. Engines like GDevelop, PlayCanvas, Flowlab, Buildbox, and Construct 3 are based on web technologies, which are poorly received by console manufacturers.
Each manufacturers uses its own SDK and graphics API (DirectX 12 on Xbox, GNM on PlayStation, NVN on Switch, Vulkan/DX12 on PC). Web-based engines like GDevelop and others typically rely on WebGL or WebGPU, which run through a browser layer.
Consoles do not natively execute web environments, they require porting through official development tools for performance, memory control, and hardware access reasons. Modern engines therefore use a graphics abstraction layer to map the same rendering logic to multiple backend APIs, like UE and Unity.
So a port is required, either by adapting the engine to replace the web rendering layer with a native graphics backend (Vulkan, DirectX 12, GNM, NVN), or by rewriting parts of the runtime so the game no longer depends on browser technologies and instead uses the console’s official SDKs.
That’s the core challenge of console porting. And that’s before even getting into platform agreements with the console manufacturer, publishers, certification and compliance testing, technical requirements, fees, and a lot more problems to solve.
Xbox does seem possible though, as thats usually a much more complicated, capable system.
Once i buy one, i will be testing extensively.