How to Real Time Translate Voice on Discord (2 Ways)

How to Real Time Translate Voice on Discord (2 Ways)

Jane
Jane
Published on: 05/12/2026

Why Discord needs a slightly different approach

Discord isn't Zoom. There's no built-in "live captions" toggle, no closed-caption track on the voice channel, and the desktop app doesn't expose its audio to other apps the way a browser tab does. So if you've been searching for a realtime voice translator that "just works on Discord," you've probably noticed nothing native exists.

The workaround is to treat Discord audio like any other audio source and pipe it into a voice translation layer that runs alongside it. Whisperr is built exactly for that — it takes whatever audio it can capture (a browser tab or a microphone) and gives you live bilingual captions in 100+ language pairs.

What this looks like in practice depends on which Discord client you're using. Two setups cover essentially every case.

What you need before you start

  • A Whisperr account — free tier is enough for short sessions. Sign up at app.whisperr.co.
  • The two languages you need — the one being spoken in the voice channel and the one you want to read in. Order doesn't matter.
  • For Method 1: Chrome, Edge, or any Chromium-based browser on a Mac or Windows machine.
  • For Method 2: an iPhone or Android phone with the Whisperr app installed, plus a separate device running Discord with the speaker turned on.

Method 1: Capture Discord in a browser tab (same-device, cleanest audio)

This is the method to use when you can. Open Discord in a browser tab on your Mac or Windows machine, join the voice channel there, and let Whisperr capture the tab audio directly. No microphone, no speaker, no second device — the audio stream goes from Discord's web client straight into Whisperr. Works with headphones, AirPods, or any output device, because the audio is captured digitally before it reaches your ears.

It's the same browser tab-capture pattern covered in our [Windows PC real-time voice translation post](https://whisperr.co/blog/en/how-to-translate-voice-in-real-time-on-a-windows-pc-(no-install,-just-a-browser)), just pointed at Discord instead of Zoom or Teams.

Step 1: Open Discord in a browser tab

Go to discord.com/app on your browser. Log in if you aren't already. If Discord asks whether you'd rather open the desktop app, choose "Continue in browser." This method only works with the web client because that's the tab Whisperr can capture.

join discord with web browser.png

Step 2: Join the voice channel you want to translate

Click into the server, then click the voice channel. Wait for the connection indicator to go green and confirm you can hear the other speakers. Keep this tab open — you'll need to point Whisperr at it in a moment.

Step 3: Open the Whisperr web app in a separate tab

In a new tab, go to app.whisperr.co and sign in. Don't close the Discord tab — Whisperr needs it open and playing to capture the audio.

Whisperr webapp signup.png

Step 4: Pick the two languages you need

Use the two language dropdowns at the top of the Whisperr interface. Choose the language being spoken on Discord and the language you want to read it in — order doesn't matter, Whisperr handles both directions. The 100+ supported pairs include long-tail combos like Indonesian ↔ English, Korean ↔ English, Polish ↔ English, and Vietnamese ↔ English that most native tools skip.

pick-language.png

Step 5: Click New Recording → Screen Capture → Chrome Tab

Click New Recording, then choose Screen Capture. Chrome will pop up its standard tab picker. Select the Discord tab from the list, and crucially, tick the Share tab audio checkbox at the bottom of the dialog. Click Share.

If you forget to tick "Share tab audio," Whisperr will get video frames but no sound — nothing to translate. This is the single most common mistake on this flow, so double-check the box.

screen-capture-button.png
choose discord on web browser tab capture.png

Step 6: Read the live translated captions

Live transcription in the source language and the translated text appear side by side, line by line, with sub-second latency. Switch back to the Discord tab if you want to talk or react; switch to the Whisperr tab when you need to read. Both keep running in the background.

If you want to keep the captions visible while you're in Discord, drag the Whisperr tab into its own window and resize it to a side strip. Works great on a single monitor.

discord live translate through screen capture on browser.png

Method 2: Listen to Discord with the Whisperr phone app (two-device setup)

This is the right method when Method 1 isn't an option — usually because you're on the Discord desktop app and can't (or don't want to) switch to the web client, or because you're listening to a voice channel on a console or a friend's machine.

The setup: Discord plays through speakers on Device A (laptop, PC, or another phone), and the Whisperr app on Device B (your iPhone or Android) listens through its microphone and translates. This is the same cross-device pattern covered in the Russian → English iPhone post, and it's the only method that works if Discord audio can't reach a browser tab on your machine.

One thing to flag up front: this method needs the audio coming out of a speaker. Headphones, AirPods, or earbuds won't work because the phone's mic can't hear them. If you'd rather wear headphones, use Method 1 instead.

Step 1: Get Discord playing through a speaker

