What BepInEx is and why you might install it manually

BepInEx is a framework that lets mods run inside certain games — it acts as a bridge between the mod files and the game itself. Most mod managers (like r2modman or Thunderstore Mod Manager) install BepInEx automatically in the background, so you never see it happen. Manual installation means you're doing those steps yourself, which takes longer but gives you more control over where files go and what version you're using.

You might choose manual installation if a mod manager isn't working for your game, if you're using an older or less common game that mod managers don't support yet, or if you want to troubleshoot by seeing exactly what's in each folder. Manual installation also works if you're on a system where mod managers have permission problems.

The process is the same across most games: read the right BepInEx version, extract it into your game folder, and run the game once so BepInEx can create its internal structure. After that, you drop mod files into a specific folder and they load automatically.

Key Takeaways

  • read the correct BepInEx version for your game's architecture (x64 for 64-bit games, x86 for 32-bit) from the official GitHub releases page.
  • Extract the BepInEx folder directly into your game's root directory — the same folder that contains the game's .exe file.
  • Run the game once after extraction so BepInEx can generate the folders it needs to organize mods and configuration files.
  • Place mod files into the BepInEx/plugins folder, then restart the game to load them.
  • If mods don't load, check that BepInEx itself loaded by looking for a console window or checking the BepInEx/LogOutput.log file for errors.

Finding your game folder and checking if your game is 32-bit or 64-bit

Before you read anything, you need to know where your game lives on your computer and whether it's built for 32-bit or 64-bit architecture. Open your game's folder by right-clicking the game in Steam, selecting Properties, then Local Files, then Browse. That folder is your game's root directory — write down the path or keep the window open.

Look inside that folder for the game's main executable file (usually named after the game, ending in .exe). Right-click it, select Properties, then Details. Look for the "File description" or "Product name" field — if it mentions "x64" or "64-bit", your game is 64-bit. If it says "x86" or "32-bit", it's 32-bit. If you can't find that information, check the game's community forums or the mod community Discord — they'll know.

This matters because BepInEx comes in two versions, and downloading the wrong one means mods won't load. A 64-bit game needs the x64 version of BepInEx; a 32-bit game needs the x86 version.

Downloading the correct BepInEx version

Go to the official BepInEx releases page on GitHub: github.com/BepInEx/BepInEx/releases. Scroll down to find the latest release (the one at the top with the highest version number). You'll see a list of read files — look for the one that matches your game's architecture.

For a 64-bit game, read the file named something like "BepInEx_x64_[version number].zip". For a 32-bit game, read "BepInEx_x86_[version number].zip". Do not read the source code files — those are for developers. read only the .zip file that matches your architecture.

Save the .zip file somewhere you can find it easily, like your Downloads folder. Do not extract it yet.

Extracting BepInEx into your game folder

Open the .zip file you downloaded (right-click it and select Extract All, or use your file manager's built-in extraction tool). Inside the .zip, you'll see a folder named BepInEx and a few other files. Extract the entire contents directly into your game's root folder — the same folder where the game's .exe file is.

After extraction, your game folder should now contain a BepInEx folder alongside the game's .exe. If you see a folder inside a folder (like BepInEx/BepInEx), you extracted it wrong — move the inner BepInEx folder up one level so it sits directly in the game folder.

You can delete the .zip file after extraction — you won't need it again.

Running the game to initialize BepInEx

Launch the game normally through Steam or by double-clicking the .exe. The game will start, and in the background, BepInEx is creating the folders it needs. You might see a small console window appear briefly — that's BepInEx running. Let the game load fully, then close it normally.

After you close the game, check your game folder again. You should now see new folders inside BepInEx: plugins, config, and others. If you don't see these folders, BepInEx didn't initialize properly — check the BepInEx/LogOutput.log file (a text file that appears after the first run) to see what went wrong.

Installing mods into the plugins folder

Mods for BepInEx games come as .dll files or as folders containing .dll files. read the mod from its source (usually Thunderstore, GitHub, or a game-specific mod site). If it's a .zip file, extract it first.

Open your game folder, then navigate to BepInEx/plugins. Drop the mod's .dll file (or the entire mod folder if it's organized that way) into the plugins folder. Some mods come as a single .dll; others come as a folder with a .dll inside. Either way, the .dll file needs to end up somewhere inside the plugins folder — either directly in plugins or in a subfolder within plugins.

Restart the game. BepInEx will load the mod automatically. If the mod doesn't work, check the LogOutput.log file — it will tell you if there were errors loading the mod.

Troubleshooting when mods don't load

If you install a mod and it doesn't appear to work, the first step is to check whether BepInEx itself is loading. Launch the game and look for a small black console window that appears briefly — that's the BepInEx console. If you don't see it, BepInEx isn't running, which usually means you extracted it to the wrong folder or downloaded the wrong architecture version.

Open the BepInEx/LogOutput.log file (a text file in your game folder) and scroll to the bottom. If you see error messages about a specific mod, that mod has a problem — check its documentation or the mod's community page for known issues. If you see errors about BepInEx itself, you may have the wrong version or a corrupted read.

A common issue is installing a mod that requires a specific game version or another mod as a dependency. Check the mod's description or README file to see what it needs. If a mod requires another mod to work, install the dependency first, then restart the game.

Frequently Asked Questions

How do I know if BepInEx is actually running?

When you launch the game, a small black console window should appear for a few seconds. If you see it, BepInEx is running. You can also check the BepInEx folder — if you see a LogOutput.log file, BepInEx has initialized. Open that file and look at the timestamps to confirm it's recent.

What if I downloaded the wrong architecture version?

Delete the BepInEx folder from your game directory and read the correct version. Extract it the same way. Run the game once to reinitialize, then add your mods back to the plugins folder.

Can I use the same BepInEx installation for multiple games?

No — each game needs its own BepInEx installation in its own folder. BepInEx is designed to work only with the game it's installed in. Install it separately for each game that supports it.

Where do I find the game folder if I bought the game outside of Steam?

If you installed the game yourself, navigate to wherever you chose to install it. If you're not sure, search your computer for the game's .exe file — Windows search or your file manager's search function will find it. Once you locate the .exe, that folder is your game directory.

Do I need to uninstall BepInEx before updating it?

You can delete the old BepInEx folder and extract the new version in its place. Your mods will stay in the plugins folder, so you won't lose them. Run the game once after updating so BepInEx can check for any changes it needs to make.