Skip to main content
If your game is already shipping on Steam with the Steamworks API, this path maps every Steam feature you’re using onto its GDK equivalent — no need to redesign around a new platform model.

What’s different

Conceptual differences: GDK vs. Steamworks

How XBOX Services, identity, entitlements, and packaging differ from the Steam model.

Feature-by-feature mapping

Initializing the GDK

Replace SteamAPI_Init with GDK initialization and user sign-in.

User auth & ownership

Steam session tickets → XUser + entitlement checks.

Cloud storage

Steam Cloud → XBOX connected storage.

Stats & achievements

ISteamUserStats → title-managed achievements.

Leaderboards

Steam leaderboards → event-based stats + query-driven leaderboards.

GDK features not in Steamworks

Quick Resume, Smart Delivery, DirectStorage, and more.

Steam features covered by PlayFab

Some Steam features don’t have a direct GDK analog and are handled through Azure PlayFab instead:

Then continue with the shared workflow

General porting workflow

Tooling, checklists, packaging.

Your engine

Unreal, Unity, Godot, and more.

Publishing your port

Cert, XR, and store submission.
Last modified on August 6, 2026