How to get RPG Maker JSON
RPG Maker MV/MZ projects store most game text inside JSON files (usually in data/). For a stable translation workflow, always start from the original project folder.
Translate from the project source (the folder you open in RPG Maker). This avoids encrypted deployments, missing data, and broken map event references.
Where the JSON files live
In both RPG Maker MV and RPG Maker MZ, the data files are typically in the data/ folder.
MyRPGMakerGame/
data/
Actors.json
Armors.json
Classes.json
CommonEvents.json
Enemies.json
Items.json
Map001.json
Map002.json
Skills.json
States.json
System.json
Troops.json
Weapons.json
img/
audio/
js/
index.html
Which JSON files usually contain text?
| File | Common text inside | Notes |
|---|---|---|
| MapXXX.json | Event dialogue, choices, item messages | Most story text often lives here |
| CommonEvents.json | Shared event dialogue / logic | Used across maps |
| System.json | UI terms, game title, menu strings | Be careful: changing certain fields can affect UI layout |
| Actors.json, Enemies.json | Names, profiles, descriptions | Keep placeholders/control codes intact |
| Items.json, Weapons.json, Armors.json | Item names, descriptions | Icons/metadata should not be edited |
| Skills.json, States.json | Skill/state names, descriptions, messages | Common in battle UI |
Do not break RPG Maker control codes
RPG Maker text often contains control codes that must remain unchanged. VNTranslator Preview/Edit can help you spot issues before exporting.
- \V[n] variable value
- \N[n] actor name
- \P[n] party member name
- \G currency unit
- \C[n] text color
- \I[n] icon index
- \{, \}, \., \| timing/formatting controls
Good:
"You got \I[64] Potion x\V[3]!"
Bad (code removed):
"You got Potion x3!"
Do not remove quotes, commas, or brackets. One missing character can break the entire file and prevent the game from loading.
If you only have a deployed game
Some deployed builds encrypt or pack assets and may not include clean project JSON. If you cannot find a readable data/ folder with .json files, ask the developer for a translation-friendly source package.
This guide does not cover bypassing protections or extracting content you don't own. Always respect the game's license and the developer's terms.
Quick checklist
- You are working from the original project folder.
- data/*.json files are readable and valid JSON.
- Control codes are preserved.
- You test the game after exporting.
