Marvel Rivals Mod Manager: How to Install and Remove Mods

To install Marvel Rivals mods, copy the mod's files into the game's MarvelGame\Marvel\Content\Paks\~mods folder and install a signature bypass, because the game ignores mod paks without one. The Mod Manager, a tab in the free RIVALSFPS.GG app, does both for you. It reads that folder directly, so mods you installed by hand are listed the first time you open it. This guide covers where the folder is, installing mods by hand and with the app, where to get them, and turning mods off or removing them.

The folder is the source of truth. The app does not copy your mods into a library of its own or rename them to fit one, so what the list shows is what the folder holds, and a change you make in File Explorer shows up after a Refresh.

Where the Marvel Rivals mods folder is

Mods load out of MarvelGame\Marvel\Content\Paks\~mods inside your Marvel Rivals install. Only the parent install directory differs between Steam, Epic Games and Loading Bay. If there is no ~mods folder yet, create it, or press Open Mods Folder in the Mod Manager, which creates it when it is missing. The tilde is part of the name, so type the folder exactly as ~mods.

A mod in there is one of two shapes. Simpler ones are a single .pak. Others are an IoStore trio: Name.pak, Name.ucas and Name.utoc sharing one stem. All three have to keep that stem or the mod does not mount, which is why the Mod Manager groups a trio into one row reading "Mod (3 files)" with the combined size instead of listing three files you have to keep straight.

A name can also carry a suffix like _9999999_P. The trailing _P marks the file as a patch pak, which is what lets it override assets already in the game's own paks. The digits in front are not a priority you can raise: when two mods overlap, their paths inside ~mods decide which one wins, which is why moving a mod can change the result. The app prints that suffix faint beside the name rather than folding it in.

What the Marvel Rivals Mod Manager shows you

The tab sits directly under Home in the left nav rail, marked with a layered stack icon. The page header holds Open Mods Folder and Browse on Nexus Mods, which opens the Marvel Rivals mods page in your browser. The list heading holds a search box, a type filter (All types, Mods, Graphic Packs, Skin Mods, Sound Mods), Import, Profiles, a Tools dropdown and a Refresh button. Each row carries a select checkbox, the mod's name, its chunk suffix, a meta line with file count and size, then an on/off switch and a red delete button.

The two rows at the top of that screen are sound mods built on the app's Sounds tab, which since 5.2.0 can also replace the announcer's calls. The two mods replace some of the same sounds, so both wear a red Conflict badge, which is covered further down. Below your own mods sit two more blocks. Skin Mods collects the character skins the Skin Manager owns, filed as their own category rather than mixed into the list above, with its count on the heading; how those work is in Marvel Rivals skin mods. Under that is Installed Mods by RIVALSFPS.GG: what the app itself put in the folder, such as the active graphic pack and the layers you applied in Graphic Pack Settings. Those rows carry no on/off switch, because the Graphic Packs tab owns them. Each one gets a button that jumps to that tab and a Remove button that hands the deletion back to it, so nothing is ever deleted out from under the thing tracking it. The blocks are there so the folder adds up: every pak you count in Explorer has a row in one of the three.

How to install Marvel Rivals mods without the app

You can install a mod with nothing but File Explorer. The steps are the same for Steam, Epic Games and Loading Bay copies; only the folder the game is installed in differs.

How to install Marvel Rivals mods with the Mod Manager

Import handles the copy. The file picker accepts .pak, .utoc and .ucas files plus .zip, .7z and .rar archives, and takes several at once. Since 5.5.0 it also takes a .rfsound file, a sound mod someone shared. With the tab open you can also drop files or archives straight onto the window, which routes them to the same import.

Each imported mod gets its own folder under External Mods, so a trio lands together instead of three files scattered at the root. Folder structure inside an archive is preserved, and non-mod files such as readme text and screenshots are left out.

Where to get Marvel Rivals mods

