VEIN Server Requirements: RAM, CPU and Player Slots Explained
The official line is 8GB of RAM just to start, but what decides whether your VEIN server stays smooth is what the world is doing: how many players are on, how many zombies and hordes the settings allow, mods and how old the world is. Here is how much RAM to buy, why CPU speed matters, how to set player slots and how to tell which resource is running out.
8GB is the official minimum just to start. Several hosts size their entry VEIN plans at 10-12GB so there is room left once people join.
No official figure. Per-core speed matters most, and you feel a weak CPU when lots of zombies are active, not on an empty server.
Official notes put the server files at about 5GB, but one Linux install was measured at 9.5GB. Saves, backups and updates need extra space.
MaxPlayers defaults to 16. Slots only cap who can join; the load comes from the players who are actually online and what the world is doing around them.
The official numbers and what they really mean
The official VEIN server guidance gives you a memory floor, not a full sizing model. That matters because hosts often market by slot count or by small RAM plans, while VEIN’s real cost comes from what the world is simulating at the same time.
| Requirement | Official figure | What it means for you |
|---|---|---|
| Memory to start | At least 8GB RAM | This is the floor for a dedicated server, not a promise that 8GB will stay comfortable once people join or settings change. |
| Idle memory on Windows | 8GB on Windows Server 2019 with no clients | This is the source of the headline number. It is an idle reading on one Windows server environment, so it already leaves little room on an 8GB plan. |
| OS and prerequisites | 64-bit OS; Windows needs Visual C++ 2012, 2013 and 2015-2022 plus DirectX End-User Runtimes; Linux build exists | Check prerequisites before blaming performance. A missing runtime or wrong environment causes startup trouble that looks like a hardware problem. |
| Server files | About 5GB | That is only the install. Leave extra space for the live save, backups and future updates. |
| CPU | No official figure | You need to judge CPU by symptoms and by workload: zombies, hordes and spread-out players matter more than an empty slot count. |
Here are the memory readings that exist for the VEIN server, side by side.
One host’s measurements on Linux, on build 0.025 Hotfix 3, put the server at about 3.1 to 3.7GB with nobody on and 4.5GB with one player, so the first player added about 1GB. That is one reading, not a rule. The Windows figure and the Linux readings come from different systems and different builds, and VEIN is still in Early Access, so neither is a promise for your server. The safe buying rule is still simple: treat 8GB as the minimum to buy for a dedicated server, because you need room for actual players, horde spikes, mods, save growth and Windows-based hosting.
How much RAM to buy
If you are sizing a first VEIN server, the right question is not “what is the smallest plan that starts?” but “what plan still has space left when the busiest session arrives?”
| Situation | Sensible starting point | Why |
|---|---|---|
| Friends on one PC via Local Multiplayer | No dedicated server needed | Ramjet points small private play to Local Multiplayer instead: start or load a game with Multiplayer on and let friends connect to you. |
| Small private group on a rented server | Do not buy below 8GB; 10-12GB entry plans are a more sensible starting place | The official 8GB line is only a start figure. A bit of headroom is useful for joins, longer sessions and future changes. |
| Public server or roughly 16-player ambition | Expect to move past the bare minimum quickly; one host recommends 10GB for around 16 players | A public server fills the slots you advertise, and more people online at once means more of everything for the server to run. |
| Raised spawn caps, horde-focused setup or mods | Start above the floor and watch the memory graph at busy times | These changes raise live world activity, and some mods increase RAM far more than others. |
| Two servers on one machine | Budget each instance separately and monitor both | Each server has its own baseline memory use and its own spikes; sharing one box multiplies the risk. |
Plans at 4GB, 6GB or 7GB do exist, but they sit below the official start figure, so they are hard to justify for a dedicated VEIN server. Many hosts instead size entry plans at 10GB or 12GB because that better matches how people actually use a persistent server. If you are comparing packages sold by slot count, remember that more slots do not magically add resources; the useful question is how that offer handles memory and CPU, which is the real issue behind slots vs RAM pricing.
A practical rule: if the memory graph sits close to the plan limit during normal busy sessions, move up a tier before you add more slots, mods or spawns. Waiting until the first crash just turns sizing into guesswork.
What actually drives load in VEIN
VEIN does not get heavy just because the server exists; it gets heavy because the world is busy. This matrix helps you see which changes mostly hit RAM, main-thread CPU or disk.
| What grows | RAM | CPU every tick | Disk and saves |
|---|---|---|---|
| Players online | Yes | Yes | Partly |
| Higher zombie spawn caps | Partly | Yes | No |
| Hordes | Partly | Yes | No |
| Mods | Yes | Partly | No |
| Old world, decay off | Partly | No | Yes |
| A second server on the same machine | Yes | Yes | Yes |
Players online
Each player who joins adds their own character, inventory and movement for the server to track and send to everyone else, and the official notes are clear that memory rises as more players connect. Zombies, loot and vehicles around each player have to be run as well, so a group split across the map is usually harder work than the same group travelling together. If the server is smooth when you play as a pack but stutters when everyone heads off in different directions, CPU is the resource running short.
Zombie spawn caps
vein.AISpawner.SpawnCapMultiplier, vein.AISpawner.SpawnCapMultiplierZombie and vein.ZombieBuckets.MaxCount=300 shape how much AI the server may keep in circulation. Raising these values means more potential actors to spawn, track and update. The immediate cost is main-thread CPU, because spawning and active AI behaviour are simulation work; the side cost is extra memory for more live world state. Lowering caps makes the world feel less crowded, but it is one of the cleanest ways to cut swarm-related lag. It helped if the server becomes noticeably steadier when large packs would normally appear.
Hordes
Hordes are a burst of load rather than a steady one. Horde spawning is on by default (vein.AISpawner.Horde.Enabled=1) at an average of 0.05 hordes a minute, each lasting 120 seconds, while the separate horde mode is off (vein.AISpawner.HordeMode=0). When a horde turns up, the server suddenly has a crowd of zombies to move, path and fight with at the same time, which is main-thread work. Lowering the chance or the duration takes pressure off, at the cost of fewer big attacks. If rubber-banding or a crash lines up with a horde arriving, start here.
AI virtualisation and async sensing
vein.AISpawner.EnableVirtualization=1 and vein.AI.AsyncSensing=1 are both on by default, and they are best left that way. Async sensing works out what each zombie can see asynchronously, away from the rest of the frame, so a crowd of zombies looking for targets does not hold everything else up. Virtualisation is the AI system’s own way of managing zombies without running every one in full all the time. Neither gives players anything extra when switched off, so if you are chasing stability, check these are still at 1 before you touch anything else.
Loot respawn
vein.ContainersRespawn.Interval=10800 controls how often containers can refresh. More frequent respawn means more item state changing around the map, which is more housekeeping for the server and more save churn over time. This is not usually the first source of combat lag, but on a long-running public world it can add up. Increasing the interval reduces that churn, but players will see slower loot refresh.
Time with nobody online
vein.Time.ContinueWithNoPlayers=0 means the world waits when nobody is online, which is helpful for a small group. If you turn it on, the server keeps advancing time and calendar events while empty. That means water shutoff at day 30 and electrical shutoff at day 46 can happen while nobody is actually playing, and it also means more world progression and state changes between sessions. Use it only if you want a world that carries on without players present.
Base decay
vein.BuildObjectDecay=1 means bases decay over time. That is a gameplay choice first, but it has a server side too: with decay off, every wall and crate anyone ever placed stays in the world for good, including the bases of players who stopped coming months ago. On a public server that grows for a long time, keeping decay on stops the save filling up with abandoned builds. You judge this one over weeks, not minutes.
Mods
Mods do not all cost the same. Some mainly add content that changes the memory baseline; others add active systems that also cost CPU when the world is busy. Make one change at a time and watch what happens after a restart and then during a genuinely busy session. If memory jumps immediately after adding a mod and stays higher before much happens in-world, that mod raised the baseline.
World age and save size
An older VEIN world has more bases, more stored items and more changes to keep track of, and all of it lives in the save. The server writes that save as one file while it runs, so a bigger world mostly shows up as disk use and longer saves, restores and copies. A useful test: if a fresh world runs well on the same plan and only the old one feels heavy, the problem is accumulated world state, not your player slots.
Edit gameplay settings in Vein/Saved/Config/WindowsServer or Vein/Saved/Config/LinuxServer, in Engine.ini under [ConsoleVariables], with the server stopped. A short default-style excerpt looks like this:
[ConsoleVariables] vein.AISpawner.Enabled=1 vein.AISpawner.SpawnCapMultiplier=1 vein.AISpawner.SpawnCapMultiplierZombie=1 vein.AISpawner.EnableVirtualization=1 vein.AI.AsyncSensing=1 vein.AISpawner.HordeMode=0 vein.AISpawner.Horde.Enabled=1 vein.AISpawner.Hordes.ChancePerMinute=0.05 vein.AISpawner.Hordes.Duration=120 vein.ZombieBuckets.MaxCount=300 vein.ContainersRespawn.Interval=10800 vein.Time.ContinueWithNoPlayers=0 vein.BuildObjectDecay=1
If you want the current list for your build, PrintAllVeinSettings in a singleplayer game prints it to the log. That matters because Early Access builds can change names, defaults and behaviour.
CPU: there is no official figure, so read the symptoms
Neither Ramjet’s dedicated server notes nor the official VEIN wiki publish a CPU requirement. For a single VEIN server, that usually means you should care more about per-core speed than about chasing lots of cores, because VEIN runs on Unreal Engine, and an Unreal server does most of its game simulation on one main game thread. Zombies, spawning, pathing and horde moments all lean on that thread.
CPU starvation and RAM exhaustion look different. When CPU is the problem, the server often stays online but starts rubber-banding, delaying movement updates or feeling worse during swarms and when players spread out. When RAM is the problem, you are more likely to see startup failure, crashes, restarts or a memory graph pressing against the plan limit. Keeping AsyncSensing and virtualisation on helps because it cuts unnecessary AI cost without reducing your slot count.
If you run two instances on one machine, each one brings another main thread under load and another memory baseline. The official VEIN wiki says multiple servers are possible, with a second instance example on ports 7780 and 7781, but CPU and memory should be monitored carefully if they are busy servers. For the broader pattern behind these symptoms, see our guides on what causes game server lag and game server hardware requirements.
Player slots: cap the server to the group you actually expect
The default player cap is 16 in Game.ini. You can raise it, and the official VEIN wiki even shows -MaxPlayers=64 in a launch example, while some host panels accept values from 2 to 32. The important point is that slots reserve nothing. An empty 32-slot server does not use 32 players’ worth of RAM or CPU; it only becomes heavier when those players actually join and start doing things.
That is why an honest slot cap matters. A private friend-group server can safely match the number you really expect online at once. A public server is different: if you advertise more slots, more people may turn up and fill them, especially once word gets around about people joining a VEIN server. Slots are a social choice first and a hardware consequence second.
Edit Game.ini in the same WindowsServer or LinuxServer config folder, with the server stopped. For example:
[/Script/Engine.GameSession] MaxPlayers=24
If a MaxPlayers=16 line disappears, that is normal. Unreal removes config lines that are set to the default value, so a vanished default does not mean the setting failed.
Disk and saves: not the first bottleneck, but easy to overlook
Official notes put the server files at about 5GB, but one host measured 9.5GB after a Linux install. That does not change live performance much on its own, but it does tell you not to buy a plan with no spare storage at all.
VEIN writes the save as one file while the server runs. As the world ages, that single file matters more during save operations, restarts, copies and restores than it does during ordinary minute-to-minute play. Backups and pre-update copies take extra space as well, which is why a server that “fits fine” on launch day can run out later. Keep room for game server backups, especially while VEIN is still changing quickly in Early Access.
If disk is the problem, the signs are usually clear: updates fail, backups stop, panel warnings appear or you cannot keep a rollback copy before patching. That is a storage issue, not a reason to keep cutting AI settings.
Network and ports for self-hosters
Networking for a VEIN server is light: one game port, one query port and an optional RCON port. Ramjet’s dedicated server notes open UDP 7777 for gameplay and UDP 27015 so Steam can check the server is up, while the official VEIN wiki uses UDP 7778 for the query port. Whichever you use, the query port is the one set by GameServerQueryPort in Game.ini, and it has to be open alongside the game port.
| Port | Protocol | Purpose | Needed by players? |
|---|---|---|---|
| 7777 | UDP | Main game traffic | Yes |
| Query port: 27015 in Ramjet’s notes, 7778 on the wiki | UDP | Server query and visibility | Not typed in, but needed for the server to show in lists |
| 7777 | TCP | RCON, optional | No |
If you run the server on your own network, the official VEIN wiki says the query port must not be between 27020 and 27050. On a rented server the panel assigns the ports for you, which is one reason people stop self-hosting a game server once they want a world that is always on. If you are choosing an operating system, the lighter Linux memory readings above are worth knowing, and our guide to Linux vs Windows game servers covers the rest of the trade-off.
Troubleshooting by symptom
Start with the trigger, not just the complaint. If the trouble appears at startup, think RAM or prerequisites; if it appears during swarms, think CPU and AI settings; if it appears after patching, think disk.
| Symptom | Likely cause | First fix |
|---|---|---|
| Server will not start or crashes on a 4-6GB plan | The plan sits below the official 8GB start figure | Move to at least the official floor. Do not spend time tuning around an undersized baseline. |
| Crashes when a horde arrives | A burst of zombies for the server to run at once | Reduce horde pressure first or keep horde mode off, then retest before adding more players. |
| Rubber-banding when many zombies are around | CPU starvation from active AI and spawn settings | Lower zombie spawn multipliers back towards default and leave virtualisation and async sensing on. |
| Lag only when players spread out | The server is running zombies and loot around several groups at once | Set a lower slot cap or expect to need stronger CPU for a wide-roaming group. |
| Memory climbing over a long session | Long-running world, mods, more explored state, or simple lack of headroom | Restart between busy periods, review recent mods and upgrade if normal sessions still sit near the limit. |
| Server missing from the browser on Windows | Admin permissions issue or wrong ports/query setup | Run with admin permissions on Windows and re-check the game and query ports. |
| MaxPlayers change does not stick | The server was not stopped, the wrong file was edited, or 16 was removed as the default | Edit Game.ini with the server stopped and do not worry if a default-value line vanishes. |
| Disk full after updates | Install files, save, backups and pre-update copies no longer fit | Clear old copies you truly do not need, then add more storage rather than risking the live world. |
| Server feels slow after raising spawn caps | More AI to spawn and update, plus extra memory pressure | Put spawn settings back near default and compare behaviour before you touch slots. |
| Second instance makes both servers lag | Shared CPU and RAM contention, sometimes plus a port clash | Use separate ports such as 7780 and 7781 for the second instance, then monitor both closely or split them up. |
Tune it or upgrade
Good tuning removes waste. It does not turn an undersized plan into a reliable public server.
| Situation | Try in settings first | Upgrade when |
|---|---|---|
| Plan is below 8GB | Do not spend long tuning around it | The server fails to start reliably or leaves no room once anyone joins |
| Lag begins with swarms or hordes | Keep virtualisation and async sensing on; reduce horde pressure or restore spawn caps to default | Default settings still struggle during ordinary peak sessions |
| Lag begins when players roam far apart | Lower the slot cap to realistic turnout and avoid over-advertising a public server | A small group still causes stutter even without aggressive AI settings |
| Memory is fine empty but high during normal evenings | Review recent mods and world settings one change at a time | The memory graph sits near the limit during routine play |
| Only the older world feels heavy | Check decay, loot churn, mods and backup habits | You need room for the live save, backups and updates on the same plan |
| Two instances on one machine | Keep them on separate ports and be conservative with slots and AI settings | Both need to be busy at the same time |
The best order is usually: keep sensible defaults, watch one busy session, change one thing, then decide if the plan is genuinely too small. If your fix is “raise slots and lower every world setting”, that is not a fix; it is a sign the plan and the server goal do not match.
If you are weighing different plan sizes and panels, use our VEIN server hosting comparison to check which options start at the official floor, which expose the config files cleanly, and which make more sense for a small private world versus a public server.
Compare the best VEIN server hostsVEIN server requirements FAQ
How much RAM does a VEIN server need?
The official figure is at least 8GB of RAM to start a dedicated server. That should be treated as a floor, not a comfortable target, because memory use rises with players, settings, mods and a long-running world. For rented hosting, entry plans around 10-12GB are often a more sensible starting point.
Is 6GB enough for a VEIN server?
It is below the official start figure, so it is not a safe dedicated-server buy. Even if a host sells a 6GB plan, you are starting under the published requirement before you add players or mods. For Local Multiplayer on one PC you may not need a dedicated server at all, but for a real persistent server 6GB is the wrong place to save money.
Does a VEIN server need a fast CPU?
Yes. There is no official CPU number, but VEIN runs on Unreal and one server’s simulation work is mostly felt on the main game thread, so strong per-core performance matters. You notice CPU limits when zombies, hordes or widely spread players make the server stutter without necessarily crashing.
How many players can a VEIN server hold?
MaxPlayers defaults to 16, and it can be raised. The real limit depends less on the cap itself and more on what those players are doing, how far apart they are, and how aggressive your AI settings are. Empty slots cost nothing, but public servers have a habit of filling the space you advertise.
Do zombie and horde settings affect VEIN server performance?
Very much so. Higher spawn caps and horde activity increase active AI, which mostly hits main-thread CPU and can also raise memory use. If a server is smooth until large groups of zombies appear, those settings are the first place to tune before blaming networking.
More VEIN and server sizing guides
Compare VEIN hosts and read the hosting basics behind this guide.
VEIN is in Early Access, so defaults, settings and host panels change between builds. Where your host’s current panel works differently from what is described here, follow the panel.