How Much RAM for a Vintage Story Server? A Sizing Guide
Use Vintage Story’s rough RAM formula, account for mods and exploration, and choose a server plan with room to monitor your own world.
You will need
- A rough player count for your group
- The mod list and world setup you expect to use
- A way to check your server’s memory and tick readout after it starts
The short answer to how much RAM for a Vintage Story server is Anego’s rough estimate: 1 GB plus 300 MB per player. That works out to 2.2 GB for four players, but it is a starting point for a normal survival world, not a measured limit for every mod list or explored map. Use it to shortlist a plan, then watch your own server’s memory and ticks as the group plays. This guide shows how to do that without turning a player recommendation or one test-world reading into a guarantee.
Start with Vintage Story’s rough RAM formula#
For a normal survival world, Anego’s self-hosting guide gives a rough, conservative estimate of 1 GB plus 300 MB per player. It says the estimate assumes players spread out and that tuning may reduce the amount. The dedicated server guide repeats the same baseline. Treat the result as a planning floor, not a promise that a particular server will stay below it.
| Players | Formula arithmetic | How to read it |
|---|---|---|
| 2 | 1.6 GB | A small starting estimate for the server process |
| 4 | 2.2 GB | The formula’s estimate for a four-player group |
| 6 | 2.8 GB | A baseline before accounting for your world and mods |
| 10 | 4 GB | More players raise the estimate, but not every workload equally |
These are calculations from Anego’s formula, not Vintage Story benchmarks. They describe server memory, not the RAM a player’s computer needs to run the client. The official system requirements currently list 64-bit Windows 10 or newer, macOS 13 or newer, and Linux for the PC game. The official store sells game accounts; each player needs their own account to play multiplayer. No console edition is listed on the current official requirements or store pages.
If you are screening your own hardware, use this RAM estimate alongside the separate requirements for a home machine covering the operating system, CPU, storage, network and server runtime.
If you are already comparing managed plans, Game Hosting publishes 4 GB, 8 GB and 12 GB Vintage Story tiers, along with player, tick and game-memory readouts in its panel. Its Vintage Story plans make the assigned memory visible, which gives you a concrete starting choice instead of relying on a slot label. The numbers below explain what that visibility can and cannot tell you.
Leave room for exploration and the world your group builds#
Two servers with the same player count can have different workloads. Players building near one another share more of the same area; players exploring in separate directions cause the server to load more terrain around them. Vintage Story’s server configuration reference lists MaxChunkRadius with a default of 12, which affects how much land can load around players. It does not publish a RAM multiplier for each radius value or map layout.
That means the player formula cannot tell you exactly how much a long-running world will use. A group that mostly gathers around one settlement may behave differently from the same group spreading across a large map. The setting’s default is a reference point, not a recommendation to lower it to solve every memory or tick problem. Changing view distance can affect what players see and how much terrain loads; check the result with your group before keeping a change.
For a new world, use the formula as your first comparison and keep the world settings in mind. For a mature world, use actual server readings after people have explored and built. Don’t assume that a month-old world needs a fixed extra number of gigabytes: no official formula or published test here supports one.
Treat mod count as a clue, not a RAM formula#
Vintage Story does not publish a fixed number of extra gigabytes for each mod. A list of 20 small interface changes and a list of 20 mods that change world behavior are not equivalent just because both contain 20 entries. There is no reliable conversion from mod count to RAM, so avoid advice such as “add 500 MB for every five mods.”
The public-server census checked on October 5, 2026 found a median of 16 mods among listed servers and 12% with more than 100. Those figures describe how common modded setups are; they do not measure memory. Your own combination, game version, world settings and player habits matter more than a raw count. Check every mod’s Vintage Story version tag and dependencies before adding it, and make sure players know which mods the server supplies. Our guide to installing Vintage Story mods on a server explains how the list and client requirements work.
When you add or remove mods, change one set at a time and note the server’s reported memory after a restart and a normal play session. That gives you evidence from your group’s world. If the number barely changes, that is useful too; the list size alone did not predict a meaningful increase.
Compare plan RAM with your server’s own readout#
Game Hosting’s Vintage Story launch testing recorded 1.2 GB without mods, 2.7 GB with the 50 most-installed mods, and 4.2 GB with 110 mods, before anyone explored. Those are observations from one 1.22.7 initial-world setup. They are not per-player measurements, a mod-by-mod comparison, or a prediction for a mature save.
The panel displays player count, tick rate and the game-memory value reported through Vintage Story’s /stats output. That is a useful way to see what the game reports while your own group plays. It is different from a universal rule for how much plan memory every world needs. Don’t subtract a /stats value from a tier and assume the remainder is guaranteed headroom for every process or future session.
Compare readings under similar conditions: after a restart, during ordinary play, and after the group has explored or added its full mod list. A single busy moment can be less informative than a repeated pattern. If the panel reports more memory as the world grows, check the trend alongside ticks and the server log before changing plans.
Pick a plan by headroom, not by a slot promise#
Game Hosting publishes three fixed Vintage Story memory tiers. Its recommended group sizes are recommendations, not player caps, and they do not promise that every group with that count will use the same amount of RAM.
| Plan memory | Monthly price | Published group recommendation |
|---|---|---|
| 4 GB | $7.99 | 6 players |
| 8 GB | $15.99 | 10 players |
| 12 GB | $23.99 | 20 players |
The practical benefit for a sizing decision is that the plan’s memory allocation is published and the panel shows Vintage Story’s players, ticks and game-reported memory. You can start with a group size and mod list in mind, then review the server’s own readings after real play. The readout helps you observe a workload; it does not prove that a plan will fit every future world or that low ticks always mean a RAM shortage.
If you are choosing between tiers, compare the official estimate with the plan size and keep uncertainty visible. A four-player group calculates to 2.2 GB on the formula, while the 4 GB plan is the smallest listed tier. That arithmetic alone does not validate a fit for a heavily modded or widely explored world. If you want a complete host checklist beyond memory, see how to choose a Vintage Story host.
For a group building shared settlements with staff and claim rules, also read this community server hosting checklist; it keeps resource estimates separate from a promise about player capacity.
Check the cause before adding more RAM#
High memory use can be a reason to investigate, but it does not identify the cause on its own. Low ticks, an “overloaded” message, a crash or slow exploration can also involve CPU work, a mod issue, or terrain generation. Treat those signs as prompts to compare the memory trend with the server log and tick rate, not as an automatic diagnosis.
Use a short check before moving up a tier:
- Compare memory readings from more than one normal session.
- Note whether the group just added mods, changed settings or explored new areas.
- Check the log and tick readout for problems that appear at the same time.
- If memory stays high during ordinary play, consider a larger allocation and compare again.
If the server keeps climbing over days, record when it started and what changed. A rising trend is different from a single peak, but it still does not prove a leak by itself. Leave CPU tuning and long-term leak diagnosis to the focused guides when you need to investigate those questions; changing RAM cannot repair a bad mod or every source of slow ticks.
Choose a starting size and reassess after play#
Use the estimate to narrow the options, then let your real workload guide the next decision. The table is a comparison process, not a new set of requirements:
| Your situation | Start with | Recheck |
|---|---|---|
| A small group on a fresh, mostly vanilla world | Anego’s player formula, then compare it with a published tier | Memory and ticks after a normal session |
| A mod list or existing world you have not measured | A tier that leaves room beyond the arithmetic baseline | Readings after the full mod list and familiar play pattern are in place |
| Players spread across separate bases or exploring often | The formula plus caution about separately loaded areas | Readings after the group has explored and built in different places |
Before you pay, check the plan’s actual memory allocation and whether its listed player figure is a recommendation or a hard cap. After your first few sessions, note the player count, recent changes, game memory and ticks together. If those readings remain comfortable, you have a baseline for your group; if they trend upward or ticks suffer, investigate what changed before deciding whether the plan needs more memory.
Sources checked October 14, 2026
- Vintage Story: self-hosting RAM estimate, dedicated server guide, server configuration, PC system requirements, and official store and game accounts.
- Game Hosting: Vintage Story plans and panel features; internal 1.22.7 initial-world observations are described above with their limits.
Quick answers
How much RAM does a Vintage Story server need for 4 players?
Anego’s rough formula works out to 2.2 GB for four players. Treat that as a baseline for a normal world, then leave room for your mods, exploration and the world your group builds.
How much more RAM do Vintage Story mods need?
There is no reliable fixed amount per mod. Mod count alone does not show how much memory your server will use, so monitor your actual world after adding the list.
Is high Vintage Story server memory use a leak?
One high reading cannot diagnose a leak. Compare readings over time and check logs and ticks; a sustained climb needs investigation rather than an automatic plan upgrade.
Is the 1 GB plus 300 MB formula a guarantee?
No. Anego calls it a rough, conservative estimate for a normal survival world, not a promise that every modded or explored world will fit.