How do I uninstall or remove a mod in Trainz?
To uninstall a mod in Trainz, we usually remove it through Content Manager rather than deleting files by hand. Find the asset, check what depends on it, then delete or disable it. If the mod was installed manually outside the database, remove those files carefully and rebuild the Trainz database if required.
Best way to remove a Trainz mod
In most Trainz versions, custom content lives inside a managed content database. That matters because Trainz tracks dependencies, versions and local edits. If we simply delete folders at random, the game can lose track of assets or report database errors.
For that reason, the safest uninstall method is nearly always through Content Manager. The exact button names vary a bit between Trainz releases, but the workflow is the same.
- Open Content Manager and search for the mod by name, asset title or KUID if you know it.
- Identify the exact asset before removing anything. Many routes, locomotives and scenery items have similar names, and deleting the wrong dependency can break a lot more than one mod.
- Check dependencies and references. Look for the option that shows what uses that asset, or what depends on it. If a route, session or rolling stock item still calls for the mod, removing it will leave missing content.
- Delete or remove the asset using the built-in remove/delete command. In some versions this may appear as deleting from local content rather than a full uninstall.
- Rebuild or refresh if prompted. Trainz may need to commit changes or refresh the database before the asset disappears fully from the list.
- Test the route or session that used the mod. If something is now missing, reinstall it or replace that dependency with something else.
What happens if a route or session uses the mod?
This is the main gotcha. In Trainz, one small asset can be used by many other items. A trackside object, cab, bogey, hornsound, script library or texture can look unimportant on its own but still be essential to a route or locomotive.
If you remove a mod that another asset needs, Trainz may show:
- missing dependencies
- faulty or obsolete assets
- routes or sessions that fail to load properly
- rolling stock with missing parts, sounds or scripts
- substituted scenery or blank placeholders
If the mod belongs to a route you still want to use, it is usually better to replace the item first rather than uninstall it immediately. For example, if a route uses a custom signal or station building, edit the route and swap that object for another one before deleting the original asset.
Can you remove built-in Trainz content?
Not always, and this catches a lot of people out. There is a big difference between a custom mod you imported and a built-in asset that shipped with Trainz or arrived as packaged add-on content.
| Content type | Can you remove it? | Best approach |
|---|---|---|
| Custom asset imported into Trainz | Usually yes | Delete it in Content Manager after checking dependencies |
| Built-in base content | Usually not fully removable | Disable it if possible, or simply leave it installed |
| Built-in asset you edited | You normally should not delete it | Revert it to the original version |
| Packaged or DLC-style add-on content | Sometimes, depending on how it was installed | Use the official package management tools inside Trainz, then refresh the database if needed |
| Very old manually copied files | Sometimes | Remove only the exact files you added, then repair or rebuild the database |
If you edited a built-in asset, Trainz often treats it as a local modification rather than a separate mod. In that case, the right fix is usually to revert it, not delete it.
How do I remove a manually installed Trainz mod?
Most modern Trainz mods are imported into the content database, often from packaged content files. If that is how the mod was added, uninstall it from Content Manager and stop there.
If you installed the mod manually by copying files into an older Trainz setup, removal depends on exactly what was copied. We recommend being cautious here, because manual deletions are where database damage usually starts.
- Find out how the mod was installed. If Trainz imported it into the database, use Content Manager. If you copied loose folders or files yourself, continue carefully.
- Back up your content or make a restore point for your Trainz installation if you can.
- Remove only the files that belong to that mod. Do not delete unrelated folders inside Trainz just because the names look similar.
- Run a database repair or rebuild if Trainz still lists the asset, shows errors, or fails to recognise the removal cleanly.
- Check for missing dependencies in any routes, sessions or rolling stock that previously used the mod.
If you are not completely sure which files belong to the mod, it is safer to leave them alone than to delete shared content by mistake.
Why we do not recommend deleting random Trainz folders
Trainz is not like a simple game where every add-on is one neat folder that can be thrown in the bin. One asset may depend on several others, and Trainz keeps records for them in its content database.
Deleting folders manually can leave behind broken references, duplicate asset problems, missing thumbnails, or content that still appears in Content Manager but no longer exists properly on disk. If Trainz offers a built-in remove, delete, disable or revert option, use that first.
How to tell whether a mod is safe to uninstall
A mod is usually safe to remove when all of the following are true:
- it is custom content you added yourself
- nothing else depends on it
- you do not use it in any route or session you want to keep
- it is not a local edit of built-in content
- it is not part of a packaged payware or bundled install you still rely on
If any of those points are unclear, pause and inspect the asset first. In Trainz, five minutes spent checking dependencies is better than an hour spent repairing a broken route.
If Trainz still shows the mod after you removed it
This usually means one of three things: the asset was only disabled rather than deleted, the database has not refreshed yet, or a packaged version of the same item still exists elsewhere in the install.
Try these checks:
- refresh or reopen Content Manager
- look for another version of the same asset with the same or similar name
- check whether the asset is built-in and therefore not truly removable
- run a database repair if the entry looks stuck or faulty
Also watch for duplicate assets. Sometimes what looks like one mod is actually a custom version plus a built-in version, and removing one does not remove the other.
The short version
If you want the safe answer: uninstall Trainz mods from Content Manager, not by deleting random files. Check dependencies before you remove anything, revert built-in edits instead of deleting them, and only use manual file removal when you know exactly how that content was installed.