FIELD NOTES / 18 / English guide
Transport Fever 3 Mod Folder: Manual and Mod Hub Paths
Find the TF3 manual mod folder for Steam, GOG and Epic on Windows, macOS and Linux, and distinguish userdata from Mod Hub downloads and staging files.
Updated Oct 11, 2026 · Based on official manuals and public tutorials, with key material rechecked. Version differences are noted; not individually playtested.
On this page
The Transport Fever 3 mod folder you need depends on the task. Manually installing an author's release uses userdata's mods directory. Mod Hub downloads have a managed location, and development uses staging_area. Putting files into whichever folder contains the word “mods” can produce duplicate or missing content.
Three locations with different purposes
Installation files contain the game's static resources and embedded additions. The official manual discourages changing those files; a game update can replace them. A store's “browse installed files” command usually takes you here, not directly to your manual-install directory.
Userdata contains player settings and saves, plus a mods subdirectory for manual packages. This is the location to use when an author supplies a supported manual release. Match both the store and the user account before copying anything.
Mod Hub content is managed by the game. The official manual says not to add, edit or remove files there manually. A cached download is not automatically a ready-to-distribute author package. Keep routine installation and development experiments separate.
Transport Fever 3 mod folder paths for manual installation
The following paths append mods to the userdata locations in the official file-location manual. They are typical locations, not a promise about a customized Steam installation. Replace account placeholders with your actual account directory.
| Store / system | Manual-install directory |
|---|---|
| Steam / Windows | C:\Program Files (x86)\Steam\userdata\<user-number>\3493540\local\mods |
| Steam / Linux | ~/.local/share/Steam/userdata/<user-number>/3493540/local/mods |
| Steam / macOS | /Users/<username>/Library/Application Support/Steam/userdata/<user-number>/3493540/local/mods |
| GOG or Epic / Windows | C:\Users\<username>\AppData\Roaming\Transport Fever 3\mods |
| GOG / Linux | ~/.local/share/Transport Fever 3/mods |
| GOG or Epic / macOS | /Users/<username>/Library/Application Support/Transport Fever 3/mods |
Some Linux Steam installations use ~/.steam/steam instead of ~/.local/share/Steam. Several accounts can have their own userdata directories. A folder from another account or the TF2 app ID is not a reliable destination for the currently running game.
The documented Windows Mod Hub cache is C:\Users\Public\mod.io\10640\mods; it is not the manual destination above. On Linux the manual lists ~/mod.io/common/10640/mods/ for managed content. For macOS and customized installations, consult the current official page before assuming an identical suffix across systems.
Console users should follow the integrated browser. These desktop filesystem paths do not establish a supported PS5 or Xbox manual-install method.
Recognize the actual package before extracting
Open the author's release archive and identify its mod directory. TF3 documents a mod.json technical definition and a content directory for resources; descriptive files belong under _metadata. A repository may contain development tools or source files in addition to the release package, so follow the author's packaging instructions.
An extra wrapper directory can leave the actual package in the wrong place. Conversely, extracting all resources directly into the top-level mods directory mixes unrelated packages. Keep each release's structure intact and check the resulting entry in the game's list before changing a save.
Use modId to identify duplicates. Folder names do not define identity in TF3, and the old TF2 major-version suffix is not its identification rule. Adding _1 is not a general fix. If a development copy shares the ID, the documented staging priority can cause that copy to win over the subscribed revision.
Moving Mod Hub downloads is a separate task
Finding a Transport Fever 3 mod folder does not prove that moving it is supported in the way you intend. Record the drive with limited space, the managed destination and any customized configuration. Back up relevant settings before following the platform's relocation instructions.
Steam and Reddit users have reported inconsistent results after changing mod.io settings, including content missing in-game and browser crashes. Do not treat a single successful reply as a guaranteed fix for every store and operating system. Use the download checklist if transfers stopped after relocation rather than copying files repeatedly between managed and manual directories.
Find logs without moving or deleting mods
For a loading or browser failure, inspect crash_dump inside userdata. Official documentation describes text logs, metadata and crash dumps, and warns that stdout.txt is reset at each start. Preserve the matching crash files before restarting again.
Record the selected Transport Fever 3 mod folder, store, account and package layout when asking for help. A screenshot of the immediate directory contents can clarify a wrapper problem; redact your personal account and home-directory information before publishing it.
Sources and next steps
Paths checked against official documentation on 12 October 2026; customized locations and operating-system differences still need checking on the player's device.