BeamNG.drive Mods Not Showing Up: 6 Quick Fixes
If a mod is sitting in your mods folder (or even shows up in Mod Manager) but is missing from the vehicle or map selector, one of these six things is almost always the cause.
1. Wrong User Folder After an Update
BeamNG.drive 0.40 moved the active user folder to AppData\Local\BeamNG\BeamNG.drive\current\mods. If you dropped the .zip into an old 0.3x folder, the game will ignore it. Always open the folder via Launcher → Manage User Folder → Open in Explorer.
2. Zip Inside a Zip (or Extracted Folder)
Open the .zip file to inspect its root. A valid car mod has a vehicles/ folder at the top level; a map mod has a levels/ folder. If there is an extra wrapper folder or another .zip inside, BeamNG cannot read it.
3. Mod Is Disabled or Needs a Rescan
- Open the in-game Repository → Mods Manager.
- Make sure the mod is toggled Active (not deactivated after a game update).
- Click the Activate All button if you recently updated BeamNG.drive — major patches automatically deactivate older mods.
4. It Is a Config or Part Mod, Not a Standalone Car
Many mods add new engines, wheels, or tuning configs to an existing vehicle (such as the Gavril D-Series or Ibishu 200BX) rather than creating a new car icon. Check inside the donor car's Configurations list.
5. Clear Cache & Check for Conflicts
Stale cache files can hide new vehicles and maps. Open the BeamNG Launcher → Support Tools → Clear Cache (Standard or Deep Clean) and relaunch.
6. Safe Mode Test
If none of your mods appear or the vehicle menu is blank, launch Support Tools → Safe Mode. If vanilla cars return, one broken or outdated mod is crashing the UI — disable half your mods at a time to isolate it.
Quick answers
BeamNG automatically disables third-party mods after major updates to prevent crashes. Open Mods Manager and re-enable them, or move them from the previous version folder into current\mods.