Verified author links, eight clean-installation steps and exact instructions for where each file belongs. Separate guidance for the original Vice City and Definitive Edition.
This guide is primarily for the original 32-bit PC version of Grand Theft Auto: Vice City (Classic). Do not transfer .asi mods, classic CLEO scripts or files intended for gta-vc.exe to Vice City – The Definitive Edition.
For Definitive Edition, choose only files explicitly labelled VC:DE or Trilogy: DE. Use CLEO Redux for scripts; the classic PC version uses CLEO for Vice City.
Before making the first change, copy the entire working game installation outside the protected Program Files folder. Install one mod at a time into the copy and launch the game after every change.
Vice City has no package manager or conflict checking. Two mods may replace the same model, texture or data line; a clean copy is the quickest way back. Keep a backup of your save files as well.
Install only those required by the mod
Core bug and compatibility fixes for the classic PC version.
It addresses a range of issues with the original port on modern Windows. It is a suitable foundation to install before graphics and content mods.
For: Vice City Classic
Download — Author's GitHub – releases →Loads plugins with the .asi extension when the game starts.
SilentPatch, Widescreen Fix, Project2DFX and many other plugins require it. Download the 32-bit x86 package for Classic.
For: Vice City Classic (x86)
Download — Author's GitHub – latest version →Loads replacement models, textures and data from separate subfolders.
Mods can be enabled, disabled and removed without overwriting the game's original archives. Keep each mod in its own folder inside modloader.
For: Vice City Classic
Download — Project GitHub – releases →A library for game scripts that add new features and missions.
Use only scripts made specifically for Vice City and check the required CLEO version. The official site lists support for executable 1.0 US.
For: Vice City Classic 1.0 US
Download — Official CLEO Download Center →Eight steps — do not skip any
Classic can be identified by the original gta-vc.exe; Definitive Edition is part of Trilogy DE. Note the executable version. Do not mix guides or files between editions.
Copy the entire working game folder and the save files. If the installation is in Program Files, place the working copy in a separate folder such as Games, where Windows does not restrict writing.
Before adding the first file, load a save and exit the game. This separates an existing installation problem from one caused by a mod.
For Classic, start with SilentPatchVC and one copy of the 32-bit Ultimate ASI Loader. If a package already includes the loader, do not add another.
Extract Mod Loader according to its README. Put each content mod in its own named subfolder so it can be removed without searching for files in the game's archives.
Use CLEO for Vice City for Classic and CLEO Redux for Definitive Edition. A script from GTA III or San Andreas is not automatically compatible.
After each mod, launch the game, load a save and test the changed feature. Keep a simple list of the name, version and files added.
Do not look for the problem by reinstalling everything. Disable the latest Mod Loader subfolder or remove the latest plugin, then check the logs and README.
No redirects — straight to the project source
Fixes · Classic
Fixes bugs in the original PC port and improves its behaviour on modern systems.
Download SilentPatchVC — Author's repository →Display and HUD · Classic
Corrects the aspect ratio, field of view and HUD layout on widescreen monitors.
Download GTA Vice City Widescreen Fix — Author's GitHub – Vice City release →Controls · Classic
Adds more modern support for XInput controllers and the correct button icons.
Download GInputVC — Author's GitHub – latest release →Draw distance and lights · Classic 1.0 US
Adds distant light coronas and extends the city's draw distance.
Download VC.Project2DFX — Author's GitHub – Vice City release →Scripts and new features · Classic 1.0 US
Allows community CLEO scripts to run without modifying the main game script.
Download CLEO for Vice City — Official CLEO Download Center →Scripts for Definitive Edition · Definitive Edition
A separate scripting platform for Trilogy – The Definitive Edition; it is not the classic CLEO VC.
Download CLEO Redux — Project GitHub – latest release →Graphics, gameplay, large packages and total conversions
Restores or reproduces selected graphical features of the PS2 and Xbox versions: colour filters, water, post-processing and rendering effects.
Edition: Classic
Requirements: ASI Loader; settings differ depending on the desired PS2, Xbox or PC appearance.
Compatibility: Do not combine it without checking with another mod that overwrites the same rendering or post-processing.
Download and documentation — Author's GitHub – releases →Adds neon elements inspired by Vice City Stories to the original Vice City.
Edition: Classic 1.0
Requirements: Widescreen Fix/ASI Loader, Mod Loader, Project2DFX with a limit adjuster and SkyGFX as specified in the author's guide.
Compatibility: This is a chain of several dependencies. Install them one at a time and launch the game after each one.
Download and documentation — Author's GitHub – documentation and download →Fixes game-logic problems that appear at higher frame rates than the original game expected.
Edition: Classic
Requirements: ASI Loader. Use a supported release and a conservative FPS limit.
Compatibility: Unrestricted FPS can still alter physics or missions. Start at 60 FPS and save before missions.
Download and documentation — Project source repository →Triggers random effects at regular intervals; includes configuration and support for viewer voting during streams.
Edition: Classic 1.0
Requirements: A downgraded 1.0 installation and the requirements listed for the specific release.
Compatibility: It is not suitable for a first playthrough or a clean 100% save. The author lists known compatibility details and conflicts with the release.
Download and documentation — Author's GitHub – releases →A substantial package of fixes and improvements intended to preserve the original character of Vice City.
Edition: Classic
Requirements: A clean installation and a new folder. Read the ReadMe for the specific version before use.
Compatibility: Do not automatically combine the complete package with individual fixes from the list; it probably already includes some of them.
Download and documentation — Official project profile on Mod DB →A package of map fixes, revised models, more detailed environments, interiors and neon lighting.
Edition: Classic
Requirements: A separate clean installation and a new save, following the project's current instructions.
Compatibility: Large packages change many of the same files; do not add another remaster without explicit compatibility.
Download and documentation — Official project profile on Mod DB →A large expansion with new scripts, interiors and features designed to build on the original game.
Edition: Classic
Requirements: A clean, unmodded Vice City; for the current branch, the authors require a new or supplied compatible save.
Compatibility: An older save from another version of the project may not work. Install it in a separate copy of the game.
Download and documentation — Official project profile on Mod DB →A large community visual package assembled from a range of modifications, textures and effects.
Edition: Classic
Requirements: Several gigabytes of space and a separate clean installation. Check the project's current files and comments.
Compatibility: Do not add further graphics packages without checking. If a problem occurs, return to the clean copy instead of manually deleting hundreds of files.
Download and documentation — Official project profile on Mod DB →A substantial themed conversion featuring several eras of Hill Valley, time machines, new vehicles, sounds and tasks.
Edition: Separate modded Classic installation
Requirements: A separate copy of the game and a separate installation following the team's documentation.
Compatibility: A total conversion is not an addition to a normal 100% playthrough. Treat it as a separate game built on legally owned Vice City data.
Download and documentation — Official team profile on Mod DB →JavaScript and TypeScript scripts created explicitly for CLEO Redux and supported Definitive Edition builds.
Edition: Trilogy – Definitive Edition
Requirements: A current CLEO Redux version and a script labelled for Vice City DE.
Compatibility: Standard CLEO VC scripts are not the same. Check every script against the supported command list and game version.
Download and documentation — Project GitHub – latest release →What can reasonably be combined
For: A first playthrough while preserving the original appearance
Contents: SilentPatchVC + Widescreen Fix + GInputVC + Mod Loader
Check the clean game first, then add the mods in exactly this order. SkyGFX is an optional later step.
For: A modern monitor and a richer city at night
Contents: Stable base + SkyGFX + Project2DFX + Vice City Neons
Monitor dependencies, the limit adjuster and performance. Running two post-processing packages at once is usually not advisable.
For: A new playthrough with plenty of new content
Contents: One project such as Vanilla Vice or Extended Features
Choose one large package and give it a separate copy of the game. Do not mix in a second modpack without documented compatibility.
For: Trilogy DE on a supported PC build
Contents: CLEO Redux + individual VC:DE scripts
Do not use the classic ASI/CLEO stack. Every download must explicitly state Definitive Edition.
Archives with descriptions, versions and community verification
Profiles of large projects, total conversions and files with an update history.
Check the date of the latest update, comments and requirements. The download is a mod archive, not the game.
Open archive →A catalogue of mods with versions, requirements, comments and the option to track updates.
An account may be required to download. Always open the Requirements and Files tabs.
Open archive →A large community archive of vehicles, skins, maps, tools and scripts.
Documentation for older uploads is often brief. Scan the archive and do not run included installers when manual installation is sufficient.
Open archive →The main source for technical plugins such as SilentPatch, ASI Loader, Widescreen Fix and Project2DFX.
Prefer a link directly from the author's documentation. The Releases section contains versions and changes; the green Code → ZIP option usually downloads source code, not the finished mod.
Open archive →Four checks before installation
Prefer the official project website or its GitHub Releases. A re-upload may be outdated, modified or missing documentation.
Scan it with current antivirus software. A typical mod consists of .asi, .dll, .cs, .ini, models, textures or data files; an unexpected .exe requires extra caution.
A matching game name is not enough. The edition, gta-vc.exe version, loader used and installation order are what matter.
This page links only to mods and tools. We do not provide game data, cracks or packages containing third-party original files.
We do not publish links to cracks, pirated copies of the game, modified APK files or packages containing original game data. Running mods requires your own legal installation of the appropriate edition.
A typical cause and a verified solution
| Problem | Typical cause | Solution |
|---|---|---|
| The game does not start after adding an .asi | The wrong loader architecture, a duplicate proxy DLL or a plugin for another game version. | Remove the latest .asi and keep only one 32-bit copy of ASI Loader. Check the supported version in the plugin documentation. |
| Mod Loader does not load the mod at all | An incorrect subfolder structure, or the mod requires a manual change, CLEO or another plugin. | Check the mod's README and the Mod Loader log. Each mod needs its own folder with the file paths preserved. |
| The game runs too quickly or a mission breaks | The original logic may be tied to the frame rate, or the limiter was disabled without a corresponding fix. | Restore the default frame limiter and SilentPatch settings. Enable higher FPS only with a fix that explicitly addresses game logic. |
| The widescreen image is stretched or the HUD is misplaced | The game's widescreen mode is enabled without Widescreen Fix, or two display fixes conflict. | Keep one Widescreen Fix, check its .ini and temporarily disable other plugins that alter the FOV or HUD. |
| The game crashes after adding cars or textures | A conflict between replaced files, a damaged archive or an exceeded engine limit. | Disable the latest mod folder. For larger packages, check the required limit adjuster and never combine two packages that change the same files without merging them manually. |
| An old save does not work after installing a mod | Some scripts or total conversions change main.scm and the save structure. | Use a clean save or start a new game as instructed by the mod. Restore the original saves from the backup only after returning to a clean installation. |
Short answers to common questions
Download from the author's official website or GitHub Releases, or from an archive with a version history and comments. Check the game edition, read the README, scan the archive with antivirus software and create a backup before installation.
Not automatically. Classic .asi plugins, CLEO VC scripts and files for gta-vc.exe are not intended for Definitive Edition. Look for the label VC:DE or Trilogy: DE; use CLEO Redux for scripts.
It depends on the type. ASI Loader and core plugins usually go next to gta-vc.exe, content replacements are safer in separate Mod Loader subfolders, and CLEO scripts go in the CLEO folder. The README for the specific mod always takes precedence.
No. Only scripts written for this library require CLEO. ASI plugins require ASI Loader, while models or textures can often be loaded through Mod Loader.
This guide and the tools listed are for PC. Mobile and console versions use different files, restrictions and procedures; do not install PC packages on them.
Community modifications are not the same as distributing the game. Do not download cracks or packages with original game data, respect the authors' licences and allow for technical risk. A backup and the author's source significantly reduce the risk, but do not guarantee an error-free result.
Start with fixes, add one mod at a time, and record the version and source of each one.