TL;DR: As of September 2026, Discord has no built-in message translation — desktop, mobile, or web. The right-click “Translate” button you keep looking for does not exist. For frictionless Chinese reading there are three main roads: Vencord’s Translate plugin on desktop (default engine ships a free endpoint, zero API keys, tested working); Discord Web in a browser with Immersive Translate (officially adapted for Discord, and the only mature way to plug in your own LLM API); a translation bot for your server (managed BabelBot, or self-hosted open-discord-translator). A fourth free side door: Greasy Fork userscripts riding Google’s keyless endpoints.

On method, so you can reproduce this: the material comes from two rounds of parallel research. Round one deployed 110 AI sub-agents across 5 angles scanning official docs, GitHub source, and plugin stores; of 107 extracted fact claims, 25 core claims went through 3-vote adversarial verification (three independent verifiers each gathering primary evidence; any challenge sends the claim back). Round two sent 12 more sub-agents to fill the gaps round one itself flagged — the BetterDiscord plugin ecosystem, Greasy Fork userscripts, managed commercial bots, and four supplementary GitHub repos. Every engine, language code, and endpoint URL was verified down to source code, not paraphrased.

Killing the official route first: the button truly doesn’t exist

This is the most valuable verification in the article. We pulled the full text of Discord’s official March 6, 2026 patch notes and searched for “translate” — 3 hits, all CSS transform style values, not a single feature entry. Immersive Translate, Talksy, JotMe — competing vendors who would love to cite an official competitor — plus years-old feature request threads in Discord’s own feedback forum all give the same answer: no native translate button, no per-channel auto-translate setting. The only option is copying messages to external tools.

Honest scope note: we verified the official changelog and multiple independent secondary sources; hidden experimental flags or A/B tests cannot be ruled out. The community-claimed “Discord Nitro voice channel auto-translate” traces back only to feature-request posts with zero official URLs — during research the Grok engine surfaced this as a “counter-claim” and we judged it likely fabricated. Not adopted.

So the real question becomes: which third-party route deserves you.

Route 1: Desktop client, Vencord Translate, the five-minute path

If you run the desktop app, this is the cheapest entry. Vencord is the most actively maintained Discord client mod; install it, go to Settings > Plugins, search “Translate”, enable. Done.

Why zero-cost works: the default Google engine hard-codes a public key in source and hits translate-pa.googleapis.com’s free endpoint. We sent a test English string with that key and got back “你好世界，你好吗?” — no money, no account registration. Output language defaults to English, so switch it to Chinese: Google engine uses zh-CN/zh-TW, DeepL uses zh-hans/zh-hant, source language defaults to auto-detect. Cantonese (yue) is also available on Google.

Interaction splits by direction: incoming messages are translated per-message manually — right-click “Translate” (listed after Copy Text) or the hover button; outgoing can enable autoTranslate, converting your Chinese to English before sending. Receive and send directions configure languages independently.

The ceiling is equally clear: the engine dropdown offers only Google / DeepL (Free/Pro) / Kagi, and grepping all 7 plugin files finds zero LLM or OpenAI-compatible endpoint traces. To wire your own DeepSeek or local Ollama into the client, see Route 5.

Route 2: The BetterDiscord ecosystem, an 1.8M-download veteran

BetterDiscord is the older client mod; its plugin directory holds exactly two real translation plugins:

Translator (by DevilBro) is the absolute heavyweight — v2.8.6, 1.8 million downloads, updated 2026-09-17. Its service list beats Vencord’s: Google (free web + API key), DeepL (both modes), Azure, LibreTranslate, plus a custom web-API endpoint. Chinese is covered. But no LLM either — its custom endpoint is a traditional translation-API shape, not the chat-completions protocol.

AutoTranslate (by Snues) is the minimal option: Google only, v0.3.2, 8.6K downloads, updated 2026-06.

A rumor killed along the way: one source mentioned a “Venz25 Translate” plugin on BetterDiscord. We checked the full betterdiscord.app translate-filtered listing and GitHub — it’s not on the site, and github.com/Venz25 has zero public repositories. That plugin does not exist.

Route 3: Discord Web in a browser, Immersive Translate — the only mature LLM vehicle

If you can live with browser-based Discord, this route has the highest ceiling of all six.

