Text Translate [LP]

The README lists this under "Other nodes" simply as "Google Translate," and that undersells it slightly - it actually gives you a choice of two translation backends. Feed it text in whatever language you're comfortable prompting in, and it comes back in English.

Why translation belongs in a ComfyUI graph at all

Almost every popular checkpoint - SDXL, Flux, Illustrious and its derivatives - was trained overwhelmingly on English captions and tags. Prompting in another language works to some degree, but it reliably underperforms compared to the same idea expressed in English, since the model simply has far less training signal tying non-English words to visual concepts. If you think and write more naturally in your own language, translating before the prompt hits the checkpoint is a small, cheap step that avoids leaving quality on the table.

How it works

• text - a multiline field for whatever you're translating, default "text".
• translator - a two-way choice: GoogleTranslator or MyMemoryTranslator. These are the actual class names from Python's popular deep-translator library, which this node is almost certainly wrapping - both of them hit free, publicly accessible translation endpoints rather than a paid API, which is why there's no API key field anywhere on this node.
• Output - labeled english TEXT in the node's own schema. Worth noting literally: the output socket itself is named for English specifically, so despite "Text Translate" sounding generic, in practice this node is built as an X-to-English translator. There's no separate source-language input, so whichever language you type gets auto-detected on the way in.

The trade-off of "free, no API key"

That's genuinely the appeal - no account, no billing, no setup beyond installing the node. But it means you're depending on the same free, unofficial endpoints anyone can hit from a browser, not Google's paid Cloud Translation API. Free endpoints like this can rate-limit under heavy or bursty use, and if the underlying service changes something on its end, the library wrapping it can start failing until it's updated to match - that's a known category of fragility for this kind of no-key translation wrapper, not something specific to how Level Pixel packaged it here.

How to install it

ComfyUI Manager: search "ComfyUI Level Pixel" or ComfyUI-LevelPixel, install, restart - auto-updates via Manager's "Update ALL." Manual:

cd ComfyUI/custom_nodes
git clone https://github.com/LevelPixel/ComfyUI-LevelPixel.git

Restart ComfyUI. Note this node specifically needs whatever translation library the pack bundles in its dependencies (the deep-translator package, going by the enum's class names) - a normal Manager or git clone install should pull that in for you as part of the pack's requirements, but if the node fails to load specifically while everything else in the pack works, that dependency is the first thing to check.

Common issues & troubleshooting

The node errors or hangs. It needs a live internet connection - it reaches out to Google's or MyMemory's translation endpoint on every single run. If you're running ComfyUI on a cloud GPU box with restricted outbound access (common on some rental platforms), this node simply won't be able to reach its target.

GoogleTranslator suddenly stops working. Try switching the translator dropdown to MyMemoryTranslator as a quick fallback - different backend, so a transient outage or rate-limit on one doesn't necessarily affect the other.

You're translating a lot of text in a batch and it starts failing partway through. MyMemory in particular publishes a daily character quota for anonymous, no-email use - heavy batch translation can hit that ceiling faster than you'd expect. If you're doing this at volume regularly, it may be worth looking at a paid translation API instead of either free option this node offers.