SCOOBY

FiveM Resource Installation Guides

Browse resources ↗

FIVEM / REDM

Server resources and custom assets

  1. Download the resource on Scooby and check the intended runtime, requirements and dependencies. FiveM and RedM use separate resource packages.
  2. If the download is a server resource, give it to the server owner or install it using the included server instructions.
  3. Keep its resource manifest, stream folders and supporting files together. Follow the readme for server configuration and startup order.
  4. For a menu preset, use the menu’s import or Open Folder control instead.

Client preset folders do not install server resources. Access to a server does not grant permission to change its resources.

FiveM setup → RedM setup →

FIVEM

Install FiveM character and animal models

  1. Choose a FiveM add-on and check the author’s supported game build, dependencies and model name. If you want pet interactions, also check which companion script supports the animal.
  2. Unpack the resource on a server you administer. Place the folder that contains fxmanifest.lua under the server’s resources directory. Keep the supplied stream folder, textures and metadata in their original locations.
  3. Add ensure <resource-folder> to server.cfg, after any required resources. To test a new resource on a running test server, enter refresh and then ensure <resource-folder> in the server console.
  4. Use the model name from the author’s instructions or the ModelName entry in peds.meta with your server’s authorized ped selector or spawning tool. The resource folder and model name can differ.
  5. Test movement, textures and any advertised outfit variants. If the model fails to load, check the server console, the exact model name, and whether the manifest mounts the supplied metadata with PED_METADATA_FILE. Restore your normal character appearance after testing a player model.
Browse FiveM character and animal models → Cfx metadata reference → Cfx server commands →

FIVEM

Install and test FiveM animations and emotes

  1. Check what the release contains. A menu such as RPEmotes Reborn is a complete resource. A pose pack can contain only .ycd clips and setup instructions for the menu you already use.
  2. For a clip pack, keep the .ycd files in the resource’s stream folder and start it as the author describes. Use the dictionary and clip names from the release when registering the emote.
  3. Follow your menu’s instructions for adding entries. RPEmotes Reborn provides AnimationListCustom.lua for custom entries. Use the matching instructions if the release gives an example for a different menu.
  4. Test the emote on the intended character and check that it starts and cancels. For a shared emote, have a second player confirm the timing and any props. Check synchronization and the game build against your menu’s setup guide if the two players see different results.
Browse FiveM animations and emotes → RPEmotes Reborn setup →

FIVEM

Install and test FiveM props

  1. Open the creator’s release and find the resource folder with fxmanifest.lua. Keep the streamed models, textures and any supplied .ytyp file together. If the author uses DLC_ITYP_REQUEST for a YTYP, keep the declaration and its path intact.
  2. Add the resource under resources on your test server and start it from server.cfg. For an example map, visit the location the author lists. For individual props, place one using the supplied model name in a compatible placement tool.
  3. Have a second player connect and check that the prop has the right texture, scale and collision. If it is missing, check the exact model name and the console for missing stream files. If it appears twice, check for an example map and a separate placement at the same spot.
  4. Configure inventory items separately if the pack provides them. Test the prop on its own first, then verify that the intended item or placement resource uses that model.
Browse FiveM props and objects → Cfx.re resource manifest reference →

FIVEM

Install and test FiveM clothing

  1. Check which freemode model the release supports. An add-on introduces a drawable or prop in a clothing collection. A texture replacement updates the appearance of an existing item, so look in the original slot when testing it.
  2. On a test server, place the creator’s resource folder under resources. Keep the manifest and streamed assets together. Add ensure followed by the resource’s folder name to server.cfg and follow any load order the creator specifies.
  3. Open the server’s appearance menu on the supported model and try the item and its textures. If an existing outfit changed or a garment shows the wrong texture, test with other packs that touch the same clothing slot disabled.
  4. When an appearance resource supports collection-based outfits, save the collection name and its local drawable index. Cfx.re documents that a GTA title update can shift the global indexes for custom collections.
