Obtain OpenIV from its developer’s official site and select the game edition it supports. For FiveM asset work, start by inspecting or exporting files into a separate workspace; installing an ASI loader is not a prerequisite for simply browsing assets.
Download and install
Use the official OpenIV website and its current download instructions. Check the supported game/edition and installer origin before running it. If the official download is unavailable, do not substitute a random repack.
Close the game, run the official installer and choose a separate application installation directory. Review any Windows permission prompt and accept it only for the installer you intended to run.
Point it at the correct game
- Launch OpenIV and select the supported game and platform.
- Choose the real game installation folder using the location shown by your game launcher. Do not select FXServer or the FiveM resource directory.
- Confirm that OpenIV recognizes the installation. If it does not, check edition support and verify the game installation through its launcher before editing files.
- Browse without enabling edit mode first. Export files needed for your authorized project into a separate workspace and keep original assets unchanged.
Understand the mods folder
OpenIV’s mods-folder workflow and ASI components concern loading modifications in a supported game installation. Follow the developer’s instructions for that specific use case. Do not add runtime injectors just to prepare a FiveM asset.
A local mods folder is not a FiveM resource. FiveM deployment requires the appropriate resource structure, metadata and license permissions. Keep a clean game installation available and respect the online service and server rules.
Verify and recover
After an asset change, test the exported resource on staging and compare it with the original. If a game installation stops working after local modifications, undo those changes using the documented procedure and verify the game files. Keep backups outside the game’s mutable folders.