There is no developer-published hardware minimum for a Core Keeper dedicated server. The practical starting point for a small, unmodded group is about 2 GB of RAM, two modern CPU cores and fast storage with room for the save to expand. Plan 3–4 GB for a larger or heavily explored world and roughly 6 GB for busy modded play. Those figures are third-party planning estimates, not guarantees. Steam’s often-quoted 8 GB requirement applies to the Windows game client, not the headless server.
What requirements are officially documented for the dedicated server?
The official setup material explains how to install the server through Steam or SteamCMD, where saves are stored and how to edit ServerConfig.json. It does not publish a minimum RAM amount, CPU model, core count or disk capacity for the dedicated process. SteamCMD identifies the dedicated-server package with app ID 1963720.
That absence matters when planning a machine. A number copied from the store page is not automatically a server requirement. The store page describes the game client, which renders the world and handles a player’s local interface; a dedicated server runs the simulation without rendering a full client.
What the Steam client listing actually says
| Platform | Minimum or recommended client specification |
|---|---|
| Windows | Windows 10 64-bit minimum; Intel Core i5-2300 or AMD Ryzen 3 1200; 8 GB RAM |
| Linux | Ubuntu 20.04 minimum; Ubuntu 22.04 listed as recommended |
The 8 GB Windows figure is therefore a client specification. It should not be used as proof that every dedicated server needs 8 GB. A server can need less or more depending on the world and workload.
How much RAM does a Core Keeper dedicated server need?
Use workload-based ranges rather than one universal number. Current planning guidance places a small vanilla group near 2 GB, larger or heavily explored worlds at 3–4 GB, and busy modded play around 6 GB. Keep additional memory available for the operating system, monitoring tools, backups and any other services on the host.
| Workload | Planning RAM | Evidence and qualification |
|---|---|---|
| Small vanilla group | About 2 GB | iTechGuides Team, 2026 estimate |
| Larger or heavily explored world | 3–4 GB | iTechGuides Team, 2026 estimate |
| Busy modded play | Roughly 6 GB | iTechGuides Team, 2026 estimate |
| General setup range | 2–4 GB | HostValues, 2026; explored map size is identified as the main factor |
| Container template default | 1.0 GB minimum; 1.5 GB recommended | Pterodactyl Eggs, 2024 template values, not a developer guarantee |
Can a 4 GB server run Core Keeper?
Four gigabytes is a sensible starting allocation for a small-to-medium vanilla server, provided the machine has more memory than that and the world is not simultaneously loading a large unexplored region, running intensive farms and hosting mods. It is not a promise of stable performance for every eight-player or heavily developed world. Treat it as a testable allocation: observe memory during exploration and increase the limit if the process approaches it or the operating system begins swapping.
What causes RAM use to rise?
- Explored-map size: More of the underground has been generated and retained as the world develops.
- Players entering new areas together: Simultaneous exploration creates more active simulation work than players staying in one base.
- Mods: Content and automation mods can add entities, scripts or storage requirements.
- Mob and pathfinding activity: Busy bases and combat areas keep more simulation state active.
- Other software: Web panels, databases, game servers and backup jobs consume the same host memory.
Measure the server process and total system use while your real group performs its heaviest routine. A fresh world with two players is not a useful stress test for a mature, modded save.
What CPU do I need for a Core Keeper server?
No official CPU minimum or benchmark is published for the dedicated server. HostValues treats two cores as a practical baseline, while iTechGuides emphasizes per-core performance because simulation, pathfinding and simultaneous exploration can depend more on fast individual cores than on simply adding many slower cores.
Practical CPU baseline
- Choose a modern processor with at least two available cores for a small private server.
- Prefer strong single-thread performance when choosing between an older many-core chip and a newer, faster one.
- Leave additional CPU headroom for larger groups, mods, scheduled backups and the operating system.
- Avoid placing a busy world on a machine already saturated by compilation, video encoding or other game servers.
These are operational guidelines, not a tested compatibility guarantee. If players report delayed interactions while the server thread is busy, lowering competing workloads or moving to a faster host can help more than adding unused cores.
How much storage does a Core Keeper dedicated server use?
The initial installation is small: HostValues estimates about 1–2 GB for the server software, while the Pterodactyl Eggs template uses 1.0 GB as a minimum and 1.5 GB as a recommendation. Those figures do not represent the lifetime size of a world. RE:NODE notes that world data grows with the amount of underground terrain players have dug out.
Plan for growth, backups and maintenance
- Reserve substantially more capacity than the initial install estimate.
- Keep at least one independent backup copy, and allow room for multiple world versions before updates or major mod changes.
- Account for logs, downloaded updates and temporary files created during maintenance.
- Use an SSD or NVMe drive when available for quicker save and load operations. The available guidance does not mandate a particular drive type or capacity.
Disk pressure is a failure mode, not merely a performance issue: a full volume can prevent saves, logs or updates from completing. Check free space as part of routine server maintenance, especially after long exploration sessions.
Do I need port forwarding for a Core Keeper dedicated server?
Not necessarily. Steam relay mode normally lets friends connect without forwarding a port. Adding a -port argument switches the server to direct-connect mode; the selected port must then be allowed through the host firewall and, when applicable, the router.
Port behavior documented by the setup material
-port 7778is documented as a direct-connect example.- LAN examples commonly use port
27015. - The Pterodactyl template reserves UDP
27015for the server and UDP27016for query traffic.
Port assignments can change with a server build or hosting panel. Verify the current behavior before publishing a permanent firewall rule. Do not open extra ports when relay mode is sufficient.
How many players should the server support?
Steam describes online co-op for 1–8 players, and the Core Keeper Codex says omitting -maxplayers leaves a default of eight. That is the documented ceiling for normal planning; there is no evidence here that a server will remain stable above eight players.
What hardware should I choose for common workloads?
The following profiles translate the published estimates into starting allocations. They are planning targets, not guarantees, and each assumes the host retains operating-system headroom.
| Use case | Starting RAM | CPU approach | Storage approach |
|---|---|---|---|
| Small private vanilla group | About 2 GB | Two modern cores with good per-core speed | Fast drive; leave room beyond the 1–2 GB installation estimate |
| Larger group or heavily explored world | 3–4 GB | Two or more fast cores, with extra headroom for simultaneous exploration | Fast drive plus capacity for expanding saves and several backups |
| Busy modded world | Roughly 6 GB | Modern high-performance cores; avoid competing heavy workloads | Fast drive with substantial free space for saves, logs, updates and backups |
Start at the low end only when you can monitor the process and adjust the allocation. A managed host should let you increase RAM, CPU or disk without rebuilding the world; on a self-hosted machine, confirm that upgrades are physically and administratively possible before committing to a long-running save.
How do I set up and size a server safely?
- Install the server: Use Steam or SteamCMD and the documented app ID
1963720. Follow the setup guide for the operating system and save location. - Confirm the configuration: Review
ServerConfig.json, player limits and any launch arguments before inviting players. - Allocate resources: Begin with the RAM range that matches your world profile, two or more modern CPU cores and storage well above the installation size.
- Choose networking: Keep Steam relay mode when it meets your needs. If you add
-port, configure the matching firewall and router rules for direct connections. - Stress-test the world: Have the expected number of players enter new areas, operate farms and trigger normal combat. Watch RAM, CPU, disk space and save completion during the test.
- Back up before change: Copy the world before server updates, mod changes or major configuration edits, and retain more than one generation when disk space allows.
- Re-size based on evidence: Increase RAM or move to a faster CPU when monitoring shows sustained pressure, swapping, failed saves or simulation delays.
Should I self-host or use managed hosting?
Both approaches can run the same dedicated-server software. The choice is mostly about who pays for uptime and who performs maintenance.
| Decision factor | Self-hosting | Managed hosting |
|---|---|---|
| Upfront cost | Uses an existing PC or server; hardware and electricity are your responsibility | Recurring hosting fee |
| Uptime | The machine and network must stay powered and connected | Designed for an always-on service |
| Maintenance | You handle SteamCMD updates, backups, firewall rules and recovery | The provider may simplify operations; verify exactly what is included |
| Control | Direct access to files, launch arguments, mods and save migration | Control depends on the panel and plan |
| Scaling | Limited by your hardware unless you upgrade it | Often easier to increase RAM, CPU or disk; confirm current terms |
| Network path | Relay or your own direct-connect and port rules | Provider networking and panel rules apply |
Managed hosting is useful when nobody wants to leave a home machine running or maintain recovery procedures. Self-hosting is attractive when you already own suitable hardware and want complete control over files and mods. Compare current regional pricing, backup policy, resource limits and export options before choosing a provider.
What are the most common sizing mistakes?
- Using the client’s 8 GB as the server minimum: Separate the Steam client specification from dedicated-server planning.
- Allocating every gigabyte to the game: The operating system and other services still need memory.
- Planning only for a fresh world: Exploration, farms and mods increase resource use over time.
- Ignoring disk growth: A small installation can coexist with a much larger, heavily excavated save and several backups.
- Assuming relay and direct connect are identical: Direct mode introduces firewall and port requirements.
- Promising performance above eight players: The documented co-op range and default are eight; higher counts need separate evidence.
- Sharing a saturated host: CPU contention and disk-heavy jobs can create lag even when the nominal RAM allocation looks adequate.
Frequently Asked Questions
How can I test whether a 4 GB allocation is enough before opening the server publicly?
Create a backup, then reproduce the busiest expected session: have players explore new regions, run automation and fight mobs at the same time. Record peak process memory, total host memory, CPU saturation and free disk space; raise the allocation or reduce competing workloads if the operating system swaps, the process is terminated or saves become unreliable.
What should I back up before installing mods or updating the server?
Stop the server cleanly, copy the complete world data and retain the previous copy separately from the live directory. Keep at least one known-good version so you can roll back if a mod changes world data or an update fails.
Can I move a Core Keeper world from a home PC to a hosting panel?
Usually the practical requirement is file access: download the world data, upload it to the provider’s designated save location and reproduce the relevant configuration. Confirm the provider permits world export and identify its exact save path before paying, because panel workflows differ.
What does the SteamCMD app ID 1963720 identify?
It is the documented Steam app ID for obtaining the dedicated-server package. Using the ID in SteamCMD targets the server distribution rather than installing only the graphical client.