10 Must-Have FiveM Scripts for RP Servers (2026)

Starting a new server and not sure what to install? Or running an existing server that feels like it’s missing something? Here’s my list of scripts every RP server needs — not a marketing piece disguised as a guide, but the actual resources I’d install if I were starting from zero today.

I’m splitting this into “you literally can’t run a server without these” and “these are what separate a good server from a forgettable one.”

The Non-Negotiables

1. oxmysql

What it does: Handles all communication between your scripts and your database.

Why you need it: Everything stores data — player inventories, vehicles, houses, money, jobs. Without a proper database connector, none of that persists. oxmysql replaced the old mysql-async and ghmattimysql connectors and it’s faster than both.

Cost: Free. GitHub.

Don’t even think about using an alternative. oxmysql is the standard and every modern script expects it.

2. A Framework (ESX Legacy, QBCore, or Qbox)

What it does: Provides the core systems — player management, jobs, money, items, interactions — that every other script builds on.

My pick: ESX Legacy. I’ve written about this in detail in my framework comparison, but the short version is: biggest ecosystem, most support available, and ESX Legacy fixed the performance issues that old ESX had. Can’t go wrong.

Cost: Free.

3. ox_lib

What it does: A shared library that provides optimized UI components (context menus, notifications, progress bars, input dialogs), utility functions, and performance-friendly alternatives to common patterns.

Why you need it: More and more scripts require ox_lib as a dependency. Even if your scripts don’t require it yet, installing it gives you access to better UI components and utility functions. It’s become the de facto standard library for FiveM development.

Cost: Free. GitHub.

4. An Inventory System

What it does: Manages items — picking up, dropping, using, trading, storing.

Options:

• ox_inventory (Free) — The gold standard right now. Clean UI, good performance, great drag-and-drop interface. Works with ESX, QBCore, and Qbox.
• qb-inventory — Fine if you’re on QBCore and want to stay in the QB ecosystem.
• Other payed inventories (Paid) — Popular premium option with more visual flair.

My pick: ox_inventory. It’s free, it’s maintained, it performs well, and it works with every framework.

5. pma-voice / Mumble VOIP

What it does: Proximity-based voice chat. Players talk to people near them, with support for phone calls, radio channels, and different voice ranges.

Why you need it: RP without proximity voice isn’t really RP. This is the thing that makes the experience feel real. pma-voice is the standard and it works out of the box.

Cost: Free. GitHub.

The Ones That Make Your Server Actually Good

6. A Phone Script

What it does: In-game smartphone with messaging, calls, Twitter/Instagram clone, banking app, GPS, etc.

Options:

• npwd (Free) — Solid React-based phone, open source, actively maintained.
• lb-phone (Paid) — Premium option with a polished UI and tons of features. Very popular.
• qs-smartphone (Paid) — Another premium choice with a different visual style.

A phone is where half of RP interactions happen — texting, calling, posting on social media. A good phone script dramatically improves immersion.

7. A Clothing/Appearance Script

What it does: Lets players customize their character’s appearance — clothes, hair, tattoos, accessories.

Why it matters: Character identity is core to RP. Players spend a surprising amount of time on this. A clunky clothing menu kills the experience.

Options:

• illenium-appearance (Free) — Fork of fivem-appearance with lots of community improvements. Works well.
• bl_appearance (Paid) — Premium option with a cleaner UI.

8. A Dispatch/MDT System

What it does: Gives police, EMS, and fire departments a computer terminal for managing calls, warrants, records, and reports.

Why it matters: Emergency services are the backbone of RP. Without a proper MDT, cops and medics are just running around with no information system. It makes law enforcement RP feel real and organized.

There are several options here from basic free CAD systems to full premium MDT suites. Pick one that matches your server’s complexity.

9. A Housing Script

What it does: Lets players buy, own, and customize properties with interior access, storage, and door locks.

Why it matters: Owning a house gives players a reason to stay on your server. It creates attachment. It’s also a money sink that keeps your server’s economy healthier.

10. Quality-of-Life Scripts

This is the catch-all category — the little things that add up to a polished experience:

• A loading screen — First thing players see. Make it look good and load fast.
• Multicharacter — Let players have multiple characters. Nearly every RP server does this now.
• HUD — Speed, health, armor, hunger/thirst. Keep it minimal and clean.
• Garage system — Store and retrieve vehicles. Sounds simple but a bad garage script is infuriating.
• Death/respawn system — What happens when you die? EMS notification, bleedout timer, respawn at hospital. We built a premium bodybag system for servers that want realistic death RP.

What to Skip

Stuff I see on servers that usually does more harm than good:

• Excessive vehicle packs — 200 addon cars that tank client performance. Pick 20-30 good ones.
• Scripts with overlapping features — Two different notification systems, three inventory scripts installed at once. Pick one and remove the rest.
• Complex drug systems on day one — You need players before you need a drug empire. Start simple, then upgrade to a polished drug system when you have an active playerbase.
• Anti-cheat overkill — Running three anti-cheat scripts that conflict with each other and false-flag legitimate players.

How to Evaluate Script Quality

Before you install anything — free or paid — check these things:

1. When was it last updated? Scripts abandoned for 6+ months often break with framework updates.
2. What’s the resmon impact? Good scripts will advertise their performance. If they don’t mention it, test it yourself.
3. Is there documentation? No docs = no support = you’re on your own when it breaks.
4. What framework versions does it support? “Works with ESX” might mean old ESX, not ESX Legacy.
5. Check reviews and community feedback. FiveM forums and Discord communities will tell you if something is broken.

Wrapping Up

You don’t need 200 scripts to run a good server. You need the right 20-30, properly configured, with good performance. Focus on the core experience first, then add niche scripts once you have players and know what they actually want.

Need scripts that work out of the box with solid performance? Check our store — everything supports ESX, QBCore, and Qbox with auto-detection.

Want to start with free resources? Grab some from our collection.

Still figuring out your setup? Come ask on Discord — happy to help you plan your server’s resource list.