Modloader is a tool that sits between your mods and the actual game files. Instead of you copying a mod straight into models, data or audio and overwriting whatever was there before, Modloader reads mods from its own folder and feeds them to the game while it runs. The original files never get touched.
That one difference changes everything about how safe modding GTA San Andreas is. You can try ten car mods, hate eight of them, and get back to a clean game in minutes instead of reinstalling.
What Modloader Actually Does
Normally, installing a mod for San Andreas means opening the game’s archive files or folders with a tool like IMG Tool, finding the right slot, and replacing a model, texture or script outright. If the mod is bad, or you want the old one back, you need a backup of that exact file to restore it.
Modloader skips that whole process. You install it once into your main GTA San Andreas folder, and it creates a folder named modloader. From that point on, you drop mods into subfolders inside that folder, and Modloader injects them into the game at runtime, layered on top of the original files. The base game install stays exactly as it was the day you bought or extracted it.
One Subfolder Per Mod
The rule inside the modloader folder is simple: each mod gets its own subfolder. Don’t dump files loose into modloader itself, and don’t mix two mods in the same subfolder, since that makes removing one of them later a guessing game.
- Open the
modloaderfolder in your GTA San Andreas directory. - Create a new folder for the mod, named whatever makes sense to you, for example
cars_elegy_remixorskin_cj_jacket. - Inside that folder, recreate the same path the file would normally sit in, matching the game’s own folder structure, so a texture replacement might sit under something like
modelsinside your mod folder, just like it would in the base game. - Copy the mod’s files into that structure and start the game.
Most mod archives already come set up this way, or the author’s readme tells you exactly where each file belongs. If a mod only comes with loose files and no folder structure, check the readme first, since guessing wrong means the mod silently fails to load.
Load Priority When Mods Collide
Sometimes two mods touch the same file, say two different handling edits or two mods that both replace the same vehicle model. Modloader needs to decide which one wins, and it does that through load order.
By default, mods load in the order their subfolders appear, which usually follows alphabetical order of the folder names. A mod in a folder that loads later will override a conflicting file from a mod that loaded earlier. Modloader also shows a small menu early in the game’s startup where you can see which mods are active and adjust their order if the default alphabetical sorting isn’t what you want.
In practice, conflicts are rare unless you’re running several car packs that touch the same vehicle slot or multiple script mods editing the same gameplay system. If something looks wrong after installing a new mod, like an old texture suddenly showing up again, check which folder loads after which, since that’s almost always the cause.
Uninstalling Is Just Deleting a Folder
This is where Modloader really pays off. To remove a mod, you delete its subfolder from inside modloader. That’s it. There’s no file to restore, no backup to dig through, because the original game file was never overwritten in the first place.
- Open
modloader. - Find the subfolder for the mod you want gone.
- Delete it.
- Start the game, the mod is gone, everything underneath it is back to default.
This also makes testing mods a lot less stressful. You can install something, play for an hour, decide you don’t like it, and remove it cleanly without worrying about leftover files breaking something else down the line.
What Works With Modloader, and Why You Still Want a Backup
Most of the common mod types work fine through Modloader: vehicle replacements, skin mods, map additions, and CLEO scripts all load through it without issue. CLEO mods in particular are made for this kind of setup, since they’re already designed to run as separate script files rather than edits to the base game.
Some mods don’t play nicely with this approach. Anything that needs to patch the game’s executable directly, or that comes with its own installer expecting to write straight into the original game folders, might bypass Modloader entirely or need extra steps the mod’s own instructions should spell out. Total conversions and some graphics overhauls sometimes fall into this category.
Because of that, keep an untouched backup copy of your GTA San Andreas install somewhere outside the game folder, even with Modloader running everything. It costs you a few gigabytes of drive space and saves you from a full reinstall if a mod does something outside Modloader’s reach, or if a script mod conflicts with the game in a way that a simple folder deletion won’t fix.
Questions people ask
Do I need to reinstall GTA San Andreas before using Modloader?
No, Modloader works with an existing install, you just drop its files into the main game folder and it creates its own modloader folder from there.
Can I run Modloader with mods installed directly into the game files?
You can, but it defeats the purpose, since those direct edits still overwrite your originals. It's cleaner to move everything you can into Modloader subfolders.
Why isn't my mod showing up after I put it in the modloader folder?
Usually the folder structure inside your mod's subfolder doesn't match what the game expects, check the mod's readme for the exact path it needs.
Does Modloader slow down loading times?
There's a small delay while it reads through your mod folders at startup, but it's minor compared to the time saved not reinstalling the game after a bad mod.
Browse all GTA San Andreas mods on CrashMods
