Skip to content

Setting up Online Subsystem Steam in Unreal

5 min readBy Eduardo Orellana ·

To set up Online Subsystem Steam in Unreal: load the OnlineSubsystemSteam module (DynamicallyLoadedModuleNames.Add("OnlineSubsystemSteam") in your build file), then in DefaultEngine.ini set [OnlineSubsystem] DefaultPlatformService=Steam, [OnlineSubsystemSteam] bEnabled=true and SteamDevAppId=480 for testing, point GameNetDriver at OnlineSubsystemSteam.SteamNetDriver with the IP driver as fallback, and add the SteamAuth packet handler. If you use Sessions, set bInitServerOnClient=true, or Create and Join Session will not work; lobbies do not need it. Run with the Steam client open, test multiplayer on two machines with two Steam accounts, and never upload the steam_appid.txt Unreal writes beside the executable.

AppImage, x86_64. Ubuntu 22.04, Debian 12, Fedora 39 or newer.

Intel or AMD Chromebook, with Linux turned on.

Download for macOSDownload for WindowsDownload for Linux

Unreal's online layer, with Steam plugged in

Unreal does not call Steam directly from gameplay code. It has an Online Subsystem, a common interface for identity, sessions, achievements, leaderboards, friends and voice, and a set of platform implementations behind it. Online Subsystem Steam is the one that talks to Valve's Steamworks SDK. Configure it once, and Blueprint nodes such as Create Session, Find Sessions and Write Achievement Progress go to Steam.

The obvious approach is to read a tutorial and paste its config. The config itself is short; what goes wrong is the handful of switches that change behaviour silently, such as the one Sessions needs and Lobbies do not. This guide goes through each line and what it does, from Epic's own documentation for Unreal Engine 5.8.

The configuration, from Epic's documentation

Add the module to your game's build file (DynamicallyLoadedModuleNames.Add("OnlineSubsystemSteam")) or enable the plugin, then add to DefaultEngine.ini:

Sources: Epic Games: Online Subsystem Steam.

INI
[/Script/Engine.GameEngine]
+NetDriverDefinitions=(DefName="GameNetDriver",DriverClassName="OnlineSubsystemSteam.SteamNetDriver",DriverClassNameFallback="OnlineSubsystemUtils.IpNetDriver")

[OnlineSubsystem]
DefaultPlatformService=Steam

[OnlineSubsystemSteam]
bEnabled=true
SteamDevAppId=480
; If using Sessions
; bInitServerOnClient=true

[/Script/OnlineSubsystemSteam.SteamNetDriver]
NetConnectionClassName="OnlineSubsystemSteam.SteamNetConnection"

[PacketHandlerComponents]
+Components=OnlineSubsystemSteam.SteamAuthComponentModuleInterface

What each line does

Every setting in the block above, and when you would change it:

Source: Epic's Online Subsystem Steam documentation (Unreal Engine 5.8 page), read 18 October 2026.
SettingWhat it doesChange it when
DefaultPlatformService=SteamMakes Steam the default online subsystemNever, if you ship on Steam
bEnabled=trueTurns the Steam subsystem onSet false for builds outside Steam
SteamDevAppId=480Uses Valve's shared test appReplace with your own App ID before shipping
GameNetDriver linesCarry game traffic over Steam's networking, falling back to plain IPRemove if you use your own net driver
bInitServerOnClient=trueInitializes the subsystem as Sessions needRequired for Create and Join Session; not for Lobbies
bUseSteamNetworking=falseTurns Steam's socket networking off (4.22 and later)You want Steam features but your own networking
SteamAuth packet handlerAuthenticates joining players; failures are kicked by defaultOverride the failure delegate to handle it yourself

Sources: Epic Games: Online Subsystem Steam.

Sessions or lobbies

Epic's documentation describes lobbies as peer-to-peer chat rooms used mainly for listen servers, the common case for indie co-op: one player hosts, friends join. To use them, set bUsesPresence and bUseLobbiesIfAvailable to true in your FOnlineSessionSettings. Sessions in the dedicated-server sense need bInitServerOnClient=true, and dedicated servers have their own requirements: bUsesPresence set to false, and the UE_PROJECT_STEAMPRODUCTNAME, UE_PROJECT_STEAMGAMEDIR and UE_PROJECT_STEAMGAMEDESC macros matching Steam's dedicated server tool page, with UE_PROJECT_STEAMSHIPPINGID set to your Steam ID for launching outside Steam.

Sources: Epic Games: Online Subsystem Steam.

The Steamworks SDK and redistributables

