Can I Run BeamNG.drive on My PC / Laptop?

Minimum is a Ryzen 5 1600 or Core i5-8400, a GTX 1060 6GB or RX 570, and 16GB of RAM. Recommended steps up to a Ryzen 7 3700X or Core i7-9700, an RTX 3060 or RX 6700, and 32GB of RAM. Both list DirectX 11, though DirectX 12 is now the default renderer after the 0.39 update.

16GB clears the official minimum and gets the game running, but BeamNG's own documentation admits it can use well past that during normal play, since every vehicle's physics data plus the streamed world and mod caches all sit in memory together. If you're running career mode, mods, or bigger maps, 32GB is the realistic number, not a luxury.

The base install is 60GB. That's just the vanilla game, though. Add maps, vehicles and mods from the in-game repository, which most long-term players do, and folder sizes past 200GB are common. An SSD isn't officially required, but it meaningfully cuts load times on larger community maps.

It runs on both Windows 10 and 11. DirectX 12 became the default renderer with the 0.39 graphics update, with DirectX 11 kept as a fallback option for older or less stable setups. The official requirement sheet still lists DirectX 11 as the baseline.

Yes, it's still in Early Access as of this writing, with the developers working toward a 1.0 release that adds a full career mode. Because it's actively developed, performance and requirements shift between updates. The 0.39 graphics overhaul, for example, raised GPU demands compared to older builds, so older benchmark numbers you find online may no longer be accurate.

No, the core single-player game runs fully offline once installed. Official multiplayer is in development but not finished, and the popular community mod BeamMP already lets you play with others online, which does require an internet connection and a server to connect to.

With one vehicle on an open map at 1080p, most GPUs from the last several generations comfortably clear 60 fps, often well past 100 on mid-range and higher cards. That number falls once you add AI traffic, a busy career-mode area, or a large crash test, because those add CPU work rather than GPU work. Expect a noticeably lower number in a twenty-car pileup than on an empty road, regardless of your graphics card.

For a physics simulation of this depth, yes, it's reasonably light on the GPU, which is why even older graphics cards handle it. The tradeoff is that the physics engine itself is CPU-intensive by nature, since it's simulating real structural deformation rather than faking it, so no amount of optimization removes the need for a decent CPU if you want busy scenes to stay smooth.

Because that drop comes from the CPU, not the GPU. Each vehicle in a scene, whether it's a background traffic car or wreckage from a crash, is simulated as its own physics object with thousands of nodes and beams. A powerful graphics card doesn't reduce that workload. If this describes your situation, lowering the traffic count or turning on Simplified Traffic Vehicles helps more than any graphics setting.

VR needs a Vulkan-compatible GPU with at least 8GB of VRAM, 10GB recommended, plus an OpenXR-compatible headset. CPU and RAM needs are the same as the recommended PC tier: a Ryzen 7 3700X or Core i7-9700 class chip and 32GB of RAM. VR is more demanding than flat-screen play since it needs to hold a higher, steadier frame rate.

It can, depending on what you add. Extra vehicles and maps mostly cost storage and load time, but detailed custom vehicles with complex physics structures add to the same CPU workload as any other vehicle in the scene. A folder full of high-detail mod cars in a busy traffic scenario will run slower than the same scene with stock vehicles.

Yes, at the lower end. With the RTX 3050 you clear BeamNG.drive's minimum, so 1080p low to medium is the target and easing back a setting helps. Comparable to the GTX 1650 Super here, roughly 55-70 fps at 1080p, since this game leans on the CPU more than the GPU.

Not really. The GTX 1650 falls under BeamNG.drive's minimum card, so you are looking at very low settings and low frame rates, if it starts at all. Below the official recommended tier but above minimum. Expect roughly 45-65 fps at 1080p with a single vehicle, less in busy scenes.

