Quick start

This guide helps you go from zero → first working translation with minimal risk.

1) Pick the correct tool

• Ren’Py (.rpy scripts): use Ren’Py Translator or Pro Ren’Py Translator

  • Single file: Ren’Py Translator
  • Multi-file project + Translation Memory: Pro Ren’Py Translator

• RPG Maker MV/MZ (data/*.json): use RPG Maker Translator or RPGM Ultimate

  • Single JSON: RPG Maker Translator
  • Many JSON files + batch pipeline: RPGM Ultimate

• Quick editing / manual fixes: Game Text Editor

2) Prepare your source files

Ren’Py

• Use the original project folder you open in Ren’Py Launcher
• Scripts are usually in: game/*.rpy

If you can’t find .rpy, read: How to get .rpy files

RPG Maker MV/MZ

• Use the original project folder
• Data files are usually in: data/*.json
  Example: Actors.json, System.json, CommonEvents.json, Map001.json

If you’re not sure which files: How to get RPGM JSON

3) Choose a translation service

VN Translator supports multiple translation backends. Most users start with:

• DeepSeek (API key) — best structure preservation for VN text
• OpenAI (API key) — highest quality, usually more expensive
• DeepL (API key) — strong for many languages, can be strict about formatting
• Lingva / Google — free options, but riskier for tag/control-code safety

See: Translation services and API keys

4) Translate in small batches

• Start with one file
• Use a batch size like 10–30 lines for the first run
• If everything looks stable, increase batch size gradually

This approach reduces:

• retries on failures
• partial outputs
• broken tags/control codes

5) QA in Preview & Editor

After translation:

• Open the tool’s Preview / Editor
• Check:
  • tags (Ren’Py {i}{/i}, {color=...})
  • variables (Ren’Py [name])
  • control codes (RPGM \V[1], \N[3], \C[2], \I[10])
  • line breaks, spacing, punctuation

Fix issues immediately, then export again.

6) Export and test in the engine

• Replace translated files back into the project
• Run the game:
  • Ren’Py: launch from Ren’Py Launcher
  • RPG Maker: playtest from the editor, or build and test

✅ Always test after each export. VN engines fail fast when formatting breaks.

A safe “first translation” checklist

• [ ] I’m translating from the original project (not a random build)
• [ ] I backed up the project folder
• [ ] I started with a small batch size
• [ ] I used Preview & Editor to check tags/control codes
• [ ] I tested the game after exporting