Skip to content

FiveM Cars for QBCore & ESX

Short answer: yes. Add-on cars are framework-agnostic. Here's why, and how to install them on any setup.

Are FiveM cars framework-specific? No.

This is the single most common pre-purchase question, and the answer is reassuring: add-on vehicles are not tied to QBCore, ESX or any other framework. A FiveM car is a streamable game asset β€” a model, its textures, handling and metadata β€” that the game client loads regardless of which scripts your server runs on top. Frameworks like QBCore and ESX handle gameplay systems (jobs, economy, inventory, garages), not whether a car model exists. So a vehicle that works on one works on all of them, and on standalone servers with no framework at all.

Where frameworks come in is the layer above the car: a garage script decides who can store and retrieve a vehicle, a dealership script decides who can buy it, and a keys script decides who can start it. Those are framework features. The car itself just needs to be streamed.

How to install an add-on car on any server

The process is identical across frameworks. Unzip the download, drop the resource folder into your server's resources directory, add it with an ensure line in your server.cfg, and restart. The model is now streamed and available to spawn by its spawn name β€” which is listed on every product page and in the included readme. From there you wire it into whatever framework systems you use: add it to your QBCore or ESX vehicle shop, register it with your garage, set a price, and you're done.

Because the car layer and the framework layer are separate, you never have to worry about buying the 'QBCore version' versus the 'ESX version' of a vehicle β€” there's only one version, and it works everywhere. If you later migrate from ESX to QBCore (or vice-versa), your cars come with you untouched.

Buying with confidence

Every Goodara vehicle and pack is a standard add-on resource: framework-agnostic, instant download, with lifetime updates and re-downloads. Whether you run QBCore, ESX, qbox or a bare standalone server, the install path is the same and the cars behave the same. That means you can pick vehicles purely on how they look and drive, not on a compatibility checkbox.

If you're still standing up your server or weighing frameworks, our guides on choosing between QBCore and ESX and on adding custom cars walk through the surrounding setup so the vehicles you buy here slot straight in.

See all

Keep browsing

Frequently asked questions

Do I need a different version of a car for QBCore vs ESX?

No. Add-on vehicles are framework-agnostic β€” there's a single version that works on QBCore, ESX, qbox and standalone servers. You only choose a framework version for scripts, not cars.

How do I add a purchased car to my QBCore or ESX dealership?

Stream the resource as normal, then register its spawn name in your framework's vehicle shop / dealership config with a price. The car layer and the shop layer are separate.

Will my cars still work if I switch frameworks later?

Yes. Because cars aren't tied to a framework, migrating from ESX to QBCore (or the reverse) leaves your add-on vehicles untouched β€” you only re-register them in the new framework's shop and garage.

More questions? Read the full FAQ or contact us.