The engine ships with a Steamworks SDK version. To update it, Epic's instructions are to place the new SDK under Engine/Source/ThirdParty/Steamworks/Steam<VERSION>/sdk, update SteamVersionNumber in Steamworks.build.cs, and copy the redistributables into Engine/Binaries/ThirdParty/Steamworks for each platform: steam_api64.dll (and the steamclient files) on Windows, libsteam_api.so on Linux, libsteam_api.dylib on Mac. Most games never need to update the SDK; do it only for a Steamworks feature the bundled version lacks.

Sources: Epic Games: Online Subsystem Steam.

Achievements, stats and leaderboards

The same subsystem carries Steam's achievements, stats and leaderboards through Unreal's achievements and leaderboards interfaces. The order of work matters:

  1. Define them in Steamworks first, with API names, and publish the changes there; the game cannot unlock an achievement Steam does not know.
  2. Use your real App ID; app 480's achievements are Valve's sample ones.
  3. Read achievements once at startup (Query Achievements in Blueprint) before writing progress, so the cache is populated.
  4. Write progress as a percentage (Write Achievement Progress), with 100 unlocking it.
  5. Test from Steam with the overlay, which shows the unlock notification and confirms the round trip.

Valve's Steamworks documentation: Step by Step: Achievements, Steamworks API Example Application (SpaceWar).

Blueprint or C++

Everything above is reachable from Blueprints through the online nodes (Create Session, Find Sessions, Join Session, Write Achievement Progress), and many small teams never touch the C++ interfaces. Reach for C++ when you need what the nodes do not expose: lobby data beyond the basics, SteamAuth's delegates, rich presence strings, or dedicated-server specifics. The configuration is the same either way; only how you call it changes.

Testing

  • The Steam client must be running and signed in. Unreal writes steam_appid.txt beside the executable before Steam initializes, so the game can start without Steam launching it, and deletes it on a clean exit; never upload it.
  • App ID 480 works for most interfaces; achievements and stats need your own App ID with them defined in Steamworks.
  • Multiplayer needs two machines and two Steam accounts, not two instances on one PC, since one Steam client signs in one account at a time.
  • Shipping builds verify ownership and shut down if the signed-in user does not own the game, so test those from Steam with your real App ID.
  • On Mac, the overlay needs the game launched through the Steam client, added as a non-Steam game while testing.

Sources: Epic Games: Online Subsystem Steam, Steamworks API Overview.

When Steam is not the only platform

Online Subsystem Steam connects Steam players to Steam players. If the game will also sell on another store or console and you want those players in the same matches, a cross-platform service such as Epic Online Services, which Unreal also supports, handles lobbies and matchmaking across stores, and Steam remains the place players buy and launch the game. Decide this before writing session code: switching subsystems later means retesting every online path.

When it does not work

  • Create Session succeeds locally but nobody can join: bInitServerOnClient is missing for Sessions, or presence settings do not match.
  • The overlay never appears: the game was not started through Steam, or the subsystem failed to initialize; check the log for Steam initialization lines.
  • Players are kicked on join: SteamAuth rejected them; read OnAuthenticationResultDelegate and check both builds share the App ID.
  • Everything fails in the packaged game but works in the editor: the Steamworks redistributables are missing from the package.

Where Flockbay fits

Flockbay builds games on the official Godot engine, where GodotSteam does what Online Subsystem Steam does here, written into the game as an ordinary autoload: lobbies, overlay invites, Join Game and SteamMultiplayerPeer. For an Unreal project, the steps above are the way, and Flockbay's free web tools for Steam pages still apply. Building in Flockbay is free.

Questions

Do I need bInitServerOnClient for Steam lobbies in Unreal?
No. Epic's documentation says it is required for Sessions; lobbies work without it.
What App ID should I use to test Online Subsystem Steam?
480, Valve's shared test app, in SteamDevAppId. Replace it with your own App ID before shipping; achievements and stats need your own.
Why are my Steam achievements not unlocking in Unreal?
Usually because they are not defined and published in Steamworks, the game is still on App ID 480, or achievements were not queried before progress was written. Test from the Steam client with your real App ID.
Can I use Steam features without Steam networking in Unreal?
Yes. From Unreal 4.22, set bUseSteamNetworking=false under [OnlineSubsystemSteam] and configure your own net driver.

Flockbay builds games for free on Godot, with GodotSteam for Steam features.

Download Flockbay free

AppImage, x86_64. Ubuntu 22.04, Debian 12, Fedora 39 or newer.

Intel or AMD Chromebook, with Linux turned on.

Download for macOSDownload for WindowsDownload for Linux

Flockbay

The free AI game maker for Windows, macOS and Linux.