How to Install Mods in BeamNG.drive

Mods are what keep BeamNG.drive interesting once you’ve driven everything the base game has to offer. Extra cars, maps, and odd experiments the developers never planned for are out there, and most take only a couple of minutes to install. The trouble starts when a zip lands in the wrong folder. Then your vehicle list stays empty and you’re left guessing.

This guide covers the whole process, from finding mods to fixing the ones that misbehave. You’ll learn the quick method using the Subscribe button, the manual method for files you download yourself, and how to check that a mod fits your version of the game. At the end, there’s a troubleshooting section for the three problems that come up most often.

Start with the Official Repository and the official forum. Those are the two places BeamNG itself points people to, and they’re the safest option for a first mod. You can find mods on other websites too, and some are great, but you’re relying on the site and the author to keep things working. For example, VGTimes has a Volvo XC90 mod with 18 configurations and the Car Jump Arena map for jumps and crash tests. Both are listed for BeamNG.drive 0.39.x.

One thing to know up front: BeamNG itself doesn’t provide official support for mods. If one breaks, you’re mostly solving it yourself. The troubleshooting section at the end covers the problems you’re most likely to run into.

When a mod is on the official repository, this is the way to go. The site and the game do the work, and you never have to touch a folder.

Head to the web repository. If it wants you to sign in, take care of that first. Then open the page for the mod you’re after and hit Subscribe. This opens BeamNG.drive, subscribes to the mod, and downloads it automatically. Once the download finishes, the mod is activated and ready to use. If you choose Download Now instead, you'll get a ZIP file that you need to install manually.

Open the Repository from the Main Menu or the sidebar menu, search for the mod, and click Subscribe on its page. Check the date on the mod before you click. Old mods are the main source of problems, and the date tells you a lot.

Not every mod lives on the repository. Plenty sit on forums or third-party sites, and those arrive as a zip you place yourself. It’s easy once you know where it goes.

Don’t extract it for a normal manual installation. BeamNG reads mods straight from ZIP archives, so there’s no need to unpack them. The game also supports unpacked mods, but those require a different folder structure. If you just want to install a downloaded car or map, leave the ZIP intact and move it to the correct mods folder.

Start the launcher first and leave the game closed. Press Manage User Folder, then choose Open in Explorer. This opens the active user folder, where BeamNG stores your mods, settings, and other personal files.

On a standard Windows installation, the current user folder is usually located at %LOCALAPPDATA%\BeamNG\BeamNG.drive\current. If you've chosen a custom location, use the launcher rather than guessing the path. Look for the mods folder inside the active user directory, not in an old backup from a previous game version.

Look inside your active user folder for a folder called mods. If it’s missing, right-click an empty space, create a new folder, and name it mods. Then:

Launch the game and look for the mod in the vehicle or level list.

You’ll often see a folder called repo inside mods. The game uses it for mods you subscribed to through the repository. Keep your manual downloads in the main mods folder instead, and don’t shuffle files around inside the repo.

Different kinds of mods show up in different places. Level mods appear in the level selector. Vehicle mods, including configuration mods, appear in the vehicle selector. Scenario mods are in the scenario menu, and vehicle part mods show up in the vehicle configuration menu. Check that you’re looking in the right menu. A car won’t show up in the level list, and a map won’t show up in the vehicle list.

Open the Mod Manager and everything you’ve installed is listed there. You can disable and re-enable individual mods, and subscribed repository mods can receive automatic updates. Mods installed manually from ZIP files generally need to be updated by downloading and replacing the archive yourself. The manager also comes in handy when something goes wrong. Disable the mod you suspect, launch a quick test, and see whether the issue disappears. Your other mods stay as they were, and nothing needs reinstalling.

Many problems people blame on installation are really version problems. A mod built for an old version might bring physics glitches, broken menus, or crashes. BeamNG gets big updates on a regular basis, with numbers like 0.38 and 0.39, and a mod that worked in one version can fall apart in the next. Checking takes about a minute.

Look for the game's version number in the main menu, usually near one of the corners of the screen. Don't rely on the name of your user folder, since the current directory doesn't always have the game version in its name.

Open the mod’s page on the repository and check its description, update history, and recent comments. The version history shows when the mod was updated, but it doesn't always tell you which game version it supports. Picture a mod that hasn't been touched since BeamNG.drive 0.31. On 0.39 or later, it might still work, but it's a gamble.

A recent update that matches your version is a good sign. An old one isn’t a guarantee of failure, but you’re taking a risk, and a newer mod may do the same job.

Even careful installs go wrong now and then. The three problems below cover most cases, and each one has a fix that takes only minutes.

Two causes are most likely. The first is the file path. Check where the zip sits. If you buried it in a subfolder, the game may never find it. Pull it back up into the main mods folder and look again.

The other cause is what’s inside the ZIP. Open it without extracting. A vehicle mod should normally have a vehicles folder at the top, while a map should have levels. Other mod types may use folders such as lua, ui, or art. If everything is buried inside another folder named after the mod, the archive may be packed incorrectly.

You can try repacking the ZIP with the correct folders at its root, but it's usually better to look for an updated download or ask the mod's author to fix it.

You spawn a car and it shows missing textures, orange text, or no wheels. That usually points to a mod that’s out of date. The game’s physics or materials have changed, and the mod’s JBeam data hasn’t caught up.

First, switch the mod off in the Mod Manager or take its zip out of the mods folder. Close the game, open the launcher, and go to Support Tools, where you’ll find Clear Cache. It doesn’t delete anything outright. Certain files are shifted into a backup folder inside your user folder, and the game ignores them from then on. Your own files stay put. Expect a slower launch afterward.

You spawn a mod and the game drops you to the desktop with a Fatal Error. That’s the worst of the three, and the usual culprit is one broken mod. The game won’t stay open long enough for you to fix anything from inside it, so you work from outside.

Start with Safe Mode to find out where the problem lives. Close the game and open the launcher. Under Support Tools, choose Safe Mode. The game starts with a temporary empty user folder, so your mods and settings sit out that session. Nothing you change there is saved, which means you can’t uninstall a mod from inside it. Treat Safe Mode as a test.

If the game runs fine in Safe Mode, something in your user folder is to blame, and a mod is the likeliest suspect. Here’s how to track it down. Close the game, open your active user folder from the launcher, and make a backup of it. Then rename the active folder from its parent directory, for example from current to current_backup on a standard installation.

Launch the game and see whether it creates a fresh user folder and runs without crashing. If it does, start moving your mods back from the backup, a handful at a time, and test after each handful. Once the crash comes back, the last handful holds the problem. Cut it in half, move one half back, and test again. Repeat until a single mod remains.

Go slowly with the batches. Move too many at once, and you can’t tell which one caused the problem. If the game still crashes in Safe Mode, the problem probably isn’t a mod. Look at your graphics drivers and check that your computer meets the game’s minimum requirements.

Take a minute before each install. Check the mod’s date and the game version it was built for. Add one mod at a time, then start the game and test it before you add the next. If something breaks, you’ll know which mod did it. When a problem does show up, go for the cheap fixes before the heavy ones.