Fine for a lighter setup. The GTX 1060 6GB clears BeamNG.drive's minimum, so target 1080p low to medium and adjust down for a steady rate. The official minimum card. Around 60-75 fps at 1080p with one vehicle on an open map, lower once traffic or a crash stacks up several vehicles at once.

Runnable. The RX 580 covers BeamNG.drive's minimum, meaning 1080p low to medium and a smoother feel after a small settings drop. Performs close to the GTX 1060 6GB in this game, roughly 60-70 fps at 1080p in the same light-traffic scenario.

Yes, comfortably. The RTX 4060 sits at or above BeamNG.drive's recommended card, so 1080p on high is smooth and 1440p is well within reach. Roughly 95 fps at 1080p and 75 at 1440p, similar class to the RTX 3060 with a bit more headroom.

Yes, though keep expectations modest. The RTX 3060 clears BeamNG.drive's minimum, so plan on 1080p at low to medium and trim a setting or two for a steady frame rate. The GPU half of the official recommended tier. Around 90-110 fps at 1080p and 70-85 at 1440p with one vehicle on an open map.

Fine for a lighter setup. The RTX 2060 clears BeamNG.drive's minimum, so target 1080p low to medium and adjust down for a steady rate. Similar territory to an RTX 3060, generally 80-100 fps at 1080p with light traffic before the CPU becomes the limiter.

Fine for a lighter setup. The GTX 1660 clears BeamNG.drive's minimum, so target 1080p low to medium and adjust down for a steady rate.

The GTX 1660 Super gets you in. It meets BeamNG.drive's minimum, so low to medium at 1080p works, and turning a couple of things down keeps it steady.

It clears the bar. The RX 6600 matches BeamNG.drive's minimum, so 1080p on low to medium is realistic once you tune a few settings. In the same range as an RTX 3060, roughly 85-100 fps at 1080p in light traffic.

It clears the bar. The GTX 1660 Ti matches BeamNG.drive's minimum, so 1080p on low to medium is realistic once you tune a few settings.

The RTX 3060 Ti is a strong fit for BeamNG.drive. It lands at or above the recommended spec, so high 1080p is comfortable and 1440p works.

Yes, on modest settings. The RTX 4050 meets what BeamNG.drive needs at minimum, so 1080p low to medium is the sweet spot.

Not really. The GTX 1050 Ti falls under BeamNG.drive's minimum card, so you are looking at very low settings and low frame rates, if it starts at all.

No trouble at all. The RTX 4070 meets or beats what BeamNG.drive recommends, so 1080p high runs well and 1440p is realistic. Similar to the RTX 3070, comfortably over 100 fps at 1080p and 1440p, with the CPU deciding fps in busy scenes.

BeamNG.drive actually dropped support for Mac, so there's nothing built for Apple Silicon or macOS, not even on an M4 MacBook Pro. Cloud streaming through GeForce Now, should it ever list the game, or an unofficial Windows layer are the only routes left, and neither is supported by the developers.

Running Windows through Boot Camp on an Intel Mac can work if the Mac's hardware clears the requirements, since it's just running the Windows build on Mac hardware. Parallels and other virtualization tools on Apple Silicon are a much rougher path, since virtualized graphics performance is well below native and this game already leans on real-time CPU physics.

Newer integrated graphics, like recent Intel Iris Xe or AMD's Radeon 780M and 760M chips found in current laptop CPUs, can run BeamNG.drive at lower settings and resolutions, since the game is lighter on the GPU than most modern titles. Older or weaker integrated graphics will struggle, and either way, a weak CPU paired with integrated graphics is more likely to be your bottleneck than the graphics chip itself.

Chromebooks lack both the hardware and the OS support to run this locally. Cloud gaming through something like GeForce Now, running the game remotely and streaming it to your screen, is the only realistic option, assuming the service currently carries it.

Yes, there's an experimental native Linux build, with Ubuntu 22.04 LTS or SteamOS listed as recommended distributions, and it needs a Vulkan-compatible GPU and drivers. It's still labeled experimental, so some players get a smoother experience running the Windows version through Proton instead.

