How to Install Oblivion Remastered Mods: Manual Installation, Vortex and OBSE

Can You Actually Install Mods in Oblivion Remastered?

Remastered runs on an odd hybrid system: the original Gamebryo engine handles the underlying logic, while Unreal Engine 5 handles the visuals. This means many old Oblivion mods still work, because the game’s core systems have not changed. Essentially, you are modding a 2006 game with prettier lighting.

Many old Oblivion mods still work because the game’s core systems have not changed

Without an official Creation Kit, you cannot just click “download with mod manager” and forget about it for every mod.

Some mods need script extenders. Others are fussy about load order. But if you have modded any Bethesda game before, this should not feel too unfamiliar.

Where Is Oblivion Remastered’s Data Folder?

Before installing anything, you need to know where your game files actually live. That depends on whether you use Steam or Game Pass.

For Steam users, the Data folder is here: C:\Program Files\Steam\steamapps\common\Oblivion Remastered\OblivionRemastered\Content\Dev\ObvData\Data\

For Game Pass, the path is: C:\XboxGames\The Elder Scrolls IV – Oblivion Remastered\Content\OblivionRemastered\Content\Dev\ObvData\Data\

Inside that Data folder, you will find plugins.txt. This little text file is effectively the brain of your mod collection. Every ESP mod you install needs to be listed here, or the game will not load it. Bookmark this location: you will be coming back often.

If you are installing PAK mods, asset packages usually containing textures or meshes, those go somewhere else: \Content\Paks\~mods\

You may need to create the ~mods folder yourself.

Which Mod Manager Should You Use for Oblivion Remastered?

There are three main options, and they all work. Choose according to how much control you want and how much effort you feel like putting in.

Vortex is the choice for most people. Nexus Mods makes it, so it integrates directly with the website: one-click downloads, automatic load order sorting with built-in LOOT and file deployment handled for you. If you have never modded before, start here. I still use it for quick collections because I do not want to babysit every file.

For this guide, I will focus on Vortex because it is the easiest starting point and covers 90% of what you will need.

Mod Organizer 2 (MO2), available through its official Discord server, is for people who want complete control. It keeps mods in isolated folders instead of dumping everything into the game directory, making troubleshooting much easier when something breaks. The learning curve is steeper, though.

ORMM, a tool by jorkXL, is built specifically for Oblivion Remastered. It is newer and rougher around the edges, but its separate tabs for ESP, PAK and UE4SS mods are quite handy. It is still in beta, so expect bugs.

For this guide, I will focus on Vortex because it is the easiest starting point and covers 90% of what you will need.

Installing Oblivion Remastered Mods with Vortex, Step by Step

Here is how to set up Vortex without making a mess.

1. Download and install Vortex
Visit Nexus Mods and download the installer. Run it and sign in to your Nexus account when prompted. The application should detect Oblivion Remastered automatically if it is already installed. Otherwise, point it to your game folder manually.

2. Install the Oblivion Remastered extension
Vortex needs its game extension to handle Remastered correctly. Accept the automatic installation prompt if shown. Otherwise, open Extensions, find the Oblivion Remastered extension and install or enable it, then manage the game.

3. Configure the settings
Open Settings > Mods. Enable Hardlink Deployment for cleaner file management. Disable “Install on Download” so you can review mods before activating them.

4. Download a mod
Visit my mod collections page, browse categories in my guide to building your own collection or search Nexus. Find a mod and click Mod Manager Download. Vortex will pick up the download and add it to your list. You will see it on the Mods tab, but it will not be enabled yet.

5. Enable and deploy
Click the mod in Vortex, choose Enable, then click Deploy Mods at the top. This writes the files to the game directory and updates plugins.txt automatically. Done.

6. Sort and review the load order
Use the game extension’s LOOT sorting option, then review its messages and the mod authors’ instructions. LOOT supports Oblivion Remastered, but sorting does not resolve every conflicting record. Use the game’s Load Order controls and supported rules to make any necessary adjustments.

7. Launch the game through Vortex
Do not launch through Steam or a desktop shortcut. Use the launch button in Vortex. This ensures everything loads correctly, especially if you have OBSE installed, which we will cover next.

That is it. Seriously. Most mods install just as smoothly.

How to Install OBSE: Oblivion Script Extender

OBSE64 is required by mods that use its extended scripting functions. Check each mod’s requirements rather than assuming a percentage of all mods needs it. It enables scripting features beyond the base game, including those used by advanced gameplay and interface mods.

Here is how to install it:

