Start with the original.
Bring your FiveM map ZIP, including its stream folder and resource files. MLO interiors and exterior maps are supported.
THE MAP WORKSHOP BETA
Keep the place.
Lose the excess.
Optimize your MLOs and exterior maps with measured texture savings and optional geometry LODs. Keep the layout you built your server around.
ZIP in. A verified copy out. No in-game script added.
Upload. Compare. Keep the version you like.
Analysis is free. Export costs 1 credit per map resource, or is included in an active Optimizer subscription. Review the quote before building.
Sign in →FROM ACTUAL MAP EXPORTS
Three corrected exports received positive owner feedback in FiveM. These figures measure files and asset data — not FPS.
| Test map | Less texture data | Fewer distant triangles* | Smaller ZIP |
|---|---|---|---|
| Apartment NY Vibe | 43.3% | 35.1% | 11.2% |
| Beach Mansion | 38.4% | 29.1% | 10.4% |
| Lombank Rooftop | 38.1% | 20.1% | 14.4% |
*Low-detail level of the models receiving new LODs. High-detail geometry retained. New LOD structures add approximately 9.0 / 15.6 / 2.0 MiB respectively. No FPS benchmark or universal saving is claimed.
A SIMPLE RESOURCE WORKFLOW
Bring your FiveM map ZIP, including its stream folder and resource files. MLO interiors and exterior maps are supported.
Keep the original resolution with Quality, or reduce eligible texture detail with Balanced or Performance. Add model LODs when useful.
Download the optimized ZIP and its report. Keep the original backup and test one version at a time on your server.
THE DETAILS MATTER
Texture data, distant geometry and archive weight are different costs. The report keeps them separate so you can choose a profile with the right trade-offs.
BEFORE YOU BUILD
A FiveM map optimizer processes map assets to reduce eligible texture data and file size. FiveMRides also offers optional distance-based geometry LODs for supported static models. Upload your original map ZIP, review the analysis, then download a separate optimized copy.
Yes. Upload a ZIP containing a FiveM map resource with YMAP or YTYP files, up to 512 MB. Supported YTD, YDR and YDD texture assets can be optimized. Optional geometry LOD generation currently supports eligible standalone static YDR models.
Quality preserves texture resolution and decoded pixels while compacting eligible opaque textures and repacking files. Balanced caps eligible textures at 2K. Performance uses up to 1K for main textures and 512 for verified normal or specular detail. Those smaller profiles can soften close-up detail. Geometry LODs are optional and change detail at a distance.
The optimizer preserves map placements, collision data, rooms, portals, scripts, manifests and resource filenames. High-detail geometry is retained when supported model LODs are added. Unsupported assets are kept rather than rebuilt. Always inspect the downloaded copy in FiveM before replacing an installed map.
No fixed FPS gain is promised. Lower-detail geometry can reduce distant rendering work, and smaller texture data may help memory pressure. Results depend on the scene and the computer. Added LODs also consume native resource memory. ZIP size, texture data, triangle counts and native allocation are reported separately; FPS requires an in-game comparison.
The tool cannot decrypt Asset Escrow or other protected assets. Unreadable or unsupported files are retained and listed for review. Use accessible original files you are authorized to modify.
No local 3D editor is required for this workflow. Processing runs on a worker, and the download keeps the FiveM resource layout. Optional LODs are stored in the supported models themselves, so this optimization does not add a runtime script to your map.
Analysis is free with an account. Export costs 1 credit per map resource, using the shared Studio wallet, or is included in an active Optimizer subscription. A ZIP containing several resources is quoted per resource before you confirm. Credits are charged only after the output ZIP is verified. Repeat downloads of the saved result do not charge again.
Back up the original resource, stop it, and install the optimized copy under its original resource name. Do not load both versions together. Restart the resource or server and inspect interiors, exterior views, glass, lights, collisions and distance transitions. Compare performance using the same route, camera and settings.
FIND THE RIGHT FIX
Identify texture weight and distant model detail, then compare the same scene before and after.
Read the MLO optimization guide →Separate player settings, resource problems and server-side asset costs before changing your map.
Fix FiveM texture loss →ZIP weight, texture data and native allocation are different measurements.
Read the oversized assets guide →For overlapping resources, inspect Map Fixer. To combine resources, see Map Merger. Optimizing textures is not the same as repairing collisions or merging maps.