What Does Purge Mods Do in Vortex — And Why You Should Care
You've been modding a game for months. Then one day your game starts crashing, or loading times crawl to a halt, and you have no idea why. Because of that, here's the thing — most people don't realize that Vortex has a built-in tool designed to clean up exactly this kind of mess. Sound familiar? Which means you've installed dozens of mods, tested a few, and left the rest sitting in your mod directory like digital clutter in an attic. It's called Purge Mods, and it might be the single most underrated feature in the entire mod manager It's one of those things that adds up..
So what does purge mods do in Vortex, exactly? And more importantly, should you be using it? Let's break it all down.
What Is Purge Mods in Vortex
At its core, the purge mods feature in Vortex is a cleanup tool. It scans your mod directory and identifies any mod files that are no longer needed — either because the mod has been uninstalled, because it's been replaced by a newer version, or because it simply doesn't match anything currently active in your mod list.
Think of it like spring cleaning for your mod folder. Vortex tracks what it knows about, but the actual files on your hard drive don't always get removed when you think they do. Plus, each time you do that, leftover files can pile up. Over time, modders install, test, remove, and replace mods constantly. That's where purge comes in.
How Purge Differs from a Standard Uninstall
When you uninstall a mod through Vortex's regular interface, the mod manager removes the mod from its internal database and usually deletes the associated files. But that's not always perfect. Sometimes files get left behind — especially if the mod was installed manually first, or if the uninstall process was interrupted That's the part that actually makes a difference..
Purge mods goes a step further. Instead of relying on what Vortex thinks should be there, it actually checks the files on disk against what's currently in your active mod list. Anything that doesn't match gets flagged and removed. It's a more thorough sweep.
What Gets Removed
Here's a quick breakdown of what purge mods typically targets:
- Mod files from mods you've already uninstalled but left behind on disk
- Outdated versions of mods that have since been replaced
- Duplicate files from mods that overlap or conflict
- Stale archives and loose files that no longer correspond to any active mod
It does not touch your save files, game configurations, or anything in the game's data folder unless those files are directly tied to a mod that's being purged. That's an important distinction, and we'll come back to it That's the part that actually makes a difference..
Why Purge Mods Matters More Than You Think
You might be wondering why this even matters. Can't you just leave old mod files sitting there? Technically, yes. But in practice, leftover mod files cause real problems — and most people don't connect the dots until something breaks.
Performance and Load Order Issues
Every file in your mod directory is something the mod manager has to process. Even inactive or orphaned files can slow down Vortex's load times and make the mod list harder to figure out. More critically, some of those leftover files can interfere with your current mod load order in subtle ways. A stale file from an old mod might conflict with a new mod you just installed, and tracking down that conflict can be incredibly frustrating And that's really what it comes down to..
Not obvious, but once you see it — you'll see it everywhere.
Disk Space
This one's simple but often overlooked. Mod files — especially for games like Skyrim, Fallout, or Starfield — can be enormous. That said, a single large mod can be several gigabytes. Multiply that by dozens of mods you've installed and removed over the years, and you could be wasting significant storage space on files you don't even know are there Worth keeping that in mind..
And yeah — that's actually more nuanced than it sounds.
Cleaner Backups and Syncs
If you use Vortex's backup or sync features — say, to move your mod setup between PCs or back it up to cloud storage — purging old files first means your backups stay lean and relevant. Backing up junk just wastes time and storage.
You'll probably want to bookmark this section.
How to Use Purge Mods in Vortex
Using the purge feature is straightforward, but there are some nuances worth knowing so you don't accidentally remove something you need That alone is useful..
Step-by-Step Guide
First, open Vortex and make sure you're on the Mods page. This is where your mod list lives, and it's where the purge tool does its work Nothing fancy..
- Look at the mod list and make sure everything you want to keep is properly installed and enabled. If a mod is missing files or has errors, purge might flag it for removal — which is the opposite of what you want.
- Click the gear icon or the mod management menu at the top of the mod list. Different Vortex versions place this in slightly different spots, but it's generally near the top-right area of the mods page.
- Look for an option labeled Purge Mods or Purge Uninstalled Mods. Click it.
- Vortex will run a scan. This might take a few moments depending on how many mods and files you have.
- A dialog will appear showing you what it found. Review the list carefully.
- Confirm the purge, and Vortex will delete the flagged files.
What to Check Before Purging
Before you hit confirm, take a minute to look at the list. Here's what to watch for:
- Are any mods on the purge list ones you think you uninstalled but actually still want? This happens more often than you'd think, especially if you have a large mod library.
- Did you recently update a mod and want to keep the old version as a backup? Purge might flag the old version files for deletion.
- Are there any manually placed files in your mod directory that aren't tracked by Vortex at all? Purge won't touch these, but it's worth knowing they exist so you don't accidentally overwrite them later.
When to Run Purge
There's no strict schedule, but here's a good rule of thumb: run purge mods after any significant mod cleanup session. If you've just removed a batch of mods, updated several others, or switched to an entirely new mod loadout for a new playthrough, purging is a smart next step.
Some people like to run it once a month as part of routine maintenance. Others only do it when they notice performance issues or load order problems. Both approaches work — the key is just doing it regularly enough that files don't accumulate to unmanageable levels Less friction, more output..
Common Mistakes People Make with Purge Mods
Assuming Purge Deletes Everything
This is the big one. Day to day, purge mods does not nuke your entire mod directory. That said, it's smart enough to distinguish between files that belong to active mods and files that don't. But it's not perfect — and if you have a messy mod setup with overlapping files or manually placed assets, there's always a small risk.
The safest approach is to make sure your active mods are all properly installed and recognized by Vortex before running purge. If Vortex doesn't know a mod is supposed to be there, it might treat its files as orphaned.
Other Pitfalls to Watch Out For
- Skipping a Backup Beforehand – Even though purge is designed to be selective, it’s easy to misjudge which files are truly orphaned. A quick copy of your entire Mods folder (or at least the subfolders you suspect might be affected) can save you from an accidental loss of a beloved texture pack or a custom mesh you forgot you’d installed.
- Neglecting Load‑Order Conflicts – Removing a mod that shares assets with another can leave behind stray files that still affect performance or cause crashes. After a purge, double‑check the load order for any remaining entries and run a quick conflict check in Vortex’s “Manage > Conflicts” tab.
- Purging While Mods Are Still Active – If you run purge on a mod that is still marked as “installed” in Vortex’s library, the tool will treat its files as in use and skip them. This can leave behind stale folders that you intended to discard, forcing you to repeat the cleanup later. Make sure every unwanted mod is fully uninstalled before invoking purge.
- Over‑reliance on the Auto‑Detect Feature – Vortex’s automatic scan works well for standard installations, but it can miss files placed manually in the game’s root directory or in custom mod folders. Those items won’t be flagged for removal, so you’ll need to verify the contents of your Mods directory yourself after the purge finishes.
- Running Purge on a Corrupted Installation – If Vortex itself is experiencing issues (e.g., database errors, missing configuration files), the purge operation may behave unpredictably, sometimes deleting more than intended. In such cases, it’s safer to first update Vortex to the latest version or reset its cache before attempting a purge.
Best‑Practice Checklist
- Close the game before initiating a purge to avoid file‑lock conflicts.
- Confirm the list of candidates in the purge dialog; uncheck any entries you still need.
- Create a temporary backup of the Mods folder or at least the suspect subfolders.
- Run purge, review the results, and let Vortex delete only the verified orphaned items.
- Launch the game once after the purge to verify that all remaining mods load correctly and that performance feels unchanged.
- Re‑run a conflict check if you notice any unexpected behavior, adjusting load order as needed.
By following these steps and staying mindful of the common missteps outlined above, you can keep your mod library tidy without compromising the stability of your game. Regular, thoughtful purges not only free up disk space but also reduce the likelihood of hidden conflicts that could otherwise surface as mysterious crashes or visual glitches. In short, treat purge as a surgical tool — use it deliberately, verify its targets, and you’ll enjoy a cleaner, more reliable modding experience It's one of those things that adds up..
Most guides skip this. Don't.