Skip to content

The FiveM collection

FiveM scripts, MLOs and vehicles. For QBCore, ESX and Qbox.

Buy one resource at a time, from single-purpose scripts through custom interiors and vehicle packs to complete framework builds. Download links go to the address you enter at checkout.

In the spotlight
Premium Vehicle Pack FiveM [5 Cars]$25.00

Start with the right foundation

Find FiveM scripts for your framework

Building a new roleplay server or expanding an established city? Choose your framework first, then explore scripts that serve a specific purpose. Use the compatibility tags to make a shortlist and the individual listings to check the details of each resource.

QBCore scripts

Add a new job, business or everyday utility to your QBCore server. Start with the activity you want players to have, then compare the controls and configuration options. Check which inventory, targeting and notification resources the script expects before adding it to your existing setup.

Explore QBCore scripts

ESX scripts

Browse ESX resources for services, player interactions and the server economy. A framework label is the first check: the supported ESX version and any extra dependencies still matter. Look through the product description for installation steps and integrations you will need to configure.

Explore ESX scripts

Qbox scripts

Use the Qbox collection to narrow your search to listings tagged for your framework. Compare their documented requirements with the resources already on your server. Pay particular attention to inventory and job integrations when choosing an addition to an established Qbox build.

Explore Qbox scripts

Give your city something to do

FiveM jobs and business scripts

Build the routines that keep a roleplay server moving: police duties, ambulance calls, workshop visits and player-run businesses. Choose a job script around the experience you want to offer, whether that is a focused public service or a business players can manage. Compare the available interactions, configuration options and required integrations before expanding the economy.

Make room for the next chapter

FiveM MLOs, maps and vehicle packs

A new workshop or restaurant gives players a destination; a vehicle pack gives them more ways to get there. Browse interiors alongside vehicle collections when planning a new district or business. Read each listing for its location and included assets, and check for conflicts with maps you already use. Job logic and business systems may need to be purchased and configured separately.

Compare a more complete starting point

Complete FiveM server packages

If you are starting a new community, compare a full framework package with building your own collection of individual scripts. Look at the included resource list, supported framework version and setup instructions. Check which systems you will still need to add and how much configuration your server concept requires. Choose a package for its contents and requirements, rather than its script count alone.

Make the next update manageable

Start free. Upgrade where it matters.

Connect the experience

What could you add next?

Plan around a player activity and explore the resources that could support it. These are suggestions to purchase individually, with their own compatibility requirements and installation steps.

The people behind the resources

Explore creators

Browse a creator collection when you want to see more resources from the same developer. Compare their available scripts and look for the features your server needs. Each product listing has its own compatibility and setup details.

A little server-side reading

From the blog

All articles

Read practical guides to FiveM development, configuration and resource selection. Use the articles to understand how your setup works and prepare for the next change, whether you are adjusting a script or adding a new system.

Build with a clear plan

How to choose your next FiveM resource

A useful server update starts with a specific goal. Compare the gameplay you want to add, the resources you already run and the work needed to connect them. This approach helps you choose between a small utility, a larger system and a complete framework package.

Start with a player activity

Write down what you want players to do: run a workshop, respond to a call, operate a shop or explore a new location. Use that activity to compare the features on each listing. It makes it easier to spot an unnecessary overlap with something your server already provides.

Read the resource checklist

Check the full setup

Review the framework version, dependencies and installation notes alongside the price. A script might need an inventory, shared library, map or another resource to provide the experience shown. Check which parts are included, which you already own and which would be an additional purchase.

Understand dependencies and load order

Test one change at a time

Keep a copy of your current configuration and try the new resource on a separate test server. Follow the supplied installation instructions, then check the player interactions your community will actually use. Introduce additional scripts gradually so you can identify the source of any conflict.

Plan a safer script update

Before you choose

FiveM resource buying questions

Use these answers to narrow your search, then check the details on the product page. For a question about a specific listing or purchase, visit Help.

Visit Help
How do I choose between QBCore, ESX and Qbox scripts?

Start with the framework installed on your server and use its collection to shortlist resources. Check the supported version, required libraries and integrations in each product description. A matching framework tag helps narrow the search, but the installation notes tell you what else the resource needs.

