Transport Fever 3 has no native cooperative or competitive multiplayer mode. The official game focuses on single-player transport management. An unofficial community project, TPF3-MP, offers an experimental multiplayer route with its own launcher, compatibility requirements and restricted actions. These are different forms of support.
Support status checked 5 October 2026.
Official multiplayer and crossplay
There is no built-in room browser or official multiplayer session to enable in the standard game. Cross-platform mod availability does not establish multiplayer crossplay: sharing a content package between platforms is different from joining the same live world.
If you want an officially supported cooperative game, do not assume installing Transport Fever 3 supplies that feature. Evaluate the community project separately if you want to experiment with shared play.
What the community project currently targets
The TPF3-MP author's v1.2.0 release targets Windows x64, Steam game build 40408. It describes invite-code rooms, hosting and joining through its launcher, and shared-world synchronization. Participants need matching game versions and mods.
Linux x64 and macOS arm64 packages are described as development builds awaiting real-game platform acceptance. That is not a verified cross-platform multiplayer promise. The release's compatibility target is also specific: a later game update can require a corresponding mod update.
The relay, launcher, hook and mod must match. This release uses protocol 17, bridge 24 and action schema 25; earlier builds cannot share a room with it. Updating only one component can leave a session incompatible.
Important limits before trying a shared world
The author lists channels still disabled pending ordinary two-player acceptance, including subsidies, renaming and recoloring, waypoints, bridge and tunnel window edits, junction tools, company perks and historic preservation. Tree and rock removal is opt-in; terrain paint and asset brushes remain refused.
Treat those restrictions as part of the current experience. A feature available in the single-player interface is not proof that the mod synchronizes it correctly. Keep an established solo save separate from any experimental shared-world test.
The project is unofficial and does not establish support from the game's developer. Its release notes describe the supported target and outstanding acceptance work; this page does not claim that the package has passed an independent in-game multiplayer test.
Getting into a room
Use the project's matching player package and launcher, then follow its installation instructions for that release. Start the game through the launcher. The author explicitly distinguishes this from a normal Steam launch, which starts the plain game and does not join the room.
Use Join a friend for a name and invite code, or the multiplayer hub for hosting and browsing rooms. Keep TPF3-MP active in the world's mod selection. Check the launcher's compatibility information before attempting to load the shared world.
The current six manual-install ZIPs in our mods catalog do not include TPF3-MP. To identify that project's player package, find the GitHub author Juliansgith and repository Transport-Fever-3-Multiplayer-Mod, then locate its v1.2.0 release and matching player installation instructions. The repository identifier is Juliansgith/Transport-Fever-3-Multiplayer-Mod. Our general mods directory is not the package-acquisition endpoint for this experimental project.
If joining fails
Check the supported game build, matching project components and matching active mods first. Then confirm that the launcher started the game and that you entered the intended room. Repeatedly starting the standard Steam game does not resolve a launcher-only session requirement.
For actions that do not appear or synchronize, consult the release's disabled-action list before rebuilding the room. Start with a small test world and supported operations so you can distinguish a setup problem from a current feature limitation.