Garry's Mod Server Requirements
There is no universal GMod server specification. A vanilla Sandbox server, a DarkRP community, and a Workshop-heavy Prop Hunt stack can have very different CPU, memory, disk, and download needs. Use the ranges below as starting points, then measure the actual server under the map and gamemode your community runs.
Last verified: September 1, 2026. Single-thread performance and Lua/entity load often matter more than a high core count. Size the server from observed console/resource data and leave headroom for Workshop updates and backups.
Starting-point tiers
| Use case | Players | Starting point | What changes the answer |
|---|---|---|---|
| Private vanilla/Sandbox | 4–16 | 2 GB RAM, fast 2+ core CPU, 15 GB+ SSD | Physics entities, large maps, and long sessions. |
| Curated Workshop or TTT | 16–32 | 4 GB RAM, high-clock CPU, 25 GB+ SSD | Lua hooks, addon dependencies, and client download volume. |
| Public DarkRP or heavy stack | 32–64+ | 8 GB+ RAM, high single-thread performance, 50 GB+ NVMe | Persistent databases, NPC/entity counts, map size, and collection growth. |
These are planning ranges, not guarantees. A small server with a poorly behaved addon can need more CPU than a larger vanilla server.
What to measure
- CPU: watch the main server thread during combat, physics bursts, and map changes.
- Memory: include the base process, Lua/addon growth, Workshop cache, and update headroom.
- Storage: count the base app, maps, collection, logs, and retained backups; Workshop collections grow over time.
- Network: account for player traffic and the first-join download burst separately.
- Recovery: leave disk and time for a clean update, rollback copy, and log collection.
Linux or Windows?
Facepunch documents Linux hosting with srcds_run and SteamCMD. Windows is convenient for local testing. Choose the platform your team can update, monitor, and recover reliably; the workload matters more than a generic OS claim.
Test before increasing slots
- Boot app 4020 on a stock map and record idle CPU/RAM.
- Add the gamemode and Workshop collection, then record startup and join time.
- Simulate the highest expected player/entity load and watch for tick drops, crashes, or memory growth.
- Keep a smaller fallback slot count in the startup script while tuning.
Related Garry's Mod guides
- Dedicated-server setup
- Startup flags and server.cfg
- Workshop collections and addons
- Server cost and plan sizing
- Connection troubleshooting
Compare measured requirements with managed Garry's Mod hosting, especially when the collection or player count changes.