{"id":789,"date":"2026-08-04T23:18:49","date_gmt":"2026-08-04T23:18:49","guid":{"rendered":"https:\/\/bestdedicatedwebhostingserver.com\/blog\/?p=789"},"modified":"2026-08-04T23:18:49","modified_gmt":"2026-08-04T23:18:49","slug":"terraria-dedicated-server-hardware-specs-tshock-setup-and-tuning","status":"publish","type":"post","link":"https:\/\/bestdedicatedwebhostingserver.com\/blog\/terraria-dedicated-server-hardware-specs-tshock-setup-and-tuning\/","title":{"rendered":"Terraria Dedicated Server: Hardware Specs, TShock Setup, and Tuning"},"content":{"rendered":"\n

A Terraria dedicated server for 8 players runs comfortably on a single 2 GHz core and 1\u20132 GB of RAM. Push to 16 players with TShock, world backups, and a few plugins, and you still stay under 4 GB. By dedicated server standards this is a featherweight workload \u2014 the decisions that actually matter are disk speed for world saves and stable single-core performance for the 60-tick simulation loop.<\/p>\n\n\n\n

Because the footprint is so small, Terraria is an ideal second or third instance on a box you already rent for another game, or a first server for a community that wants to dip into self-hosting without buying enterprise hardware. If you are picking a machine, compare dedicated server plans side by side<\/a> \u2014 even the entry tier is overkill in the best way for Terraria alone.<\/p>\n\n\n\n

Hardware sizing that matches your player count<\/h2>\n\n\n\n

Terraria’s server is a single process with modest threading; it does not scale across many cores, so prioritize clock speed over core count. The table below is what we recommend based on measured usage across community servers.<\/p>\n\n\n\n

Players<\/th>CPU<\/th>RAM<\/th>Disk (free space)<\/th><\/tr><\/thead>
4<\/td>1 core @ 2 GHz<\/td>1 GB<\/td>1 GB<\/td><\/tr>
8<\/td>2 cores @ 2.5 GHz<\/td>2 GB<\/td>5 GB<\/td><\/tr>
16 (TShock + plugins)<\/td>2\u20134 cores @ 3 GHz<\/td>4 GB<\/td>10 GB<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

RAM usage grows with world size and player count because the server holds the loaded world in memory; a large world with heavy builds sits near the top of those ranges. World files themselves are small (tens of MB), so disk is rarely a concern unless you keep many backup generations.<\/p>\n\n\n\n

Setting up the vanilla server and TShock<\/h2>\n\n\n\n

The official server is distributed through SteamCMD under app ID 1281930, and it runs natively on Linux \u2014 no Wine required. Install it with steamcmd +login anonymous +app_update 1281930 +quit<\/code>, then launch with .\/TerrariaServer.bin<\/code> to generate a config. For anything beyond a handful of friends, install TShock on top: it adds per-user permissions, banned-item control, anti-cheat, region protection, and a web-based remote console that makes moderation much easier.<\/p>\n\n\n\n

Key config values live in serverconfig.txt<\/code>: worldname<\/code>, autocreate<\/code> (world size), maxplayers<\/code>, port<\/code> (7777 by default, TCP and UDP), and npcstream<\/code>, which controls how many NPC updates are sent per tick and is the main dial for reducing lag on weak connections. TShock adds its own config.json<\/code> for permissions and server settings on top of the vanilla file.<\/p>\n\n\n\n

Networking is the part people get wrong. Terraria’s server listens on port 7777 for both TCP and UDP \u2014 TCP carries the bulk of the game traffic while UDP handles some status queries \u2014 and both must be open in your firewall and forwarded on any router between the box and the internet. The server also registers itself on Steam’s server list, which requires outbound access to Steam’s matchmaking endpoints. If players can connect directly by IP but the server does not show up in the in-game browser, it is almost always a UDP rule or Steam query port issue rather than a hardware one.<\/p>\n\n\n\n

Tuning and maintenance that prevent heartbreak<\/h2>\n\n\n\n