ESX Framework: Origins, es_extended, and Overextended

ESX is one of the most widely deployed roleplay frameworks for FiveM. The name comes from "EssentialMode Extended" - it started as an extension of the older EssentialMode framework. This post covers what ESX is, what es_extended is, and how Overextended fits in, all sourced from the official ESX framework documentation and the project's GitHub repos.

What ESX is

From the official ESX framework documentation: ESX is "a roleplay framework for FiveM developed on top of EssentialMode (aka ES), thus commonly named ESX." The "X" in the name is the "Extended" part.

The core resource is named es_extended. Per the docs: "es_extended is the main script for the ESX Framework that handles all kinds of things, from registering commands, callbacks, money, jobs and can be extended upon easily using the functions it provides from other scripts."

The two main maintained branches

As of 2026, two organizations maintain active ESX forks on GitHub:

• ESX-Official (github.com/esx-framework) - the historical organization, hosting what is commonly called "ESX Legacy."
• ESX Overextended (github.com/esx-overextended) - a more modern, extensively re-architected fork.

What ESX Overextended changed

From the Overextended documentation: "Unlike esx-legacy, where only limited overrides were possible for player objects, the esx-overextended introduces extensive extendability, allowing developers to override existing methods, functions, and fields or even add new ones within the player class, the vehicle class, and the ESX object."

Specific additions called out in the Overextended documentation:

• Added modules for safe events, OneSync scope, and routing bucket
• Multiple group support with backward compatibility with ESX Legacy
• Reinstatement of the original ESX HUD
• The esx:getSharedObject event for loading the ESX object in external resources

What ESX gives you

At a high level, ESX provides the foundation that custom roleplay-server scripts build on:

• Player accounts (money, bank, jobs, gangs)
• Inventory (basic; many servers swap to ox_inventory for more)
• Vehicle ownership and garages
• Database integration (typically via oxmysql or mysql-async)
• An event-based extension model so resources can hook into player join, money change, job change, etc.

How vehicles fit in

From a vehicle creator's perspective, ESX itself does not change how a vehicle pack is built. The YFT/YTD/meta files are framework-agnostic. What ESX integrates with is the surrounding ecosystem - tuning shops, garage scripts, vehicle ownership, and price catalogs - which read from vehicles.meta and reference the model name you defined there.

Where to read further

The ESX framework documentation site at docs.esx-framework.org is the canonical reference for the Legacy branch's API. The Overextended documentation lives in its own org's repos and at overextended.dev.

Sources

• ESX Framework Docs: es_extended
• ESX Overextended GitHub: es_extended
• ESX-Official GitHub: es_extended (Legacy)