Browse FiveM clothing and textures → Cfx.re clothing collection reference →

FIVEM

Install and test a FiveM vehicle add-on

  1. Choose the creator’s FiveM package and confirm its game build, edition and dependencies. Locate the folder with fxmanifest.lua. Keep the stream folder and the vehicle, handling and tuning metadata together.
  2. Copy that resource folder into resources on a test server. Add ensure followed by its folder name to server.cfg. Start any dependencies first and check the console for missing files.
  3. Use the model name from the release notes or the modelName entry in vehicles.meta in your vehicle spawner. For example, the Sunrise R resource is hycsunrise and its model is hycsun.
  4. Spawn the vehicle before adding it to a shop or job. Check the doors, lights, sound and any advertised tuning options. If it only breaks when another pack is enabled, compare their model and metadata names before changing either package.
Browse FiveM vehicle add-ons → Browse FiveM sound packs → Cfx.re vehicle metadata reference →

FIVEM

Install and test a FiveM map add-on

  1. Check the maintainer’s required server edition, game build and dependencies. A YMAP places map objects. A custom interior can also include models, textures, collision and YTYP definitions. Keep the author’s files together.
  2. On a test server, copy the folder with fxmanifest.lua into resources and add ensure followed by its folder name to server.cfg. If the archive wraps several resources, start the map folder named in the instructions.
  3. Connect and visit the area with other maps for that location disabled. Check entrances, floors and doors from both sides. Reconnect and check again so you can catch missing assets that only show up when a player first joins.
  4. Enable the other maps one at a time. If walls flicker, objects appear twice or collisions no longer match, stop the last resource you enabled and compare again. Keep a copy of the previous server.cfg so you can restore the working setup.
Browse FiveM map add-ons → Cfx.re resource manifest reference →

FIVEM

Install FiveM graphics packs and textures

  1. Open the listing’s author page and choose the FiveM release. Check whether it is a client graphics pack, a ReShade preset, or a server-streamed resource.
  2. For a client graphics pack, close FiveM, extract the archive, and follow the author’s installation path. For example, Hiromasa documents %LOCALAPPDATA%/FiveM/FiveM.app/plugins for its packs. Keep a backup of any files you replace.
  3. For a ReShade preset, install the required shaders and any named base mod, such as QuantV. Put the preset .ini in your ReShade presets folder and select it in the overlay.
  4. For a server-streamed package such as Oulsen’s satellite map, have the server operator keep the manifest and stream files together, add the resource to the server’s resources directory, and enable it in server.cfg.

Cfx.re documents that client graphics mods are unavailable in FiveM for GTA V Enhanced during early access. Check the game edition and the server’s client-mod policy before installing.

Cfx.re compatibility notes → Browse FiveM graphics packs and textures →

FIVEM

Compare graphics packs and check performance

  1. Start with stock graphics and take a baseline in a private test session. Keep the same location, camera angle, resolution and game settings for both passes.
  2. Check the same street in clear daylight, at dusk and at night. In daylight, look for detail in white walls, clouds and signs. At dusk, check for lost detail in shaded doorways. At night, check whether streetlights bloom over road markings or make the HUD hard to read.
  3. Walk the same route and pan past fences, foliage and signs. These fine details make shimmer, ghosting and oversharpening easier to spot. At a waterfront, check that the sunset reflection keeps detail around the brightest part.
  4. Repeat the route with one pack or preset changed. Compare frame times and visible stutter along with average FPS. A clip recorded on a different server or at a different time of day is useful for judging the look, but cannot establish a performance gain.

If the result looks wrong or FiveM crashes, close the game, roll back the last change and retest the stock setup before adding anything else.

FIVEM

