Space Engineers Dedicated Server Guide 2026

Space Engineers is a voxel-based sandbox where players build ships, stations, and planetary bases in a fully destructible environment. The physics simulation, voxel deformation, and programmable block scripting make it one of the most resource-intensive games to host as a dedicated server. This guide covers setting up a Space Engineers server in 2026, using the Torch server manager, managing PCU (Performance Cost Units), configuring worlds, installing mods, and keeping the server running smoothly as your players build increasingly ambitious creations.

Hardware requirements

Space Engineers is heavy. The physics engine simulates every grid (ship, station, rover) independently, and voxel operations (mining, explosions) require significant CPU and memory. Requirements depend heavily on what your players build.

RAM is the most common bottleneck. Each loaded planet consumes 2 to 4 GB on its own, and complex grids (large ships with many blocks) add up fast. NVMe storage is important because Space Engineers world saves can be large (1 to 10 GB) and frequent saves on slow storage cause server hitches.

CPU clock speed matters because the physics simulation, while multithreaded to some extent, still has critical single-threaded bottlenecks. High boost clocks on the AMD Ryzen 9 7950X translate directly to smoother simulation.

Installing the dedicated server

Keen Software House distributes the Space Engineers Dedicated Server through Steam. Install via SteamCMD:

1. Download: steamcmd +login anonymous +force_install_dir /home/se/server +app_update 298740 validate +quit.
2. Configure the world through the SpaceEngineers-Dedicated.cfg file or the built-in server configurator GUI (Windows).
3. Set the world name, game mode (survival or creative), and scenario (Empty World, Star System, or a custom save).
4. Start the server: SpaceEngineersDedicated.exe -console on Windows.

For Linux hosting, the server runs under Wine or Proton. This adds a small performance overhead but works reliably. Many providers, including HostValues, handle the Wine layer transparently so you interact with the server through a standard game panel.

Torch: the essential server manager

Torch is a community-built server manager that wraps the Space Engineers dedicated server and adds critical features: plugin support, automated restarts, performance profiling, grid management, and an entity cleanup system. For any server beyond a handful of friends, Torch is practically mandatory.

Key Torch features:

• Plugin system: extend server functionality with C# plugins. Essential plugins include Essentials (admin commands, motd, grid management), Concealment (unloads distant grids to save CPU), and Profiler (identifies which grids consume the most simulation time).
• Automated restarts: schedule restarts with warnings, automatic saves, and player notifications.
• Grid management: list, delete, transfer, and analyze grids from the Torch console without being in-game.
• Performance profiling: see exactly which grids, blocks, or scripts are eating server performance. Invaluable for diagnosing lag.
• Remote access: Torch provides a built-in web interface and API for remote management.

Install Torch by downloading the latest release from the Torch GitHub repository, extracting it into your server directory, and running Torch.Server.exe instead of the vanilla dedicated server binary. Torch manages the underlying game server process.

Understanding PCU limits

PCU (Performance Cost Units) is Space Engineers' built-in system for limiting server load. Every block has a PCU value: a light armor block costs 1 PCU, a refinery costs 90, a programmable block costs 100, and turrets cost 225 each. The total PCU consumed by all grids on the server determines how much the physics engine needs to simulate.

Server PCU settings:

• Total PCU limit: the global cap across all players and grids. A typical survival server sets this between 100,000 and 500,000.
• Per-player PCU: limits how much any individual player can build. Common values range from 25,000 to 100,000.
• Enforce vs. advisory: you can enforce PCU limits (players literally cannot place blocks past the cap) or set them as advisory (warnings only). Enforcement is recommended for performance.

Finding the right PCU balance is the core challenge of Space Engineers server management. Too low and players feel restricted. Too high and the server grinds to a halt when everyone builds capital ships with dozens of turrets. Start with conservative limits and raise them only if performance allows.

Planet and asteroid configuration

Space Engineers supports three world types: planets only, asteroids only, or both. Each has different performance implications.

