Discord Translation Bot Setup Guide (Step-by-Step, 2026)

The version we wish existed when we set up our first multilingual server: prerequisites, slash commands, verification, the six most common day-one errors, and exactly when to upgrade tiers. Tested against the bots that actually work in 2026.

Setting up a Discord translation bot looks intimidating in screenshots and is genuinely fast in practice. Most working configurations take under five minutes from a blank channel to translated messages in two languages. The guide below is the version we wish existed when we set up our first multilingual server: every step laid out in order, with the prerequisites you actually need, the slash commands you actually run, the verification you should actually do, and the errors that most servers hit on day one.

It uses Kiki The Translator as the primary example because its setup commands are the shortest, but the conceptual shape (invite, configure, verify, scale) is identical for every serious Discord translation bot.

Before you start: the three prerequisites #

A translation bot needs three things from your server. Confirm each one before you invite the bot, because finding out you are missing one halfway through setup is the most common reason a bot install stalls.

1. Manage Server permission. Only server admins can invite bots. If you do not have Manage Server, ask whoever does to invite the bot for you; they can grant you per-bot configuration permissions afterwards without making you a full admin.
2. A channel structure that matches your intent. Decide before installing the bot which channels will be translated. The common patterns are: one shared channel translating between two languages (the simplest); one shared category with multiple channels translating between two-to-four languages; or separate language-specific rooms that are mirrored to each other (advanced). You can change this later, but knowing the rough shape avoids reconfiguring three times in the first hour.
3. A clear primary language. Pick the language new members and announcements default to. This is the language your channel names, your #rules, and your #welcome message will live in. Translation bots work in both directions, but a server with no defined primary language tends to drift and confuses new joiners.

If you have all three, you are ready to install.

01Invite the bot #

Every Discord bot installs through the same OAuth flow. The bot's website provides an invite link; clicking it opens Discord and asks which server you want to add the bot to, along with a list of requested permissions.

