What is fxmanifest.lua?
fxmanifest.lua is the required manifest file at the root of every FiveM resource folder, declaring the resource's `fx_version` and `game` (the minimum fields), plus which files load as client, server, or shared scripts, its dependencies, metadata like author and version, and — for UI-based resources — its NUI entry point. FXServer parses this file before running any of the resource's code, so a missing required field or a syntax error prevents the resource from starting at all.
In one linefxmanifest.lua is the manifest file every FiveM resource must include, declaring the resource's target version, its scripts, dependencies, and metadata, which FXServer reads before executing any of the resource's code.
The longer answer.
Every FiveM resource is identified and loaded through its fxmanifest.lua, and FXServer validates this file before the resource's actual Lua, JavaScript, or C# code ever runs. The two fields every current resource needs are `fx_version` (the manifest format version, `'cerulean'` on current builds) and `game` (typically `'gta5'`, or `'common'` for resources shared with RedM) — a resource missing either produces a startup warning or error rather than silently working.
Beyond the minimum, the manifest declares which files run where: `client_script(s)` for code that runs on the player's game process, `server_script(s)` for code that runs only on FXServer, and `shared_script(s)` for files both sides load — typically config tables, locale files, and event-name constants. `lua54 'yes'` opts a resource into Lua 5.4 (integer division, bitwise operators, and better performance over the older default), and the dependency field names other resources this one relies on.
Metadata fields — `author`, `description`, `version` — don't change runtime behavior, but a missing `version` produces a console warning on modern FXServer builds, and a dated, incrementing version is how a serious seller's changelog and a buyer's installed copy stay in sync. Resources shipping a NUI interface add a `ui_page` pointing at the HTML entry point and a `files` block listing the web assets to package. Getting the manifest wrong is one of the most common reasons a resource fails to start at all — check it first when a resource won't load.
Common fxmanifest.lua fields
| Field | Purpose |
|---|---|
| fx_version | Manifest format version, such as 'cerulean' — required |
| game | Target game, typically 'gta5' — required |
| client_script(s) | Files that run on the player's client |
| server_script(s) | Files that run only on FXServer |
| shared_script(s) | Files loaded by both sides — config, locales, constants |
| dependency / dependencies | Other resources this one relies on |
| lua54 | Opts into Lua 5.4 when set to 'yes' |
| ui_page / files | NUI entry point and the web assets to package |
| author / description / version | Metadata; a missing version triggers a console warning |
Where this is covered in full.
People asking this also ask.
Where to go from here.
Published 2026-09-02 · Last reviewed 2026-09-02 · Vice Drip · All answers