A vanilla Terraria dedicated server has one firm published starting point: the Official Terraria Wiki lists 500 MB of free RAM for a small world. Memory rises with world size and player count. There is no official CPU model, core-count, clock-speed minimum, or total disk quota for the dedicated server. Steam’s 2.0 GHz processor, 2.5 GB memory, and 200 MB disk figures describe the Windows game client, not a standalone server.
For planning, match the host to your world size, concurrent players, mods, and uptime needs; reserve storage beyond the game files for worlds, logs, backups, updates, and mod content. The default network port is TCP 7777, and the default player cap is 16, both configurable.
What are the official Terraria dedicated-server requirements?
The published requirements establish a small-world RAM baseline and the software, platform, and network settings needed to make a server reachable. They do not provide a complete hardware recipe for every player count or world size.
| Area | Published information | How to apply it |
|---|---|---|
| RAM | 500 MB of free RAM for a small world; usage depends on world size and player count. | Use it as a documented small-world baseline, not as a universal capacity guarantee. |
| CPU | No dedicated-server model, core count, or clock-speed minimum is published. | Choose a modern processor with headroom for the intended activity; do not relabel the client minimum as a server requirement. |
| Client-only context | Steam lists a 2.0 GHz processor and 2.5 GB memory for the required Windows client configuration. | Apply these figures only when that machine also runs the Terraria game client. |
| Storage | Steam lists 200 MB of hard-disk space for the client; dedicated-server documentation gives no disk quota. | Reserve extra capacity for worlds, logs, backups, updates, and mods. |
| Runtime | The server requirements list .NET Framework 4.0 and XNA Framework. | Install the runtime versions compatible with the server build and operating system. |
| Platforms | Windows, Linux, and macOS server files and launch guidance are documented. | Use the platform you can administer and keep updated. |
| Network | TCP port 7777 is the default. Cloud guidance calls for TCP and UDP 7777. | Allow or forward the port only when players outside the host need access. |
| Players | The default maximum is 16, and it can be changed in startup or configuration settings. | Set the cap to the actual group you intend to support. |
These are requirements and documented defaults, not a performance benchmark. Your real operating point depends on the world, activity, server software, and whether the machine is also doing other work.
How much RAM does a Terraria server need?
The strongest official figure is 500 MB of free RAM for a small world. The same guidance says memory depends on world size and number of players, so the number is a baseline rather than a promise that a large or busy server will remain below it.
Small vanilla worlds
A lightly populated vanilla server with a small world can begin from that 500 MB free-RAM reference. “Free RAM” means memory available to the server process and the operating system; it is not the total physical memory installed in the machine. Leave operating-system headroom so swapping or other services do not compete with the game.
Larger worlds and busier groups
Moving to a larger world or adding concurrent players changes the workload. The authoritative guidance does not publish a player-by-player or world-size-by-world-size table, so any exact formula would be an estimate rather than an official requirement. Measure the server process and the host’s available memory during exploration, events, saving, and peak attendance, then increase the allocation if the system approaches exhaustion.
How to plan RAM without inventing a number
- Start with the documented small-world baseline only when your world and group are genuinely small.
- Count the operating system and any co-hosted services in the machine’s total memory budget.
- Test the busiest expected activity, not just an empty spawn area.
- Keep a reserve for world saves, updates, and short-lived load spikes.
- For a modded server, size from observed usage because no separate official modded-memory table exists.
What CPU do I need for a Terraria dedicated server?
No official source names a dedicated-server CPU model, minimum clock speed, or required core count. Steam’s 2.0 GHz processor requirement and its dual-core 3.0 GHz recommendation belong to the Terraria client listing, so they should not be presented as dedicated-server specifications.
What determines CPU demand?
CPU demand varies with concurrent players, world activity, server software, and mods. Exploration, combat, automated farms, projectile-heavy events, and scripted mod content can create different loads even with the same player count. A host that runs only the server has more CPU available than one simultaneously rendering the game, recording video, or running several other services.
Choosing a processor in practice
Use a current, well-supported processor and prioritize consistent single-thread performance and thermal stability over a paper clock-speed comparison. Because there is no published minimum, treat a specific model recommendation as an engineering choice, not an official Terraria requirement. Watch CPU utilization and tick responsiveness while the busiest players are online; sustained saturation or lag during activity indicates that more processing headroom is needed.
How much storage does a Terraria server use?
There is no published total disk quota for a dedicated server. Steam’s 200 MB figure is the Windows client’s hard-disk requirement, not the complete space needed for a persistent server.
What must fit on the disk?
- The dedicated-server executable and its runtime files.
- One or more world files, including alternate worlds used for testing or events.
- Logs and crash information generated during operation.
- Backups and temporary copies created before updates or world edits.
- Updates, configuration files, and any mod or dependency content.
The official material does not quantify these categories, and their size changes with how many worlds and backups you retain. Reserve working room rather than allocating only the client’s 200 MB figure; a nearly full volume can prevent saves, updates, or log writes.
Where are world files stored?
The documented default locations are:
- Windows:
Documents/My Games/Terraria/Worldsinside the user profile. - Linux:
~/.local/share/Terraria/Worlds. - macOS:
~/Library/Application Support/Terraria/Worlds.
Use the configured world path when the server is installed elsewhere. These locations are useful when checking growth, copying a world to another host, or verifying that a backup job is saving the files you actually load.
What software and operating systems can run the server?
The official server requirements list .NET Framework 4.0 and XNA Framework. The documentation provides Windows server files, separate Linux downloads, and setup paths for Linux and macOS, so the practical choice is the platform whose runtime and administration tools you can maintain.
Windows
Windows is covered by the supplied server files and is often the simplest choice when your administration tools and backups are already Windows-based. Install the required runtime components for the particular build, keep the executable and worlds in a location with adequate permissions, and allow the server through the host firewall when remote access is intended.
Linux and macOS
Linux has separate download guidance, while the setup documentation describes Linux and macOS launch paths. Confirm that the downloaded binary, runtime, service account, file permissions, and restart policy match the operating system before exposing the port. A lightweight server operating system can reduce background overhead, but the official sources do not assign a different hardware minimum to it.
Configuration settings
The configuration can define the world path, world creation behavior, world name, difficulty, maximum players, port, password, message of the day, and related settings. tModLoader documents corresponding options such as world, worldname, and autocreate. Keep configuration files in your backup plan because they preserve the launch behavior as well as the world data.
What port does a Terraria dedicated server use?
The server listens on TCP port 7777 by default. Players connecting from outside the local network may also require a router port-forwarding rule and a host firewall exception.
Home hosting
For a home server, forward the chosen TCP port from the router to the machine running Terraria, then permit that port through the operating-system firewall. If you change the port in configuration, forward and advertise the new value instead of 7777. Restrict administration interfaces and avoid exposing unrelated services on the same public address.
Cloud hosting
The official cloud guidance for services such as AWS or GCP says to allow both TCP and UDP on port 7777. Apply that rule to the cloud firewall or security group as well as the guest operating system. This dual-protocol instruction is specific to the documented cloud setup; do not assume that every local-network rule needs UDP when the server is using its default TCP listener.
Player limit
The default maximum is 16 players, and the value can be changed at startup or in the server configuration. Raising the cap does not create additional CPU, RAM, or network capacity, so set it to a number your workload testing supports rather than treating it as a performance guarantee.
How should I size a server for 10 players?
There is no official 10-player hardware profile. Ten players fit below the documented default cap, but the required resources still depend on world size, vanilla versus modded software, activity, and what else runs on the machine.
- Choose the world size and difficulty you will actually use.
- Decide whether all ten players may be online concurrently or whether ten is only a registration limit.
- Start from the 500 MB small-world RAM reference only if the world is small and lightly loaded.
- Include operating-system memory and reserve space for worlds, logs, backups, updates, and mods.
- Run a peak-load session with exploration, combat, and saving, then inspect memory, CPU, disk, and network behavior.
- Increase resources or move to a larger host if the operating system swaps, the process is repeatedly throttled, saves fail, or players report simulation delay.
This method produces a workload-based decision without pretending that an unpublished player-count formula is authoritative.
Can I run a Terraria server on a VPS, home PC, or managed host?
All three can be viable; the trade-off is control versus administrative effort, not a different official Terraria requirement. Compare the options against uptime, resources, storage, network access, and mod support.
| Hosting choice | Strengths | Costs and risks to evaluate |
|---|---|---|
| Home PC | No separate hosting subscription, direct access to hardware, and full control of files and mods. | Electricity, home upload reliability, router configuration, firewall maintenance, outages, and the need to keep the computer running. |
| VPS | Persistent data-center connectivity, selectable virtual resources, administrative access, and convenient remote backups. | Recurring cost, operating-system administration, virtualized CPU variability, security updates, and responsibility for firewall and port rules. |
| Managed game host | Usually simpler deployment, automated restarts, control panels, and hosting-side maintenance. | Less operating-system control, provider-specific mod support, limits on storage or backups, and recurring fees; no official provider benchmark or price is established here. |
Whichever option you choose, verify that you can change the port, retrieve world files, create independent backups, and increase RAM or CPU allocation if observed usage grows.
How do I set up and verify a dedicated server?
Use the official server files and follow the launch path for your operating system. The following checklist focuses on the decisions that affect requirements and reliability.
- Select the platform and install its required runtime. Match the documented .NET Framework 4.0 and XNA Framework requirements to the server build.
- Place the executable and configuration in a persistent directory. Do not store the only copy inside a temporary download folder.
- Choose or create the world. Set the world path, world name, difficulty, and any autocreation behavior in the documented configuration.
- Set access controls. Define the maximum players, password, message of the day, and port; retain a copy of the configuration.
- Open networking only as needed. Permit TCP 7777 by default, and apply the documented TCP-and-UDP rule for cloud deployments.
- Connect locally first. Confirm the server loads the intended world and accepts a client before troubleshooting router or cloud rules.
- Test remote access. Use a player outside the host’s local network and verify the advertised address and port.
- Monitor and back up. Observe memory, CPU, disk free space, logs, and save behavior during a busy session; copy worlds and configuration files to separate storage.
What changes for a tModLoader dedicated server?
tModLoader documents dedicated-server configuration and launch options, but it does not publish a separate CPU, RAM, or storage minimum. Mod count, dependency behavior, world size, and concurrent players therefore remain workload variables rather than values that can be reduced to one official specification.
Modded sizing procedure
- Record the exact tModLoader version and enabled mods.
- Load the target world and test the activities that trigger the heaviest mod logic.
- Measure peak process memory and CPU rather than idle usage.
- Keep additional disk space for mod files, updates, logs, and rollback copies.
- Change one major variable at a time when diagnosing lag so you can identify whether a mod, world, or player load is responsible.
Do not quote a fixed “RAM per mod” rule unless the author of the exact mod pack supplies one for your player target. Two packs with the same mod count can have very different behavior.
What are the common requirement mistakes and fixes?
- Using client figures as server figures: The 2.0 GHz processor, 2.5 GB memory, and 200 MB disk values come from Steam’s client listing. Label them as client requirements, especially when a machine runs both the game and server.
- Treating 500 MB as a universal cap: It is the documented small-world baseline. Larger worlds, more players, and mods can require more memory.
- Allocating only 200 MB of disk: The client figure excludes the practical space needed for worlds, logs, backups, updates, and mods.
- Opening the wrong port: The default is TCP 7777. A changed port must be changed consistently in the configuration, firewall, router, and connection details.
- Forgetting the cloud protocol rule: The cloud guidance calls for both TCP and UDP 7777, in addition to the guest firewall setting.
- Backing up only the executable: A usable recovery set includes world files and configuration, with enough historical copies to recover from corruption or an unwanted change.
- Assuming the player cap is capacity: The configurable maximum controls admission; it does not guarantee that the host can process that many active players smoothly.
Frequently Asked Questions
Does the server need the full Terraria game installed?
The dedicated package and its documented runtime are the relevant server components; the Steam client requirements apply when the same machine also runs the playable client. Keep server files and world data in a persistent location rather than relying on a client installation directory.
Do I need a static public IP address for a home server?
A static address is not listed as a Terraria requirement. If your public address changes, players may need the new address, so an address-management method or a host with a stable endpoint can make access easier.
How often should I back up a Terraria world?
Choose a schedule based on how much progress your group can afford to lose, and create an extra copy before updates, major builds, or mod changes. Store at least one copy separately from the live machine so a disk failure or mistaken deletion does not remove every version.
What should I check when players cannot connect?
Confirm that the server is running the intended world and port, that the host firewall allows the listener, and that any router or cloud rule targets the correct machine. Test from inside the local network and then from an external connection to distinguish a server problem from a forwarding or address problem.