Start

Framework Converter

Upload a FiveM resource and get it back on another framework: ESX, QBCore, Qbox or ox_core, in any direction.

What the Framework Converter does

The Framework Converter takes a FiveM resource written for one framework and rewrites it for another. You upload the resource, pick the framework your server runs, and get the converted resource back as a zip.

What is being translated during a conversion of esx_shops to QBCore: each framework construct with its kind, how often it occurs, the old call and what it becomes, hardest first. — A conversion from ESX Legacy to QBCore while it runs: every ESX construct it found, next to what it becomes.

It converts between four frameworks, in any direction:

ESX Legacy, the long-running standard with the shared object and xPlayer methods.
QBCore, with the core object and Player.Functions.
Qbox, the QBCore fork built on ox_lib and ox_inventory.
ox_core, the Overextended core with characters and groups.

The resource keeps its outside: command names, event names, exports, callbacks and item names stay exactly as they were. Other resources on your server that talk to it keep working without changes.

What you get

A finished conversion gives you four things:

Output	What it is
The resource	A zip with the converted resource folder, ready to put into resources.
Six checks	Files, Syntax, Leftovers, Calls exist, Contract and Wiring, each passed or failed.
A diff of every file	Each file before and after, line by line, on the result page.
`CONVERSION_REPORT.md`	Inside the zip: the checks, every decision the conversion took and what it could not check.

The resource
A zip with the converted resource folder, ready to put into resources.
Six checks
Files, Syntax, Leftovers, Calls exist, Contract and Wiring, each passed or failed.
A diff of every file
Each file before and after, line by line, on the result page.
CONVERSION_REPORT.md
Inside the zip: the checks, every decision the conversion took and what it could not check.

Images, sounds and fonts are not converted. They travel along unchanged and come back in the zip. See What gets read and what travels along.

What it costs

Reading a resource and the preview of what would change are free. So is Just write the plan for free, which writes every decision without converting.

A conversion costs what it uses, at least 100 credits. Before you start, the button shows the range, for example Convert for 100-210 credits. It never charges more than the upper number.

Bigger resources cost more: the upper end of the range grows with the number and size of the files.
The convert button always shows the range before you start, and the result shows what the run cost.
No subscription is needed. Any credits work, including the 25 free credits every account gets on each day it signs in.

What it checks, and what it cannot

Every conversion is checked before you get it. The checks prove that every Lua file parses, that no code of the old framework is left, that every call exists in the new framework, and that the names other resources use are unchanged.

Test it before your players do

The checks read the code, they do not run it. Behaviour that depends on your database, your items, other resources or timing is only proven on a server. Start every converted resource on a test server first.

Next steps

Your first conversion

Six steps from a zip to a converted resource, about 60 seconds of waiting.

The free preview

What it found, what each call becomes, what it costs.

Reading the result

The six checks, the findings and the diff.

Installing on your server

Replace the old resource, dependencies and start order.