Before you start: you should have finished ID@XBOX onboarding and have the GDK installed. If not, go to the Home page and follow the guided path from step 1.
Start with where you’re porting from
The fastest path depends on the platform your game currently ships on. Pick the one that matches your game.From Steam
Steamworks → GDK feature mapping: auth, cloud saves, achievements, leaderboards.
From a prior XBOX generation
XBOX One ERA / XDK → GDK: WinRT replacements, memory model, MSIXVC packaging.
From other platforms
Bring a title from another console or platform to XBOX Series X|S.
From PC (non-Steam)
Bring a Win32 / storefront-agnostic PC build to XBOX and the Microsoft Store.
Then work through the shared porting workflow
General porting workflow
The GDK porting reference — tooling, checklists, and cross-gen guidance.
General Porting
Core porting workflow.
Engine-specific porting
Notes for Unreal, Unity, Godot, GameMaker, and custom engines — jump to your engine’s dedicated Get Started group.
Engine paths
Engine setup and porting notes.
Ship your port
Certification, XR requirements, and store submission for ported titles.
Publishing
Cert and store submission.
Go deeper in the main docs
Build
Porting reference — tooling, checklists, cross-gen.
Services
Identity, achievements, multiplayer, economy.
Optimize
Profilers, diagnostics, and performance tools.
Publishing
Certification, XR, and store submission.
API References
Gaming Runtime, XBOX Services, and platform APIs.
Related API documentation
- XGameRuntime features reference — GDK feature list ports target
- XSAPI overview — XBOX Services surface for ported titles
- XErr API reference — decoding HRESULTs during porting