Framework Compatibility
ESX, QBCore, QBox, or standalone, pick the right substrate before you write a line of code
The framework you choose decides 80% of every architectural decision after it. This hub compares the four FiveM substrates that matter in 2026, links to a deep dive on each, and walks you through every head-to-head pair so the choice is made with the real trade-offs in front of you.
Framework matrix
| Framework | Player API | Default inventory | Database | Academy |
|---|---|---|---|---|
| ESX (Legacy + Modern) Largest catalog | ESX.GetPlayerFromId(source) → xPlayer | esx_inventoryhud or ox_inventory | mysql-async (legacy) → oxmysql (modern) | Full |
| QBCore Framework Modern standard | QBCore.Functions.GetPlayer(source) → Player | qb-inventory or ox_inventory | oxmysql (canonical) | Full |
| QBox (qbx_core) Fast-growing | exports.qbx_core:GetPlayer(source) → Player | ox_inventory (required) | oxmysql (required) | Full |
| Standalone (no framework) Specialized | GetPlayerName(source), custom registry as needed | build your own or pull in ox_inventory standalone mode | oxmysql or raw MySQL driver, your choice | Partial |
Per-framework deep dives
ESX (Legacy + Modern)
One of the largest FiveM ecosystems and script catalogs, classic xPlayer pattern.
Released 2017 · esx-framework org (GitHub: esx-framework)
QBCore Framework
Modern, opinionated successor to ESX, strong community, large script catalog.
Released 2021 · QBCore Framework organization
QBox (qbx_core)
Performance-first QBCore fork, ox_lib + ox_inventory required, leaner core.
Released 2023 · Qbox Project
Standalone (no framework)
Direct CFX natives + chosen libraries, maximum control, maximum responsibility.
Released 2014 · n/a (CFX natives only)
Head-to-head comparisons
When you're narrowed to two candidates, these pages walk through the decision with real trade-offs (not vibes).
Common questions
- Which FiveM framework should I pick in 2026?
- ESX if you have a script catalog you can't easily port. QBCore for a modern, opinionated start with broad ecosystem support. QBox for a greenfield server wanting the leanest, ox-library-enforced base. Standalone for single-purpose servers. The /compatibility/<a>-vs-<b> pages walk through the trade-offs in detail.
- Does FiveM Coach by Quasar support all four?
- Yes, ESX, QBCore, and QBox are first-class targets for the Developer path and Elite weekly code review. Standalone Lua, NUI, and ox_lib patterns are framework-agnostic and covered by the same curriculum.
- Can I switch frameworks later?
- Technically yes, but cross-family migrations (ESX ↔ QBCore, ESX ↔ QBox) are multi-week efforts because the player object, event names, inventory schema, and metadata patterns all change. Pick well now to avoid that bill later.
- Are these the only FiveM frameworks?
- These are the four with meaningful 2025-2026 production share. vRP exists historically but has lost active community attention; bespoke in-house frameworks exist on large RP servers but aren't broadly available.
Need help picking, or porting?
FiveM Coach by Quasar is coaching, not just content. Book the free assessment and we'll route you to the framework that actually fits your project, team, and timeline.