What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
For a current Rust dedicated server, Facepunch’s setup guidance starts at 12 GB of free RAM and 15 GB of free disk space, with SSD or NVMe storage highly preferred. Those figures are a starting point, not a guarantee: map size, concurrent players, plugins and other workloads change the requirement. A 6k world uses more memory, larger worlds consume more storage, and higher player limits require a faster CPU.
Prefer not to run the server on your own PC? Godlike.Host offers hosted Rust servers with free DDoS protection and up to three free backups a day.
What the official requirements actually mean
Facepunch’s Rust Wiki describes free resources available to the server process, rather than a complete specification for every community. “Free” RAM means memory left for Rust after the operating system and other services have taken their share. “Free” disk space means room for the server installation, world files, logs, updates and growth; it is not a recommendation to fill a drive to its limit.
As an Amazon Associate I earn from qualifying purchases.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteThe guidance also makes clear that population and use matter. A lightly populated vanilla server can behave very differently from a busy server running a large map and many plugins. Facepunch does not publish a universal formula that converts map size or player count into an exact RAM figure, so any precise calculator found elsewhere should be treated as a third-party estimate, not an official guarantee.
- RAM: begin with the official free-memory baseline, then leave headroom for the operating system, plugins and peak activity.
- CPU: size for the maximum concurrent players you intend to permit. Facepunch’s wording is direct: “The more players, the faster your computer CPU needs to be.”
- Storage: use SSD or NVMe when possible and allow more space for larger worlds, updates, backups and logs.
- Network: the game server and query server use UDP; RCON uses TCP. Both UDP ports must be reachable, and the game and query ports cannot be identical.
RAM: how much a Rust server needs
The published baseline
Facepunch lists 12 GB of free RAM for server setup. This is the clearest official starting point for a dedicated server, but it is not a promise that every map, population or plugin collection will run comfortably at that level.
#1 Best Overall
- MEET THE NEXT GEN: Consider this a cheat code; Our Samsung 990 PRO Gen4 SSD helps you reach near max performance with lightning-fast speeds; Whether you’re a hardcore gamer or a tech guru, you’ll get power efficiency built for the final boss
- REACH THE NEXT LEVEL: Gen4 steps up with faster transfer speeds and high-performance bandwidth; With a more than 55% improvement in random performance compared to 980 PRO, it’s here for heavy computing and faster loading
- THE FASTEST SSD FROM THE WORLD'S FLASH MEMORY BRAND: The speed you need for any occasion; With read and write speeds up to 7450/6900 MB/s you’ll reach near max performance of PCIe 4.0 powering through for any use
- PLAY WITHOUT LIMITS: Give yourself some space with storage capacities from 1TB to 4TB; Sync all your saves and reign supreme in gaming, video editing, data analysis and more
- IT’S A POWER MOVE: Save the power for your performance; Get power efficiency all while experiencing up to 50% improved performance per watt over the 980 PRO; It makes every move more effective with less consumption
Why map size changes memory use
The Rust guide specifically warns that a 6k map uses more memory. It also says requirements vary with use and population. A larger procedural world has more terrain and world state to load and maintain, while a busy server has more entities, player activity and events to process. The documentation does not state how many additional gigabytes a 6k map needs, so do not turn the baseline into a fixed “6k equals X GB” rule.
What consumes headroom
- World data and the currently loaded map.
- Connected players, entities and ongoing simulation activity.
- Plugins, mods or custom server frameworks.
- Operating-system services, monitoring, backups and update tools.
- Short-lived peaks during restarts, saves, wipes or large events.
Plan for unused memory rather than running at the edge of physical RAM. When the operating system starts swapping to disk, a fast drive cannot fully compensate for insufficient memory; simulation stalls and connection timeouts become more likely. If your workload grows, increasing RAM is generally a more predictable fix than relying on swap.
CPU: choosing a processor by player capacity
There is no official model or clock-speed minimum
Facepunch does not name a required processor generation, model, clock speed, core count or benchmark score for a Rust server. Do not copy the minimum or recommended CPU from Rust’s player-game requirements: those specifications describe the client game, not a dedicated server.
Use maximum players as the planning anchor
The official relationship is qualitative: the more players you allow at once, the faster the CPU needs to be. Set your target from the maximum concurrent population, not from the number of community members in a Discord server. A server advertised for 200 players should be provisioned for busy moments near that cap, not for its usual weekday average.
Rank #2
- Ideal for high speed, low power storage
- Gen 4x4 NVMe PCle performance
- Up to 6,000MB/s read, 4,000MB/s write
- Includes Acronis cloning software
- 5-year limited warranty
When comparing machines or rental plans, look for the provider’s stated CPU allocation or performance tier and whether resources are dedicated or shared. A nominal core count alone does not reveal single-thread performance, contention or sustained turbo behavior. Ask what happens when neighboring tenants are busy if the plan uses shared CPU.
Symptoms of a CPU limit
- Tick or frame-time warnings during population peaks.
- Delayed entity actions, rubber-banding or slow interaction despite adequate free RAM.
- Performance recovering when players leave or when the maximum-player setting is reduced.
Lowering the player cap, reducing expensive plugins or moving to a faster CPU addresses a processor bottleneck. Adding RAM will not fix a CPU that cannot process the simulation quickly enough.
Storage: capacity, SSDs and NVMe
The official setup figure is 15 GB of free disk space. Facepunch also says SSD/NVMe is highly preferred and notes that larger maps need more disk space. The page does not specify a universal drive capacity, model, interface generation or speed rating beyond that preference.
Treat the free-space figure as room for the initial installation, not the total lifetime allocation. Reserve additional capacity for:
Rank #3
- SPEED UP PROJECTS. Launch creator applications fast with uncompromising PCIe 4.0 read speeds up to 7,100MB/s,[2] (1TB and 2TB[1] models) and write speeds up to 6,700MB/s[2] (1TB[1]-4TB[1] models).
- CREATE AND STORE MORE. Make more room for your 4K videos and high-resolution images with capacities from 500GB[1] up to 4TB[1] on M.2 2280 built with our trusted 8th generation SANDISK BiCS QLC 3D CBA NAND.
- IT GOES WHERE YOU GO. With an all-new power efficient design, your drive delivers high performance with low power, giving you more time to be productive while on the go.
- UNCOMPROMISED RELIABILITY. With up to 1,200 TBW[3] (4TB[1] model) endurance rating, your drive is designed for creators.
- KEEP YOUR DRIVE UPDATED. Monitor your SSD’s performance and check for updates with the downloadable SANDISK Dashboard application.[5]
- World saves and generated map data.
- Server updates and temporary files.
- Logs, crash dumps and administrative tools.
- Backups or multiple identities and worlds.
SSD or NVMe reduces load and save latency compared with a mechanical disk, particularly during world generation, restarts and busy save cycles. NVMe is not stated as mandatory, and no particular model is endorsed; the practical requirement is reliable solid-state storage with enough free capacity.
Self-hosting: installation and network requirements
Self-hosting gives you control over configuration and hardware, but you are responsible for operating-system maintenance, updates, firewall rules, backups and recovery. Facepunch documents SteamCMD for installing and updating the dedicated server on both Windows and Linux. The Rust server’s Steam application ID is 258550.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteDeployment checklist
- Prepare the machine. Start with the official free-memory and free-space baselines, then add headroom for your planned map, player cap, plugins and other services. Prefer SSD or NVMe.
- Install through SteamCMD. Use SteamCMD with Rust application ID
258550, following the current Windows or Linux procedure in the Facepunch Rust Wiki. Keep the installation account and server files separate from unrelated services where practical. - Set world and population values. Configure the server identity, map type, seed, world size and maximum players. The documented world-size range is 1000 through 6000. Larger values require more memory and disk space.
- Assign distinct ports. Configure a game/server port and a separate query port. Both are UDP. The query port is what allows server-browser visibility, so opening only the game port can leave a running server undiscoverable.
- Configure administration securely. RCON uses TCP. Restrict it with firewall rules and strong credentials rather than exposing it broadly to the internet.
- Publish the service. Allow the required traffic through the host firewall. A machine behind a home router will most likely need port forwarding for outside connections, and the forwarding must point to the server’s local address.
- Test externally. Check that players outside your local network can connect and that the server appears in the browser. Test after every router, firewall or port change.
Keep the Facepunch guide open while deploying: startup arguments and update behavior can change as the server software evolves. The values above describe the roles and protocols documented by Facepunch, not a promise that a copied configuration will suit every host.
Rented or managed hosting versus your own machine
Rented capacity removes much of the hardware and network administration, but you still need to select resources that match your world and population. A managed panel may simplify wipes, updates and backups; a self-hosted machine may provide more control and predictable access to the operating system.
Rank #4
- HUGE SPEED BOOST: Get random read/write speeds that are 40%/55% faster than 980 PRO; Experience up to 1400K/1550K IOPS, while sequential read/write speeds up to 7,450/6,900 MB/s reach near the max performance of PCIe 4.0*
- BREAKTHROUGH POWER EFFICIENCY: Use less power and get more performance; Enjoy up to 50% improved performance per watt over 980 PRO, plus optimal power efficiency with max PCIe 4.0 performance**
- SMART THERMAL CONTROL: Samsung's own nickel-coated controller delivers effective thermal control; With its slim size, 990 PRO is a perfect fit for desktops and laptops that meet the PCI-SIG D8 standard***
- THE CHAMPION MAKER: Up to 65% improvement in random performance enables faster loads for an ultimate gaming experience on PS5 and DirectStorage PC games****
- SAMSUNG MAGICIAN SOFTWARE: Get the most out of your SSD with Samsung Magician's advanced yet intuitive optimization tools; Monitor drive health, protect valuable data, and receive important updates for your 990 PRO
| Decision area | Self-hosted machine | Rented or managed server |
|---|---|---|
| CPU | You choose the processor and must monitor contention and thermal limits. | Compare the stated performance tier, dedicated versus shared allocation and upgrade path. |
| RAM | You can install more memory, subject to the motherboard and operating system. | Choose an allocation that leaves room above the official baseline for map, players and plugins. |
| Storage | You select capacity, backups and SSD/NVMe hardware. | Verify free space, storage type, backup policy and whether extra worlds consume quota. |
| Network | You configure firewall rules, router forwarding and external access. | Confirm UDP game/query ports, control over port changes and the provider’s network limits. |
| Location | You are limited by your own datacenter or home connection. | Pick a region close to most players and check latency and routing before committing. |
| Protection and recovery | You arrange DDoS mitigation, monitoring and off-machine backups. | Check the included DDoS protection, backup frequency, restore process and support response. |
| Administration | Full operating-system and file-level control, with more maintenance work. | Convenient panel controls, but possibly restricted plugins, files or startup arguments. |
For an advanced hidden-server deployment, Facepunch recommends a dedicated server with strong DDoS protection. That guidance is a security principle for that use case, not a current ranking of commercial hosts or a price comparison.
How to size a server before you buy or deploy
- Set the maximum concurrent players. Use the cap you will actually publish, including likely event peaks.
- Choose the world size. A 6k world needs more memory, and any larger world needs more storage than a small map. Do not assume the baseline covers every size.
- List software overhead. Count plugins, custom frameworks, scheduled jobs, monitoring and backup retention.
- Start above the baseline. Leave free RAM and disk capacity rather than allocating every available byte to Rust.
- Measure after launch. Watch memory usage, CPU saturation, disk latency, save times and network errors during the busiest period.
- Scale the limiting resource. Add RAM for memory pressure, move to a faster CPU for simulation delays, and use faster or larger storage for I/O and capacity problems.
This process is more reliable than a single “players per gigabyte” rule because Facepunch has not published such a formula and real workloads differ substantially.
Common failures and fixes
The server runs but does not appear in the browser
Confirm that the query port is configured, uses UDP, differs from the game port and is allowed through the host firewall and router. The query port is required for browser visibility; a successful local connection does not prove that outside players can discover the server.
Outside players cannot connect
Check the public address, router forwarding, host firewall and whether your internet service places you behind carrier-grade NAT. Forward the game and query UDP ports to the correct local machine, then retest from a different network.
Best Value
- This product has been replaced by our latest generation. Please search for the SANDISK Optimus GX 7100 NVMe SSD
- HIGH-OCTANE GAMING. Experience speeds up to 7,250MB/s read and 6,900MB/s write (1-2TB models), with up to 35% faster performance than previous generation.
- PURPOSE-BUILT. Designed for serious on-the-go gamers, with a PCIe Gen4 interface and SANDISK’s next generation TLC 3D NAND.
- MORE TIME TO CLEAR THAT CHECKPOINT. Built with laptops and handheld gaming devices in mind, with up to 100% more power efficiency over the previous generation.
- DO MORE WITH DASHBOARD. Ensure your drive is optimized for prime performance with the downloadable WD_BLACK Dashboard (Windows only).
Memory usage keeps climbing or the process is terminated
Check the map size, player peaks, plugin load and free memory available to the operating system. A 6k map and a heavily modified server can exceed the setup baseline. Reduce the workload or move to a machine with more RAM, then verify that backups and other services are not competing for memory.
Players report lag during peaks
Measure CPU utilization and simulation timing while the server is busy. A higher player cap can require a faster CPU even when RAM remains available. Reduce the cap or expensive plugin activity, or select a stronger processor tier.
Restarts and saves are slow
Check available disk space and storage latency. SSD/NVMe is highly preferred by Facepunch; replace a saturated or mechanical drive and retain enough free capacity for updates, saves and logs.
Bottom line for Rust server requirements
Use Facepunch’s 12 GB free RAM and 15 GB free disk guidance as the entry point, not the finish line. Select CPU performance from your maximum player capacity, give larger maps and plugins additional headroom, prefer SSD/NVMe, and validate UDP game/query access before inviting players. If you rent a server, compare real CPU allocation, RAM, storage, location, controls, backups and DDoS protection rather than choosing by headline player slots alone.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →
