Getting Started with GTA: San Andreas Modding

GTA: San Andreas modding has accumulated two decades of community work. The toolchain is older than most games on this list, but the conventions are mature: install CLEO for scripted mods, install modloader for asset mods, drop everything into the right folders.

This guide walks the standard install on the original 2004 PC release (not the Definitive Edition — that's a separate, mostly-incompatible track).

Step 1 — Confirm original 2004 release

The Definitive Edition's modding scene is much smaller and largely incompatible with original-era mods. For the mature catalog, stay on the original.

Steam's current default for "Grand Theft Auto: San Andreas" varies by region and date. Look for the original at retro Steam sales, GOG, or community-distributed installers (legal grey area; pick what your conscience supports).

Step 2 — Install CLEO

CLEO 5 (current major version) is the script-loading framework most modern GTA SA mods need.

Download CLEO 5 from cleomods.com. Run the installer; it auto-detects your GTA SA install.

After install, your SA folder has a CLEO/ subdirectory. Drop .cs script mods here.

Step 3 — Install modloader

modloader by junior_djjr (still hosted on legacy GTAGarage mirrors and GTAinside) transforms how SA modding works.

Without modloader: asset mods require editing IMG archives.

With modloader: asset mods drop into a modloader/ folder and are applied at runtime without modifying base game files.

Install per the README. Create a modloader/ folder in your SA directory.

Step 4 — Install your first mods

Three popular first picks:

• HOODLUM cleanup (or equivalent) — patches the original 2004 SA executable for modern Windows (1.0 EU/US version is required by most mods, sometimes called "downpatching" if your install is on a different version).
• Widescreen Fix — adds native widescreen support the original lacks.
• SkyGFX — restores PS2-style lighting and visuals (the original PC port simplified PS2's lighting; SkyGFX brings it back).

Scripts go in CLEO/. Asset mods go in modloader/<mod_name>/.

Step 5 — Optional: install graphical mods

San Andreas's modding scene has produced extensive graphical overhauls:

• SilentPatch — community bug-fix patch, near-universal install.
• ENB series for SA — shader injection. Multiple presets available.
• Texture overhauls — various HD texture packs available on GTAinside.

Each goes in modloader/ or follows mod-specific install instructions.

Step 6 — Multiplayer: SAMP or MTA?

Two competing multiplayer scenes:

• SAMP (San Andreas Multiplayer) — older, larger player base, roleplay-server-dominated.
• MTA (Multi Theft Auto) — newer, more flexible scripting.

They're entirely separate — different servers, different mod ecosystems. Pick one based on what your friends play.

Common gotchas

• Game version mismatch. Many mods require GTA SA v1.0. Use a downpatch tool if your install is v1.01 or v2.0.
• modloader install fails. Confirm the version compatibility against your SA executable.
• CLEO mod doesn't load. CLEO 5 has compatibility with most older .cs mods but not all. Some legacy mods are CLEO 3 / CLEO 4 only.
• Texture mod looks corrupt. Often an IMG archive issue. modloader avoids this by keeping mods out of base IMG files.
• Performance dropped on graphical mods. SA's engine has hard limits; piling on shader effects past ENB can produce stuttering.

San Andreas modding is mature enough that the failure modes are documented and the fixes are usually one Google search away. Two decades of accumulated knowledge is a real asset.