1. Download OBSE64
Visit Nexus and download it manually, rather than through Vortex, to be on the safe side. You will get a ZIP archive.

2. Extract the files
Open the OBSE64 archive with 7-Zip or WinRAR. Use the DLL and EXE files from the Remastered OBSE64 package, not the older Oblivion OBSE files. The src folder contains source code and is not needed to play.

3. Copy them to the game folder
Copy the package’s DLL and EXE files into: \Oblivion Remastered\OblivionRemastered\Binaries\Win64\

This is the same folder that contains the main game executable.

4. Launch through OBSE
Instead of launching Oblivion Remastered.exe, run obse64_loader.exe. It loads the script extender first, then launches the game. If you use Vortex, configure its settings to launch through OBSE.

5. Check that it works
Launch through obse64_loader.exe, then inspect the OBSE logs under Documents\My Games\Oblivion Remastered\OBSE\Logs. A successful loader start and log output are the useful first checks; read any reported version or path errors before troubleshooting dependent mods.

How to Install Mods Manually When Vortex Is Not Enough

Some mods do not get along with mod managers. Perhaps the author packaged the mod strangely, perhaps it uses a PAK instead of an ESP, or perhaps you simply prefer doing everything yourself. Here is how manual installation works.

For ESP mods:

1. Download and extract
Download the mod archive and extract it. Look inside for .esp or .esm files.

2. Copy to the Data folder
Move those ESP/ESM files into: \OblivionRemastered\Content\Dev\ObvData\Data\

3. Edit plugins.txt
Open plugins.txt, located in the same Data folder, with Notepad or Notepad++. Add the mod’s filename at the bottom, one filename per line, including the .esp extension. Save and close.

Your plugins.txt should look something like this after adding mods:

For PAK mods containing assets such as textures or meshes:

1. Extract into the mods folder
PAK files go here: \Content\Paks\~mods\

If that folder does not exist, create it yourself.

2. Check the filename
Keep the mod author’s filenames and folder layout. The _P suffix is commonly used for patch priority, but it is not a universal requirement for every PAK. Rename a file only when that mod’s installation instructions explicitly tell you to do so.

3. Launch and test
Test the mod after installation. PAK priority can depend on mount and patch ordering as well as filenames, so use the author’s conflict and load order instructions rather than assuming alphabetical renaming is always sufficient.

That is it. Manual installation gives you complete control, but also makes you responsible for troubleshooting when something breaks.

Setting Up xEdit for Oblivion Remastered

xEdit, launched as TES4REdit for Remastered, helps inspect plugin records, identify conflicts and review edits. It is not required for a basic setup, but becomes useful as your list grows. Use a build that explicitly supports Oblivion Remastered; a classic TES4Edit build is not interchangeable.

Here is how to set it up:

1. Download xEdit
Get a build with explicit Oblivion Remastered support through the official xEdit development channels. Check its release notes and setup instructions rather than relying on an old version number.

2. Extract and rename
Place the xEdit executable in the game directory, specifically inside: SteamApps\common\Oblivion Remastered\OblivionRemastered\Content\Dev\ObvData

This is the ObvData parent directory; the ESP files themselves are in its Data subfolder. Use Remastered mode: rename xEdit.exe to TES4REdit.exe when required by your build’s instructions, so it loads Oblivion Remastered rather than classic Oblivion.

This is critical: rename xEdit.exe to TES4REdit.exe.

3. Run it
Launch TES4REdit.exe in Remastered mode and select the plugins to inspect. Use “Check for Errors” to investigate invalid records and the conflict filters to compare overlapping edits. Do not automatically clean every reported difference: follow the author’s or xEdit documentation’s instructions.

xEdit is mainly for advanced users, but even using it just to check for conflicts can save you a lot of frustration later.

Why Are My Oblivion Remastered Mods Not Working?

You installed everything, launched the game and… nothing. The mod is missing. Or the game crashes. Or textures have disappeared. Here is how to fix the most common problems.

Mods do not load at all:

Check plugins.txt. Open it in Notepad and make sure your mod is listed. If it is not, the game will not load it. Also make sure the ESP is actually in the Data folder. Downloads sometimes fail, or you accidentally put a file in the wrong place.

Save a backup after editing. Use Read-only only as a deliberate manual-installation workaround, and clear it before asking Vortex to update the plugin list. Do not assume Windows itself is the cause of every overwritten change.

The game crashes on launch:

Check the load order, missing requirements and supported game versions. Use LOOT where appropriate, then review its warnings. Disable recently added mods individually to isolate the problem, and verify core game files through Steam if corruption is suspected.

