The best translation providers for Japanese games (2026): DeepL vs ChatGPT vs Claude vs Google
Honest comparison of DeepL, OpenAI GPT-4o, Anthropic Claude, and Google Translate for translating Japanese RPGs and visual novels. Quality, cost per million chars, and when to use which.
Picking a translation provider for a Japanese game is genuinely the most consequential decision in the workflow. Engine compatibility determines whether the game can be translated at all; the provider determines whether the result is readable, in-character, and affordable. This post is the comparison I wish I'd had when I started: four providers, real costs, what each one is actually good at, and when to pick which.
All four providers are supported in RuneTranslate out of the box. You can mix and match per project — or, on Supporter tier, use provider routing to send short strings (item names, menu items) to a cheap provider and longer dialogue to a premium one.
The four providers, ranked by use case
1. DeepL — the workhorse for narrative dialogue
What it's best at:long-form Japanese narrative translation. DeepL is a statistical / neural MT system specifically tuned for JA ↔ EN among a few other pairs. It produces fluent, naturally-phrased English that other MT systems consistently underperform on.
Cost: Free tier covers 500,000 characters/month. Pro is $7/month or $25/month for the higher tiers. For a typical 10,000-line Wolf RPG game (~150k chars of dialogue) the free tier handles it comfortably.
Where it falls short:stylized speech, slang, onomatopoeia, character voice. DeepL outputs grammatically perfect but flat English — every character ends up sounding the same. It also doesn't handle context across lines well.
Use it for:RPG Maker, Ren’Py kinetic novels, Wolf RPG, anything narrative-heavy. Especially for first drafts you intend to hand-edit.
2. OpenAI GPT-4o (ChatGPT) — context-aware quality
What it's best at:context-aware translation with consistent character voice. The 4o family genuinely understands what kind of game this is from the surrounding lines and adjusts register accordingly — formal NPC vs colloquial party member. Handles English slang for stylized character speech well.
Cost (as of 2026): gpt-4o is about $2.50 per million input tokens, $10 per million output. For a 10,000-line VN: ~$0.30 to ~$0.80 depending on how long each line is.
Where it falls short:can be inconsistent on long runs — same character may shift register between batches. Occasionally adds creative liberties that break canon. Refuses adult content sometimes (a real issue if you're translating eroge).
Use it for:visual novels with strong character voice (Kirikiri / TyranoBuilder VNs are perfect fits), games where register matters. Avoid for plain narrative — you'll pay for quality you don't need.
3. Anthropic Claude — the eroge / VN specialist
What it's best at:preserving tone, character voice, and onomatopoeia — the three things visual novels live and die by. Claude is more willing than GPT to translate stylized speech (slang, dialectal Japanese) instead of normalizing it to textbook English. Also significantly more willing to handle adult content in eroge / doujin translation without refusing or over-sanitizing.
Cost:Claude Sonnet is roughly $3 per million input tokens, $15 per million output — comparable to GPT-4o. Haiku 4.5 is cheaper (~$1/$5) and surprisingly capable for short strings.
Where it falls short: can occasionally over-format the output (adds unwanted line breaks, quotation marks). Slightly more expensive than GPT-4o for similar quality on plain dialogue.
Use it for:visual novels, especially adult ones. Games where you want the translator to actually convey character rather than flatten everyone's speech.
Combined with RuneTranslate's Glossary feature (Supporter+), Claude becomes near-publication-quality on long VNs. The glossary locks every character name, place name, and signature attack to a specific rendering before the batch ever reaches the provider — so Claude's tone-preservation work happens on top of stable, consistent terminology. Long VNs where the heroine was randomly "Alice" / "Aris" / "Arisu" depending on which scene Claude was translating: that whole class of bug just goes away.
4. Google Translate (scrape) — the free fallback
What it's best at: being free and fast for short isolated strings. Item names, button labels, menu strings, hai / iieoptions — Google handles these instantly with no API key.
Cost: $0. RuneTranslate uses the public translate endpoint, not the paid Cloud Translation API. No setup, no key.
Where it falls short:dialogue. Google's JA-EN is noticeably worse than DeepL for any sentence with subordinate clauses. It also has a bad habit of returning the source unchanged for onomatopoeia or grunts (RuneTranslate detects this and marks the unit failed so you can retry on a smarter provider).
Use it for:the "short-string lane" in provider routing. Free users on RuneTranslate's free tier translating items + menus and not worrying about dialogue quality.
Practical recommendation by game type
- JRPG (RPG Maker MV / MZ, Wolf RPG): DeepL for dialogue, free Google for item names via provider routing. Fall back to Claude only for stylized antagonist speech.
- Visual novel (Kirikiri, TyranoBuilder, Ren’Py): Claude for everything if budget allows. GPT-4o is a close second. DeepL is fine if you're going to hand-edit anyway.
- Eroge / adult VN: Claude. GPT will refuse some content; DeepL flattens character voice; Google butchers the slang.
- Free-tier user, any genre: free Google for the first pass, then re-run failed units on DeepL free tier (500k chars/month) for the dialogue lines that Google butchered.
Provider routing makes the choice less binary
On Supporter and Pro tier, RuneTranslate's provider routinglets you set a length threshold (default 12 characters) and route everything shorter to a cheap provider while keeping dialogue on your premium one. For a typical VN this cuts your LLM bill by 60–80% because most of the unit count is short item / menu strings, not dialogue.
That makes the choice less "pick one provider for the whole game" and more "pick a premium provider for dialogue, and let cheap MT handle the rest." My current setup: Claude Sonnet on dialogue, free Google on routing-lane short strings. Comes out around $1 per typical visual novel.
Quality is also about hand-editing
No provider produces a publication-ready translation on the first pass. RuneTranslate's editor exists for the hand-fix pass: scan through the project, mark up the lines that are wrong, retype them. The provider gets you 90% of the way there; the human gets you the last 10%.
On Supporter / Pro tier, those hand-edits are cached in translation memory— the same Japanese line in a different game uses your hand-fixed translation instantly, free. Over a few games this compounds into a substantial private memory of game-specific terminology that machine providers consistently miss.
Download RuneTranslateto try any of these providers head-to-head on a real game. Free tier works with every provider — just slower.
Ready to try RuneTranslate?
Free tier unlocks every engine + every translation provider. Supporter ($3/mo) unlocks full speed.
Download for Windows