Browse on Nexus Mods, at the top of the Mod Manager, opens the Marvel Rivals mods page on Nexus Mods in your browser. The same button in the Skin Manager opens the Characters category, where skin mods are listed. Download each mod from its own page, where its author describes it and lists its files, and import the archive as it arrived. A copy re-uploaded somewhere else can be an older build, or something other than what its page claims.

The app never runs anything inside a mod. Import extracts an archive to a temporary folder and copies the mod files in, and what is inside those files is down to whoever made them. Some mods change more than how the game looks, and the app flags the ones it knows about, so read Are Marvel Rivals mods bannable? before you install one.

How to turn off or remove Marvel Rivals mods

The switch on a row unloads a mod, it does not delete one. On disk an .off marker is appended to each of the mod's files, so Hela_P.pak becomes Hela_P.pak.off, and the files stay exactly where they were. The engine no longer sees a pak-family extension and skips them. Switching the mod back on strips the marker again. Nothing is ever moved, which matters because a pak's path inside ~mods is what decides its load order. The marker is appended rather than replacing the extension so a trio's three members cannot collide on one name.

To remove a mod for good, press the red delete button on its row, or check several rows and press Delete in the bulk bar. Delete asks first and names what it is about to remove. By hand, close the game and delete the mod's files from ~mods, all three of a trio.

Two items in the Tools menu work on everything at once.

• Disable All Mods turns every mod off, plus your skins and the app's own graphic packs, so the game runs stock. It leaves the Signature Bypass installed and goes one way only: there is no Enable All Mods beside it, because which mods were on is a set of choices you made one at a time. To put mods back, check the rows you want, or the select-all box on the list heading, and press Enable in the bulk bar.
• Disable Bypass removes the signature bypass and nothing else. Every mod stays on disk and stops loading until you install the bypass again, so you can switch modding off without touching a single mod.

Checking any row swaps the toolbar for a bulk bar with Enable, Disable and Delete plus a selection count. The select-all checkbox on the heading is scoped to the filtered rows, so typing "hela" in the search box and hitting select-all picks only the Hela mods. The same bulk bar is how you find a mod that breaks the game, by switching half off at a time, and Marvel Rivals mods not working walks through that and the other checks in order.

To switch between whole sets of mods, use Profiles, next to Import. Save current as… saves which mods are on as a named profile, and clicking a profile later turns its mods on and your other mods off. Nothing is deleted when you switch. Skin mods and sound mods are part of a profile; the app's own graphic packs are not. Marvel Rivals mod profiles covers updating, renaming and deleting them.

Conflict detection and how it works

Two enabled mods conflict when they both contain the same game asset. The engine loads one copy, so one mod silently overrides the other. That is how a mod that works on its own can stop working once you install a second one.

After the list paints, the app reads each enabled mod's asset index and compares them. For a .pak-only mod it parses the pak's own index. For a trio it reads the .utoc directory index, because with IoStore the .pak is a near-empty shell and the real file list lives in the table of contents. Indexes only: no payload is decompressed, results are cached per file, and the scan runs after the rows are on screen so it never holds up the list.

Paths are normalized first, because Unreal mounts every project's Content folder onto the same /Game root. Two mods cooked under different project names still fight over the same runtime asset, so Marvel/Content/Characters/X and SomeSeason/Content/Characters/X compare as one key.

You get a red banner naming how many mods conflict and how many assets are involved, with a View details button that opens a paged list of the exact assets. Conflicting rows get a red Conflict badge whose tooltip names the other mods. The scan is skipped below two enabled mods, and it can be switched off under the Mod Manager section on the App tab in Settings.

Add-ons are the exception. A mod made to change part of another mod, such as tattoos or a hair color for a skin, overlaps its base on purpose, so the app does not count it as a conflict. It gets an Add-on badge instead, which says to keep both on. If the base loads first and covers the add-on's changes, the badge reads Add-on hidden and a Load first button sits beside it. Pressing it puts a ! in front of the add-on's folder name so it loads ahead of the base. The skin add-ons guide covers it in more detail.

