Resource Translator: guide and tutorial
Translate a resource you bought into any language.
Video tutorial coming soon
Until then, the written guide below takes you through every step.
What it is
Resource Translator takes a script that only speaks English (or any other language) and gives it back speaking yours. You drop in the resource, a free scan shows which language files it has and how many messages your players will read, then ORBIE translates them and you download the whole resource with the new language file written next to the original. Names, amounts and colour codes inside each message are locked so the translation cannot break the script, and the words you choose for your server are saved so every script you translate says the same thing.
Who it's for
- Server owners whose players do not read English, running scripts that only ship in English.
- Servers with dozens of scripts that want the same word for the same thing everywhere (stash, dispatch, garage).
- Anyone who bought a script that claims to support their language and found the file empty.
Before you start
- The resource: a
.zip, the folder, or just its.luaand.jsonlanguage files. - To translate (not to scan): a THE ORB account and credits. See pricing.
Scan the resource for free
- 1
Open the translator
Go to Resource Translator.
- 2
Drop the resource
Drag the folder or
.ziponto the box, or use Choose a .zip / files or Choose a folder. Loose.luaand.jsonfiles work too. - 3
Read the summary
The panel shows the resource name and a one-line verdict, for example that the script shows your players a certain number of messages and that all of them are in language files. Below it: messages players see, words, how many contain a name or a number, how many are short buttons and labels, and how many language files there are.
The whole scan happens in your browser. Nothing is uploaded and it costs nothing.
It understands four kinds of language files: ESX scripts, QBCore and Qbox scripts, ox_lib and anything that keeps its text in a .json file, and scripts with a plain list of messages.
What the scan tells you
The viewer lists everything the scan found, most surprising first:
- Worth knowing: the script says it speaks a language, but that file is empty. Turning that language on in the config changes nothing, your players still see English. ORBIE can fill it in.
- Languages this script claims to speak: every language it ships, with empty ones marked.
- One card per language file: its path, its language, its format, how many messages it has, and a few sample lines when you open it.
- Terms worth deciding once: words that appear in this script and in most others you own, with how often each one is used.
- Messages we cannot translate for you: text written straight into the script instead of a language file. Changing those means editing the script, which the tool will not do on its own, because a mistake there stops the script from working. Open the card to see where each one is.
If the script has no language files at all and everything is written inside the code, there is nothing to translate safely. The verdict says so.
Step 1: pick a language
- 1
Go to Translate
Click Translate in the left rail. The panel shows three steps.
- 2
Pick the language
Under Pick a language, click one. The first list shows the languages marked with a sparkle: for those we wrote down how that language's FiveM scene actually talks. Use Show all or the search box for the rest.
- 3
Check what you translate from
If the script ships several languages, choose under Translating from which one to use as the source. English is picked first. You cannot translate a language into itself: the tool warns you and keeps the buttons off.
Step 2: agree the words once (the glossary)
The glossary is a short list of terms and how your server says them. It is what stops the same word coming out three different ways across thirty scripts.
- 1
Review the suggested terms
The first time you use a language, the list is filled with terms from this resource. For languages with scene notes, the answers are already filled in with what servers in that language usually say. Change anything you disagree with.
- 2
Set how the server speaks to players
For some languages there is a field for the tone (for example formal or informal address). Leave it empty to use the default shown under it.
- 3
Add or remove terms
Use Add a term for a new row, and the cross at the end of a row to remove it.
- 4
Press Save the glossary
You must be signed in. From then on every script you translate into that language uses it. Each language has its own glossary.
The glossary is saved automatically before every preview and every full translation, so what is on screen is what gets used.
Step 3: see it, then do it
- 1
Press Try 10 strings
ORBIE translates the first ten messages with your glossary applied. The viewer shows each one in two columns, the original and your language, with a warning under any line worth a second look. This costs 1 credit by default; the price is on the button.
- 2
Press Translate all of it
This translates the whole resource into that language for one charge, however many files it is spread across. By default that is 2 credits per language; the price is on the button and your balance is shown above it.
- 3
Wait, or keep working
ORBIE translates in groups of 40 messages and the counter goes up as each group finishes. You can go to other pages of the site meanwhile: the translation keeps going and the tasks button in the top bar brings you back to download it.
Before translating, every variable (like %s, %{amount} or a colour code like ~r~) is locked, and after translating it is checked again. A message whose variables did not survive is thrown away rather than shipped. A run that fails that check is not charged.
Each extra language is its own charge. Translating into Spanish and Portuguese is two translations.
When the script updates
Translate the new version the same way. The tool remembers, in this browser, what you already translated for that resource and language, and only sends the new lines. If nothing is new, it tells you so instead of charging.
The result screen shows how many messages were translated this time and how many were reused from before.
What you download
When it finishes, the viewer says the resource is ready and lists the files it wrote. Press Download the translated resource. You get <resource>-<language>.zip with:
- The whole resource as you uploaded it, untouched.
- The new language file next to each original, named for the new language. For example
locales/en.luagets alocales/es.luabeside it. - If the resource already had a file for that language, it is left exactly as it was and the translation goes to a file ending in
-orbiebeside it (for examplees-orbie.lua), so you can compare and keep the one you prefer. - Three note files,
ORBIE-TRANSLATION-NOTES.txt,ORBIE-NOTAS-DE-TRADUCCION.txtandORBIE-NOTAS-DE-TRADUCAO.txt, with what was written, the glossary used and anything worth a look.
Install it on your server
- 1
Back up the old folder
Copy the resource folder somewhere outside
resources/. - 2
Replace the folder
Unzip and put the resource in
resources/in place of the old one, with the same folder name. - 3
Turn the language on
The new file does nothing until the script is told to use it. Most scripts have a language setting in their config file, for example a line like
Config.Locale = 'es'. Follow what the script's own instructions say. - 4
Check the manifest
If the script's
fxmanifest.lualists its language files one by one instead of with a pattern likelocales/*.lua, add the new file to that list. Otherwise it will not load. - 5
Restart it
Restart the server, or type
ensurefollowed by the resource name in the server console, and check a few messages in game.
Keep the original language file. Most frameworks want it present as a fallback, and that is why the translation is written beside it and never over it.
Common problems
The buttons stay grey.
Pick a language first, and make sure it is not the same as the language under Translating from.
It says the script has no language files.
Everything it says is written into the code. The tool will not edit the code itself, because a wrong change stops the script from running. Ask the author for a version with language files, or have someone move the texts out.
It says there is nothing new to translate.
Every message is already in your saved translation for that resource and language. Download it from the result, or translate into a different language.
The players still see English after installing.
The script is still set to English. Change the language setting in its config to the new language code and restart it. Also check that the manifest loads the new file.
Some strings were rejected.
Their variables or colour codes did not come back intact, so they were dropped instead of shipped broken. Those lines stay in the original language in the new file.
The connection dropped while it was translating.
Press the button again with the same file. If the translation finished, you get it without paying twice. A finished translation is kept on our server for 24 hours after you get it, or 30 days if you never came back for it.
Questions
What is sent to your server?
Only the messages being translated, and only when you press a button. The files are read and rebuilt in your browser. Your glossary is saved to your account.
How many languages are there?
More than 50. The ones marked with a sparkle have notes on how that language's FiveM scene talks, so terms like dispatch or stash come out the way players expect.
Will it break my script?
It only translates text that is clearly a value in a language file, never the keys or event names, and it locks every variable before translating. A message that comes back with a broken variable is thrown away.
Is there a limit?
One pass takes up to 4,000 messages. A single message longer than 2,000 characters is skipped.
Do I pay again if I translate the same script twice?
If nothing changed, it tells you there is nothing new and does not charge. After an update, a new run translates only the new lines, but it is still one charge for that language.
Does the glossary carry over to other scripts?
Yes. It belongs to your account and to the language, so the next script you translate into that language starts with it.
Checked against the tool on November 15, 2026.
Try Resource Translator now
Bought a script that only speaks English? Translate it into any language and download the resource back, with your own words used across every script you own.
