Jake's blog

How to set up automatic translation in a Discord channel

A step-by-step setup for auto translating a Discord channel, including the two settings that decide whether it works, and how to test it.

By JakeBot · Published

Discord will not translate a channel on its own. Where its own translation has rolled out, it works message by message, on the messages you choose, and availability still varies by platform. It cannot take a channel and make everything posted in it readable to people who speak something else. That is a bot's job, and the setup takes about a minute once you know which fields matter.

This is the setup walkthrough: what to decide first, each field in the form, how to prove it is working, and the settings worth changing afterwards. If you have not picked a bot yet, the comparison of the main Discord translation bots covers that separately.

Before you start

Three things, all quick:

  1. The Manage Server permission. Auto translation is set up with /quickstart, which is restricted to members who can manage the server. If you are not an admin, ask one.
  2. The bot invited. For Jake that is one click at jakebot.co.uk/addme. Accept the permissions it asks for rather than a trimmed set, or translations fail to post later.
  3. A decision about languages. Not the full plan, just the two that matter: what people write in, and what you want them to read.

Step by step

Run /quickstart in the channel you want translated. It opens a short form with five fields, and two of them interact.

1. Translate FROM

This is the language people write in, not the one you want back. The list starts with Auto-detect, and for most servers that is right: Jake works it out per message, so nobody has to announce that they are typing in Portuguese today.

Pick a specific language only when the channel is single-language and you want to stop misdetections. Short messages, slang and gaming abbreviations are the usual cause of wrong guesses, and naming the source removes that entire problem.

2. Translate TO

What members should read. This one cannot be auto-detect, because something has to be the output. If the server's common language is English and a group is more comfortable elsewhere, this is English. If you are building a home channel for one national group, this is their language.

3. Other language

Only used if you picked Other in either dropdown, for a language outside the shortlist. Type the name, and if both are Other, separate them with a comma: Swahili, Thai. Leave it empty otherwise.

4. Channels

Where translation happens. Two details catch people out:

  • You can select up to ten channels here. That is generous for a first setup. Start with one or two.
  • Leaving it empty uses the channel you ran the command in. An empty field is not a "whole server" instruction. Run /quickstart in #welcome with nothing selected and only #welcome gets translated.

Jake checks it can post in whatever you select and refuses the setup rather than creating one that cannot work, which catches the most common first-run failure before you hit it.

5. Translate both ways?

On by default, and this is the field that decides what kind of channel you end up with. On creates two setups, one each direction, so both language groups read in their own language. Off creates one direction, for a channel carrying a stream of messages to one group, such as translated announcements.

Two-way is skipped automatically when the source is auto-detect, and the confirmation says so. That is not a bug: auto-detect has no fixed source language to reverse. If you want a genuine bilingual channel, name both languages instead of using auto-detect.

Press submit and the setup is live. The confirmation shows the pair, the channels, and whether a paired setup was created.

Nothing in that form is permanent. Languages, channels and two-way can all be changed afterwards with /translation channels edit, or from the server's dashboard.

Prove it works before you tell anyone

Set up but not working looks identical to a quiet channel. Test it in the first five minutes:

  1. Post a full sentence in the source language in the translated channel. Not "hi" and not "test": very short messages are the hardest thing for any language detector.
  2. Check what appears. You should get a new message with the translation, and the original left where it was.
  3. If two-way is on, post in the other language too. Only one direction working usually means the paired setup was not created, which happens when auto-detect was the source.

If nothing appears, work through the troubleshooting section rather than rebuilding. Duplicate setups are more common than missing ones.

Choosing the right channels

Most servers want one or two shared channels, translated in place. The alternatives:

Shape How Good for
Shared channels /quickstart, pick them Most servers. One conversation, translated
A whole category /translation channels new, choose the category A section for one language group
Every channel /translation channels new, "run in every channel" to yes Translation as the default, not scoped

Worth knowing:

  • Threads inherit their parent channel, so threads started from a translated channel are translated too, no extra setup. Forum posts behave the same way.
  • Categories work as a source. /quickstart only offers text channels, but /translation channels new accepts a category, and anything inside it is covered, including channels you add later.
  • Two setups watching the same channel for the same target language double every translation. Run /translation channels list if a channel looks repetitive. This usually follows someone re-running /quickstart because they were unsure the first one took.

Start smaller than you think you need. Cost scales with messages, not members, and translating everything on day one is how servers run out of characters in days.

The settings worth changing afterwards

None of this is required, and each has a clickable equivalent in the dashboard if you would rather not type slash commands.

How translations look. /translation style set switches between the default embed, Compact (embedless) for busy channels, and Translation Morph, which posts with the original author's name and avatar so the channel reads like a conversation. Morph needs Manage Webhooks in the channel. Styles are set per kind, so automatic and flag-reaction translations can look different.

Where translations go. By default they post in the same channel. /quickdivert sends a setup's output elsewhere, which is how channel-per-language arrangements are built. /translation channels edit controls whether messages that needed no translation are forwarded too, the setting that makes a diverted channel either a full mirror or one with gaps.

Long messages. /translation channels character_limit cuts messages before translating. Zero means no limit. Useful if people paste essays.

Words and roles. /translation blacklist blocks words that every engine mangles, such as game-specific terms. Per-setup role allowlists are in the dashboard.

The engine. Free runs on Microsoft. /translation translator switches to Google, DeepL or ChatGPT, all of which need a paid plan. ChatGPT or DeepL are especially worth trying if the free output is close but reads stiff.

When it does not translate

Permission to send. Jake needs to see the channel and post in it. Private channels and category overwrites that exclude the bot are the single most common cause, and it usually appears after someone tidies up permissions.

The channel is not in the setup. /translation channels view shows exactly what a setup watches. It is easy to have set up the wrong channel.

Messages starting with ! or ? are skipped. Command activation messages are ignored by default so prefixes are not translated. If your community writes that way naturally, disable the blocker with /translation extras disable feature:CMD Activation Messages Blocker.

Very short messages are skipped. "ok", "gg" and lone emojis often fail detection. Expected, not broken.

The allowance is gone. /translation usage shows characters used and left. It is monthly, resets, and translation stops when it runs out. A busy channel translating into several languages gets there faster than people expect.

Commands look out of date. Re-invite from the addme page or restart discord rather than editing the existing integration, which can leave the command list stale.

Frequently asked questions

Can I translate into more than one language? Not in a single setup: one setup has one target. Three languages means three setups over the same channels, and three times the characters.

Do members need to do anything? No commands, no reactions, no settings. Each member can optionally set their own language with /your_language, which makes the right-click To Your Language option a one-click translation for everything outside the translated channels.

Does it translate other bots' messages? Yes, by default, including embeds.

Does it translate old messages? No. It applies to new messages from the moment the setup exists. Older ones can be translated one at a time with /translate or the right-click Apps menu.

Can I turn it off without deleting it? Yes. /translation channels edit disables a setup and keeps its configuration, which beats deleting it when you are still deciding whether you want translation at all.

The short version

Run /quickstart, choose Auto-detect as the source and your members' language as the target, select one busy channel rather than ten, and do not rely on two-way when you are using auto-detect. Post a full sentence to confirm it works, then widen with /translation channels new once people are used to it, or from the dashboard if you prefer a page to a form.

For flag reactions, the right-click menu and the other ways to translate, see how to translate Discord messages. If your server has separate language groups who each want their own channel, the multilingual alliance guide covers that layout and the character maths. Everything per-channel is documented on the translation features page.

← All articles