Measure what an FPS pack changes

  1. Press F8 to open the FiveM console and run cl_drawperf true. The overlay shows FPS and GPU usage. Keep your resolution, frame cap and graphics settings fixed during the comparison.
  2. Choose a route on a test server you control. First compare the stock client and the pack at the same time of day and in the same weather. Then repeat in a second condition, such as at night, to check whether the result holds when lighting changes.
  3. Let the scene load before recording your readings. Run the same route twice for each setup and note FPS during movement and any recurring stutter. Check whether any improvement comes with changes to shadow detail, reflections or road textures that matter to you.
  4. Run cl_drawperf false when you finish. Keep your measurements with your settings so you can repeat the comparison after changing the pack.
Cfx.re performance overlay commands →

FIVEM

Check whether your FiveM client supports the old custom crosshair

In September 2026, Cfx removed its crosshair guide and the drawing code from the FiveM source repository. The old commands may be unavailable on your installed build.

  1. On a test server you administer, or in FiveM single-player, press F8 and enter cl_customCrosshair by itself. If the console returns a setting, record its value and try cl_customCrosshair true. If the setting is unknown or the reticle never appears, use the game’s available HUD options.
  2. If the reticle appears, try cl_crosshairsize 3 for line length and cl_crosshair_drawoutline true for an outline. Record the original values before changing them. Compare the result on a bright wall and against a dark background at the resolution you play at.
  3. Restore the values you recorded. To disable the old custom reticle, use cl_customCrosshair false on builds that support it. If a server disables the setting, follow the server’s HUD rules.

PNG and GIF crosshair packs are image files. The old F8 commands draw a reticle from settings such as line length and color. For a server HUD that supports images, use the file format and dimensions its maintainer specifies.

Archived Cfx crosshair reference → Cfx source change →

FIVEM

Test sky colors, timecycles and vehicle lights

  1. Decide who should see the change. A client timecycle pack changes the view on your installation. For vehicle lighting that players should share, have the server operator test a compatible server resource.
  2. Choose the FiveM package on the maintainer’s page. For VisualVanilla, that is 2.0 for FiveM (FINAL) in All Versions. For U1D GFX Core, choose FiveM 1.0.0. Follow the selected package’s written instructions.
  3. Hold the camera still on a test server and compare the same weather and time with the pack on and off. Then advance from daylight to dusk to see how the colors blend. Check cloud edges, street markings and building shadows. A striking sky at one hour can look very different during the transition.
  4. For server lighting, have a second player join the test server and look at the same vehicle at night. If the lights are too bright or differ between clients, check which server resources and client presets affect lighting. Test one change at a time.
Browse FiveM sky and lighting packs →

FIVEM

Load and tune a ReShade preset

  1. On a compatible FiveM Legacy setup where the server allows ReShade, save the preset .ini in the presets folder named by its author. Keep your current preset as a separate file.
  2. Open the ReShade overlay and select the new file from the preset selector on the Home tab. If an effect fails to load, check the author’s shader list and the overlay log. In a preset, the Techniques line can help you identify missing .fx files.
  3. Compare effects on and off from the same camera angle. If shadows look flat or signs lose detail, try adjusting the color or contrast effect first. If pavement and brick edges look grainy while moving, turn down sharpening and check whether more than one sharpening effect is active.
  4. Save your changes to a copy. If the overlay never appears, check your game edition and the server’s policy before changing anything else.
ReShade preset instructions →

FIVEM

Tell a preset from a full client pack

  • A ReShade preset is typically an .ini with a list of shader dependencies. Load it through your compatible ReShade installation and keep your previous preset so you can switch back.
  • A pack with a citizen folder can replace client files. Check the archive against the maintainer’s file list and game edition before changing anything. If the archive includes runtime DLLs or has no original release, skip it and choose a documented pack.
  • An archive labelled DLSS may bundle ReShade and third-party DLLs. Upscaling, frame generation and neural rendering have different hardware requirements. Check the original project’s compatibility notes for your exact GPU and edition before installing; a filename naming a GPU series is insufficient. Cfx.re says graphics mods are unavailable on FiveM Enhanced during early access.

