Can You Enable or Disable All Mods at Once in Vortex?
If you manage a large mod list in Vortex, Nexus Mods' official mod manager, you've probably wondered whether there's a way to toggle everything on or off without clicking through each mod individually. The short answer is yes — but how well it works, and what you need to watch out for, depends on a few important factors.
What Vortex Actually Lets You Do
Vortex includes a bulk enable/disable feature that lets you select multiple mods and toggle their state simultaneously. Here's how it works in practice:
- Open the Mods tab in Vortex.
- Use Ctrl+A to select all mods in your list, or hold Ctrl and click to select specific ones.
- Right-click the selection to bring up the context menu.
- Choose Enable Selected or Disable Selected.
This applies the enabled/disabled state to every mod in your selection without requiring individual clicks. For large load orders — some players manage hundreds of mods — this is a significant time-saver.
There's also a checkmark column on the left side of the mod list. Clicking the header checkbox may select or deselect all entries depending on your Vortex version, though UI behavior has shifted slightly across updates.
The Difference Between "Disabled" and "Removed"
This distinction matters and trips up a lot of players. In Vortex:
- Disabling a mod means it's no longer active in-game, but it stays installed and tracked by Vortex. You can re-enable it anytime without re-downloading.
- Removing/uninstalling a mod deletes its files from the staging folder and your game directory.
When you disable all mods at once, you're essentially running the base game — useful for troubleshooting crashes, testing vanilla performance, or verifying whether a specific mod is causing a conflict.
Why You Might Want to Enable or Disable All Mods at Once 🎮
There are a few common scenarios where bulk toggling is genuinely useful:
- Conflict diagnosis — disable everything, then re-enable groups to isolate which mod is breaking something.
- Game updates — when a game patches, mods often break. Disabling all of them before launching lets you update safely.
- Profile switching — Vortex supports profiles, which let you save different mod configurations for the same game. Switching profiles effectively enables or disables entire mod sets.
- Performance testing — temporarily running without mods helps confirm whether a performance issue is mod-related or hardware/settings-related.
Profiles: The Smarter Bulk Toggle
If you regularly switch between "all mods on" and "all mods off" (or between two different mod setups), Vortex Profiles are worth understanding.
Each profile stores:
- Which mods are enabled or disabled
- Load order settings
- Plugin configuration
You can create a "vanilla" profile with everything disabled and a separate profile for your full mod list. Switching between them is a single click — cleaner and more reliable than manually selecting and deselecting mods each time.
Profiles are found under the Settings menu or the profile switcher at the top of the Vortex interface, depending on your version.
Variables That Affect How This Works for You
Not every player gets the same experience with bulk toggling. A few factors change how straightforward — or complicated — this gets:
| Variable | Why It Matters |
|---|---|
| Number of mods installed | Larger lists take longer to process and have higher conflict risk |
| Game type | Bethesda games (Skyrim, Fallout) use plugin systems that interact differently with enable/disable than, say, mod-injected games |
| LOOT integration | If you use LOOT for load ordering, disabling/re-enabling mods may prompt a re-sort |
| Mod dependencies | Some mods require others to function — disabling a master file while leaving dependent mods enabled can cause issues |
| Vortex version | UI layout and bulk selection behavior have changed across releases |
Dependency Conflicts: The Hidden Complication
One thing bulk disabling doesn't automatically handle is dependency chains. If Mod B requires Mod A as a master, and you disable Mod A while Mod B stays enabled (or vice versa), Vortex will often flag warnings — but it won't always prevent you from making the change.
Before doing a full disable, it's worth knowing whether your list contains mods with hard dependencies. Vortex's conflict panel and any active LOOT metadata can surface these relationships before you make a change you have to manually untangle. 🔍
When Bulk Toggle Doesn't Behave as Expected
A few situations where players run into friction:
- Mods deployed via hardlink or symlink may not reflect their disabled state immediately without redeployment.
- Script extender plugins (like SKSE or F4SE plugins) sometimes operate outside Vortex's tracking and won't respond to a disable action the way standard mods do.
- Sorting state — if your mod list is filtered or sorted, Ctrl+A may only select visible mods, not your full list.
After any bulk enable/disable action, it's good practice to check the deployment status in Vortex to confirm changes were actually applied to the game directory.
The Part That Depends on Your Setup
The mechanics of bulk enable/disable in Vortex are consistent — the feature exists and it works. But whether a single "disable all" operation is actually safe and reversible for your list comes down to how your mods are structured, whether you're using profiles, how Vortex is deploying files, and which game you're modding. A 20-mod Stardew Valley list behaves very differently than a 300-mod Skyrim SE build with complex dependency trees. Understanding your own setup — how many mods you're running, whether any share dependencies, and how Vortex is configured — is what turns a simple bulk toggle into a reliable tool rather than a source of new problems. 🛠️