How do I install mods in Train Simulator Classic?

Install Train Simulator Classic mods by first reading the add-on’s instructions, then use the method supplied: subscribe to Steam Workshop items, import .rwp packages with Utilities.exe, run a trusted installer, or copy manual files into the RailWorks folder. Back up overwritten files and check every required dependency.

In Train Simulator Classic, “mod” can mean a route, scenario, locomotive reskin, sound pack, scenery asset or replacement file. There is no single installation method, and the simulator’s package manager does not find missing dependencies for you.

Which installation method should I use?

Use the method that matches the downloaded file rather than converting, renaming or opening it with another installer.

Before copying any Train Simulator Classic files

Find the active RailWorks installation and protect anything the mod may replace. In Steam, open Train Simulator Classic’s installed-file location; the common default ends in Steam\steamapps\common\RailWorks, but another Steam library may place it elsewhere.

The correct root contains Assets, Content, Utilities.exe and the simulator executables. If the base game is incomplete or installed in the wrong library, follow our PC installation and file-location checks before adding content.

• Close Train Simulator Classic and Utilities.exe.
• Extract compressed downloads to a temporary folder first.
• Read the supplied documentation for required routes, locomotives and asset packs.
• Back up every original file that the mod says it will overwrite.
• Keep the downloaded archive and readme so you have an uninstall record.

Older instructions often call the simulator RailWorks or RailWorks 2. That is the same product line, and the retained folder name is normal; our background on the older RailWorks naming and add-on system explains why legacy packages use those terms.

How do I install each mod format?

RWP packages belong in Utilities, manual archives must preserve their folder structure, and Workshop items are delivered by Steam.

Installing an RWP package

An .rwp file should be imported with Train Simulator Classic’s own package manager.

1. Extract the download. If the .rwp is inside a ZIP or another archive, unpack it first.
2. Open Utilities. Run Utilities.exe from the active RailWorks folder.
3. Select Package Manager. Choose its installation option and browse to the extracted .rwp file.
4. Review overwrite warnings. Continue only when the documentation expects existing files to be replaced. Utilities does not create a dependable rollback copy.
5. Restart the simulator. If the new content is absent, use Train Simulator Classic’s Clear Cache command under its settings or tools area, then restart again.

Installing an RWP does not install its prerequisites. A locomotive reskin, for example, normally requires the original locomotive because the package may contain only replacement textures and configuration files.

Installing ZIP files and manual folders

Manual mods must be merged into the RailWorks root without adding an extra folder level.

1. Inspect the extracted archive. Look for top-level Assets and Content folders.
2. Copy into RailWorks. Merge those folders with the existing folders of the same names; do not put them inside a new folder named after the mod.
3. Handle conflicts cautiously. Replace existing files only when the instructions require it and you have a backup.
4. Clear the cache if requested. This rebuilds the simulator’s content catalogue; it does not repair missing dependencies.

Assets contains rolling stock, scenery, sounds and other provider products. Routes and scenarios normally belong under Content\Routes. A common mistake we see is copying everything into Assets, which prevents route and scenario files from reaching their required locations.

If the archive begins with a provider folder rather than Assets, follow its readme carefully; it may belong under Assets\Provider\Product. Leave existing .ap archives intact unless the mod author explicitly instructs you to extract or alter them. Many replacement mods work by supplying loose files in the matching folder structure.

Installing Steam Workshop items

Workshop content installs by subscription and should not be copied manually into RailWorks.

1. Subscribe to the item. Remain signed into Steam and let its download complete.
2. Launch Train Simulator Classic. Find the route or scenario in the appropriate game menu.
3. Check the requirements. Workshop scenarios and routes can depend on commercial or freeware assets that are not included with the subscription.

Unsubscribing removes the Workshop item, but it does not remove separately installed dependencies.

Why doesn’t my Train Simulator Classic mod appear or work?

Most missing mods are caused by the wrong RailWorks folder, an extra nested directory, an unmet dependency or a stale content cache.

Clearing the cache can refresh menus and asset records, but it cannot supply missing DLC or correct a bad folder structure. Running everything as administrator is also a poor first fix; confirm the path and folder permissions instead.

How can I uninstall a Train Simulator Classic mod safely?

Remove a mod with the same system used to install it, while preserving shared assets required by other routes or scenarios.

• Workshop: unsubscribe through Steam.
• RWP package: select the registered package in Utilities.exe and use its uninstall function.
• Manual installation: delete only the files listed by the author, then restore any originals from your backup.
• Executable installer: use its supplied uninstaller when one exists.

Never delete an entire provider folder merely to remove one repaint or locomotive. Several add-ons may share it. Steam’s file verification can restore modified official files, but it does not remove every untracked third-party file and may undo replacement mods that intentionally alter default content.