TranslationPlugin for IntelliJ IDEs: In-Editor Translation, TTS and a Word Book

The problem TranslationPlugin solves in a JetBrains IDE

Reading foreign-language documentation, commit messages or variable names usually means leaving the editor, opening a browser tab, pasting text, and coming back. TranslationPlugin removes that round trip by putting translation inside the IDE. The README describes it as a "Translation plugin for IntelliJ based IDEs/Android Studio", and the compatibility list covers Android Studio, Aqua, AppCode, CLion, DataGrip, DataSpell, GoLand, HUAWEI DevEco Studio, IntelliJ IDEA Community and Ultimate, MPS, PhpStorm, PyCharm Community and Professional, Rider, RubyMine, RustRover and WebStorm.

The intended user is a developer who reads and writes in more than one language: someone translating a doc comment before editing it, checking what a Chinese or Japanese identifier means, or listening to a pronunciation. Two features point at that audience rather than at casual translation. Replace with Translation rewrites the selected text in place, and the README says that when the target language is English the output can be camel case, word-separated, or kept in the original format. The Word Book, listed among the features, is for terms you look up repeatedly.

Seven engines, three TTS backends, and where the keys come from

The plugin is a client, not a translation service. The README lists Microsoft Translator, Google Translate, DeepL Translator, OpenAI Translator, Youdao Translate, Baidu Translate and Alibaba Translate as the translation engines, plus Microsoft Edge TTS, Google TTS and OpenAI TTS for speech. Which engine answers a given request is a user setting, and the README describes switching between the translation engine and the TTS engine through the engine widget in the status bar or with Ctrl + Shift + S on Windows (Control + Meta + Y on macOS).

That architecture explains the first setup step. The README states that most translation services require user registration, naming OpenAI, DeepL and Youdao Translate as examples, and that you obtain an authentication key and bind it in Preferences(Settings) > Tools > Translation > General > Translation Engine > Configure... Nothing in the README suggests a bundled key or a proxy operated by the plugin author. The practical consequence is that the plugin's quality and quota are the quality and quota of whichever service you configure, and that a service going down or changing its API is visible to you as a failed translation rather than as a plugin bug.

Installing TranslationPlugin from the JetBrains Marketplace

The README gives two installation routes. The first is inside the IDE: open Preferences(Settings) > Plugins > Marketplace, search for "Translation", and install. The plugin is published on the JetBrains Plugin Repository under the id 8579, and restarting the IDE after installation is required.

The second route is a manual install from a downloaded package, which is what you need on an air-gapped machine or when the Marketplace is blocked:

# Download the plugin package from GitHub Releases or the JetBrains Plugin Repository,
# then in the IDE: Preferences(Settings) > Plugins > gear icon > Install plugin from disk...
# Select the package and install (no need to unzip). Restart the IDE afterwards.

The README notes that the package is installed without unzipping. After the restart, the first real use is the translation dialog, which the README says appears on the toolbar by default and opens with Ctrl + Shift + O on Windows or Control + Meta + I on macOS. The second is the context menu path: select text or hover over it, right-click, and choose Translate. If you want the result to overwrite the selection instead of appearing in a dialog, use Replace with Translation, bound by default to Ctrl + Shift + X on Windows and Control + Meta + O on macOS.

Replace with Translation and the documentation workflow

The action that distinguishes this plugin from a browser tab is Replace with Translation. The README describes the output formats for an English target: camel case, a word-separated form whose separator is configurable under Translation Settings > Replace with Translation > Separator, and the original format. That is a naming decision, not a cosmetic one, because the result lands in source code. Camel case suits a Java or Kotlin method name; the word-separated form suits a comment or a Markdown heading.

The documentation path is the other workflow worth knowing. The README states that Quick Documentation and Inline Documentation can be translated from the context menu or by shortcut, and that Translation Settings > Other > Automatically translate documentation makes Quick Documentation translate itself when you open it. For a codebase whose doc comments are not in your first language, that setting turns every hover into a readable definition. The README does not describe caching behaviour for those automatic translations, so if you are on a metered API key, watch your usage before enabling it globally.

Where TranslationPlugin is the wrong tool

The plugin assumes an IDE. Its whole surface is editor actions, context menus, documentation popups and a status-bar widget, so it does nothing for a translator working in a CAT tool, a documentation team reviewing a whole site, or anyone who needs batch translation of a repository. The README's Document translation feature covers documents opened in the IDE, not a directory-level pipeline.

The second limit is the key requirement. The README is explicit that most services need registration and an authentication key. If your organisation blocks outbound calls to translation APIs, or forbids sending source code to third-party services, the plugin has no offline mode described in the README. That is a policy problem, not a configuration one: pasting a proprietary comment into a hosted translation API is the same act whether you do it in a browser or through the plugin.

The third limit is scope. The README documents translation, speech and a word book. It does not describe code-aware translation that understands a compiler error or a stack trace, and it does not describe a glossary that forces consistent terminology across a team. For those, look elsewhere.

TranslationPlugin compared with a VS Code translation extension

The closest thing to a direct alternative is a VS Code translation extension, which is also what people search for. The difference is not feature parity but platform: TranslationPlugin is built for IntelliJ-based IDEs and Android Studio, and the README's compatibility list is entirely JetBrains products plus HUAWEI DevEco Studio. A VS Code extension cannot be installed into IntelliJ IDEA, and TranslationPlugin cannot be installed into VS Code, so for most teams the choice is made by the editor the team already uses rather than by the feature list.

Within the JetBrains ecosystem the meaningful comparison is against doing nothing and using an external service. A browser translator is free of setup and needs no key; TranslationPlugin costs a restart, an engine choice and, for most engines, an API key, and returns the result inside the editor where Replace with Translation can act on it. If your translation needs are occasional, the browser is the cheaper tool. If you translate several times a day while reading code, the setup cost amortises quickly.

Maintenance, licence and what an upgrade costs you

The repository is not archived, and the last push was on 2026-09-18, three days before this article's reference point. The recent release history shows v3.9.1 on 2026-08-26, v3.9.0 on 2026-08-23 and v3.8.4 on 2026-07-25, so releases have been arriving through 2026. The project is written in Kotlin, built with Gradle (build.gradle.kts, settings.gradle.kts, gradlew), and the top-level entries include CHANGELOG.md, which is where release notes live.

Upgrade cost is low for users: the IDE installs plugin updates, and because the plugin is a client for external APIs, an engine changing its terms affects you regardless of the plugin version. What you should actually track is your own API keys and quotas, since a key that expires looks exactly like a broken plugin.

The licence is MIT, which covers the plugin source. It does not cover the translation services: the README links to Microsoft, Google, OpenAI, DeepL, Youdao, Baidu and Alibaba, each with its own account and terms, and those terms govern what you may send and how much. This is not legal advice; check the terms of the specific engine you configure before sending anything sensitive through it.

Editorial conclusion

Adopt TranslationPlugin if you work in an IntelliJ-based IDE and regularly read documentation, comments or identifiers in a second language; the Word Book and Replace with Translation actions are the parts that pay off daily. Skip it if you expect a free, key-free translation service, because the README says most engines require registration and an authentication key. Before rolling it out, verify which engine you can actually authenticate against and whether its terms allow your usage; the MIT licence covers the plugin code, not the translation services it calls.

Frequently asked questions

Official sources

1. License: MIT
2. Project website
3. README
4. Releases
5. YiiGuxing/TranslationPlugin on GitHub