How to Install Custom Maps and MLOs in FiveM

Custom maps and MLOs (Map Level Objects — interiors and exterior add-ons) are among the highest-impact additions you can make to a FiveM server. A detailed Miami Ghetto district or a faithful NYC block grid transforms your server from a stock map into a unique world. But unlike scripts, map resources involve multiple file types, ytyp registration, and a set of fxmanifest directives that, if any one is missing, produce the same frustrating result: an invisible or entirely absent map.

This guide walks through the complete installation process for any custom FiveM map or MLO resource — from understanding the files involved to troubleshooting missing models and dealing with newer DLC build requirements.

Understanding the Files in a Map Resource

Before touching fxmanifest.lua, it helps to understand what each file type does. A well-packaged map resource will include some or all of the following in its stream/ folder:

The .ytyp file is the most commonly misunderstood and most commonly missing piece. Without it, GTA V's streaming system has no record of your custom archetypes, and the .ymap placement data references entity types that the engine considers non-existent — resulting in invisible or missing objects.

Setting Up the Stream Folder

All map files must be placed inside a folder named stream/ within your resource directory. FiveM automatically streams every file from this folder to connecting clients. The folder structure for a map resource should look like this:

• my-custom-map/ — resource root
• my-custom-map/fxmanifest.lua — resource manifest
• my-custom-map/stream/ — all model/placement/texture files go here
• my-custom-map/stream/custom_building.ydr — model geometry
• my-custom-map/stream/custom_building.ytd — textures
• my-custom-map/stream/custom_building.ybn — collisions
• my-custom-map/stream/custom_building.ytyp — archetype registration
• my-custom-map/stream/custom_map.ymap — world placement data

fxmanifest.lua for a Map Resource

The fxmanifest.lua for a map resource has two directives that are different from a regular script resource: this_is_a_map and the data_file entry for DLC_ITYP_REQUEST. Both are required for the map to work correctly. The this_is_a_map directive signals to FiveM that this resource contains world placement data. The DLC_ITYP_REQUEST data_file registers your .ytyp archetype file with the game engine.

fx_version 'cerulean'
game 'gta5'

author 'Your Name'
description 'Custom map or MLO resource'
version '1.0.0'

this_is_a_map 'yes'

files {
    'stream/**'
}

data_file 'DLC_ITYP_REQUEST' 'stream/custom_building.ytyp'

Registering the Resource in server.cfg

Your map resource must be listed in server.cfg with ensure. Place it in a logical position relative to other resources — after your base game config but before any scripts that reference the map's interior or exterior zones.

# server.cfg — ensure map resources
ensure my-custom-map

# then ensure scripts that use it
ensure my-target-zones
ensure my-interior-script

sv_enforceGameBuild for Newer DLC Props

GTA V has received multiple DLC updates since launch, each adding new props, interiors, and entity types. If a custom MLO uses props that were added in a specific DLC, clients without that DLC build will be missing those prop models — causing partial or fully invisible interiors. The sv_enforceGameBuild convar in server.cfg forces all connecting clients to load a specific game build.

# server.cfg — force a specific game build
# Example: build 2944 includes The Contract DLC content
sv_enforceGameBuild 2944

# Or for Cayo Perico content
# sv_enforceGameBuild 2189

Check the documentation or release notes for your specific MLO or map pack to find out which game build it requires. If the map creator does not specify a build, it likely uses only base-game props and does not need enforceGameBuild.

Load Order: Why It Matters for Maps

FiveM loads resources in the order they are listed in server.cfg (accounting for dependencies). For maps, incorrect load order causes the streaming system to attempt placing entities before their archetype registrations exist. The correct order is: core FiveM resources first, then map resources, then any scripts that interact with those maps.

1. System resources (sessionmanager, mapmanager, etc.) — these load automatically
2. Framework resources (es_extended, qb-core, etc.)
3. Map resources and MLOs
4. Script resources that reference map locations (target zones, teleport menus, job scripts tied to interiors)

Installing NYC and Miami Map Packs

Large-scale city map packs — like the NYC or Miami map packs available from CRM Development — follow the same installation process but typically contain multiple ytyp files, dozens of ymap placement files, and multiple texture dictionaries. Each ytyp must have its own DLC_ITYP_REQUEST entry. When installing a pack like the NYC or Miami Ghetto maps, carefully read the included installation instructions, as these packs often specify a required sv_enforceGameBuild value and a recommended load order position.

• Extract the resource folder into your server's resources directory.
• Add every .ytyp file as a separate DLC_ITYP_REQUEST data_file line in fxmanifest.lua (most packaged maps have this pre-configured).
• Ensure the resource in server.cfg in the correct position.
• Set sv_enforceGameBuild in server.cfg if the pack requires it.
• Restart the server fully — do not attempt a resource restart for map resources, as the streaming data must be loaded at server start.

Troubleshooting: Invisible or Missing Map Objects

If your map installs without errors but objects are invisible or missing in-game, work through this checklist systematically.

1. Verify every .ytyp file has a corresponding DLC_ITYP_REQUEST data_file entry in fxmanifest.lua.
2. Confirm this_is_a_map 'yes' is present in fxmanifest.lua.
3. Check that the resource is listed with ensure in server.cfg and appears in the F8 console resource list.
4. Check the server console and F8 client console for streaming errors referencing unknown archetype names — these point to missing or misnamed ytyp registrations.
5. Confirm sv_enforceGameBuild is set to the value required by the map, and that all clients are on that build.
6. Verify the .ybn collision file is present and named correctly — a map can be visually present but passable (no collisions) if the ybn is missing.
7. If only textures are missing (grey/pink models), check that the .ytd texture dictionary is in the stream/ folder and matches the reference name inside the .ydr.
8. Try teleporting directly to the map coordinates using a command — sometimes the issue is the camera spawn point being far from the map location, not an actual streaming failure.

Collisions, LODs, and Performance

A well-optimized custom map includes LOD (Level of Detail) models — lower-polygon versions of buildings and objects that render at distance, reducing GPU load. LOD files typically follow the naming convention _lod or _slod appended to the base model name and have their own ytyp archetype entries. If your server has frame rate issues near a custom map, the most common causes are missing LOD models (forcing the engine to render full-detail geometry at all distances) and uncompressed or oversized texture dictionaries.

Installation Checklist Summary

• All map files (.ydr, .ytd, .ybn, .ymap, .ytyp) are in the stream/ folder
• fxmanifest.lua contains fx_version 'cerulean' and game 'gta5'
• this_is_a_map 'yes' is present in fxmanifest.lua
• Every .ytyp file has a data_file 'DLC_ITYP_REQUEST' line in fxmanifest.lua
• Resource is ensured in server.cfg in the correct load order position
• sv_enforceGameBuild is set if the map requires a specific DLC build
• Server was fully restarted (not just the resource) after installation
• F8 console and server console show no streaming or archetype errors

Ready-to-Install Map Packs from CRM Development

If the installation process feels overwhelming or you want to skip straight to a working result, CRM Development's map packs — including the NYC city grid and the Miami Ghetto/coastal district — are packaged as ready-to-install FiveM resources with pre-configured fxmanifest.lua files, correct ytyp registrations, and detailed installation guides. Every pack is tested against current FiveM builds and includes support for any setup questions. Drop the folder in, add one line to server.cfg, and your server has a new world to explore.