The FiveM scripts every server actually runs
33 resources, what each one is for, how to install it, where its real documentation lives, and the mistake people make with it. We build maps for these servers, so we run this stack ourselves. Repository figures were read on 2026-09-22; the documentation links go to each project’s own site, not to a copy of it.
The 2026 starting stack
If you are building a roleplay server today and do not want to spend a week comparing options, this is the combination the rest of the ecosystem assumes you are running. Each row links to the full write-up.
| Role | What to run | Why |
|---|---|---|
| Server manager | txAdmin | Bundled with the artifacts. Recipes, restarts, bans, console. |
| Database | oxmysql | Prepared statements by default, with a shim for old mysql-async scripts. |
| Framework | qb-core or es_extended | QBCore for a new server, ESX if your script library already targets it. |
| Library | ox_lib | Menus, notifications, progress bars, zones and callbacks in one dependency. |
| Inventory | ox_inventory | Per-slot metadata, durability and weapons as items. |
| Interaction | ox_target | Third-eye targeting with job, group and item filtering. |
| Zones | ox_lib zones, or PolyZone | PolyZone is still required by older scripts that import it directly. |
| HUD | ps-hud | Player-configurable status rings, speedometer and minimap frame. |
| Voice | pma-voice | Runs on the Mumble server FXServer already hosts. Nothing to install. |
| Appearance | illenium-appearance | Character creator, clothing, barber and tattoo shops with framework bridges. |
The full directory
Search by name, by category or by what you are trying to do. Write-ups marked with another domain live on one of our sister sites — the weapons shop covers inventories and frameworks, the loading screen builder covers server infrastructure and NUI — because each one is written by the people who work with that half every day.
Framework
The original FiveM roleplay framework, still running a very large share of live servers — jobs, money, society accounts and a huge script catalogue.
Overextended's own framework: small, strict and built around the rest of the ox stack rather than around a legacy player object.
The roleplay framework most new FiveM servers are built on, with the largest modern script ecosystem and a one-click txAdmin recipe.
A maintained fork of QBCore rebuilt on ox_lib and ox_inventory, with typed exports, semantic versioning and a much cleaner core.
The oldest of the roleplay frameworks still in circulation, built around a permission and group model rather than a job string.
Inventory
The slot-based inventory most new FiveM servers start with, with first-class support for addon weapons, durability, metadata and shops.
QBCore's own inventory: the default on every stock QBCore server and still the most widely installed inventory in the ecosystem.
Library
A compatibility layer that lets one script run on ESX, QBCore, Qbox and ox_core without a fork per framework.
The shared library half the modern FiveM ecosystem depends on: menus, notifications, progress bars, zones, callbacks and a cache.
The shared dependency behind the Renewed Scripts range — banking, vehicles, weapons and the rest of that ecosystem.
Interaction
The original FiveM third-eye targeting resource, and the ancestor of both qb-target and ox_target.
The third-eye interaction system most modern scripts target: look at a thing, get a menu, click an option.
QBCore's third-eye targeting system, and the export signature a very large number of existing scripts are written against.
Zones
The zone library that taught FiveM to think in shapes: polygons, boxes, circles and entity zones with enter and exit events.
Database
The original FiveM MySQL wrapper: still installed on a very large number of live servers, no longer the right choice for new code.
The MySQL wrapper the modern FiveM stack runs on: promise-based, prepared-statement aware and a drop-in replacement for mysql-async.
HUD
World
Door locking for every door on the map, configured from an in-game menu instead of a config file full of coordinates.
A small, dependency-light fuel system: petrol stations, jerry cans, electric charging and per-class consumption.
Jobs
A police mobile data terminal: reports, profiles, warrants, BOLOs and a dispatch map, as a modern React interface.
Appearance
The character creator and clothing shop most roleplay servers run: a full appearance editor with framework bridges and a modern UI.
Admin
An in-game admin menu with ace-based permission tiers — the usual choice when txAdmin's web panel is not enough and vMenu is too much.
The web panel bundled with every FXServer build: process management, recipes, players, bans, scheduled restarts and live console.
The standalone admin and player menu that freeroam, drift and deathmatch servers are built on — no framework required.
Voice
The default proximity voice resource on most roleplay servers: proximity talk, radio channels, phone calls and intercom, on Mumble.
The TeamSpeak-backed voice system serious roleplay communities use for radio-heavy play — better audio, richer radio, more setup.
Phone
The open-source FiveM phone: messages, calls, Twitter, marketplace, camera and a plugin API, built as a modern React NUI application.
Audio
Positional audio from URLs and YouTube: car radios, boomboxes, club systems and anything else that has to play sound at a place in the world.
Discord
Reads a player's Discord roles on the server and turns them into FiveM ace permissions — the basis of most whitelists and donor perks.
Utility
The official Cfx.re resource for taking a screenshot of the game and uploading it — the backbone of every in-game camera, report and evidence system.
Core
The official base resource set every FiveM server starts from: mapmanager, chat, spawnmanager, sessionmanager, hardcap and friends.
Tooling
Lua type definitions for the ox stack and the FiveM natives — autocompletion and type checking in your editor.
Questions people ask before picking a stack
What scripts does every FiveM server need?
Which FiveM framework is the most used in 2026?
Do these scripts work with a custom minimap?
What is the difference between ox_lib and PolyZone?
How do I know which version of a resource I am running?
Can I run two inventories or two targeting systems at once?
None of this changes the map
Every resource on this page leaves the minimap alone — they draw blips on it, they never replace it. The picture underneath is a streamed texture, and it is the one part of the screen that is entirely yours.