Nodes/ComfyUI Level Pixel/Text Translate Manual [LP]
ComfyUI Node

Text Translate Manual [LP]

Free translation with a short, human-readable language list

By LevelPixel·Created 2 years ago·Updated 6 months ago· 31
Text Translate Manual [LP]
    • text
    texttext
    source_langauto
    target_langEnglish
    translatorGoogleTranslator

    This is the friendlier of the pack's two translation nodes. Same free, keyless translation underneath - same idea as its TextTranslateManualAll-LP sibling - but instead of asking you to know a two-letter ISO code, the dropdowns here are spelled-out language names: English, Русский, Deutsch, Français, Italiano, 简体中文, 日本語, and a handful more. If you're only working across a small set of common languages and don't want to look up codes, this is the one to reach for.

    What it does

    The README lists "Google Translate" among the pack's "Other nodes" without much elaboration, and this node - along with its "All langs" sibling - is what that refers to. You give it text and pick source and target languages from a curated list of roughly 16–17 human-readable names rather than raw codes, choose a translation backend, and get translated text back. The translator option (GoogleTranslator or MyMemoryTranslator) matches the class names from the deep-translator Python package closely enough that it's almost certainly what this node is built on - both are free, no-signup translation backends, which is why the node can just work without asking for an API key.

    "Manual" describes how you pick languages - from a fixed dropdown, by hand - not how the translation itself happens; the actual translating is still fully automated by whichever backend you selected.

    Inputs and outputs that matter

    • text (required, multiline, defaults to "text") - the text to translate.
    • source_lang (required, dropdown of ~17 language names plus auto, default auto) - the language text is in.
    • target_lang (required, dropdown of ~16 language names, default English) - the language to translate into.
    • translator (required, dropdown: GoogleTranslator / MyMemoryTranslator, default GoogleTranslator) - which backend performs the translation.

    Output: text - the translated string, ready to wire into a CLIP text encoder or any other text-consuming node.

    Installing it

    Through ComfyUI Manager, search "ComfyUI Level Pixel" or "ComfyUI-LevelPixel." Manual install:

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

    Restart ComfyUI. Needs live internet access at run time to reach the translation backend - it won't function offline.

    Common issues & troubleshooting

    Your language isn't in the dropdown. This node deliberately trades coverage for readability - it exposes a curated subset of common languages, not the full list. If the language you need isn't here, TextTranslateManualAll-LP covers the much larger raw-code list (100+ languages) at the cost of needing to know or look up the right two-letter code.

    Translation stalls, errors, or seems rate-limited. Both backends are free public services, not something this pack hosts itself, so intermittent failures are more likely network or service-side than a bug in the node. Toggling translator between GoogleTranslator and MyMemoryTranslator is a reasonable first troubleshooting step, and MyMemory in particular tends to have a daily cap on anonymous usage that a long session can run into.

    Translated text feeds into an encoder and results feel off. For prompts headed into encoders that read certain languages natively - Chinese-capable Qwen-based encoders being the current example - community feedback favors DeepL over Google Translate for that specific conversion. Neither backend offered by this node is DeepL, so if that's the workflow, treat this node's output as a fast first pass rather than the final word, and spot-check important prompts.

    auto source-language detection guesses wrong. If your input text is short, mixed-language, or ambiguous, automatic detection can misfire. Setting source_lang explicitly instead of leaving it on auto removes that guesswork entirely.

    CategoryLevelPixel/Text

    Inputs (4)

    NameTypeDefaultDescription
    textSTRINGtext
    source_langCOMBOauto17 options: auto, English, Русский, Deutsch, Français, Italiano, +11
    target_langCOMBOEnglish16 options: English, Русский, Deutsch, Français, Italiano, Polski, +10
    translatorCOMBOGoogleTranslator2 options: GoogleTranslator, MyMemoryTranslator

    Outputs (1)

    NameTypeDescription
    textSTRING