Will every QBCore resource work on Qbox?

Qbox supports many QBCore resources through its compatibility layer, but there are exceptions. Scripts that rely on unsupported core behaviour or direct access to internal data can need changes. Use the Qbox tags as a starting point and confirm the requirements of the individual resource.

Read the official Qbox compatibility FAQ
Does a FiveM MLO include the business or job script?

An MLO provides an interior or location. The gameplay systems for running a restaurant, workshop or department may be separate resources. Check the included files and description before buying. If you need a working business, plan for both the location and the script that manages its interactions.

Should I buy individual scripts or a complete server package?

Individual scripts let you change a specific part of an existing server. A complete package is worth comparing when you are starting a new build and want to review a collection of included systems together. Check the full contents, configuration work and dependencies against your own server plan.

Can I start with free FiveM resources and add paid upgrades later?

You can plan a build around both free and paid listings. Evaluate each resource for its features and requirements, then add paid functionality where it serves your project. A zero-priced resource can still have dependencies, so check the complete setup before deciding what the update will cost.

What should I check about source access and updates?

Look for the source-access terms, editable configuration and update information on the product page. These can differ between resources. If your plan involves changing how a script works, establish which files you can edit and what support is available before making the purchase.

Compare escrow and source access

Where to start on a QBCore, ESX or Qbox server

A FiveM catalogue is easy to browse and hard to buy from, because the decision in front of you is rarely which script looks best in its trailer. It is which shelf your server belongs on. So what follows is routing, not another grid. Each section names the shelf that answers one question, and the guide worth reading before you spend anything on it.

Your framework decides most of the catalogue

Almost every resource badged for QBCore carries a Qbox badge too. QBCore and Qbox share enough that creators ship a single download for both, so the QBCore and Qbox shelves end up looking nearly identical to each other. That is accurate rather than lazy. ESX is the one that goes its own way. A good share of listings name QBCore and never mention ESX at all, so if ESX is what you run, start on its own shelf instead of filtering a QBCore listing and hoping. Moving between the big frameworks is a project in itself. The ESX to QBCore migration guide covers what survives the trip.

A new server buys jobs before it buys anything else

An empty city gives players nothing to do. That is why job scripts are the largest group in this catalogue: police, ambulance, mechanic, delivery, mining, and the player-owned businesses that keep a district busy through a whole session. Close the obvious gaps from the free shelf first. A free HUD, a chat theme and a couple of jobs are enough to make a fresh build feel inhabited, long before there is any money coming in to spend on it. First install? Read the QBCore install guide, then the beginner's guide to installing scripts, in that order.

An established city buys places, not systems

Once the systems work, what a server usually lacks is somewhere to use them. MLOs are the custom interiors that turn a locked door into a police station, a hospital or a working garage, and they care about stream limits rather than about your inventory. Car packs follow the same rule, with a much larger download attached. Add either kind one at a time. Watch what happens. A heavy interior and a heavy vehicle pack cost frames in a way a job script does not, and the notes on running several heavy resources at once explain what to measure.

Starting from nothing is a different purchase

If there is no server yet, assembling one resource at a time is the slow route. The ready-made framework servers here arrive as complete builds, with jobs, economy and interiors already wired together. That is a different decision from buying a single script, at a different price to match it. Bundles sit in between: a themed set of resources priced to be bought together, built around one job or one corner of a city. Settle the hardware first, though. The specs you rent set the ceiling on everything you install above them.

Buying several things from one studio pays off later

Resources from a single studio share a config layout, a notification style and usually a boss menu. A city assembled from a new creator every time asks your players to relearn the controls with each addition. Most studios selling here also publish free work, which turns the free release into a cheap audition. Open the config. See whether the code is laid out for somebody who is not the author, and expect the same habits in the paid resource. The collection index lists every studio on the store alongside the framework and type shelves.

Read the badge, not the title

A product name is written to be found. The framework badge on the card comes from the compatibility list its creator filled in, so believe the badge where the two disagree. The dependency line in the description matters just as much: a script built against one inventory fails on a server running another, and it fails looking like a broken resource rather than a mismatch. The vetting checklist is the long version. Escrow versus open source decides what you are allowed to edit afterwards, and it is the one part of the purchase you cannot revisit.