Resolution is yours. The app never reorders, renames or deletes anything on its own to fix a conflict, because a pak's position in load order is half of why two of them collide. You disable one of the two or delete it, and the banner clears on the next scan.

The other badges on a row

A mod whose index cannot be read, from an unrecognized pak version or a damaged file, gets a Not scanned badge and sits out the conflict check; one bad file must never fail the whole scan. A stale disabled copy beside a live one gets a gold Duplicate badge, left behind when an import kept both. Its toggle is blocked until you resolve it and a "Remove stale copy" link appears on the row. Nothing is deleted for you.

Three red badges say a mod cannot load as it is. Outdated means the mod is still packaged the way it was before the September 3, 2026 game update, and the gold Fix button beside it runs the same repair as the Tools menu, for that mod only. Broken means the mod's .pak is missing, so only its data files are there and there is nothing for the game to mount. Damaged means the mod's own files do not match each other. Neither of those two has a fix in the app: the answer is a fresh download.

Two more badges come from the game itself. After you launch, each mod that was on says Loaded or Not loaded, based on what Marvel Rivals reports, and a note beside Import sums it up, such as "Last launch: 7 of 8 mods loaded." A switched-off mod shows neither. When the game crashes and the app can name the one mod it was loading, that mod gets a red Crashed badge, which stays if you turn it off. Both are covered in Marvel Rivals crashing with mods.

Separately, the app scans the whole Paks tree against a compiled-in registry. Mods the app knows can get accounts temporarily banned carry a Flagged badge with the reason and a support code. A flagged pak with no row, such as one dropped straight into Paks\ rather than ~mods, gets a red banner with a Remove button, since such a pak mounts just the same. Nothing is removed until you press Remove. If a .pak in your mods folder carries its own game config, the app shows it with a Config badge and the reason "Contains its own game config", and asks you to remove it before it launches the game (Remove config pak and launch). The app's own warning says Marvel Rivals shows its in-game modification warning while such a pak is installed, and that it can override the settings RIVALSFPS.GG applied. Whether mods are worth the risk at all is covered in Are Marvel Rivals mods bannable?.

The Tools menu, item by item

Disable All Mods and Disable Bypass are covered above, under turning mods off. The other three items:

Nothing loads without the signature bypass

Marvel Rivals checks pak signatures and ignores an unsigned one. That applies to every mod in the folder however it got there, so a fresh install with ten mods and no bypass looks exactly like a game with no mods at all. The tab shows a gold banner saying so, with an Install Bypass button. The bypass ships inside the app, so there is nothing to download. It is DeathChaos's work (Nexus Mods mod 2940), redistributed with the author's permission, and it installs into the game's Binaries\Win64 folder. That folder usually sits under Program Files, so Windows usually shows a permission (UAC) prompt when you press the button. The full story, including the three files it writes, is in what the Signature Bypass is.

The same gate covers graphic packs, skins and sound mods, which is why it is one shared install rather than something each tab does for itself.

What it will not do

Nothing here happens on its own. The app's automatic cleanup, the pass that runs just before it updates itself, still only ever touches files it installed, and this tab adds no exception to it: deleting a mod the app did not install is always a button you pressed. Managing someone else's mod means listing it and giving you the controls, not taking ownership of it. The app does not reorder load order, does not rename files behind your back, and does not remove a duplicate or a conflicting mod until you click the button. Organize Mods, Load first and Update my mods all move or rewrite files, and each of them runs only when you press it.

Two empty states cover the rest. "No mods installed" prompts you to import or drop one, and "Marvel Rivals not located" points you at Settings. The app is free, Windows only, supports Steam, Epic Games and Loading Bay, and updates itself at launch. If you came for frame rate rather than mods, read how to increase FPS in Marvel Rivals instead.

Common questions