Affiliate disclosure: Some links in this guide are affiliate links. If you purchase a server hosting plan through one of our links, we may earn a small commission at no extra cost to you. This does not influence our recommendations.
Setting up a modded Terraria server is not the same as hosting a vanilla one. If you have used TerrariaServer.exe before and assume tModLoader works the same way, you will run into problems immediately. This guide explains exactly what is different, walks you through the full self-hosting process step by step, and covers the best paid hosting options for groups running heavy mod packs like Calamity or Thorium. If you are new to tModLoader itself, start with our complete tModLoader guide before following this one.
Why tModLoader Server Hosting Is Different
Vanilla Terraria multiplayer uses TerrariaServer.exe — a dedicated server application included with the game. tModLoader replaces this with its own server application called tModLoader Server, which is a completely separate executable. The vanilla server cannot load .tmod files, so it is entirely incompatible with modded play.
The critical constraint that makes modded server management more complex than vanilla is this: every player connecting to your server must have the identical set of mods installed, in the identical load order. If your server runs Calamity 2.0.5.3 and a player has 2.0.5.2, they cannot connect. If you have 12 mods enabled and a player has 11, they see a mismatch error. This mod synchronisation requirement is the main reason many groups prefer paid hosting — hosts like Shockbyte and Bisect provide web panel mod managers that handle versioning automatically.
| Feature | Vanilla Server (TerrariaServer.exe) | tModLoader Server |
|---|---|---|
| Application | TerrariaServer.exe | tModLoaderServer.exe |
| Mod support | None | Full .tmod support |
| Default port | 7777 | 7777 |
| Mod sync required | N/A | Yes — all players must match |
| RAM for Calamity | ~512 MB | 2 GB minimum |
| Paid host support | Universal | Shockbyte, Bisect, others |
Self-Hosted tModLoader Server: Step-by-Step
Self-hosting is free and gives you full control, but requires port forwarding and keeping your PC running. If you want a 24/7 server without the overhead, skip to the paid hosting section below.
Step 1: Download tModLoader Server from GitHub
Go to the tModLoader GitHub repository and navigate to the Releases page. Look for the latest stable release. In the Assets section, you want the file labelled tModLoaderServer (not the full tModLoader client install). Download the zip for your operating system (Windows, Linux, or macOS).
Step 2: Extract to a dedicated folder
Extract the contents to a folder you will remember, such as C:\tModLoaderServer\ on Windows. Keep this separate from your client tModLoader installation to avoid file conflicts.
Step 3: Install your mods
The server needs the same .tmod files that your players will use. Create a Mods folder inside your tModLoader Server directory and place all your .tmod files there. You can download .tmod files from Thunderstore or export them from your local tModLoader mod browser. The filenames and versions must match exactly what players have installed.
Step 4: Configure the server
Create a configuration file (or edit the existing serverconfig.txt) with the following key settings:
worldpath— full path to your .wld world filemaxplayers— number of player slots (4–8 is typical)password— optional server passwordport=7777— default port, change only if neededautocreate— set to 1 to auto-generate a new world on first launch
Step 5: Launch tModLoaderServer.exe
Run tModLoaderServer.exe (or the equivalent launch script on Linux/macOS). The server will load your mod list, generate or load the world, and print a “Server started” message to the console when ready. If it crashes immediately, the most common cause is insufficient RAM for the mods you have loaded — see the Hardware Requirements section below.
Step 6: Port forward 7777 TCP/UDP
Open your router admin panel (typically 192.168.0.1 or 192.168.1.1) and create a port forwarding rule for port 7777, both TCP and UDP, pointing to the local IP address of the PC running the server. You can find your local IP by running ipconfig in Command Prompt and looking for the IPv4 address. Disable Windows Firewall for the tModLoaderServer process if players cannot connect after port forwarding is set up.
Players need your external (public) IP address to connect. You can find this by searching “what is my IP” in a browser. In Terraria, they select Multiplayer → Join via IP, enter your external IP, and port 7777. All players must have the identical mods installed locally through their tModLoader client before they try to connect. See the Mod Sync Solution section below for the fastest way to ensure everyone matches.
Related: terraria mining guide.