It's Steam Deck Playable, meaning it runs but needs some manual tweaking, not a plug-and-play experience. A known issue is that the default Proton version can fail to spawn traffic and crash in scenarios that need it, which breaks some missions. Switching to the game's native Linux build, rather than the Windows build through Proton, and using a lower graphics preset gets more consistent results.

Yes, and generally with fewer headaches than Steam Deck, since both run Windows natively rather than through Proton, so they use the standard Windows build without the traffic-spawning bug some Steam Deck players hit. Expect to keep vehicle and traffic counts modest and settings on the lower end, since these handhelds have similar power budgets to the Deck.

No. There is no mobile version of BeamNG.drive for iOS or Android. The only way to play on a phone or tablet is streaming it from a PC or a cloud gaming service to a mobile screen.

As of this writing, BeamNG.drive is not listed among the major cloud gaming catalogs. Cloud game libraries change fairly often, so it's worth checking the current app list on GeForce Now or a similar service directly rather than assuming either way.

Not yet, but it's coming. BeamNG announced a PS5 and PS5 Pro version in 2026, its first console release after more than a decade as a PC-only game, but no firm release date had been confirmed beyond 'later in the year' at the time of writing. This page covers the PC version, which remains the primary platform.

No Xbox version has been announced. The only confirmed console release so far is PS5 and PS5 Pro, expected sometime in 2026.

No. There is no PS4 version, and the only console version announced is for PS5 and PS5 Pro, not the older PlayStation 4 hardware.

No Switch version exists or has been announced. Given how CPU-intensive the physics simulation is, the original Switch's hardware would struggle regardless, and even a Switch 2 release hasn't been confirmed.

Within limits. At the official minimum of a Ryzen 5 1600 or Core i5-8400 class chip, you can expect 1080p at around 60 fps with a single vehicle on an open map. A weaker chip like a lower-end i3 or Ryzen 3 will likely run below that, and will struggle noticeably once traffic, AI opponents or a multi-car crash enter the scene, since those scale directly with CPU power rather than graphics settings.

Yes, on GPUs around an RTX 4060 and up, roughly 55 to 60 fps in light-traffic scenes at 4K. Busier scenarios with heavy traffic or a large pileup will pull that number down regardless of the GPU, since the CPU sets the ceiling once vehicle counts climb.

Yes, comfortably on anything around an RTX 3060 or better, generally 70 fps or higher with a single vehicle on an open map. As with every resolution in this game, adding traffic or crash scenarios lowers the number more than switching GPUs does.

An RTX 3060 or RX 6700 class GPU, paired with a Ryzen 7 3700X or Core i7-9700 class CPU and 32GB of RAM, the official recommended tier, holds 60 fps at Ultra in typical solo driving. Busy career-mode traffic or a big crash test can still pull that below 60 even on this hardware, since that load is on the CPU.

6GB, matching the official minimum, is the real floor and covers 1080p at moderate settings. 4GB is below what the game now expects, especially after the 0.39 graphics update added heavier lighting and reflection effects, so it's a risk at anything beyond low settings. 8GB, the recommended figure, removes VRAM as a concern at higher settings or on bigger maps.

Too many vehicles for your CPU to handle is the top cause by far, whether that's AI traffic, a crowded multiplayer server, or wreckage stacking up after a crash, since each one adds real physics work every frame. Lower the traffic density slider first, and switch on Simplified Traffic Vehicles if your scenario offers it. If what you're seeing is a flat low frame rate rather than sudden drops, turn down Dynamic Reflections and shadow distance next, the heaviest GPU-side settings since the 0.39 update.

A 6-core CPU is a reasonable baseline and handles roughly five to seven AI vehicles before the physics simulation starts falling behind real time. A 4-core CPU will run the game but hits that ceiling sooner, so expect noticeable slowdown in busy traffic or large crashes even if your GPU has plenty of headroom left.