Vintage Story Server Requirements for a Home PC
Check Vintage Story server requirements for RAM, CPU, storage, network, and client compatibility before running a group world at home.
You will need
- An estimated player count and whether the group plans to use mods
- A Windows or Linux machine you can leave running while friends play
- The current Vintage Story server package and matching .NET runtime
Vintage Story server requirements for a home PC start with the game’s rough CPU and memory guidance and a machine that stays online for your group. For a normal survival world, Anego estimates 1 GB of base RAM plus 300 MB per player and recommends 4 CPU threads; the dedicated-server wiki gives a slightly different per-player CPU frequency estimate. These are planning figures, not benchmarks. This guide separates server requirements from the PC requirements for playing, then shows how to screen a vanilla or modded group without pretending a formula predicts every world.
Separate Vintage Story server requirements from client specs#
A dedicated server and the game you play are separate workloads. The current Vintage Story client requirements list Windows 10 or newer, macOS 13 or newer, or Linux, with 8 GB RAM minimum and 16 GB recommended for the client. Anego’s dedicated-server table lists Windows or Linux, 4 CPU threads, and a rough memory formula. It does not give the server the client’s 8 GB minimum, and it does not list a GPU requirement for the server.
| What you are checking | Officially listed guidance | What it means |
|---|---|---|
| Dedicated server OS | Windows or Linux | macOS appears on the client page, not the dedicated-server hardware table |
| Dedicated server memory | 1 GB + 300 MB per player | A rough estimate for a normal survival world |
| Dedicated server CPU | 4 threads recommended | A recommendation, not a player-slot promise |
| Client PC | Windows 10+, macOS 13+, or Linux; 8 GB minimum / 16 GB recommended | This is for launching and playing the game, not a server-only minimum |
Each person joining needs a Vintage Story game account. The official account page says an account is required to download and start the game and includes multiplayer access. Do not disable account authentication to make an underpowered machine work; hardware sizing and player authentication are separate issues.
If you mean to run the server and play on the same computer, that computer has to handle both processes plus the operating system. The server-only arithmetic below cannot certify that combined workload. The dedicated-server wiki recommends a separate data path for same-machine hosting so the server’s saves and settings do not mix with the client’s files; same-PC hosting adds the game client’s workload, so use separate server readings before deciding whether that setup works for your group.
Apply the official RAM formula to your group#
Anego’s self-hosting guidance calls its estimate rough and conservative for a normal survival world where players spread out: 1 GB base RAM plus 300 MB for each player. It says tuning may lower the requirement. Use the equation to get an initial server-memory estimate, not a guarantee that the world, mods, operating system, and other processes will all fit.
| Group example | Arithmetic | Formula estimate |
|---|---|---|
| 2 players, vanilla | 1 GB + (2 × 0.3 GB) | 1.6 GB |
| 5 players, light mods | 1 GB + (5 × 0.3 GB) | 2.5 GB |
| 15 players, heavy mods | 1 GB + (15 × 0.3 GB) | 5.5 GB |
The words “light mods” and “heavy mods” describe the examples, not a mod surcharge in the equation. Official sources do not publish a fixed number of additional gigabytes per mod or a validation that these three combinations run well. The RAM sizing guide explains why world layout, exploration and the actual mod list can move memory beyond a player-count estimate.
A group clustered around one settlement and a group exploring in many directions may not load the same amount of world data. As a world grows, compare the formula with the server’s actual memory use during ordinary play. If the process runs out of memory or stops, the formula did not prove the machine had enough headroom; check the logs and the specific workload instead of assuming that adding a particular amount per mod will solve it.
Check threads and CPU frequency as a planning range#
The official sources agree on 4 recommended CPU threads but differ on the per-player frequency estimate. Anego’s self-hosting page says 1 GHz base plus 150 MHz per player. The dedicated-server wiki says 1 GHz plus 100 MHz per player. Keep both values visible rather than choosing one as if it were a measured threshold.
| Players | RAM arithmetic | CPU frequency arithmetic from the two official estimates |
|---|---|---|
| 2 | 1.6 GB | 1.20–1.30 GHz |
| 5 | 2.5 GB | 1.50–1.75 GHz |
| 15 | 5.5 GB | 2.50–3.25 GHz |
Each CPU figure is calculated from 1 GHz plus 100–150 MHz for each player. It is not a benchmark or a statement that any processor at that advertised clock will sustain the corresponding group. Clock numbers alone do not capture processor generation, cooling, competing work, or how your world behaves. Keep the 4-thread recommendation in view too; a CPU listing that only gives a headline boost clock does not tell you the machine’s available threads or sustained performance.
If you need to compare processor models in more detail, use a dedicated CPU comparison. This page sticks to the official broad requirements and the source’s frequency range.
Give the save and network a practical check#
The official dedicated-server specification table does not give a disk-size target or a minimum upload-speed number. The wiki’s performance troubleshooting guide recommends keeping the save on an SSD when investigating performance problems. That supports choosing an SSD as a practical storage choice; it does not establish SSD capacity, an upload rate, or a measured guarantee for a particular group.
For players joining over the internet, your home connection must allow the game traffic through the router and firewall. The default server port is 42420 for both TCP and UDP in current setup guidance; see the port walkthrough for the separate network steps. The server hardware figures cannot tell you whether your ISP allows inbound connections, whether your router forwards both protocols, or whether a firewall rule is correct.
A wired connection is a sensible way to reduce one source of wireless variability, but do not treat it as a substitute for testing from outside your home network. There is no supported bandwidth threshold in the sources used here. If players report connection trouble, follow a network diagnosis rather than upgrading the CPU based on the symptom alone.
If your group has outgrown the owner’s PC and is comparing managed options, use this community-server host checklist to compare resources, access controls and recovery terms.
Match the current server software to its runtime#
Vintage Story’s dedicated-server guide currently says .NET 10 is required for game versions 1.22.0 and newer, .NET 8 for 1.21.x, and .NET 7 for versions before 1.21. The official version history lists stable 1.22.7, released August 16, 2026, so a new 1.22.7 server needs the .NET 10 runtime. Check the version you intend to run before installing a runtime; “latest .NET” is not a substitute for the version-specific requirement.
The official client is available for PC on Windows, macOS, and Linux, but that client platform list does not expand the dedicated-server OS guidance beyond Windows and Linux. The sources checked here do not list a console client. Each player also needs their own game account, and the client and server should use a compatible Vintage Story version. A machine that meets the hardware arithmetic still needs the correct server files and runtime to start.
Decide whether the home PC fits how your group plays#
Self-hosting can make sense when you already have a Windows or Linux machine, can leave it powered on while people play, and are comfortable maintaining its software and network access. The official self-hosting page describes free home hosting as one of the available routes. There is no reason to rent solely because a formula exists if your own server is stable for the way your group uses it.
A home machine may be the wrong fit if it has to shut down when you leave, your upload or router cannot support outside connections, or you do not want to maintain updates and backups. If the world should remain available without relying on a home PC, Game Hosting’s Vintage Story plans publish 4 GB, 8 GB, and 12 GB memory tiers and list Ryzen 9 9900X hardware with 4 CPU threads. That gives you a managed option with published memory allocations; it still does not guarantee that a particular player count or mod list will fit a tier. If you decide to rent, compare Vintage Story hosting options against the needs of your group. Compare the plan’s memory with the same rough estimate, then check how your actual world behaves.
Use this checklist before calling the machine ready#
A quick screening can rule out an obvious mismatch, but it cannot replace a session with your group. Before inviting everyone, check each point:
- Operating system: the dedicated-server guidance names Windows or Linux.
- Memory: calculate 1 GB + 300 MB per player, then leave room for the world, mods, other processes, and normal system use.
- CPU: account for the recommended 4 threads and treat the official 100–150 MHz-per-player range as a rough guide.
- Storage and internet: prefer SSD storage for the save, check that your connection and router can serve players, and verify both TCP and UDP on port 42420 if hosting publicly.
- Software and accounts: match the server version to the required .NET runtime; each player joins with their own game account.
- Real use: start the world, inspect its logs, and let your actual group play before treating the setup as adequate.
If the server reports memory errors or cannot keep up during real use, revisit the logs and the task causing the load. These official numbers are a starting screen, not a pass/fail certification, a tested player cap, or evidence that a specific mod combination will work. For the full installation path, start with the publisher’s dedicated server guide.
Sources checked October 14, 2026
- Vintage Story: self-hosting requirements, dedicated-server guide and downloads, PC client system requirements, game account, and version history.
Quick answers
What are the minimum server requirements for Vintage Story?
The official guidance is a rough estimate for a normal survival world: Windows or Linux, 1 GB plus 300 MB per player, and 4 CPU threads. Treat those as planning figures, not guaranteed minimums for every world.
How much RAM does a Vintage Story server require?
Anego’s formula is 1 GB plus 300 MB per player. It does not specify extra RAM per mod, so check your own server after adding its world and mod list.
Do I need a server to play Vintage Story multiplayer?
No. One player can host a world while playing, or you can run the separate dedicated-server program. Each player still needs a Vintage Story game account.
Can I run a dedicated server on macOS?
The current official dedicated-server hardware guidance lists Windows or Linux. macOS is listed for the game client, but not in that server operating-system guidance.