- ESX
- Standalone
- QBCore
- vRP
Standalone Scripts
Standalone FiveM scripts are listed as running without ESX, QBCore or Qbox as the base framework. That suits features that never touch player money or jobs: notifications and text UIs, kill feeds, crosshairs, animation menus, weapon recoil and components, vehicle utilities such as speed limits, airbags and tire slashing, scoreboards, whitelists and small minigames. About half of the listings also carry an ESX or QBCore tag, usually for optional framework features.
Standalone Scripts – 10 resources
- ESX
- Standalone
- QBCore
- ESX
- Standalone
- QBCore
- Standalone
- ESX
- Standalone
- QBCore
- Standalone
- Standalone
- Standalone
- Standalone
- ESX
- Standalone
- vRP
Can't find the exact script? Generate it.
Describe a custom script. 3 free credits per day, up to 15 per calendar month; no card needed.
What standalone does and does not mean
The tag only says no roleplay framework is required. The script can still depend on another resource, such as a database library, a sound or voice system or a target resource, declared in its manifest (the fxmanifest.lua documentation describes dependency entries) or only in its install notes. Find out where it keeps its data, in a database table, a file or key-value storage, and whether an update can erase it.
How to choose
If you run ESX or QBCore and want the script tied to your money, items or jobs, prefer listings that also carry your framework’s tag; a purely standalone script has to handle those itself or not at all. If you run a custom base, the standalone tag is the one that matters. Either way, install one script at a time and test it as a player, as described in how to install a FiveM script, and go through the pre-purchase checklist before you buy. For the bigger choice, see FiveM frameworks compared.
FAQ
How can I tell a script is really standalone?
Search its readable files for es_extended, qb-core or qbx_core. QBCore resources get the core object through an export, documented in the QBCore documentation, so a hit means the script refers to that framework, possibly only in an optional bridge. Files protected by Asset Escrow cannot be searched this way; rely on the listing and install notes.
Can it use my ESX or QBCore money and jobs?
Only if the listing says it has a bridge or separate code for that framework. For multi-framework options, browse ESX scripts or QBCore scripts.
Are standalone scripts lighter?
Not by default. Performance depends on the code, not the tag, so measure it on your server.