Comparison

RuneTranslate vs Sugoi Toolkit

The structural difference is simple: Sugoi Toolkit translates a game while it runs, and RuneTranslate translates the game's files before you run it. Sugoi reads text out of the live process, off the screen or from the clipboard and shows you a translation for as long as it is running beside the game. RuneTranslate parses the game's own data, turns every string into an editable project, and writes a translated copy you launch on its own. Everything else on this page follows from that one difference — what you can proofread, what you still have tomorrow, and which games each one can reach at all.

Made by: MingShiba
Licence: Mixed (NTT model licence; Sugoi Hook GPL-3.0)
Runs on: Windows 10+

The short version

If you want to read one route tonight, on a game no extraction tool has ever opened, with no API key and nothing leaving your machine, Sugoi Toolkit is the better answer — and for many titles it is the only one. If you want a script you can proofread as a body of work, a glossary that keeps a character's name steady across forty hours, and a translated copy that still works next year with nothing running beside it, that is what RuneTranslate is built for. The two are not opposed: a large part of Sugoi's role in this ecosystem is being the free offline engine behind tools that do patch files. The honest deciding question is not which tool is better but whether you want to read a game or produce a translation of it.

When Sugoi Toolkit is the better choice

Start here if your game is not on anyone's adapter list. Sugoi reads text out of the running process or off the screen, so it does not care whether the engine is a bespoke in-house toolchain, an obscure doujin build, or an archive format nobody has documented — its coverage has no list to fall off, and a file-based tool always does. It is also genuinely free and genuinely offline: the bundled Japanese-to-English model (JParaCrawl-derived, running under CTranslate2 since V9) works on your own CPU with no API key, no account, no quota and no text leaving the machine, which matters both for a 100,000-line JRPG where per-token billing adds up and for material you would rather not send to a cloud provider. There is no extract, translate, export, test loop at all — point Sugoi Hook or Sugoi Lens at a running game and read, which is a far shorter path when you have one evening. It is also much more than a game tool: manga OCR and typesetting, EPUB to EPUB for light novels, an audio and video translator, browser extensions, Sugoi Cloud and Sugoi Chat, so one install covers most of what you read and watch. And it is a good citizen in other people's pipelines — Translator++, XUnity.AutoTranslator and py3translationServer all speak its server API, so its local model can sit behind a file-patching workflow instead of competing with one. It is maintained full-time on a roughly monthly cadence (V25 dated 1 July 2026) with a large community, so most problems already have an answer somewhere.

When RuneTranslate fits better

RuneTranslate is the right tool when the deliverable matters more than the speed of the first line. It reads the game's own data — RPG Maker JSON, Ren'Py scripts, Kirikiri XP3, Wolf RPG archives, Unity assets, Unreal .locres and a dozen more families across 17 engines and formats — pulls every string into a project you can sort, filter, search and correct, then writes a playable translated build you keep and can come back to months later with nothing running beside it. That persistence is what makes ordinary quality work possible: fix a name once and a glossary holds it everywhere, a private cloud translation memory carries your phrasing into the next project and onto your next PC, and an optional AI second pass re-reads lines you have already translated. It is also strongest exactly where runtime capture is weakest — on nw.js RPG Maker MV and MZ the text comes out of the data files rather than off a canvas. The Image Studio covers the Japanese painted into title screens and menu buttons: detect it, inpaint it, typeset the translation and bake it into the exported build, rather than reading it off the screen again every session. Providers are yours to choose, including three that need no API key at all and a local model over Ollama or LM Studio.

Where the two actually differ

Checked in August 2026 against each project's own site, blog and public repositories. Both ship frequently, so verify anything decision-critical.

