AiNiee: Batch AI Translation for Game Exports, Novels and Subtitles, With the Extraction Left to Other Tools
AiNiee is a tool focused on AI translation, offering one-click automatic translation for RPG/SLG games, Epub/TXT novels, PDF/Word/Markdown documents, and Srt/Vtt/Lrc subtitles and other complex long-form text.
At a glance
- What is it?
- AiNiee is a Python desktop tool that translates folders of game text exports, ebooks, subtitles and documents through an online AI interface or a local model. It does not extract text from games, and its README is written for Chinese-speaking users first.
- Who is it for?
- AiNiee suits people who already hold exported game text, ebooks or subtitle files and want folder-level AI translation with glossaries and prompt control. It is a poor fit if you expect it to unpack a game for you, need a headless server tool (the README points to a separate command-line fork for that), or plan to profit from output, since the license statement excludes illegal commercial use.
- Can I use it commercially?
- Yes, with strict conditions. AGPL-3.0 is a network copyleft licence: if people use a modified version over a network, for example as a hosted service, you must offer them its source code under the same licence.
- Is it still maintained?
- Yes. The repository last received commits 2 days ago.
- What is it written in?
- Mainly Python, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- NEKOparapa/AiNiee6,510 ★ · +215
| Repository | 2026-09-23 | 2026-11-15 |
|---|---|---|
| NEKOparapa/AiNiee | 6.3k | 6.5k |
215 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
Game translation starts in a separate extraction tool, not in AiNiee
The README says that novels, subtitles and documents can be translated directly, but games need a text extraction tool working alongside AiNiee. AiNiee reads the exported files; it does not open a game and pull the dialogue out itself.
Four extraction tools are listed. Mtool is described as easy to start with and recommended for new users, producing Mtool export files. Translator++ is complex but powerful, producing T++ export files or Trans project files. ParaTranz is medium difficulty and powerful, and RenPy SDK is medium difficulty and powerful, each with its own export format. Supported game text tools named in the introduction also include VNText and SExtractor, and a StevExtraction tutorial covers RPG Maker MZ and MV games.
The consequence is a two-program workflow. You extract with one tool, translate with AiNiee, and then put the result back with the extraction tool's own method. The README distinguishes an external-patch style of translation, which the Mtool guide covers for RPG, RenPy and Krkr games, from an embedded style, which the Translator++ guide covers. Which style you get is decided by the tool you picked in step one, so choose it before you start translating.
The three-step flow hides a folder convention you have to follow
The advertised workflow has three steps: configure the interface, drag in a folder, click start. The one-click claim is that dragging a folder and clicking is enough, with files and languages detected automatically and no settings required.
The folder rule is the detail that matters. Put the source files alone in a new folder and drag that folder into the input box. Multi-file batches are handled by putting everything to be translated in the input folder, and nested folder structures are supported. A folder that mixes unrelated files will give the tool unrelated work.
The first step is not optional, whatever the one-click wording suggests. Before anything is translated you must configure an interface, which means obtaining and entering access to an AI service. The README names the online route first and gives a wiki page for DeepSeek setup. So the one-click experience begins only after an account, a key and a configuration exist. The download link for the program points at the project's GitHub releases page.
Online interfaces cost money and local models need a separate runner
The README splits the engine into two routes. Online interfaces require payment, which the README calls good value; they need no graphics card and support all languages. The README gives no prices, so the cost of a translation job is set by whichever provider you choose and by the length of your text.
The local route uses models you run yourself. Three launcher tools are listed: Sakura_Launcher_GUI, a dedicated GUI launcher for Sakura models; LM Studio, a platform for deploying large language models locally; and ollama, an open-source cross-platform LLM tool. AiNiee does not bundle the model or the runner, so you install one of them first.
That difference has consequences for privacy and effort. A local model keeps text on your computer but pushes the hardware requirement onto you, and the README states no minimum specification. An online interface needs no GPU, but your text goes to the service you chose. There is no verdict in the README on which route produces better translations, so run a short sample through both before committing a long book or game.
Long-text quality depends on glossaries, prompts and tables you maintain
AiNiee claims coherence and accuracy over long texts through a lightweight translation format, chain-of-thought translation, an AI glossary and context association. Prompt control covers basic prompts, character introductions, background settings and translation style. Additional functions include AI polishing of table entries and one-click extraction of terms.
Three tables are documented in the wiki: an AI glossary, an AI do-not-translate list and text replacement. They are where consistency comes from. A character name that must stay fixed goes in the glossary or the do-not-translate list, and a recurring tag that breaks the output can be handled by replacement.
The flip side is upkeep. The quality claim in the README is stated as an aim, and no scores or comparisons with other translators are given. A long project needs you to review the first chapters, build the tables, and run again. Nothing in the README promises that the first pass is publishable, and the wiki pages for the tables are the place to learn how each one is applied.
Multiple keys must be comma-separated on one line from the same kind of account
For speed, the program can rotate through several API keys. The instruction is exact: use keys from the same type of account, and type them with an English comma between each one and no line breaks, for example key1,key2,key3. The README says the number of keys scales the speed of translation and spreads out consumption.
Mixing key types or pasting one key per line breaks that format, so the failure is a formatting mistake rather than a subtle bug. Using several keys also means several accounts to pay for and monitor.
Settings live in config.json inside the resource folder. When you download a new version, copy that file into the new version's resource folder to keep your configuration. The README gives no other migration path, so skipping that copy means re-entering your interface settings, keys and prompts. Back up the file before every upgrade, especially since the project publishes a Beta build and frequent point releases.
AGPL-3.0 and a personal-use statement limit what you can do with it
The code is licensed AGPL-3.0, a copyleft license whose network clause matters if you modify the program and offer it as a service. A separate statement in the README adds a restriction on use: the tool is for personal lawful purposes only, and any direct or indirect illegal profit-making is outside the authorization and receives no support or endorsement.
Translating a game, novel or subtitle file usually involves someone else's copyright. The README does not tell you what rights you hold over the source text or over the output, and the license covers the software, not the content you feed it. Check the rules for the material you translate, especially before sharing a patch or a translated book.
One piece of project history is stated openly. The developer neavo left AiNiee development at version 5.2, and the README thanks him for his work between 2024-09 and 2025-02, in particular the version 5 interface redesign. Contact is through QQ groups and a backup Telegram group, so support for English speakers is limited to what the wiki and the issue tracker offer.
The Beta build tracks source, while a separate fork serves headless deployment
The release list shows how the project ships. The Beta entry, dated 2026-11-02, is described as a development test version packaged automatically from the latest source. Stable releases AiNiee7.2.6 and AiNiee7.2.5 followed within days of each other, on 2026-10-29 and 2026-10-25. The last push to the main branch was on 2026-10-12. Beta is the build to avoid for a long job you cannot repeat.
The main program has a graphical front end. The README points people who want a command-line setup to AiNiee-Next, a fork by ShadowLoveElysia that restructures the core logic for the command line, introduces uv and runtime stability changes, and targets long unattended runs, server deployment and automation. The same list includes ainiee-translate-skill, an independent agent-native novel translation system for any source and target language.
For contributors, the README names the places to work: file readers and writers under Backend/infrastructure/files, a regex library at Backend/resources/regex/regex.json that supports embedded game patching, and interface localization text under Frontend/resources/localization.
Editorial conclusion
AiNiee suits people who already hold exported game text, ebooks or subtitle files and want folder-level AI translation with glossaries and prompt control. It is a poor fit if you expect it to unpack a game for you, need a headless server tool (the README points to a separate command-line fork for that), or plan to profit from output, since the license statement excludes illegal commercial use.
Frequently asked questions
Is AiNiee free to use?
The software is open source under AGPL-3.0. Its online AI interfaces are described as paid, though good value, while local models run through tools such as LM Studio or ollama.
How much does AI translation cost with AiNiee?
The README gives no price. Cost depends on the online interface you configure, such as DeepSeek, and the amount of text; local models avoid per-use charges but need your own hardware.
Can AiNiee translate games directly?
Not on its own. Novels, subtitles and documents can be translated directly, but games need a text extraction tool such as Mtool, Translator++, ParaTranz or RenPy SDK.
How do I use several API keys in AiNiee?
Use keys from the same type of account and separate them with English commas on one line, for example key1,key2,key3. Do not put them on separate lines.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/nekoparapa-ainiee)Star history chart for your README
[](https://hysenlabs.com/projects/nekoparapa-ainiee)Was this useful?