On Device A, open Discord (desktop app, web, or mobile — it doesn't matter for this method) and join the voice channel. Switch the audio output to speakers, not headphones — System Settings → Sound → Output on Mac, or the speaker icon in the system tray on Windows. The Whisperr app needs to hear the audio in the air to translate it.

Step 2: Install and open the Whisperr app on Device B

Get the Whisperr app from the iPhone (App Store) or Android (Google Play Store). Sign in with the same account you'd use on the web. The phone needs mic permission — grant it when prompted.

iphone dark mode home screen english japanese.png

Step 3: Pick the two languages

In the app, tap the language selectors and choose the two languages you need — the one being spoken in the voice channel and the one you want to read in. Order doesn't matter. The same 100+ pairs available on the web are available in the app.

select input language iPhone dark mode English.png

Step 4: Place the phone close to the speaker

Within about 30–50 cm (1–1.5 ft) of the speaker is ideal. Mute notifications on the phone so they don't interrupt the recording. If the room is noisy, point the phone's bottom mic toward the speaker — that's the one most phones treat as primary for live audio translate capture.

Step 5: Tap the mic icon and start translating

In the Whisperr app, tap the mic icon and choose In-App Microphone. The app starts capturing the speaker output as if someone were standing in the room talking. Live translated captions appear on the phone screen, scrolling line by line as the voice channel progresses.

iPhone dark mode start recording options english.png
iPhone dark mode English Japanese translation.png

Bonus: Broadcast the translation to the rest of the server

Both methods above are set up for you — you're the one reading the captions. But you can flip a single switch and share the live translation with everyone else in the Discord server too.

Before you start the recording, tick the Broadcast checkbox (web app) or toggle Broadcast mode from the vertical "..." menu in the bottom left (mobile app). Whisperr generates a public room URL. Paste it into the Discord text channel attached to the voice channel — anyone who clicks the link reads the live captions in their own browser, on any device. No sign-up, no install, no mic permission needed on their end.

This is useful when:

  • One person on the call doesn't speak the language the rest are using, and you want them to follow along.
  • You're the one speaking a non-native language and want listeners to read your translated captions in real time.
  • The whole server is multilingual and one person runs the translation that everyone else reads.

Same broadcast pattern covered in the Microsoft Teams two-way translation guide, just with Discord's text-channel-next-to-voice-channel layout as the share surface.

Which method should you pick?

Your situation

Best method

You're on a Mac or Windows machine and don't mind using Discord in a browser

Method 1 (browser tab capture) — cleanest audio, single device

You're on the Discord desktop app and can't switch to the web client

Method 2 (phone app + speaker) — works without changing your Discord setup

You want to wear headphones or AirPods while listening

Method 1 — tab capture grabs the audio digitally before it reaches your output device, so headphones are fine

You can't (or won't) use speakers — late night, shared space, dorm room

Method 1 — Method 2 won't work without an audible speaker for the phone mic

You're happy to put audio on a speaker, and your second device is a phone

Either works, but Method 2 keeps your main screen free for Discord itself

You're on Discord mobile and someone else in the voice channel is the non-native speaker

Method 2 with a second device, or ask someone on desktop to run Method 1 with Broadcast on

Why this beats the alternatives

Discord's built-in translation does not exist. There's no official live caption track on voice channels, no Discord bot that translates voice in real time at decent quality, and the third-party bots that claim to do it usually rely on text translation only — typing your message and getting the bot to read it aloud, which defeats the point of a voice channel.

General-purpose translator apps assume in-person conversation. Google Translate's conversation mode wants two people in the same room taking turns with one phone. That model doesn't work for Discord, where the speakers are remote and the audio comes through a screen.

Whisperr's tab-capture and broadcast patterns are platform-agnostic. The same mechanics covered here work on Zoom, Teams, Webex, Google Meet, YouTube, Twitch, and any other audio source playing in a browser tab or on a speaker. Discord is just one more endpoint. One subscription, one workflow, every platform you care about.

100+ language pairs, including the ones gaming servers actually use. International Discord communities skew toward pairs that consumer translation tools under-serve — Korean ↔ English for K-pop and gaming servers, Mandarin ↔ English for fan communities, Russian ↔ English for esports, Vietnamese, Indonesian, Polish, Arabic. Whisperr covers all of these.

Common questions

Does Whisperr have a Discord bot? Not as of writing — the workflows above use Whisperr alongside Discord rather than inside it. The browser tab capture and broadcast URL methods cover the use cases a bot would address, without the latency overhead of a server-side bot pipeline.

Will the people I'm talking to on Discord know I'm using a realtime voice translator? Only if you tell them. Methods 1 and 2 are entirely on your side — Discord sees no difference. Broadcast mode is visible by design (you're sharing a URL), but that's the point.

Does it work on Linux? Method 1 works on Linux — any Chromium-based browser handles tab audio capture the same way on Linux as on Windows or Mac. Method 2 works too (Whisperr's Android app on a phone next to a Linux speaker). Broadcast mode is OS-independent.

Can I record the translated transcript? Yes. Inside Whisperr, you can save the bilingual transcript at the end of the session. Useful for game recaps, study sessions, or community meetings where someone needs to follow up later.

What about latency — is it fast enough for a real voice channel? Sub-second on a decent connection. Fast enough for casual conversation; not fast enough for competitive callouts in a shooter. For high-stakes split-second comms, you still want a shared common language.

Is the audio sent anywhere I should worry about? Audio is processed in real time and not stored unless you explicitly save the transcript. Nothing lingers on your machine, and nothing about the voice channel content is shared back to Discord or anyone else in the server — it stays between Whisperr and you.

Try it on your next interview

The whole flow, top to bottom: