FiveM & RedM Tools

fxmanifest.lua Generator

Every FiveM and RedM resource needs an fxmanifest.lua in its root, the manifest that tells the server which fx_version and game to target, the resource metadata, and which shared, client and server scripts to load. Fill in the fields below and copy a valid manifest. Everything runs in your browser, with no login.

Example resource, ready to edit

Header & metadata

The fx_version and game come first, then optional metadata. Blank metadata fields are left out of the manifest.

Scripts & files

One path per line. Globs like client/*.lua are allowed, as are @resource/file.lua references. Empty lists are omitted from the manifest.

fxmanifest.lua output
fx_version 'cerulean'
game 'gta5'

name 'my-resource'
author 'you'
version '1.0.0'
description 'A short description of what this resource does.'

lua54 'yes'

shared_scripts {
    '@ox_lib/init.lua',
    'shared/*.lua',
}

client_scripts {
    'client/*.lua',
}

server_scripts {
    'server/*.lua',
}

ui_page 'html/index.html'

files {
    'html/index.html',
}

dependencies {
    'ox_lib',
}

Save this as fxmanifest.lua in the root of your resource folder (next to your client, server and shared directories). Empty sections are skipped automatically.

How fxmanifest.lua works

fx_version and game are the two lines every manifest needs. fx_version selects the manifest feature set (use cerulean, the current version) and game declares the target, gta5 for FiveM or rdr3 for RedM. To support both, this tool emits a games { 'gta5', 'rdr3' } block instead.

Metadata (name, author, version and description) is optional but recommended. It shows up in server tooling and helps you and your players tell resources and their versions apart.

Script lists control what actually runs. shared_scripts load on both sides, client_scripts on the game client and server_scripts on the server. Files load top to bottom, so list configs and libraries before the code that depends on them. Use ui_page plus a files entry for any NUI/HTML interface, and dependencies to require other resources start first.

Tip: any asset referenced by NUI (HTML, CSS, JS, images) must also be listed under files, or the client will fail to load it even though ui_page points at it.

FAQ

fxmanifest.lua, explained

What is fxmanifest.lua?+

fxmanifest.lua is the resource manifest every FiveM and RedM resource needs. It sits in the root of the resource folder and tells the server how to load that resource: which fx_version and game it targets, its metadata, and which shared, client and server scripts (plus any UI files) to run. Without a valid fxmanifest.lua (or the older __resource.lua) the server will not recognise the folder as a resource, so it never starts.

What fx_version should I use?+

Use cerulean. It is the current, recommended fx_version and enables the latest manifest features, so almost every new resource should target it. bodacious and adamant are older versions kept for backwards compatibility with legacy resources. Unless you are maintaining something old that depends on their behaviour, pick cerulean.

What is the difference between shared, client and server scripts?+

server_scripts run only on the server and are where you keep trusted logic, database access and anything a player must never see or tamper with. client_scripts run on each player's game client and handle rendering, input, NUI and local gameplay. shared_scripts load on both sides. Use them for config tables, shared functions and libraries like ox_lib that both the client and server need. Files load in the order listed, so put configs and libraries before the code that uses them.

Can one resource target both FiveM and RedM?+

Yes. A single manifest can declare support for both games with a games block (games { 'gta5', 'rdr3' }) instead of a single game line. Select the "Both (gta5 + rdr3)" option here to emit that block. In practice most resources still target one game because the native functions and assets differ, but shared libraries and framework code often support both.

Is it free?+

Yes. This fxmanifest.lua generator runs entirely in your browser with no login, no account and nothing sent to a server. Fill in the fields, copy the output, save it as fxmanifest.lua in your resource root, and you are done.

More Digital Den tools

Browse the rest of our free, no-login utilities and bots.

All tools →