Make sure you launch through obse64_loader.exe

If you use OBSE, make sure you launch through obse64_loader.exe rather than the regular game executable. Some mods simply will not work unless OBSE is active.

Textures are missing or look strange:

PAK mods normally belong in \OblivionRemastered\Content\Paks\~mods\. Check the mod’s own installation path and keep its supplied filenames; do not add _P indiscriminately.

Item names contain [NL]:

This is a known bug with some mods. Download the NL-Remover mod from Nexus or use xEdit to clean the affected records manually.

Mods conflict with each other:

Open the affected plugins in xEdit and use the conflict filters to compare overlapping records. Decide which changes should win, or build a compatibility patch if you need parts of both. Consult Wrye Bash documentation for supported patching workflows; a Bashed Patch is not a universal fix for every script, mesh or Unreal asset conflict.

Performance drops after installing mods:

Some texture mods use absurdly high resolutions and eat your VRAM. Check GPU usage in Task Manager while playing. If it is maxed out, disable texture packs or lower their resolution. Also download Ultimate Engine Tweaks from Nexus: it helps smooth out frame drops.

Most problems come down to file paths, load order or missing dependencies. Double-check the basics before assuming the mod itself is broken.

Load Order Conflicts and How to Fix Them

Load order determines which mod “wins” when two mods edit the same thing. If Mod A changes iron sword damage and Mod B also changes iron sword damage, the one that loads last overwrites the other.

LOOT can help sort supported plugins, but does not merge conflicting edits. Use Vortex’s game-specific sorting controls, review warnings and follow the mod authors’ requirements. Deploying files alone does not guarantee a compatible load order.

General rules:

• Keep the game’s official plugins in their intended order. Remastered does not enforce the classic rule that every ESM must load before every ESP; dependencies and author instructions matter more than a blanket filename-extension rule.
• Place overhauls according to their requirements and compatibility patches. For a project such as Oscuro’s Oblivion Overhaul, use the Remastered-specific release and its instructions rather than dropping an original-game package into this installation.
• Patches load last. A compatibility patch for two mods must load after both of them.

If you have conflicts:

1. Open xEdit
   Load your entire mod list. xEdit highlights conflicts in red or orange.
2. Identify the problem
   Click the conflicting record. You will see which mods edit it and what changes they make.
3. Choose a winner
   Decide which mod’s changes you want to keep. Move that mod lower in the load order so it loads last. In Vortex, you can drag plugins on the Plugins tab.
4. Create a patch, optionally
   If you want changes from both mods, you need a merged patch. This is advanced territory: look for Wrye Bash tutorials if you want to tackle it. I rarely bother unless I am running a huge mod list.

For PAK mods, use each author’s priority and conflict instructions. Filenames and patch suffixes can affect mounting, but renaming two archives alphabetically is not a reliable general solution to every conflict.

Use LOOT as a starting point, then check warnings, dependencies and the instructions for the particular mods you are combining.

All the Tools You Need to Mod Oblivion

Here is a quick breakdown of what each tool does and when you need it.

• OBSE64: required for most heavily scripted mods. If a mod description mentions OBSE, you need it. Download it from Nexus, copy the DLL and EXE files into Binaries\Win64 and launch through obse64_loader.exe.
• UE4SS: a scripting framework used by mods on the Unreal Engine side. Install the Remastered-specific package required by the mod and check its Steam or Game Pass support; support depends on the loader package and mod, not simply on whether it uses UE4SS.
• xEdit (TES4REdit): detects conflicts and cleans dirty edits. Not essential for basic modding, but very useful when running 30+ mods. Rename the executable to TES4REdit.exe before launching it.
• LOOT: a load order sorter. Already built into Vortex, so you do not need to download it separately unless you use MO2 or install manually.

Start with Vortex and OBSE64. Add the other tools as needed.

Now You Are Ready to Mod Oblivion Remastered

Modding Oblivion Remastered is not the nightmare some people make it out to be. Vortex handles most of the heavy lifting, OBSE opens up the interesting stuff, and manual installation covers unusual cases. Once you understand the basics, building a load order becomes trial and error: enable mods, test, fix conflicts and repeat.

My advice is to start small. Install five or ten mods, make sure they work, and only then go wild. Do not dump 100 mods in at once and wonder why the game will not launch. I have done that, and it sucks. Back up plugins.txt and your saves. And when something inevitably breaks, check the comments on the mod’s Nexus page first: someone has probably found a solution already.

Questions About Modding Oblivion