CLEO is what lets GTA San Andreas run script mods that go way beyond what the base game allows: new animations, vehicle tweaks, extra radio commands, cheat-style triggers, you name it. On its own, San Andreas can’t load these scripts. CLEO sits between the game and the mod files and makes that possible.
Once CLEO itself is installed, adding or removing individual scripts is just moving files in and out of one folder. The tricky part is usually figuring out which key starts a script and sorting out why two mods are fighting each other.
What CLEO actually does
Think of CLEO as a loader library, not a mod by itself. It hooks into the game’s executable and gives it the ability to read and run .cs script files that wouldn’t normally do anything. Without CLEO installed, dropping a .cs file into your game folder does nothing at all.
Most script mods for San Andreas, from simple key-triggered effects to full gameplay overhauls, depend on this library being present. If a mod’s description mentions a CLEO folder or a .cs file, you need CLEO running first.
Installing the CLEO library
The library itself comes as a small package of files that go straight into your main GTA San Andreas game folder, the same one that holds gta_sa.exe. Once you extract and place those files there, a new folder named CLEO appears inside your game directory. That folder is where every individual script will live.
- Download the CLEO library package for San Andreas.
- Extract its contents into your main game folder, next to
gta_sa.exe. - Confirm a
CLEOfolder now exists in that same directory. - Launch the game once to make sure it still starts normally.
If the game refuses to launch after this step, double check you extracted the files into the correct folder and not into a subfolder by mistake.
Adding script mods
With the library in place, installing any individual script mod is simple: you drop its .cs file, and any extra files it needs, into the CLEO folder. There’s no registry, no separate installer menu, no activation inside the game’s options screen.
- Download the script mod, usually a
.zipor similar archive. - Open it and look for one or more
.csfiles. - Copy those files into your game’s
CLEOfolder. - Some scripts come with extra supporting files like images or text; read the included readme to see where those go, since not all of them belong in the CLEO folder itself.
Start the game and load a save. If the script doesn’t show any obvious menu or message, that’s often normal. Many CLEO scripts stay silent until you trigger them.
Triggering scripts: keys and cheat codes
This is where people get stuck most often. CLEO doesn’t define how you activate a script. Each script’s author decides that themselves, and it varies a lot from one mod to the next. Some use a key combination, some use a classic cheat-code-style sequence of buttons, and some run automatically in the background with no input needed at all.
There’s no universal key to “turn on” a CLEO mod. The only reliable way to know is to read the mod’s description or readme file. Authors almost always list the exact key or code needed, and sometimes they let you change it by editing a line inside the .cs file or a linked settings file.
If a script seems to do nothing, before assuming it’s broken, go back and check that you’re pressing the right key combination at the right moment, for example while standing still versus while driving.
Dealing with conflicts between scripts
CLEO can run many scripts at once, but that doesn’t mean they always get along. Two common problems show up:
- Too many scripts running at the same time can slow the game down or cause odd glitches, especially if several of them are constantly checking player input or world state in the background.
- Two scripts that both try to control the same thing, like the same key combination, the same vehicle handling value, or the same animation slot, can conflict. One might override the other, or the game might behave unpredictably, freeze briefly, or crash.
If you notice weird behavior right after adding a new script, the simplest test is to remove it temporarily and see if the problem goes away. Add scripts one at a time when you’re building up a collection, rather than dumping a dozen files in at once, so you can actually tell which one caused an issue if something breaks.
Removing scripts and keeping track of what you added
Uninstalling a CLEO script is as straightforward as installing it: delete the .cs file (and any supporting files it came with) from the CLEO folder. There’s no separate uninstaller and nothing else to clean up in most cases.
The real trouble comes from forgetting what you put in there in the first place. After a while the CLEO folder can fill up with files whose names don’t tell you much. Keep a simple running list somewhere, a text file is fine, noting:
- The script’s file name
- What it does
- What key or code triggers it
This saves a lot of guesswork later when you’re troubleshooting a conflict or just trying to remember why a particular file is sitting in your CLEO folder months after you installed it.
Questions people ask
Do I need CLEO for every mod in GTA San Andreas?
No. Many mods, like texture replacements or car models, work without it. You only need CLEO for mods that come with .cs script files.
Why doesn't my CLEO script do anything when I press the key?
Check the mod's readme or description for the exact activation key or cheat code, since each author sets their own, and there's no standard key that works for all scripts.
Can having too many CLEO scripts crash the game?
Yes, running a large number of scripts at once, or two scripts that control the same feature, can cause slowdowns, glitches, or crashes. Remove scripts one at a time to find the culprit.
How do I uninstall a CLEO script cleanly?
Just delete its .cs file and any extra files it added from the CLEO folder inside your game directory. Nothing else needs to be touched.
Browse all GTA San Andreas mods on CrashMods
