How to Auto-Translate a Discord Channel (2 Ways)

First, one click of setup

Add Talksy to your server — it posts a welcome message the moment it joins, in your server's language. If you're an admin, click ⚡ Set up, pick the channels where translation should run, confirm. Done — that is the entire server-side setup. (Prefer commands? /server enable then /server channel add #general does the same.)

Way 1: Inline auto-translation (mixed-language channels)

This is for channels where people chat in different languages side by side. Each member who wants their messages auto-translated runs one command:

From then on, that member's messages are automatically posted in their chosen language — as them, with their own name and avatar, via webhooks. No bot replies cluttering chat, no DMs. A Spanish speaker with /talksy english types "¿cómo están?" and the channel sees their message in English, attributed to them.

Members who never run the command are never translated — it's opt-in per person. And anyone can still translate any single message by reacting with a flag emoji (🇫🇷 🇪🇸 🇰🇷) — that needs no setup and no account at all.

Way 2: Channel routes (mirror a channel into another language)

This is for language-segregated servers: keep #general in English and give your Spanish community a #general-es that receives everything, automatically translated. On the welcome message click 🌐 Add route and pick source, target and language — or use the command:

Routes don't just copy text. The linked channels behave like one conversation: deleting the original deletes its translations, replies carry a quote of what was replied to (in the reader's language, with a jump link), forwarded messages cross over translated, and emoji reactions mirror onto the translated copies.

Every server gets one route free (200 translated messages/month included). Unlimited routes with no cap are part of Talksy Pro — one subscription covers the whole server.

Which way should you use?

• One shared channel, many languages → inline auto-translation (Way 1).
• Separate channels per language → routes (Way 2).
• Both at once works fine — many communities run a mixed #international alongside routed language channels.
• Just reading the occasional foreign message → don't set up anything; flag reactions already work.