BeamNG.drive itself does not provide the dedicated server process. Multiplayer servers use BeamMP-Server, whose published estimate is roughly 30–100 MiB of usable RAM (the FAQ says 50+ MiB), a CPU faster than 1 GHz with a multicore processor preferred, no GPU, and about 10 MiB of disk space before mods and plugins. It also estimates 5–10 Mb/s of upload bandwidth. Those figures are for the server process only, not for running the BeamNG.drive game.
If the same computer will also launch BeamNG.drive, size it as a gaming PC: 16 GB RAM and a 6 GB-VRAM graphics card are the official minimum tier, while 32 GB RAM and an 8 GB-VRAM card are recommended. Storage starts at 60 GB for the game, with additional room needed for mods, logs, backups, and updates.
What are the actual BeamMP dedicated server requirements?
A server-only installation is exceptionally small compared with the game client. BeamMP’s README and FAQ describe estimates rather than service-level guarantees, and they caution that values can change between releases. The safer planning figure is the higher RAM estimate plus room for the operating system and your content.
| Deployment | Memory | CPU | GPU | Storage | Network and operating system |
|---|---|---|---|---|---|
| BeamMP server only | 30–100 MiB usable estimate; FAQ says 50+ MiB | Above 1 GHz; multicore preferred | None | About 10 MiB, plus mods and plugins | Windows or Linux; 5–10 Mb/s upload estimate |
| Server plus BeamNG.drive, minimum client tier | 16 GB | Ryzen 5 1600 or Core i5-8400 class | 6 GB of VRAM | 60 GB, plus mod space | Windows 10 64-bit |
| Server plus BeamNG.drive, recommended client tier | 32 GB | Ryzen 7 3700X or Core i7-9700 class | 8 GB of VRAM | 60 GB, plus mod space | Windows 10 64-bit |
The first row describes a headless process. The other rows apply only when the host also runs the BeamNG.drive client, streams or records gameplay, or performs other desktop work. BeamNG.drive’s official requirements are not requirements for a standalone BeamMP process.
How much RAM does a BeamNG dedicated server need?
Plan for at least 100 MiB of usable memory for BeamMP itself, then add operating-system overhead, mods, plugins, logs, monitoring, and backups. The project README gives a 30–100 MiB estimate, while the FAQ describes 50+ MiB; using 100 MiB as the floor avoids planning against the lower end of two slightly different statements.
Usable RAM is not the same as installed RAM
“Usable” refers to memory available to the process, not the total capacity printed on a computer or VPS listing. A small Linux VPS may show plenty of free memory after the service starts, whereas a Windows host has a larger baseline before BeamMP launches. Keep headroom so the operating system can cache files and the server can absorb bursts when players join, maps change, or a plugin writes logs.
Why a 2 GB VPS is usually a practical starting point
The published BeamMP estimate is measured in tens of MiB, but VPS plans are sold in whole gigabytes and must run an operating system and administration tools. A 1–2 GB instance leaves far more practical headroom than the process technically consumes. More memory becomes useful when you run several server instances, install memory-heavy plugins, retain extensive logs, or host other services on the same machine.
What the figures do not prove
No cited BeamMP document supplies a validated player-count limit, a memory-per-player formula, or a repeatable benchmark method. Do not convert the RAM estimate into a promise that a particular server can support a specific number of players. Test your intended map, mod set, and plugin combination under realistic load instead.
What CPU do I need for a BeamMP server?
BeamMP lists a processor above 1 GHz and says a multicore CPU is preferable. That is a very low server-process requirement, so almost any current desktop, mini-PC, or entry-level VPS will exceed it; the harder question is how much work you expect the host to perform besides networking.
Server-only workloads
For one lightly modded instance, prioritize a stable, continuously available system over peak gaming performance. A modern two- or four-core processor gives the operating system room for updates, file compression, monitoring, and backup jobs while BeamMP remains responsive. Consistent single-thread performance can matter during busy simulation moments, but the published material does not provide a CPU scaling curve.
Combined gaming and server workloads
When the same computer runs BeamNG.drive, use the game’s processor tiers rather than the BeamMP minimum. The official minimum names a Ryzen 5 1600 or Intel Core i5-8400; the recommended tier names a Ryzen 7 3700X or Intel Core i7-9700. These recommendations cover the client’s simulation and rendering workload, with the server sharing CPU time in the background.
Virtual CPU cautions
VPS providers often advertise virtual cores rather than a specific physical processor. Two plans with the same core count can behave differently if one has heavy host contention or strict CPU limits. Look for a stated vCPU allocation, sustained CPU policy, and monitoring access, then watch frame time or server tick behavior after installing your actual content.
Does a BeamNG dedicated server need a GPU?
No. BeamMP-Server is headless and does not render the game, so a server-only machine needs no dedicated graphics card. A basic integrated adapter is sufficient for local administration, and a fully headless Linux VPS can run without a graphical desktop.
When a graphics card becomes necessary
A GPU is required when the host also launches BeamNG.drive as a player. BeamNG’s minimum client tier calls for a card with 6 GB of VRAM; its recommended tier calls for 8 GB. Those are client requirements, not additional requirements for the network service.
Running the game and server together
On a combined Windows machine, leave enough resources for the game to load large maps and mods while the server remains online. BeamNG Support warns that the game can use a lot of RAM, including more than 16 GB in demanding situations. Closing browsers, recording tools, and other GPU-intensive applications can prevent the client from competing with the game for memory and graphics resources.
How much storage does a BeamMP server use?
The BeamMP project estimates about 10 MiB of disk space for the server files before adding mods and plugins. That is the executable footprint, not the capacity you should allocate for a long-running public service.
Server-only storage plan
- Reserve the base installation space and a separate directory for downloaded mods and plugins.
- Budget for log growth, crash reports, configuration backups, and temporary update files.
- Keep free space for staging a new version before replacing the live installation.
- Store backups on another disk or host so a failed drive does not remove both the server and its recovery copy.
Combined BeamNG.drive storage
The official game requirement is 60 GB of available storage, and the documentation explicitly notes that mods increase that amount. A 1 TB NVMe SSD is optional headroom for a combined machine, not a BeamMP minimum; it gives room for the game, a large mod library, logs, and local backups without constantly pruning files.
Drive type and reliability
BeamMP does not require an SSD, but solid-state storage reduces installation, update, and map-loading times. For a small server, reliability and an independent backup matter more than maximum throughput. Monitor free space because a full volume can stop log writes, updates, or the operating system itself.
Can I host a BeamNG server on a VPS or at home?
Yes. BeamMP documentation supports native operation on Windows and Linux. A home server is workable when your internet connection offers inbound IPv4 reachability and configurable port forwarding; a VPS is often easier to secure and keep online because it already provides a public network address and data-center connectivity.
Home hosting requirements
- Install BeamMP-Server on a supported Windows or Linux system.
- Give the host a stable local address on your router, preferably with a DHCP reservation.
- Forward the configured server port, commonly 30814, for both TCP and UDP to that local address.
- Allow the same protocols and port through the host firewall.
- Verify the service from outside your home network rather than relying on a local connection test.
Carrier-grade NAT, a changing public address, or an internet plan that blocks inbound traffic can prevent public access even when the server is configured correctly. In those cases, request a public IPv4 address, use a suitable tunnel, or move the service to a VPS.
VPS selection checklist
| Capability | Why it matters |
|---|---|
| Public IPv4 address | Players need a reachable endpoint; IPv6-only plans may not work for everyone. |
| TCP and UDP firewall control | The server port must be reachable over both protocols. |
| Sustained upload bandwidth | BeamMP’s estimate is 5–10 Mb/s upload; leave margin for updates and administration. |
| Persistent disk and snapshots | Protects configurations, mods, logs, and save data. |
| Console or recovery access | Lets you repair firewall rules or services if remote access fails. |
| Mod deployment controls | Makes it easier to synchronize content and roll back a bad update. |
Hosting documentation describes VPS deployment as easier and more secure than exposing a home network, but security still depends on your firewall, updates, credentials, and backup practices. Check the provider’s current IPv4, bandwidth, snapshot, and port policies before ordering because availability and pricing change.
How should I size one computer for BeamNG.drive and BeamMP?
Use the BeamNG.drive recommended client tier as the baseline for a comfortable combined machine, then reserve additional capacity for the server and your mod set. The server itself adds little compared with the game, but running both workloads removes the safety margin of a game-only PC.
Minimum combined configuration
- Windows 10 64-bit.
- Ryzen 5 1600 or Intel Core i5-8400 class processor.
- 16 GB system RAM.
- Graphics card with 6 GB of VRAM.
- 60 GB available for BeamNG.drive, plus mod and operating-system space.
Recommended combined configuration
- Windows 10 64-bit.
- Ryzen 7 3700X or Intel Core i7-9700 class processor.
- 32 GB system RAM.
- Graphics card with 8 GB of VRAM.
- At least 60 GB for the game, with substantial additional room for mods, logs, and backups.
The 32 GB recommendation is for the game client and a comfortable multitasking margin; it should not be presented as the minimum memory for a server-only installation. If you plan to stream, record, run a browser with many tabs, or host several instances, treat 32 GB as a starting point rather than a ceiling.
What network speed and latency should I plan for?
BeamMP’s published estimate is 5–10 Mb/s of upload bandwidth. Upload capacity is the limiting direction for a home host because the server sends state and content to players; downloads mainly affect updates and mod retrieval.
Bandwidth is an estimate, not a player guarantee
The documentation does not state how many players fit within 5 Mb/s or how bandwidth changes with vehicle count, map complexity, physics events, or mods. Measure sustained upload use while your busiest expected session is running and leave headroom for other household or VPS traffic.
Latency and packet handling
Low, stable latency and minimal packet loss usually matter more than having an enormous peak bandwidth number. Choose a wired connection where possible, avoid saturating the uplink with backups during play, and monitor packet loss at the same time as CPU and memory. A server with ample RAM can still feel poor if the route to players is unstable.
What are the most common setup mistakes?
Applying game requirements to a headless server
Buying a gaming GPU or 16–32 GB of RAM for a machine that only runs BeamMP wastes money and power. Start with the small server estimate, then add capacity for the operating system, content, and any other services.
Forgetting both transport protocols
Forwarding only TCP or only UDP can make the server appear unreachable or cause inconsistent connections. Configure the chosen port in the router, host firewall, and BeamMP settings for both protocols.
Running out of disk space
The 10 MiB base estimate can create a false sense of security. Mods, plugins, logs, backups, and update staging consume the remaining space; set an alert before the volume becomes full.
Assuming a minimum CPU predicts capacity
“Above 1 GHz” is a compatibility estimate, not a tested capacity target. Watch CPU utilization and server behavior with your own player count and content, and move to a faster or less-contended host if the service cannot maintain stable updates.
Ignoring release changes
BeamMP labels its figures as guesstimates subject to change with each release. Recheck the project README and FAQ after upgrades, especially when adding plugins or changing the operating system.
Which requirement should I prioritize first?
For a dedicated BeamMP-only host, prioritize reliable connectivity, public IPv4 reachability, a multicore CPU, and enough disk for content and backups; the process’s RAM and GPU needs are minimal. For a combined gaming machine, prioritize the BeamNG.drive recommended CPU, 32 GB of RAM, an 8 GB-VRAM GPU, and storage beyond the game’s 60 GB installation requirement. Because no source establishes a player-count benchmark, validate the final configuration with the exact maps, mods, and number of players you intend to support.
Frequently Asked Questions
Can BeamMP run on Linux without a desktop environment?
Yes. BeamMP supports native Linux operation, and a server-only installation does not need a graphical session or GPU. Use a service manager, restrict administrative access, and keep a console or recovery path available in case a firewall or update prevents remote login.
Do all players need the same BeamNG mods as the server?
In practice, clients must have compatible content for the server’s map and gameplay configuration. Keep a versioned mod list and distribute updates before a scheduled session; mismatched files are a common cause of failed joins or missing assets.
How can I tell whether my home internet uses carrier-grade NAT?
Compare the router’s reported WAN address with the public IPv4 address shown by an independent internet service. If they differ, or the WAN address is in a private or shared address range, inbound forwarding may not work; ask your provider for a public IPv4 address or use a VPS.
Should I virtualize a BeamMP server?
Virtualization is reasonable for a small, server-only instance because the published process footprint is tiny. Avoid aggressive CPU or memory overcommit, reserve persistent storage, and test network performance under the same contention your other virtual machines create.