Installing a FiveM MLO is usually straightforward: download the resource, put it in the right folder, start it from server.cfg, and check the interior in-game. A lot of install problems come from missing ensure lines, wrong folder nesting or forgotten dependencies, not from the map itself. This guide walks through a clean install path that works for typical map resources on ESX, QBCore and standalone servers.
When you need interiors to install in the first place (hospitals, mechanic shops, houses and other FiveM maps), browse the digital downloads at FiveM MLOs.
What you need before you start
- Server files with access to the resources folder and server.cfg
- A purchased (or otherwise licensed) MLO package as a zip/rar
- Ability to restart the server or start/stop resources
- Optional but useful: txAdmin or your host panel, and a second account to test as a player
Map/MLO packages are usually framework-agnostic. Job scripts that use the location (EMS, mechanic, housing) may still be ESX- or QBCore-specific, so install those separately and match versions carefully. No server yet? Start with our guide on how to make a FiveM server.
Step 1: Download and unpack the MLO
- Complete checkout and open your account downloads (or order email if your vendor uses that).
- Download the archive to a safe folder on your PC or host.
- Extract it. You should see a resource folder that contains something like fxmanifest.lua (or __resource.lua on older packs), plus stream and sometimes meta or audio folders.
Common mistake: extracting so you get resources/my-mlo/my-mlo/… (double nest). The folder you ensure must be the one that directly contains the manifest.
Step 2: Place the resource on the server
Copy the resource folder into your server’s resources directory. Many hosts use a structure like:
resources/
[maps]/
your-mlo-name/
fxmanifest.lua
stream/
…
Using a [maps] or [mlos] group folder is optional but keeps the tree tidy. The important part is a single, correctly named folder with a valid manifest at the top level of that resource.
Step 3: Ensure the resource in server.cfg
Open server.cfg and add a start line. Examples:
ensure your-mlo-name
Or, if you use a group folder and prefer starting the whole group:
ensure [maps]
Prefer ensuring the specific resource name while you test. It makes failures easier to spot in the console.
Order tips:
- Start map/MLO resources before scripts that teleport players into those interiors
- If the product page lists a required dependency (e.g. a base map or asset pack), ensure that dependency first
Save server.cfg when you are done.
Step 4: Restart and watch the console
Restart the server (or start the resource from txAdmin / your panel). In the console, look for:
- The resource starting without errors
- Missing file or manifest parse errors
- Asset/stream warnings that repeat every tick (investigate those)
If the resource fails to start, fix the error before you hunt for the interior in-game. A map that never started will still look like “vanilla” GTA.
Step 5: Test in-game
Join the server and go to the location the MLO replaces or adds:
- Walk every entrance, stair and elevator you care about
- Check collisions (floors, counters, garage doors)
- Spot-check lighting and major props
- If you use housing, mechanic or EMS scripts, run one full job loop in the new space
Bring a second player if possible. Some collision and streaming issues only show under load.
Extra checks if you run txAdmin
These take a few minutes and save a lot of guessing later:
- Back up first. Copy server.cfg and your resources folder before you add anything. If the server lives in Git, commit first so you can roll back in one step.
- Keep the resource name simple. Lowercase, no spaces, no brackets or special characters: pd_mission_row works, “Mission Row PD (new) FINAL” causes trouble. The name in your ensure line has to match the folder exactly.
- Use the CFG Editor and a full restart. In txAdmin, add the ensure line in the CFG Editor, save, then restart the whole server from txAdmin instead of starting the one resource from the live console. Players who are already online when a map starts may need to reconnect before it shows up properly, and a full restart takes that out of the equation.
- Read the first red error. If the server won’t come up, scroll the txAdmin live console to the first red line after the restart. Later errors are often side effects of that one. It is usually a missing dependency or a typo in the resource name.
- Check day and night. Change the time with your admin menu and look at the interior in daylight and at night. Then stand still for a minute and make sure textures stay sharp.
- Run resmon. Open the F8 console, type resmon 1, and compare the numbers inside and outside the building. A plain map resource should sit close to 0.00 ms. If something spikes when you walk in, it is usually a script tied to that location, not the map.
- Test on older PCs. FiveM is PC only, and texture loss or late-loading walls show up first on lower-end machines. Ask a couple of players with older PCs to walk through before you announce the new location.
Troubleshooting quick fixes
| Symptom | Likely cause | What to try |
|---|---|---|
| Interior still vanilla | Resource not ensured or failed to start | Check console; verify folder name matches ensure |
| Invisible walls / fall-through | Incomplete collision or wrong stream files | Re-extract archive; confirm you didn’t drop files |
| Crash on approach | Heavy props / conflict with another map | Disable other maps in the same area; test alone |
| Script markers in wrong place | Job coords still point at old interior | Update script coordinates to the new MLO |
| Works for you, not for others | One-sided cache / didn’t restart fully | Full server restart; players clear cache if needed |
Still stuck? Check the product page for install notes, then contact the store’s Discord or support with your resource name, framework (ESX / QBCore / standalone), and the exact console error.
After install: keep the city maintainable
- Document which MLOs you run and where they sit in the folder tree
- Avoid stacking two maps that edit the same shell (e.g. two Pillbox replacements)
- Update one major interior at a time so rollbacks are simple
- Keep purchase receipts and download links, because you will need to reinstall at some point
Soft next step: pick interiors worth installing
A clean install process only helps if the map fits your server. If you are still choosing locations, start with high-traffic needs: a FiveM hospital MLO, a mechanic bay and a few houses, then expand. The catalogue at FiveM MLOs is built for digital delivery: pay with PayPal or card, download from your account once the payment clears, then follow the steps above.
That is the whole loop: buy a clear listing, install with a correct ensure, test collisions, and only then wire job scripts into the new interior.