Space Engineers Dedicated Server Requirements and Sim Speed: Fix or Upgrade?
Space Engineers dedicated server requirements look modest on paper, but sim speed is what decides whether your world stays playable. Here is how to read Keen’s specs for a rented plan, diagnose a slow server, and decide whether to fix settings or upgrade.
3.2 GHz CPU, 3 logical cores, 6 GB RAM and 5 Mbps. It will still run below that, but Experimental mode is forced on.
4.5 GHz CPU, 3 logical cores and 10 GB RAM. That should tell you this game cares more about fast cores than a big core count.
The main simulation thread. A panel can show average CPU use looking fine while one core is effectively maxed and the whole server slows down.
Keen’s official dedicated server requirements
If you are comparing Space Engineers dedicated server requirements against rented plans, start with what Keen actually publishes and then translate that into a hosting decision. The server is Windows only, does not need a GPU, and installs at roughly 8 GB before logs, saves and mods. It also needs .NET Framework 4.8 and the Visual C++ redistributables. If you install it yourself through SteamCMD, the dedicated server uses Steam app ID 298740 and downloads with an anonymous login, so the server itself does not need to own the game.
| Item | Minimum | Recommended | What it means for a rented server |
|---|---|---|---|
| CPU | 3.2 GHz, 3 logical cores | 4.5 GHz, 3 logical cores | Clock speed matters more than adding lots of cores, because the main simulation thread is the bottleneck. |
| RAM | 6 GB | 10 GB | RAM follows world size: planets, grids, saves and mods push it up over time. |
| Connection | 5 Mbps | — | Enough bandwidth matters, but low sim speed is usually not caused by bandwidth alone. |
| Storage | Roughly 8 GB install | — | Leave headroom for save growth, logs and mod content. |
There are a few practical limits worth remembering. The default game port is UDP 27016. Dedicated servers cannot be hosted on consoles. Linux is only possible through unofficial Wine setups and is unsupported, so if you want the least awkward route, stick with Windows hosting. Also, if you intend to run a crossplay server, you cannot use Steam Workshop mods, which changes the sort of plan and management tools you may want.
What those specs actually mean when you rent a plan
The key mistake people make is treating Space Engineers like a game that scales neatly with extra cores. It does not, at least not in the way most host adverts suggest. The main simulation thread is what usually caps server performance, so strong single-core clock speed matters more than a generous-looking core count. If a plan offers more cores but weaker clocks, that can be a worse choice than a smaller plan on faster hardware.
The second thing to read properly is RAM. More RAM does not directly raise sim speed by itself, but it does give a larger world room to exist without turning every save, load and background task into trouble. Think of RAM as following world size. A modest world with sensible limits can sit comfortably on lower RAM, while a long-running modded world with large grids, planets and lots of saved entities tends to want the recommended 10 GB rather than the minimum 6 GB.
Also be careful with host dashboards. An averaged CPU graph can hide one maxed core. Space Engineers can look fine at a glance because total CPU use is spread across logical cores, while the one thread that matters is already at the wall. That is why you can see a server with “spare CPU” in a panel but still get poor sim speed in-game.
So the simple reading is this: if you are choosing between plans, prioritise faster CPU clocks first, then enough RAM for the size and age of the world, then the useful admin access that lets you change settings and inspect saves properly.
Sim speed, FPS and network are different problems
Before you fix anything, make sure you are looking at the right symptom. Sim speed 1.0 means real time, and the in-game Shift+F11 overlay shows it as Server simulation speed. That number is shared by the whole server. If it drops, everyone is playing on a slowed simulation.
- Low sim speed: whole-server slowdown. Machines tick slower, physics feels delayed, and everyone shares the same problem.
- Low client FPS: one player’s graphics or local machine is struggling. Other players may be fine.
- Network issues: rubber-banding, delayed interaction or packet loss style symptoms. Sim speed may still read normally.
This matters because the remedy is different. Poor client FPS is not fixed by buying more server RAM. Packet trouble is not fixed by lowering PCU. And low sim speed caused by a heavy world will often survive restarts, because the load is in the save itself.
Sim speed triage: heavy world or struggling host node?
Once you know the problem really is sim speed, the next decision is whether the save is simply too heavy or whether the machine underneath your rented server is having a bad day. These two cases look similar if you only watch the player experience, but the pattern over time is different.
| Symptom | Usually points to | Why |
|---|---|---|
| Performance declines gradually as the world grows | Heavy world | More grids, more subgrids, more debris, more scripts and more active production accumulate load. |
| Server stays slow after a restart | Heavy world | The save still contains the same expensive entities and settings. |
| Sim speed drops suddenly with nothing changed in the world | Struggling host node | If the save is unchanged, a sudden shift often points below the game layer. |
| Performance is bad at some times, then recovers later | Struggling host node | That pattern fits shared hardware pressure more than a permanently heavy save. |
A heavy world usually tells on itself. You will see more rotors, pistons and hinges, more moving grids, more floating objects, more scripts, more industry, more combat leftovers and more save bloat. A bad node is different: you log in to the same world, with the same activity, and the server suddenly behaves worse than it did before.
If you suspect the host node, collect clean evidence first: the sim speed reading, the time the issue happened, whether the world was unchanged, and whether it cleared up later without any edits. That gives you a stronger case than simply saying it “felt laggy”.
Fix it or upgrade? Use this decision table
Most Space Engineers servers should be tuned before money is thrown at them. Upgrading too early wastes budget; upgrading too late means you spend hours chasing settings on hardware that was never good enough for the save.
| If you see this | Try fixes first? | Upgrade plan? |
|---|---|---|
| Gradual long-term sim speed decline as builds and debris pile up | Yes | Maybe later if clean-up and limits no longer hold 1.0 |
| Lots of subgrids, scripts and floating objects | Yes | Only after you cut the obvious drains |
| Sudden sim speed collapse with nothing changed in the save | Not mainly | Possibly, or ask to be moved if the node is the issue |
| Average CPU graph looks fine, but in-game sim speed is poor | Yes | Often points to weak per-core performance if the save is already tidy |
| RAM pressure on a large or modded world | Partly | Yes, if world size is the real constraint |
If your world is tidy, scripts are controlled, floating objects are limited, autosave is sensible, and you still cannot hold sim speed, then better per-core hardware is the sensible next step. That is where our Space Engineers hosting comparison is most useful: not as a shopping list for the biggest plan, but as a way to filter for the sort of server access and hardware profile this game actually rewards.
If the world is already well-managed and the main simulation thread is still the wall, move to a plan that prioritises stronger per-core speed and solid file access over headline core counts.
Compare the best Space Engineers server hostsThe two-file trap: why changing the panel sometimes does nothing
This catches a lot of rented servers. SpaceEngineers-Dedicated.cfg holds server-level settings, but its SessionSettings only seed a new world. Once a world already exists, the live session settings come from Saves\<World>\Sandbox_config.sbc. So if you keep changing values in the dedicated config and an existing save ignores them, that is not a mystery: you edited the wrong file for that stage of the server’s life.
Edit with the server stopped. If the server is running, it can rewrite the world config again on save and wipe your manual changes. On self-managed installs, a clean stop via taskkill /IM SpaceEngineersDedicated.exe saves first; adding /f kills it without saving. Rented hosts usually expose these files through a panel or file manager, which is fine, but the same rule still applies: stop the server before editing the world config.
<SessionSettings> <MaxFloatingObjects>100</MaxFloatingObjects> <AutoSaveInMinutes>15</AutoSaveInMinutes> <EnableIngameScripts>false</EnableIngameScripts> <BlockLimitsEnabled>PER_PLAYER</BlockLimitsEnabled> <TotalPCU>20000</TotalPCU> </SessionSettings>
Do not blindly paste those values. Read your world’s own values first and then change them deliberately. The point of the excerpt is simply to show the keys to look for. If you run more than one world or use command-line options such as -path, -port, -ip, -maxPlayers, -console, -noconsole or -ignorelastsession, document that clearly so you know which save you are actually editing.
Settings-first fixes, in the order that usually matters most
When sim speed slips, go after the big drains first. Space Engineers has some very predictable offenders, and you will usually get more benefit from controlling them than from tweaking minor options.
- Deal with subgrids first. Rotors, pistons and hinges are expensive, especially when they collide or create messy moving assemblies. If you need hard limits, use block limits by block pair name or tag; for example, a limit of 6 pistons is a perfectly sensible guardrail on a shared world.
- Cut floating objects and debris. The dedicated server UI caps and defaults max floating objects at 100, but lower is lighter. If your server has regular combat, mining leftovers or dropped inventories everywhere, bring this down and use trash removal.
- Disable in-game scripts if nobody truly needs them. Set EnableIngameScripts off for groups that are not using programmable block logic. Scripts can be a steady drain rather than a dramatic one, which makes them easy to overlook.
- Lengthen autosave. Use a longer interval such as 10-15 minutes to reduce save spikes. Never set autosave to 1 minute unless you enjoy turning routine saving into a constant hitch.
- Set sensible PCU and block limits before the world gets busy. Default max PCU is 100,000, but many communities are better served by a lower ceiling such as 20,000. BlockLimitsEnabled can be NONE, GLOBALLY, PER_PLAYER or PER_FACTION. Raising limits later is easy; lowering them later means deleting people’s builds, which is always the ugly version of admin work.
- Use PauseGameWhenEmpty. If nobody is online, stop simulating. Drifting ships, running refineries and spinning rotors stop costing CPU while nobody is there to see them. It is a server-level option in SpaceEngineers-Dedicated.cfg rather than a world setting.
- Clean up expensive entities with admin tools. The Alt+F10 admin screen lets you sort the entity list by PCU, block count and owner last logout, which makes abandoned heavy grids easier to find. Trash removal settings are part of the same maintenance routine, not an afterthought.
- Watch remotely instead of guessing. Keen’s Remote Client, VRageRemoteClient.exe, shows simulation speed and lists grids and floating objects remotely. That is useful when you want evidence without logging into the world every time.
Other common drains that cause spikes
Even on a good plan, certain activities can drag sim speed down: copy-pasting large grids, gatling guns, explosions and missiles, many drills running at once, complex asteroids, many refineries and assemblers, and leaving physics debug overlays on through F11. These do not always mean your plan is too small; sometimes they simply mean the world rules are too loose for the kind of activity happening on it.
Pre-purchase checklist: what to ask a host before you rent
If you are shopping carefully, especially around cheap UK game server hosting, ask questions that expose whether the plan suits Space Engineers specifically. This is not a game where vague “powerful hardware” wording tells you much.
| Question to ask | Why it matters |
|---|---|
| What matters more on this plan: stronger per-core speed or just more shared cores? | Space Engineers lives and dies on the main simulation thread. |
| Can I access or edit Sandbox_config.sbc as well as SpaceEngineers-Dedicated.cfg? | You need world-level file access, not just a simple panel toggle. |
| Can I view logs, saves and mod files directly? | Troubleshooting is much easier when file access is not locked down. |
| Can I change ports and launch parameters if needed? | Useful for custom setups using options such as -port, -path or -maxPlayers. |
| Is Windows hosting standard for this service? | That is the supported route for the dedicated server. |
| If I suspect a bad host node, can support investigate or move the service? | A sudden unexplained sim speed drop is not always a world problem. |
| How easy is it to back up, replace or clone a world? | Important when testing stricter limits or cleaning a heavy save. |
| Does the panel clearly separate new-world settings from existing-world settings? | This helps avoid the two-file trap. |
The good hosts for this game are not necessarily the ones with the loudest spec list. They are the ones that make it easy to see what your world is doing, edit the right files, restart cleanly and escalate a hardware issue when the save itself is not the cause.
Space Engineers 2 status: relevant, but not your server answer yet
As of late October 2026, Space Engineers 2 does not have dedicated servers yet. Keen’s current plan is player-hosted co-op for up to 4 players in early 2027, after previously expecting it with VS4 in late 2026. Dedicated servers are planned later, but there is no date yet.
The Hostile Encounters update arrived on 19 October 2026, but that does not change the server reality: if you need a persistent rented server now, you are still making that choice around the current Space Engineers dedicated server requirements, not around Space Engineers 2. So for the moment, “fix or upgrade?” is still a Space Engineers question, not a sequel question.
Space Engineers server FAQ
How many players can a Space Engineers dedicated server handle?
There is no honest one-line number, because world design matters more than a simple headcount. A tidy server with sensible limits can handle far more comfortably than a chaotic world full of subgrids, scripts and debris. Judge it by sim speed under your group’s actual building habits, not by a generic player claim.
Does a Space Engineers dedicated server need a GPU?
No. A GPU is not required for the dedicated server. CPU performance and enough RAM for the world are the parts that matter far more here.
Can I host a dedicated server on Linux or consoles?
Consoles cannot host dedicated servers. Linux is only possible through unofficial Wine setups and is unsupported, so Windows is the normal supported route.
Can a crossplay Space Engineers server use mods?
Not Steam Workshop mods. A crossplay server cannot use Steam Workshop mods, so if crossplay is a firm requirement, plan your world rules and content around that from the start.
Will adding more RAM fix low sim speed?
Not by itself in most cases. More RAM helps larger worlds remain healthy and gives headroom for saves, mods and entity growth, but the main simulation thread is usually the direct sim speed limiter. If one core is the wall, extra RAM alone will not turn a slow tick into a fast one.
Related Space Engineers hosting pages
Once you know whether you need tuning or a better plan, these pages cover the next step.
This guide is based on the current dedicated server behaviour and published game details, but game updates, control panels and host tooling do change. If your host’s current panel labels or workflow differ, follow the host’s live documentation and panel options where they clearly map to the same settings.
