Install FiveM resourcesUpload scripts, include them and read errors

Published on September 2, 2026 · last updated on November 4, 2026

What a resource is

A resource is simply a folder in the resources directory. For FXServer to recognize it as one, it must contain an fxmanifest.lua - this file describes which scripts run on the server, which on the client and which files are delivered along with it.

If this file is missing or faulty, the resource does not even show up at startup. That is the first thing to check when a freshly uploaded resource refuses to start.

Uploading

You upload resources via WebFTP in the browser or with an SFTP client. For individual scripts, the browser is enough; as soon as vehicles or MLOs with hundreds of files are involved, an SFTP client is the much faster choice.

Two rules save a lot of searching:

• No folder inside the folder. After unpacking, the actual resource folder often sits inside another directory of the same name. The fxmanifest.lua has to be directly in the resource folder, not one level deeper.
• No spaces or special characters. Folder names made of lowercase letters and underscores save you trouble, because the name appears exactly like that in the server.cfg.

Category folders with square brackets

Folders such as [esx], [jobs] or [vehicles] are not resources but containers. FXServer looks inside and treats every subfolder as a resource of its own. The gain: instead of thirty lines in the server.cfg, one is enough.

ensure [jobs]

Category folders can be nested, but not too deeply. One level by purpose - framework, jobs, vehicles, maps - is enough for almost every project and keeps the load order manageable.

Starting and order

An uploaded resource does nothing at first. It needs its ensure line - and that has to be in the right place. The order in the file is the start order:

1. Database connector
2. Framework core, for example ESX or QBCore
3. Libraries and modules that other scripts access
4. Jobs, vehicles, HUDs and everything else

While the server is running, you can also start, stop or restart a resource via the console - handy for testing, because you do not have to restart the whole server. It only becomes permanently active through the entry in the configuration, though.

Reading the console

The live console in the web interface is your most important tool when installing. These are the messages you encounter most often:

• Resource not found. The name in the server.cfg does not match the folder name, or the folder sits one level too deep.
• Error in the fxmanifest. Usually a typo, or a file that is listed in the manifest but missing.
• Dependency missing. The script expects another resource that has not started yet - check the order.
• Database error. The matching .sql was not imported, see set up the database.

A habit worth adopting: install one resource after another and restart in between. Anyone who adds ten scripts at once and then sees an error searches considerably longer.

Resources from third-party sources

A large part of the FiveM world consists of scripts by third parties - free or paid. A few habits that pay off:

• Check the framework version. A script for an older ESX version often does not run on a newer one.
• Read first, then start. A quick look at the files shows whether a resource phones home or requests rights it does not need.
• Back up beforehand. A script that restructures tables at startup cannot be undone without a database export.

And after every larger extension, it is worth looking at the load: the number of resources is rarely the problem, but a single badly written one often is - see improve server performance.

Frequently asked questions