Check the server’s client plugin policy first. To troubleshoot a compatible pack, start with the stock client, add one documented component at a time and back up the exact files you replace.

Cfx.re client plugin guidance →

FIVEM

Set up a mixed FiveM pack one component at a time

  1. Open the archive outside FiveM and check its folder tree. A bundle can put a ReShade preset, audio replacements and a citizen folder under a single wrapper directory. Open any nested archive separately and match each component to its original maintainer’s instructions and supported edition.
  2. Close FiveM. Confirm the path to your active installation before changing files. Cfx.re’s installer normally uses %LOCALAPPDATA%\FiveM and can also install into a folder you choose. Write down the files each component adds or replaces and keep copies of the originals outside the game folders.
  3. Try the component you want first. Launch FiveM and test it before adding the next one. If two components name the same destination file, choose one unless the maintainer provides a combined version. To compare a dramatic color grade or night sky, check whether the HUD and light surfaces stay readable during ordinary play. Montage cuts and slow motion make it hard to judge how a preset behaves live.
  4. If a change causes a crash, missing audio or a modified-file error, close FiveM, remove the files that change added and restore the copies you made. Launch again with the restored setup. If you no longer have the original files, use the official support instructions for the affected installation.
Cfx.re installation paths → Cfx.re client troubleshooting →

FIVEM

Check and compare FiveM sound packs

  1. Check what the archive contains before installing. Files such as RESIDENT.rpf and WEAPONS_PLAYER.rpf are replacement archives. A server audio resource instead comes with a manifest and can declare its own AUDIO_WAVEPACK. Use the maintainer’s instructions for the correct package type and game edition.
  2. Check the server’s rules for client replacements. Where allowed, back up the exact files the maintainer says to replace and try one pack at a time on a private test server. Two packs that replace the same archive can overwrite one another.
  3. Compare the same sound at the same distance and in the same location with your game and system volume unchanged. Listen to both a single sound and a short burst, then check whether voice and ambient sounds stay clear. Recording volume and compression vary between clips, so use the live comparison to judge loudness and distortion.
  4. If sounds go missing, crackle, or the client reports modified files, restore the originals and retest. For a server resource, have the operator check the manifest, dependencies and console.
Browse FiveM sound packs → Cfx.re audio resource reference →

FIVEM

Deploy a public server recipe with txAdmin

  1. Pick the correct Legacy or Enhanced FXServer build. Start FXServer to open txAdmin, link your Cfx.re account and have your own server registration key ready. On Windows, Enhanced requires the Visual C++ redistributable listed in the Cfx.re setup guide.
  2. Choose a fresh server-data directory. For a basic Cfx.re server, skip database setup. For Qbox, ESX Legacy or QBCore, start MariaDB and have a database connection ready. Qbox requires MariaDB 10.9 or newer and does not support MySQL or XAMPP.
  3. Choose the listed template in Popular Recipes for the Basic Server, Qbox Framework or ESX Legacy. For Qbox Lean or QBCore, open the recipe page, copy the YAML file’s Raw URL and paste it into Remote URL Template. The older QBCore guide shows a Popular Recipes entry that txAdmin has since deprecated.
  4. Review and run the recipe. After the server starts, check the console for resource or database errors and connect to the test server before opening it to players. Keep your own configuration and database backup before replacing an existing installation.
Browse FiveM server recipes → Cfx.re txAdmin setup →

FIVEM

Add a Lua menu to a FiveM resource

  1. Check the menu dependency your script expects. MenuV runs as a standalone resource, the context menu is part of Ox Lib, and qb-menu is common in QBCore setups.
  2. Install the dependency in the server’s resources directory according to its maintainer. Start it before your script and check the server console for missing dependencies.
  3. Connect to your test server and open the menu through the resource that uses it. Check that each option works for the roles that should see it. Enforce permissions for server actions on the server even when the client menu hides the option.
Browse FiveM Lua Menus → Cfx.re resource setup →