How Many Languages Can a Discord Translator Bot Handle? A Supported-Languages Guide

The short answer, first: a mainstream Discord translation bot supports 100-plus languages today, and the three bots this site compares each say so on their own pages. Interaction Bot advertises “over 100 languages” on its homepage and in its FAQ, iTranslator lists 109+, and TranslateBot claims 100+. Those counts are the headline, not the story. What decides whether a bot works for your community is which languages sit inside that number, how the bot detects the language of a short or emoji-heavy message, and whether the headline describes what every member actually gets on the plan you run. This guide covers all three, with the numbers as they stood in August 2026.

The 100+ counts, as they stood in August 2026

Interaction Bot’s homepage says the bot “lets you translate your messages into over 100 languages”, and the FAQ explains why that makes detection careful: “the bot supports more than 100 languages, so it must detect all these languages in any message”. iTranslator’s homepage lists “109+ Languages supported” alongside a 99.9% uptime claim and an average translation speed under 0.2 seconds. TranslateBot’s homepage says “over 100 languages available” and reports more than 9 million messages translated a month across over 3,000 servers.

Two things to keep in mind about any of these counts. First, they are snapshots: a bot can add or rebalance languages as it changes engines, so check the current list rather than the homepage number. Second, a count is a ceiling, not a floor. What you actually get can be smaller, and the rest of this article is about what sits inside the number.

What “100+” means in practice

A translator bot does not translate anything itself. It forwards message text to a cloud translation API, such as Google Cloud Translation, Microsoft Translator, or DeepL, and posts the result back to Discord, as this site’s article on what a translator bot is explains. The bot’s “supported languages” list is literally the set of language codes that its engine accepts as a source and a target. As the site’s bot comparison notes, the three bots above draw from the same pool of machine translation engines, which is exactly why their counts all land in the same 100-ish band instead of 10 or 10,000.

A set of more than 100 codes leaves room for every major world language, and that is what these lists contain. It also means every major writing system. Chinese (simplified and traditional), Japanese, and Korean each use distinct scripts, and a busy international channel can show all three in a single scroll.

The set also covers right-to-left scripts. Arabic and Hebrew are ordinary entries in a 100+ list, and Discord renders them without special handling, so a channel with an Arabic target behaves like any other.

Where the headline gets fuzzy is regional variation. A single “language” can be several dialects, and engines disagree on how to split them. Portuguese may be one code that covers Brazil and Portugal, or two separate entries, and the same is true for regional varieties of Spanish, Arabic, and English. The useful habit is to treat “100+” as a promise that the majors are covered, then confirm the specific variant your members speak against the actual list before you set it as a channel target.

How language detection works, and where it fails

Before the bot can translate, it has to guess what language the message is in. Detection is a statistical estimate: the engine scores the text against models for every language in its list and returns a language code with a confidence value, and this site’s article on what a translator bot is walks through the mechanics. Most detectors treat a score of 0.8 or above as a reliable guess and skip anything lower.

Detection fails in predictable places, and the Interaction Bot FAQ names them directly: “sometimes the message is too short to determine the language or contains too many unwanted elements like emojis or other things.” Each common failure mode follows from that:

• Short messages. A detector needs evidence, and “lol ok” has almost none. Microsoft makes the same point in its language detection documentation, noting that automatic detection works better with longer input, as the site’s article on how automatic translation bots work reports.
• Emoji and noise. A message that is mostly emoji, mentions, or links carries no natural-language text to weigh.
• Mixed languages. The detector has to choose one code per message, so a sentence that starts in Spanish and ends in Portuguese is a coin flip no matter how good the engine is.
• Dialects. A regional form can sit close enough to the standard code that the match looks right but the translation is off, or the detector may consistently confuse two similar languages.

Two fixes come out of the same FAQ. An admin can raise the minimum message length before a message is auto-translated, through the /config detector command or the dashboard, and a language that is “too often confused with another” can be banned so the detector must pick something else. The article on how automatic translation bots work adds the third safeguard: a well-behaved bot protects mentions, links, code blocks, and commands so a translation never pings the wrong person or breaks syntax.

Per-channel target languages are not your Discord UI language

This is the confusion that trips up more admins than any other. A Discord translation bot has two separate “languages” that have nothing to do with each other.

The first is the per-channel target. In the Interaction Bot dashboard’s channel translation page, a rule is built from three fields: the channel to watch, the channel where the translation gets sent, and the LANGUAGE field, the target for everyone reading that channel. Any message in the watched channel that is not in that language is translated to it, and the result is posted where the whole server can read it.

The second is your own Discord application language. Interaction Bot also offers an app-menu Translate option: you right-click any message, choose Translate, and the bot replies with a translation based on your Discord client’s language. That translation is ephemeral, the translation command reference notes, meaning only you can see it.

So one setting is server-wide and permanent (the dashboard’s per-channel LANGUAGE) and the other is personal and temporary (app-menu Translate, which follows your Discord language). An admin with an English Discord client who right-clicks a French message and sees an English translation has not broken anything. That is the per-user path. The channel’s own auto-translation, meanwhile, might be configured to translate the same message into Spanish for the rest of the room. Same message, two correct results, two different settings.

iTranslator’s official demo, Discord Automated Translation, Translate Messages in Multiple Languages, is a 49-second look at its automatic mode handling several target languages, and it makes the per-channel model visible quickly:

How to get a bot’s complete language list

The headline count is a teaser; the full list is what you configure against. For Interaction Bot it is one command: /languages prints the entire set inside Discord, and the same list feeds the language field of every automatic translation rule, as the on-demand commands article explains. Run it once during setup and keep it open while you build channel rules. The dashboard dropdown, the /translate command’s language argument, and /detect all draw on that same list.

For iTranslator, the count is 109+, and the language choices appear in its web dashboard; the homepage carries the headline. For TranslateBot, which is configured by commands rather than a dashboard, the supported set is whatever its linked-channel and flag features accept. Whichever bot you are evaluating, the test is the same: find the mechanism that lists supported languages, usually a command like /languages, a dashboard dropdown, or the documentation, and read the tail of that list, not the headline.

Choose by the languages your members actually speak

The buying decision is rarely “100+ yes, 40 no”. It is “does the exact language my members speak exist in this bot’s list?” A server with English, Spanish, Portuguese, and Japanese members probably works with any of the three bots above. A server whose members want Brazilian Portuguese treated as a distinct target, or whose community relies on a minority language, needs to check the list before choosing anything.

One more reason to check rather than trust the headline: the count on the box is not always the count you get. iTranslator’s free tier serves only a subset of its languages, 30 of them, with the full 109+ on Premium, as this site’s comparison of Discord translation bots details. TranslateBot puts its 100+ behind character packs you buy once. Interaction Bot does not gate its language set by plan; its FAQ discusses paying to improve translation quality, not to unlock languages. A fuller comparison of features, pricing, and performance lives in that companion article.

The short answer

A Discord translator bot today handles about 100-plus languages: Interaction Bot at 100+, iTranslator at 109+, and TranslateBot at 100+, as of August 2026. Treat the count as a promise that the major languages and writing systems are covered, verify the exact languages, regional variants, and scripts your members speak against the bot’s actual list, and remember that “supported” and “available on your plan” can be two different numbers. That verification, not the headline, is what makes a multilingual server actually work.