Terraria Server Requirements Calculator

Terraria's server requirements split cleanly into two worlds: lightweight vanilla, and resource-hungry modded (tModLoader). Understanding which you're running is the key to sizing correctly.

RAM

Vanilla Terraria is remarkably efficient. The official guidance is roughly 512 MB of free RAM for a small world with a few players. In practice, 1 GB comfortably handles a 2-4 player co-op session, and 2 GB is the sweet spot for a medium or large world with up to 8 players, leaving headroom for events and invasions. World size affects RAM only modestly in vanilla - small, medium, and large worlds differ by a noticeable but not huge amount.

Mods change everything. With tModLoader, expect:

• 1-3 GB for quality-of-life and light content mods,
• 4 GB for a single large content mod such as Calamity or Thorium,
• 4-6 GB or more when stacking multiple content mods.

Content mods are the heavy hitters - each adds hundreds of items, enemies, and bosses that raise baseline memory use, and usage climbs during entity-heavy boss fights. A practical rule is to budget roughly 2-2.5x your vanilla figure for a meaningfully modded server.

32-bit vs 64-bit (critical)

tModLoader ships in both 32-bit and 64-bit builds. The 32-bit build has a hard ~4 GB addressable-memory ceiling regardless of how much RAM the machine has, and it will crash with out-of-memory errors on large modpacks. Always use the 64-bit build for modded servers. It idles slightly heavier but removes the ceiling.

CPU

This is where Terraria is unusual: the server is single-thread-bound. The world simulation runs on one main thread, so clock speed matters far more than core count. A 3 GHz or faster core is ideal; a 2 GHz dual-core can manage a small vanilla world, but below 3 GHz players often report enemies teleporting and item-pickup lag during busy fights. A quad-core at 3 GHz+ is a comfortable recommendation, with extra cores mainly helping the OS, backups, or running multiple instances rather than a single world.

Storage

Disk needs are small. A vanilla install plus a large world and several backups fits easily within 5 GB. tModLoader adds a few hundred megabytes to a couple of gigabytes of mod files depending on your pack. Worlds themselves are only a handful of megabytes (Terraria's cloud quota for all worlds and players combined is around 950 MB). SSD/NVMe is recommended not for capacity but for speed - faster world saves reduce the periodic hitching large worlds can cause.

Network

Bandwidth requirements are light. A 5-10 Mbps upload handles a typical server smoothly; busy public servers benefit from more headroom. Per-player monthly egress is modest (roughly a few GB per active player), so for most hosts the limiting factor is latency to your players, not raw bandwidth. The default game port is 7777.

Player limits

The server supports up to 255 players via the maxplayers setting. The default is 16 in current versions (it was 8 before update 1.4.0.1), and most servers run 4-16 in practice. Each connected player adds physics simulation to the single main thread, so large groups during boss fights are where you'll hit CPU limits long before RAM runs out.

Performance & optimization

Terraria's server performance comes down to managing a single busy thread and keeping memory in check. These steps make the biggest difference.

Use the 64-bit tModLoader build for any mods

The 32-bit build hits a hard ~4 GB memory ceiling and will crash with large content mods. The 64-bit build removes that wall - this is the single most important fix for modded crashes.

Pick the right world size

Larger worlds (large is 8400x2400 tiles) increase memory use and lengthen save times. If you don't need the extra space, a small or medium world reduces load and hitching, especially when combined with mods. Avoid expanded-world mods unless your hardware can spare the RAM, as maximum-size worlds can drive a 32-bit build past its 4 GB limit on their own.

Tune player count and active simulation

Set maxplayers in serverconfig.txt to a realistic number (the current default is 16). Each player adds projectile, NPC, and dropped-item physics on the same main thread. Large groups during boss fights or invasion events are where you'll feel CPU bottlenecks - keeping public servers around 8-16 players is the safe zone.

Trim and order your modpack

Content mods are the heavy hitters; quality-of-life mods are cheap. Remove redundant content mods you aren't actively playing, and watch for mods known to be poorly optimized. Fewer, well-maintained mods beat a giant stack.

Reduce disk-related hitches

Run the world on SSD/NVMe storage. Avoid overly frequent autosaves on slow disks, and keep backups on the fast volume so save operations don't stall the main thread.

Lock in the CPU

Prefer a host advertising a specific high-clock CPU (3 GHz+). If you're self-hosting, disable aggressive CPU power-saving so the main thread isn't throttled down between bursts of activity.

Choosing a host for Terraria

Terraria is light on resources but unusually sensitive to a few specific things, so weigh these factors when choosing where to run your server.

• High single-thread CPU performance. Because the world simulation runs on one main thread, raw clock speed (3 GHz or higher) and modern per-core performance matter far more than the total core count advertised. Ask what the actual CPU model and clock speed are, not just "X cores."
• Generous RAM headroom for mods. Vanilla barely needs 1-2 GB, but tModLoader with content mods can climb to 4-6 GB. Pick a plan that lets you add RAM without migrating, and confirm it runs the 64-bit tModLoader build.
• One-click mod/tModLoader install and mod management. Hosts that let you switch between vanilla and tModLoader, upload mods, and manage a modpack from a panel save a lot of manual file juggling.
• Low latency to your players. Terraria is real-time, so choose a region close to your group. Look for the ability to pick a data-center location.
• DDoS protection on the game port (default 7777), which is the most common attack target for public game servers.
• Automatic backups and easy restores. World corruption happens; frequent, restorable backups protect your progress.
• Console, FTP/SFTP, and config access so you can edit serverconfig.txt, set maxplayers, and pull logs when troubleshooting.
• SSD or NVMe storage for faster world saves, which reduces the periodic hitching large worlds can cause on slow disks.

Match the plan to whether you're running vanilla or a heavy modpack - the right host for a 4-player vanilla world is very different from one hosting a Calamity playthrough.

CPU note: Single-thread-bound: the Terraria/tModLoader server runs its world simulation on one main thread, so clock speed (3 GHz+) matters far more than core count. Extra cores only help the OS, backups, and running multiple instances. Below ~3 GHz you may see enemy teleporting and item-pickup lag during boss fights and invasions.

Vanilla Terraria is extremely light: the official minimum is ~512 MB free RAM for a small world and most servers idle under 1 GB. The big variable is mods. tModLoader content mods (Calamity, Thorium) are the heavy hitters and can each add gigabytes of baseline usage. CRITICAL: only run the 64-bit tModLoader build for modded servers - 32-bit builds hit a hard ~4 GB addressable-memory ceiling and crash with large modpacks. World size (small 4200x1200 / medium 6400x1800 / large 8400x2400 tiles) affects RAM only modestly in vanilla but significantly with mods or expanded-world mods. Player count adds relatively little RAM but adds physics/projectile/NPC simulation load on the single main thread, which is why most public servers stay around 8-16 even though maxplayers can be set up to 255.