Discord Translate Bot: On-Demand Translation Commands for Any Channel

A Discord translate bot gives a server two ways to close the language gap. The on-demand route is a command like /translate: you call it when you need it, name the message and the target language, and the bot replies. The automatic route has the bot watch configured channels and translate every message that is not already in that channel’s target language. On-demand is for the moment you need a translation; automatic is for a room where different languages share one thread. Interaction Bot, a translation bot active in more than 55,000 Discord servers (homepage figure), offers both, and this guide covers the command side, the shortcuts, the language list, and how the two styles compare.

The /translate command, and the two commands around it

Command-based translation in Interaction Bot is three slash commands, per the official translation command reference:

The syntax is exactly what it looks like. You type the text you want translated into the first argument and the language name into the second, for example /translate ¿A qué hora empieza? English. The <language> argument accepts any language the bot knows, so you pick the target fresh on every call. If a message is in an unknown script or you are not sure what it says, run /detect <message> first and it identifies the source language. And /languages prints the full list so you never guess a name.

The same command line also exposes the automatic side. /config detector <char> sets the minimum number of characters a message needs before the bot will auto-translate it, /config get <option> shows the current configuration, and /config flag_translation turns on the flag-emoji shortcut described below.

There is one more on-demand option that needs no command at all. Select any message in Discord, open the app menu, and choose Translate. On Interaction Bot this translation is ephemeral: the target language is taken from your Discord application language, and the result is visible only to you. It is the least intrusive on-demand option of all, since nobody else in the channel sees it.

Gehsture’s walkthrough of a Discord translator bot, at around seven minutes, shows the automatic listener mode alongside translating individual messages on demand, which is a useful visual for both styles:

The shortcuts that need no typing

On-demand does not always mean a command. Interaction Bot supports two shortcuts that trigger a translation without you forming a sentence.

Flag reactions. On a channel where the admin has enabled flag translation, any member can click a country flag emoji on a message and the bot translates that message. The dashboard lets the admin choose whether it translates on every new reaction or only the first time a message is handled, and whether the output auto-deletes. As the customer’s own setup guide puts it, flag mode is the lowest-noise option for channels where most members share a language but occasionally need help. It is the closest thing to a universal shortcut: a reaction, not a sentence, requests the translation.

Mentions. The command parameters accept Discord mentions, so rules can be aimed at a specific #channel, @role, or #category rather than typed out in full. For a one-off /translate, though, the message and the language are all you need.

How many languages can a translate bot handle

Interaction Bot supports more than 100 languages, according to its FAQ. /languages prints the full list, and the same list feeds the language field of every automatic translation rule, so it is worth running it once before you configure a channel.

Because detection has to choose among 100+ languages, a very short message or one packed with emoji can be identified incorrectly. That is a strong argument for the on-demand command: /translate <message> <language> states the text and the target, so there is no guessing step at all. If you rely on automatic detection instead, raising the minimum message length with /config detector reduces the margin for error, which the FAQ recommends for short or emoji-heavy messages.

Command-based translation versus auto-translate

The two modes answer different questions, and a server usually runs a mix. Here is the direct comparison:

Automatic translation is event-driven: Discord sends the bot an event when a member posts, the bot detects the source language, translates into the rule’s target, and posts the result, usually as a bot reply or embed. The customer’s article on how automatic translation bots work on Discord walks through that pipeline in detail. Automatic rules also carry output options such as embedding as a webhook, deleting the original when it is not in the target language, or automatically removing the translation after a time that depends on message length.

The practical difference is control. On-demand puts the decision in your hands for that message only. Automatic sets a policy for a whole channel, so a speaker of the target language stops seeing back-to-back duplicate translations overhead, which is exactly why auto-translation cuts the noise in a busy multilingual room.

Where on-demand commands earn their keep

Automatic translation shines in a channel where people genuinely share a single thread. On-demand shines everywhere else. Internationally staffed teams, the kind that hire across borders and manage mixed-language communication every day, rarely need every message in every room translated for everyone. Forcing an entire team into one auto-translated channel replaces one problem with another.

In that setting, on-demand scales cleanly. A project manager sends one /translate to read a partner’s update, a support agent calls /detect on a ticket that arrived in the wrong language, and a member asks one question with a flag reaction instead of a sentence. Nobody reads more than they need, and no translation is published it was not requested. For international teams that is the polite and efficient default, with auto-translate reserved for the handful of rooms where languages genuinely share the conversation.

Putting on-demand translation to work

The command side works the moment the bot is in the server. To get there, add a translator bot to Discord in roughly five minutes: authorize it through Discord’s permission screen, open the dashboard, and pick your server. A short checklist once it is live:

1. Run /languages to see the supported language list.
2. Use /translate <message> <language> for one-off requests.
3. Use /detect <message> when the source language is unclear.
4. Ask an admin to enable flag translation on the channels where members share a language but occasionally need help.
5. Reserve full auto-translate, via /config or the dashboard, for channels where different languages genuinely share one thread.

The short answer. A Discord translate bot’s on-demand commands are /translate <message> <language> for a one-off translation, /detect <message> to identify a language, and /languages to see what the bot supports, with flag-emoji reactions as the no-typing shortcut. They cover more than 100 languages and differ from auto-translate in one word: control. Command-based translation happens when you ask and goes exactly where you point it; auto-translate applies a fixed policy to a whole channel. Most multilingual servers, especially international teams, are better served starting with on-demand and adding auto-translate only where the conversation really needs it.