For Kiki, the invite link is on the homepage at artranslationtechnologies.com. Click "Add to Discord," pick your server from the dropdown, and review the permissions. The bot needs to read messages (to detect language), send messages (to post translations), manage webhooks (to post translations under the original author's name and avatar), and add reactions (for flag-emoji translation). All of these are required; declining any of them breaks the feature they support.

Confirm, and the bot appears in your server's member list. It does not start translating yet; that requires the setup command in Step 3.

02Decide the configuration scope #

The first decision is whether translation runs server-wide or only on specific channels. The Kiki setup command (/set_2_langs) takes a language_setup_for parameter with two values:

• this_channel_only: translation runs only in the channel where you run the command. Best for servers where most channels are single-language and only a few are international.
• the_entire_server: translation runs on every channel, including channels you create later. Best for fully multilingual servers where every conversation crosses languages.

03Run the setup command #

This is the core moment. In the channel you picked (or any channel, if you chose server-wide), type:

/set_2_langs language1: <first language> language2: <second language> language_setup_for: <scope>

Discord's slash-command UI auto-completes the language fields as you type. Pick the two languages your community uses; the order does not matter (the bot translates in both directions). For language_setup_for, pick this_channel_only or the_entire_server as decided in Step 2.

Hit enter. The bot replies within a second or two confirming the configuration. If you see an error message instead, jump to the "Common errors" section near the end of this guide.

For three or four languages the commands are /set_3_langs and /set_4_langs respectively. The parameter shapes are the same, with a third (and fourth) language field. Note that three-language setup requires the Whisker Whispers ($3) tier or higher, and four-language requires Meow Majesty ($6); the free Purrfect Pals tier supports two-language setup only.

04Verify with /status #

The single command every new install should run before declaring success is /status. It opens a paginated, multilingual menu that shows exactly what the bot thinks your configuration is.

The Overview page lists:

• Your server's current tier (Purrfect Pals, Whisker Whispers, Meow Majesty, or Feline Finest)
• The server-wide language configuration (if you chose the_entire_server)
• The current channel's specific configuration (if you chose this_channel_only)
• The translation theme
• Auto-backup status
• AI Server Assistant availability

If the configuration matches what you set in Step 3, you are done. If something looks wrong (for example, the channel is listed as having no configuration), the most likely cause is that you ran the command in a different channel or scope; re-run Step 3 in the correct channel.

05Send a test message #

The final verification is a live translation. Post a short sentence in the configured channel using one of the two languages. Within a second or two, a second copy of the message should appear, translated, posted by what looks like you (same avatar, same display name). This is the webhook trick: the bot posts via a Discord webhook configured to mimic the original author, so the translated message reads as if you posted it yourself in the other language. This is intentional and preserves conversation flow.

Reply to the bot's translation. Your reply should also be translated, anchored to the right thread. Reactions on either copy should work normally.

If the bot does not respond at all, check that the bot has not been silenced in the channel (Channel Settings → Permissions → Kiki → Send Messages must be on) and that the message is actually in one of the two configured languages. A message in a third language is detected but not translated, because there is no target.

Advanced setup: 3 and 4 languages #

For communities with members across three or four languages, the setup pattern is identical to two, just with a different command:

/set_3_langs language1: English language2: Spanish language3: Portuguese language_setup_for: the_entire_server
/set_4_langs language1: English language2: French language3: German language4: Italian language_setup_for: this_channel_only

Three-language requires Whisker Whispers tier ($3/month); four-language requires Meow Majesty ($6/month). The tier check happens at command time; if your server does not have the right tier, the bot refuses the command and explains why.

A practical note: more languages mean exponentially more translations per message. A three-language setup translates each message twice (once per other language); a four-language setup translates each message three times. The translation word count scales the same way. Budget for it.

Advanced setup: channel mirroring within a server #

Mirror translation (also called dedicated-language translation) is for the situation where you want one channel per language but want them to stay in sync. French speakers post in #lounge-fr, Japanese speakers post in #lounge-jp, and a message in either appears, translated, in the other.

The command is /set_dedicated_lang. You run it once per channel, giving each channel a language and a shared channel_group name. The group name is what tells the bot these channels belong together.

/set_dedicated_lang language: French channel_group: lounge

Run the same command in each channel that should be part of the group, with the appropriate language and the same group name. After all channels are configured, post a message in any of them; it appears, translated, in every other channel of the group.

Mirror translation requires Meow Majesty ($6/month). To unlink the group, use /delete_group <name>. To unlink one channel, run /set_dedicated_lang again with a different group name (which moves it) or use the dedicated unlinking command.

Advanced setup: cross-server bridging #

The most advanced configuration links channels across two separate Discord servers. Gaming alliances, partner communities, and the regional branches of one organisation use this to keep a shared channel running without merging their servers.

The command is /set_interserver_translation. The flow is a handshake:

1. On the first server, in the channel you want to bridge, run /set_interserver_translation. The bot generates a unique group ID and shows it to you.
2. Send the group ID to the admin of the second server.
3. The second admin runs the same command in their channel and enters the group ID when prompted.
4. The two channels are now bridged. A message in either one appears, translated, in the other.

Both servers need the Meow Majesty tier or higher because cross-server translation consumes substantially more API capacity. Test from both directions before declaring success; cross-server bridges sometimes hit Discord rate limits in one direction first.

Common errors and fixes #

Six errors cover roughly 90% of the day-one problems we have seen:

• "This server needs a higher tier." The command you ran requires Whisker Whispers, Meow Majesty, or Feline Finest. Either start a free trial with /free_trial (one per server, every six months) or buy tokens at the pricing page.
• "Kiki cannot send messages in this channel." The bot's role lacks Send Messages permission in this specific channel. Open Channel Settings → Permissions, add the Kiki role, and grant Send Messages, Embed Links, and Manage Webhooks.
• The bot does not respond at all. Most likely the bot is offline (rare) or the bot's role has been silenced server-wide. Run /status in DMs with the bot to verify it can hear you.
• Translations appear without the original author's avatar. The bot's role is missing Manage Webhooks permission. Webhook-mode translation falls back to plain bot-message mode without this permission, which works but reads awkwardly. Grant the permission and re-test.
• Some messages get translated, others don't. The language detection treats very short messages (one or two words, single emoji, URLs) as low-confidence and skips them to avoid garbage translations. This is intentional; long-form messages translate reliably.
• "This language pair is not supported." Both languages in your configuration must be in the bot's supported list. Kiki supports 100+ languages but a handful of regional dialects are not yet covered. Use /status to see the full list, or pick the closest standard language as a substitute.

When to upgrade tiers #

Most servers start on Purrfect Pals (free, 300 words/day/member, two-language only) and stay there until one of three things happens:

1. They run out of free words during the day. A server of 30 people pools roughly 9,000 free words/day. If your translation volume exceeds that consistently, you will see members hit the cap by evening. Upgrade to Whisker Whispers ($3) or higher.
2. They need a third or fourth language. Free tier supports two languages only. Whisker Whispers adds three-language; Meow Majesty adds four-language and mirror translation.
3. They need AI features. Multilingual onboarding, scheduled announcements, AI server management ("Hey Kiki, create a tournament category"), and themed translations are Feline Finest ($9). These features pay for themselves quickly on a large, active server; they are overkill on a small one.

Compare full tier features on the pricing page, or for a head-to-head against other free options see the free Discord translator bot comparison.

What to do after setup is done #

Once your bot is configured and you have verified live translation works, three things are worth doing in the first week:

• Watch the analytics for a week. Run /status periodically. Note the translation count, daily-words-claimed count, and active-user count per language. These tell you whether your configuration matches actual usage; you will almost always want to adjust something after seven days of real data.
• Block other bots from being translated. Music bots, giveaway bots, and moderation bots post text that the translator will dutifully translate into chaos. Run /block_translation (or your bot's equivalent) for every non-translator bot. This is the single most common cleanup task after install.
• Pin a short explanation in the translated channels. A two-sentence pinned message ("This channel auto-translates between French and English; reply in either language") prevents the first week of confused new joiners. New members notice the pinned message faster than they notice the bot.

What to do if something is off #

Translation bots are mature in 2026, but Discord rate-limits and the occasional API blip do happen. The fast-path debug:

1. Run /status and confirm the configuration is still set.
2. Send a test message in a known-supported language; if it translates, the bot is healthy and the original issue was a one-off.
3. Check the bot's support server; most serious bots run one. Kiki's is at discord.gg/c2733c4HJ9. Posting your server ID and the failing command gets you a fast answer.
4. If the issue persists, the contact page is the right escalation for paid customers.

The goal is to have translation feel boring within the first week: running quietly in the background, doing the thing it was installed to do, no daily babysitting. With the setup above, most servers reach that point on day one.