What you are comparing	RuneTranslate	Sugoi Toolkit
How the translation reaches you	Parses the game's own data files, extracts every string into a project, and writes the translations back.	Reads text out of the running game via Sugoi Hook, off the screen via Sugoi Lens or Visual Novel OCR, or from the clipboard, then displays it.
What you have afterwards	A playable translated build you keep, plus a project file you can reopen and revise later.	For games, nothing persists — the translation exists only while the toolkit is running next to the game.
Engine coverage	17 named engines and formats. A finite list: a game outside it is not supported, and only some engines have a confirmed in-game-playable baseline.	No list at all. Anything that draws text on screen is reachable, including engines nobody has ever written an adapter for.
RPG Maker MV and MZ	Read straight from the data JSON; MV and MZ are among the confirmed playable baselines.	nw.js RPG Maker is a long-documented weak spot for the Textractor hooking that Sugoi Hook wraps; the screen-OCR route is the practical fallback.
Translating with no API key	Three no-key providers (Google, plus two free DeepL endpoints) and a local model via Ollama or LM Studio. No model is bundled.	The bundled offline model runs on your own CPU — no key, no account, no quota, no per-line cost, and no text leaving the machine.
Translation quality model	Pick per project: DeepL, OpenAI, Anthropic, DeepSeek or any OpenAI-compatible endpoint, with a glossary and an optional AI second pass.	Sentence-level neural MT, line by line with no document context — strong for a free local model, and newer versions can also route to Google, DeepL or Sugoi's own LLM and cloud options.
Proofreading a whole script	The project is the unit of work: filtering, find and replace, translation memory, glossary, and live collaborative editing with others.	Output arrives one line at a time with no persistent script behind it, so a correction cannot be made once and made to stick everywhere.
Japanese baked into artwork	Image Studio detects it, inpaints it, typesets the translation and bakes it into the exported build. Supporter tier and up; this is the one place the free tier is read-only.	The OCR overlay can read artwork text on screen, but the game's images are unchanged. Its separate manga translator does write edited image files.
Running alongside the game	Nothing runs at play time — the exported build is the game.	A local translation server plus continuous hooking or OCR, with roughly 8 GB of RAM on top of the game and multi-second per-line latency on CPU without a CUDA card.
Beyond games	Games only, deliberately.	Manga, light novels and EPUB, audio and video, browser extensions, Sugoi Cloud and Sugoi Chat.
Working with other tools	Uses its own provider list and does not currently speak Sugoi's server API. The Developer tier exports CSV, JSON, PO and XLIFF for work done elsewhere.	Widely used as a translation back-end by tools that do patch files — Translator++, XUnity.AutoTranslator and py3translationServer all speak its API.
Source and target languages	Built for Japanese source; 35 target languages, with the interface in 18.	The offline model is Japanese to English. Other source languages and non-English targets are recent and vendor-stated, and their quality is not well documented.
Cost and access	The free tier is a throughput throttle rather than a feature paywall — every engine, every provider, the whole editor — but runs roughly half speed on AI providers with one project open, and a Patreon account and sign-in are required even then. Supporter $3/month, Pro $5/month.	Free, and usable with no account: the public download link is posted on the 15th and 16th of each month, while Patreon members ($6 and $10/month) get it immediately plus cloud access. The bundle is large — the V5 public archive alone was 2.7 GB.
Source availability and licensing	Closed-source desktop app. Its output is a modified copy of the game you already have, for your own play.	Sugoi Hook is GPL-3.0, but the toolkit ships as a closed bundle and the original repository is gone. The offline model carries NTT's JParaCrawl research license, which restricts redistribution and commercial use.

RuneTranslate is not affiliated with Sugoi Toolkit or its author, MingShiba. Details on both sides were verified in August 2026 against each project's own site, blog and public repositories; both release frequently, so check anything decision-critical before relying on it.

Questions people ask

Can Sugoi Toolkit export a translated copy of a game?

Sugoi Toolkit does not produce a translated game build. For games it works entirely at runtime — it reads text out of the running process or off the screen and shows a translation while it is running beside the game — so the game's own files are never opened or rewritten and there is nothing left once you close it. Its non-game components do write files, including translated manga images, EPUB output and subtitles, but those are for books, manga and video rather than games. If you want a playable translated copy of the game itself, you need a tool that works on the game's data files.

Is RuneTranslate a straight replacement for Sugoi Toolkit?

No, and it is worth being clear about that. RuneTranslate covers 17 engines and formats and gives you an exported build, an editable project, a glossary and a translation memory, but a game outside that list is simply not supported. Sugoi Toolkit has no adapter list to fall outside of and reaches anything that puts Japanese on screen, at the cost of leaving nothing behind. Plenty of people keep both installed and use whichever the specific game allows.

Can I use Sugoi Toolkit's offline model as a provider inside RuneTranslate?

Not today. RuneTranslate talks to Ollama, LM Studio and any OpenAI-compatible endpoint for local translation, and Sugoi's translation server speaks its own API rather than that one, so there is no built-in Sugoi provider. If free offline translation is the priority, RuneTranslate's local-model route covers that need, and it also ships three cloud providers that need no API key. Translator++ and XUnity.AutoTranslator do have dedicated Sugoi endpoints if pairing Sugoi's model with a file-patching workflow is what you want.

Does Sugoi Toolkit work well on RPG Maker MV and MZ games?

That is the weakest case for Sugoi's hooking path. nw.js-based RPG Maker MV and MZ have been a long-standing difficulty for Textractor, which Sugoi Hook wraps, with several unresolved upstream issues to that effect. The screen-OCR route, Sugoi Lens or Visual Novel OCR, is the practical fallback and works on anything that renders. RuneTranslate takes the opposite route on those games and reads the strings out of the data JSON, which is why MV and MZ are among its confirmed playable baselines.

Which is cheaper for translating a long JRPG?

Sugoi Toolkit is very hard to beat on marginal cost. The bundled offline model runs on your own CPU with no key, no quota and no per-token bill, so a 100,000-line game costs nothing but electricity and time. RuneTranslate also has three providers that need no API key and can drive a local model, but its free tier is throttled — roughly half speed on AI providers and one project at a time — and full speed starts at $3 a month. If you choose a paid LLM provider, that bill is yours in either tool.

Do I need an account, and do either of these run on Linux?

Sugoi Toolkit can be used with no account at all: the full public download link is posted on the 15th and 16th of each month, and Patreon membership at $6 or $10 a month buys immediate access and cloud services rather than the core offline capability. RuneTranslate requires a Patreon sign-in even on its free tier, with no anonymous mode, which is a real friction cost worth knowing before you download. Both are Windows tools; on Linux or a Steam Deck you are in Wine or Proton territory with either one.

Check your game against the engine list

RuneTranslate is free to download, and the free tier unlocks every engine, every provider and the whole editor — it runs slower, not smaller. Start by checking your game's engine against the supported list. If it is not there, Sugoi Toolkit is very likely the better answer today, and there is no sense pretending otherwise.

Download for Windows Get Supporter ($3/mo)