𝙆 AIO Translater

The simplest of KayTool's three translation nodes: one text box in, one language picked from a dropdown, translated text out. No source language to specify - it auto-detects - and no API key to go register for. That last part is worth being precise about, because the pack's own README markets it as a "built-in high-efficiency AI translation engine" that needs no manual key, while the node's own schema description says plainly it's calling the Tencent Translate API underneath. Both are true at once: it is Tencent's API doing the work, the pack's author is just fronting it so you don't need your own credentials - unlike Baidu Translater, elsewhere in this same pack, which does make you bring your own App ID and Key.

That convenience is also the thing to be a little wary of. A translation node that works with zero setup means the credentials and the request routing live entirely on the author's side, not yours - if that backend gets rate-limited, changes, or goes away, this node stops working with no key of your own to swap in and fix it. Fine for quick prompt translation while you're working; less fine to depend on for anything production-critical.

How it works

You type or wire in text, pick a target language from the To dropdown (14 options including English, Chinese, German, Spanish, French, Italian, Japanese, Korean, Portuguese, Russian, Arabic, Thai and two more), and the node sends it off and returns the translated string. Source-language detection is automatic - there's no From field on this node, which is the main thing distinguishing it from KayTool's Tencent Translater node (same backend, but with an explicit source-language picker and two parallel text slots instead of one).

The inputs and output that matter

• Text (STRING, multiline) - the text to translate.
• To (choice of 14 languages, default English) - target language.
• Translated_Text (STRING, output) - feed straight into a CLIP Text Encode, a save-text node, or a display node to check it.

Installing it

Whole-pack install, same as everything else here: ComfyUI Manager → search KayTool → install → restart, or cd ComfyUI/custom_nodes && git clone https://github.com/kk8bit/KayTool and restart. No separate API setup needed for this specific node - that's the entire pitch.

Common issues

If translation comes back empty or errors out, the likeliest cause is the hosted backend being unreachable - a network hiccup, a rate limit on the author's side, or the service being temporarily down - rather than anything wrong with your input text or node configuration. There's no local fallback and nothing to debug on your end besides checking your own internet connection first. If you need a translation path you control (your own account, your own rate limits, more predictable uptime), Baidu Translater in this same pack takes your own API credentials instead of relying on the shared backend - worth switching to if this node becomes a dependency you can't afford to have go quiet mid-project.