Paid Hosting for tModLoader (Recommended for Calamity/Thorium Runs)
Self-hosting works, but it requires your PC to stay on and you to manage port forwarding. For groups doing a full Calamity playthrough that spans weeks, a paid host is far more practical. Two providers with reliable tModLoader support are Shockbyte and Bisect Hosting. Both support tModLoader servers directly through their control panels, with no manual file management required.
See our full comparison in the best Terraria server hosting guide for pricing breakdowns and uptime data. Here is the key workflow for each:
Shockbyte
When creating your server on Shockbyte, select tModLoader as the server type instead of vanilla Terraria. This installs the correct tModLoader Server application automatically. From the control panel, use their built-in mod manager to search for and install mods by name — Shockbyte pulls from the tModLoader mod browser so versions stay current. Once your mod list is configured on the server, all players in your group still need to install the same mods locally through their tModLoader client.
We go through the multiplayer options in terraria server setup.
Bisect Hosting
Bisect offers a similar workflow: select tModLoader during server creation, then use their Multicraft-based panel to manage mods. Bisect is slightly cheaper at the entry tier but has fewer data centre locations than Shockbyte. For EU and AU players, check latency before committing to a plan.
Hardware Requirements
Modded Terraria is significantly more demanding than vanilla at the server level. The base game server runs comfortably on 512 MB RAM, but large mod packs change that substantially:
| Configuration | Minimum RAM | Recommended RAM |
|---|---|---|
| Vanilla Terraria server | 512 MB | 1 GB |
| tModLoader + Calamity only | 2 GB | 3 GB |
| Calamity + Thorium + QoL mods (4 players) | 3 GB | 4 GB |
| Large mod pack (10+ mods, 6+ players) | 4 GB | 6 GB |
Most paid hosting plans offer 2–4 GB RAM at the base price tier. If you are running Calamity + Thorium + several quality-of-life mods on four players, the 4 GB plan is the safe choice. Crashes on world load are almost always a RAM issue — upgrade the plan or reduce your mod count before troubleshooting anything else.
For information on which mods to prioritise for a Calamity run, see our Calamity Mod beginner guide.
Mod Sync Solution: Keeping Every Player’s Load-Out Identical
The most common reason players cannot connect to a modded server is a mod mismatch. tModLoader checks mod names, versions, and load order on connection. Even a single version difference causes an immediate rejection.
The fastest solution is tModLoader’s built-in mod pack export feature:
- The server host opens tModLoader and navigates to Workshop → Manage Mods.
- Click Export Mod Pack — this creates a small .json file containing the full mod list with versions and load order.
- Share the .json file with all players (Discord, Google Drive, etc.).
- Each player opens tModLoader, goes to Workshop → Manage Mods → Import Mod Pack, and selects the shared .json file.
- tModLoader automatically downloads and enables all mods in the correct order.
This process takes under five minutes per player and eliminates the most common connection errors. Whenever you update a mod on the server, re-export the pack and share the new .json so everyone stays in sync.
Troubleshooting Common tModLoader Server Issues
| Error | Likely Cause | Fix |
|---|---|---|
| Connection refused | Port 7777 not open or wrong IP | Verify port forwarding rule on router; check Windows Firewall; confirm you are sharing the external (public) IP, not the local one |
| Mod mismatch error on connect | Player mod list does not match server | Export mod pack from server host’s tModLoader and have all players import the .json file |
| Server crashes on world load | Insufficient RAM for mod count | Upgrade hosting plan or remove lower-priority mods; Calamity alone needs 2 GB minimum |
| Server loads but lags heavily | CPU throttling on low-tier VPS | Switch to a provider that guarantees dedicated CPU threads; shared-CPU plans underperform with modded Terraria |
| Mods folder not found on startup | Wrong directory structure | Ensure the Mods folder is in the same directory as tModLoaderServer.exe, not a parent or subdirectory |
Sources
- tModLoader Team. tModLoader — A Terraria Modding API. GitHub
- Re-Logic / Terraria Team. tModLoader — Official Steam page. Steam
- Shockbyte. Terraria Server Hosting — tModLoader server plans. Shockbyte.com
I've been playing video games for over 20 years, spanning everything from early PC titles to modern open-world games. I started Switchblade Gaming to publish the kind of accurate, well-researched guides I always wanted to find — built on primary sources, tested in-game, and kept up to date after patches. I currently focus on Minecraft and Pokémon GO.
