GoogleTranslator
Write your prompt in your own language, let Google fix the English
- STRING
Every text encoder that matters was trained mostly on English text. So if English isn't your first language, you face a choice every time you write a prompt: think in your native language and butcher the translation, or write English at half your speed. GoogleTranslator ("Simple Gooogle Translator Client" in the node menu - yes, the typo is in the source) is the small fix for that: you write the prompt the way you actually think, and it hands English to the CLIP encoder.
The name is a lie in the good way - it doesn't call any paid API and needs no key. It uses the googletrans library, which rides Google's public (unofficial) translate endpoint the same way the web page does. Free, no account, works out of the box. It just needs internet access, which is the node's one real dependency on the outside world.
How it works is boring in the best sense: you drop in a text (multiline, so paste your whole prompt), pick a translate_to target from the dropdown - en, pt, ru, es - and it outputs a single STRING with the translated prompt. Wire that straight into the prompt input of a CLIP Text Encode node, and you're done. The print_to_screen toggle just mirrors your input and the translation to the ComfyUI console, which is useful once or twice and harmless after that.
The community instinct this node formalizes is well-worn: translating your intent to clean English before the encoder beats feeding it broken half-translated phrases. The default target is en because that's the whole point - and the author's Brazilian-Portuguese background (pt is a first-class option) explains why a "simple tools" pack includes a translator at all.
The gotchas
- The endpoint is unofficial. Google can throttle or temporarily block it, and you'll occasionally hit a timeout or a garbled response. Restart the queue and re-run; it's usually transient. If you need reliability at scale, this free route isn't it - but for a prompt or two per generation, it's fine.
- The pinned version matters. The pack installs
googletrans==3.1.0a0, and that pin is doing real work: the newer 4.x release candidate is the famously broken one ('NoneType' object has no attribute 'group'on import). The author pinned the version the community converged on, so don't "upgrade" it. - Only four target languages. The dropdown limits you to en/pt/ru/es. The author explicitly left the list expandable - open
google_translator.pyinComfyUI/custom_nodes/comfyui_simpletools/and add any language code you like to the list.
Install
ComfyUI Manager → search "SimpleTools" and install "ComfyUI SimpleTools Suit", or:
cd ComfyUI/custom_nodes
git clone https://github.com/celsojr2013/comfyui_simpletools
pip install -r requirements.txt # pulls googletrans==3.1.0a0
Restart ComfyUI. No model downloads - the googletrans dependency is the only thing this pack needs, and only this node uses it. It's a one-node solution to a problem everyone who doesn't natively speak English has quietly worked around for years.
Inputs (3)
| Name | Type | Default | Description |
|---|---|---|---|
| text | STRING | — | |
| translate_to | COMBO | en | 4 options: en, pt, ru, es |
| print_to_screen | COMBO | 2 options: enable, disable |
Outputs (1)
| Name | Type | Description |
|---|---|---|
| STRING | STRING | — |