Immersive Translate officially maintains a Discord adaptation: it auto-detects and inline-translates channel messages, DMs, and server announcements — bilingual side-by-side, hover translation, and input-box translation (type Chinese, auto-render English before sending) all supported. Its GitHub issue stream carries roughly 10 Discord-related issues from 2023–2025; issue #3684 (2026-02) live-confirmed channel messages translate correctly, and the developer shipped discord.com-specific rule refreshes. Long-term maintenance is real.

The killer feature is engine breadth: official docs list 28 switchable engines — DeepL, OpenAI, DeepSeek, Claude, Gemini, Ollama, OpenRouter all present, plus a dedicated Custom API endpoint page. That means you can point it at any OpenAI-compatible LLM gateway and run full-page translation on a cheap model, a quality tier above classic machine translation. Among all six routes, Immersive Translate is the only fully mature vehicle for the custom-LLM-endpoint requirement — Vencord doesn’t, BetterDiscord doesn’t, userscripts have scattered single-author attempts.

Two mandatory caveats. First, a known bug: code blocks in Discord Web don’t get translated (issue #3684, reported 2026-02) — discount the marketing word “seamlessly”. Second, in August 2025 the Chinese community erupted in controversy — a Juejin article claimed the product “fully banned custom APIs” and the founder was embroiled in a doxxing/privacy storm; but the article itself notes the official account “promptly denied” the announcement, timelines are vague, the security allegations were never independently confirmed, and the Custom API feature demonstrably still exists in official docs today — directly contradicting the “full ban”. Recorded as an unverified community controversy, not a functional fact.

Shopping warning: a Chrome Web Store extension named “Discord Translator - immersive” (ID nenhidhf...) is not the official Immersive Translate — it’s an independent third-party product by slowcodehub (~4,000 users, 18 reviews, 3.7 stars) advertising “100+ languages, two-way auto-translate” with no third-party testing. The official listing ID is bpoadfkcbjbfhfodiogcnhhhpibjhbnh.

Route 4: The free side door, Greasy Fork userscripts

Install Tampermonkey/Violentmonkey, open Discord Web. We downloaded all 8 relevant scripts from Greasy Fork’s “discord translate” search and grepped each source for engine, language, and endpoint; Sleazy Fork confirmed zero. Notables:

• discord-translate (script 543665, updated 2025-07): three engines — LLM (defaults to api.deepseek.com/v1/chat/completions, OpenAI-compatible, swappable), LibreTranslate, DeepL. Target language is free-text config; zh-CN works. A rare true-LLM userscript.
• Discord AI 自动翻译及回复助手 (566879, updated 2026-02): Chinese-language UI, default target Simplified Chinese, LLM presets OpenAI/DeepSeek/custom, plus context-aware translation and reply suggestions.
• #1 Universal Translate (581180, updated 2026-06): multi-site (FB/Telegram/X/Reddit/Discord), DeepL/LibreTranslate/MyMemory chained fallback with caching, optional AI-review pass.
• Discord Universal Translator (562045, updated 2026-01): purely free, rides translate.google.com/m keyless, auto-translate queue with a drag widget.
• Translate Discord Messages (489409): rides translate.googleapis.com/translate_a/single?client=gtx keyless — but target language is hardcoded const translateTo='en'; you must edit source for Chinese.

A fact that overturned our own expectation: we assumed userscripts would use the translate-pa.googleapis.com hard-coded key (Vencord’s pattern), but after ripping open all 8 script sources, not one uses it — the userscript world’s real free endpoints are translate.googleapis.com’s gtx parameters and translate.google.com/m, both keyless. These unofficial endpoints have no SLA and could die any day, but they’ve run stably for years.

Route 5: LLM inside the client, a narrow door

To wire your own LLM directly into Vencord, there’s exactly one door: TheRealMagyar/Vencord-ai-plugin. Its Custom provider connects to any OpenAI or Anthropic compatible endpoint — Ollama at 127.0.0.1:11434/v1, LM Studio, vLLM, llama.cpp, OpenRouter are all named in the README; translation happens via prompts.

Honest weaknesses: a 4-star single-author userplugin requiring you to build Vencord/Equicord from source, Desktop/Vesktop only, no Vencord Web. Single-author abandonment risk is structural — choosing it means accepting you may inherit the project one day.

Route 6: Translation bots, the server-grade route

The first five routes are “I read comfortably”; bots solve “the whole server reads comfortably” — channel-level auto-translation and bilingual mirror channels.

Managed bots (invite and go): nvu.io’s Translator is the incumbent — ~309,000 servers — but its free tier allows only 2 target languages, no updates since October 2025; a dormant operation. BabelBot is the most active: v2.21.9 released 2026-09-23 (the day before this article), AI-engine translation, and server-level custom glossaries — names, slang, and memes can be pinned to fixed translations, its unique killer feature; free tier also caps at 2 target languages, Pro at 5. Talksy gives 100 auto-translations/month free with all 100+ languages including Chinese. RitaBot runs open-source + managed dual-track; self-hosted with your own Google Cloud key. iTranslator and TranslateBot round out the list — the latter’s site footer still says 2023, choose carefully.

Shared limitation of managed bots: none support custom LLM endpoints; you use their engines and your messages transit their servers.

Self-hosted bots: the pick is open-discord-translator — Apache-2.0, Docker/K8s/Node deployment, four backend drivers (google_search free / google_cloud / DeepL / LibreTranslate), with zh-CN and zh-TW in the default language list. Two modes: right-click apps > translate per-message into the user’s client language (personal reading), and channel-level replicas bilingual mirroring (community channels). No LLM driver, but the README documents the plugin mechanism — drop a module implementing init() + translate() into ./src/translations/drivers/, set TRANSLATION_API_DRIVER, and you’re on your own LLM. Three warnings on the label: unmaintained since 2024-03, README says it’s designed for a small number of guilds (translation API quota limits), and replicas are off by default and require the MESSAGE_CONTENT privileged intent.

For LLM plus active maintenance, fall back to llmcord (jakobdylanc/discord-llm-chatbot, 834 stars, updated 2026-08): any OpenAI-compatible endpoint, Docker Compose one-liner. It’s fundamentally an LLM chat bot, not a translator — you write the translation prompts and triggers yourself.

One dead-repo warning for your own GitHub searches: GuySensei8/discord-translator — a 2021-02 fork, zero commits in five years, hard-codes 4 channels and en/es/fr/de language pairs (no Chinese), and its package.json main points at a nonexistent index.js; it won’t even npm install. “Perfectly named but long dead” repos litter these search results — always check last-push dates.

Selection cheat sheet

Risks and traps, all verified at source level

Client mods and ToS. Vencord/BetterDiscord modify the client, technically violating Discord’s Terms of Service. Long-term community observation: Discord has never launched ban waves against mod users; enforcement is extremely lax in practice. The risk is real but small — weigh it yourself, and don’t do it on an account with prior organized violations.

The nature of free endpoints. Vencord’s hard-coded key and the userscripts’ gtx endpoint are unofficial Google interfaces — no SLA; one day Google adds verification and it’s all gone. Ride it, but don’t build your workflow on it.

Small-project shelf life. CriDos/DiscordTranslator (6 stars), Vencord-ai-plugin (4 stars) — single-author abandonment is the norm, not the exception. Only products with a commercial entity and a maintained issue stream (Immersive Translate) merit long-term trust.

Data flow deserves thought. Translated content necessarily transits whoever owns the engine — Google for free endpoints, bot operators for managed bots, Immersive Translate’s servers for its defaults. Wiring your own LLM endpoint (Immersive Translate Custom API, userscript custom endpoints, self-hosted bots) is the only way to keep message content inside a gateway you control. The August 2025 data-security controversy around Immersive Translate (full-PDF upload, token collection allegations) was never independently confirmed and was officially denied — but the principle “don’t route sensitive content through default clouds” doesn’t depend on that controversy being true.

MESSAGE_CONTENT intent. Self-hosted bots reading other people’s messages must apply for this privileged intent from Discord — a procedural hurdle, not a technical one, but it has blocked many.

My final advice compressed to three sentences: personal reading, quality matters, LLM API in hand — browser + Immersive Translate + Custom API is the 2026 optimum for this problem. Just want it working in five minutes — Vencord on desktop, right-click translate. Moving a whole Chinese community into an English server — BabelBot, or self-hosted open-discord-translator’s replicas. One closing fact: Discord launched in 2015; the translation feature-request thread has hung in the official feedback forum for a decade; in the March 6, 2026 patch notes, all 3 occurrences of “translate” are CSS properties — for the foreseeable future, the third-party routes in this article are the whole map.