Planets are the heaviest load. Each planet is a voxel sphere that consumes significant memory (2 to 4 GB per planet loaded in active range). The default Star System scenario includes the Earth-like planet, Mars, the Moon, Europa, Titan, and the Alien planet. Running all of them simultaneously demands 16+ GB of RAM. If your server does not need all planets, use a custom scenario with fewer.

Asteroids are lighter individually but can add up. Procedural asteroid fields generate rocks dynamically as players explore. Set the ProceduralDensity in your config to control how many spawn. Lower density means fewer objects for the server to track.

Recommended approaches by server size:

• Small server (2 to 6 players): Star System with default planets works fine with 12+ GB RAM.
• Medium server (6 to 16 players): custom scenario with 2 to 3 planets, moderate asteroid density.
• Large server (16+ players): single planet or asteroid-only world. Add planets only if RAM allows.

Mod support

Space Engineers has an active modding community on the Steam Workshop. Server mods install through the server config by adding Workshop IDs to the mod list. Players automatically download mods when connecting.

Popular server mods in 2026:

• Modular Encounters Spawner: adds NPC encounters, pirate ships, and random events. Makes survival worlds feel alive.
• WeaponCore: overhauls the weapon system with modded weapons, better turret AI, and new damage types.
• Build Vision: quality-of-life improvement for block placement.
• Aerodynamic Physics: adds realistic atmospheric flight mechanics.
• Shield mods: energy shields for ships and stations, adding strategic depth to combat.

Each mod adds processing overhead. Mods that spawn NPC entities (like Modular Encounters) are the heaviest because each spawned grid consumes PCU and physics simulation time. Monitor server performance after adding mods and remove any that cause disproportionate load.

Performance tuning

Space Engineers servers degrade gradually as players build. Proactive management keeps things playable:

• Use the Concealment plugin. It unloads grids that no player is near, dramatically reducing physics simulation cost. This is the single biggest performance improvement for most servers.
• Clean up abandoned grids. Players who leave the server often abandon ships and stations that continue consuming resources. Torch's grid management tools let you identify and remove grids belonging to inactive players.
• Limit programmable blocks. In-game scripts (programmable blocks running C# code) execute every tick. Poorly written scripts or too many active scripts drag down the simulation. Consider limiting programmable blocks per player or disabling them on performance-sensitive servers.
• Cap turret count. Turrets are among the most expensive blocks because they constantly scan for targets. Limit turrets per grid or globally to prevent turret farms from destroying performance.
• Set trash removal. Enable the built-in trash removal system to automatically delete floating objects, small debris, and grids below a configurable block count.
• Schedule daily restarts. The simulation accumulates overhead from physics interactions, voxel damage, and entity tracking. A daily restart during off-peak hours resets this.
• Use the Profiler plugin. Identify which specific grids or blocks consume the most simulation time, then work with their owners to optimize or remove them.

The target simulation speed is 1.0 (real time). When it drops below 0.8, players notice sluggish physics and delayed interactions. Below 0.5, the game becomes frustrating. Monitor simulation speed through Torch and take action before it reaches critical levels.

Frequently asked questions

Can Space Engineers run on Linux natively?

The dedicated server is Windows-only, but it runs reliably under Wine or Proton on Linux. Many hosting providers, including HostValues, handle this transparently. Performance overhead from the compatibility layer is minimal (roughly 5 to 10%) and does not affect gameplay quality.

How much RAM do I need per planet?

Budget 2 to 4 GB per actively loaded planet. The exact amount depends on how much voxel deformation (mining) has occurred and how many grids are near the planet. An untouched planet uses less memory than one that has been heavily mined. If you run the full Star System with six bodies, plan for at least 16 GB total for the server.

Should I use Torch or the vanilla dedicated server?

Use Torch. The vanilla dedicated server lacks essential management features: no plugin system, no performance profiler, no automated grid cleanup, and limited remote management. Torch wraps the vanilla server and adds everything you need to run a server that lasts longer than a week. The only reason to use vanilla is if you are testing something in isolation.