Translated subtitles on BIGO LIVE appear only when four official conditions line up: the host's UID is on BIGO's whitelist, the stream is a single-host room, the host speaks Chinese or English and your language is on that host's list, and your app is at least iOS 6.28 or Android 6.29.
Source check: every rule below comes from BIGO's own product article, "Bigo Live Introduces Real-Time Translation for Global Users", which was published 2025-04-18 and shows a page update date of 2026-02-04. I re-fetched and read it on 2026-11-07 (Asia/Shanghai, UTC+8). The page does not say what changed on 2026-02-04, so this guide treats that date as a page update only, not as a feature change.
This guide checks the official conditions from a viewer's side of the screen. It is not a complaint round-up, and it is not a hack. It is the stuff I wish someone had laid out for me the first time I hopped between two streams and only one of them had subtitles.
The short version: four gates, all of them must be open
Think of the subtitle as the end of a hallway with four doors. If any one door is shut, you see the raw stream with no translated captions. Here are the four doors, word for word where it matters.
| Gate | What the official article says | Who controls it | Source and date |
|---|---|---|---|
| 1. Host eligibility | "available to hosts whose User ID (UID) is included in our designated whitelist" | BIGO (the host can't switch it on alone) | BIGO article, 2025-04-18, updated 2026-02-04 |
| 2. Room type | "currently available in single-host rooms": single video, single audio, single rooms integrated via channels, single rooms engaged in cross-room connections | The host, by choosing the room type | Same article, 2025-04-18, updated 2026-02-04 |
| 3. Language direction | Chinese-speaking hosts → 10 listed languages; English-speaking hosts → 10 listed languages | The host's spoken language plus your language | Same article, 2025-04-18, updated 2026-02-04 |
| 4. App version | iOS from version 6.28; Android from version 6.29 | You (and the host), by updating the app | Same article, 2025-04-18, updated 2026-02-04 |
Only one of those four gates is fully in your hands as a viewer: the app version. The rest depend on the host and on BIGO. That alone explains a lot of "why does this room have captions and that one doesn't" moments.
Original Buffget graphic built from BIGO's real-time translation article (published 2025-04-18, updated 2026-02-04; fetched 2026-11-07).
First, be clear about which "translation" we're talking about
Here's where a lot of confusion starts. People say "translation" on BIGO and mean three totally different things. The official article covers exactly one of them.
In BIGO's words, the feature "translates the broadcaster's spoken content into the viewer's preferred language, displaying translated subtitles" (BIGO article, 2025-04-18, updated 2026-02-04).
So it's the host's voice, turned into on-screen subtitles. That's it.
| Thing people call "translation" | What it is | Covered by the real-time translation article? |
|---|---|---|
| Live-speech subtitles | The host's spoken words shown as translated captions on your screen | Yes. This is the feature the article describes (2025-04-18, updated 2026-02-04) |
| Comment or chat text translation | Typed messages in the chat area | No. The article talks only about "the broadcaster's spoken content" |
| App interface language | The language of menus, buttons and settings | No. The article doesn't tie subtitles to the menu language |
Why this matters: if you switch your app menus to another language and expect captions to change, you're mixing two separate systems. And if you see typed comments in a language you can read, that tells you nothing about whether the host's speech is being subtitled.
For the rest of this guide, "subtitles" means live-speech subtitles only.
Gate 1: the host has to be on BIGO's UID whitelist
This is the gate most viewers never think about. The official wording is short and firm: the feature "is available to hosts whose User ID (UID) is included in our designated whitelist" (BIGO article, 2025-04-18, updated 2026-02-04).
Three things follow directly from that sentence.
- It's per host, not per viewer. The whitelist is made of host UIDs. Nothing in the article puts viewers on a list.
- It's BIGO's list. The article calls it "our designated whitelist", so it's maintained by BIGO, not by the host.
- It's not public. The article doesn't publish the list, so you can't look up a host's UID and check it yourself.
In plain terms: two hosts can run the same kind of room, speak the same language, and you can be on the same app version, and one stream has subtitles while the other doesn't. If the second host's UID isn't on the list, nothing you do on your phone changes that.
One thing I'm deliberately not mixing in
BIGO's site has other pages that talk about language and cross-language chatting in general terms. When it comes to who can use this specific feature, I'm sticking with the product article above, because it's the page BIGO filed under "Product Update" for this feature (BIGO Product Update page, checked 2026-11-07). If another page seems to describe eligibility differently, the product article is the one that names the rule.
What this gate does not involve
None of the four official conditions mentions diamonds, top-ups, VIP or any other purchase (BIGO article, 2025-04-18, updated 2026-02-04). The host-side gate is a UID whitelist, full stop. So if anyone tells you that spending unlocks subtitles, that claim isn't on the official page.
Gate 2: it has to be a single-host room
Second gate. The article says the feature "is currently available in single-host rooms" and then lists four room types (BIGO article, 2025-04-18, updated 2026-02-04).
| Room type (official wording) | Listed for real-time translation? | What it looks like from the viewer side |
|---|---|---|
| Single video rooms | Listed | One host on camera |
| Single audio rooms | Listed | One host on voice |
| Single rooms integrated via channels | Listed | A single-host room you reached through a channel |
| Single rooms engaged in cross-room connections | Listed | A single host connected to another room |
| Multi-guest rooms | Not listed | Several people on seats or panels in one room |
Source for the four listed types: BIGO article, 2025-04-18, updated 2026-02-04. The last row is my reading of what's missing: multi-guest rooms simply aren't among the listed room types.
Notice the word "currently" in the official sentence. It describes the state of things as written; it doesn't promise multi-guest rooms are coming, and it doesn't rule them out forever. So the honest way to put it is: multi-guest rooms are not listed.
The cross-room detail is easy to miss
A lot of viewers assume that as soon as two rooms connect, everything "extra" switches off. The official list explicitly includes "Single rooms engaged in cross-room connections" (BIGO article, 2025-04-18, updated 2026-02-04). So a connection by itself isn't listed as a blocker, as long as it's a single-host room.
BIGO treats room types differently in other rules too
Room type isn't a translation-only quirk. BIGO's host task rules also separate solo-live from multi-live activity, which we covered in our check of why BIGO Daily Task progress stalls in multi-live rooms (Buffget, 2026-11-07). Different feature, same habit: always check which room you're in before assuming a feature applies.
Gate 3: the language direction has to be on the official list
This is the gate with the most moving parts, so let's go slowly.
The article lists exactly two host languages, each with its own set of target languages (BIGO article, 2025-04-18, updated 2026-02-04):
| Host speaks | Speech can be translated into (official list) | Count |
|---|---|---|
| Chinese | English, Korean, Japanese, Vietnamese, Indonesian, Thai, German, French, Portuguese, Russian | 10 |
| English | Arabic, French, Indonesian, Vietnamese, Japanese, Chinese, German, Malay, Thai, Spanish | 10 |
Two things jump out once you lay them side by side.
- It isn't "any language to any language." Each host language has its own fixed list. Chinese hosts don't have Spanish on their list; English hosts don't have Korean on theirs.
- Hosts speaking other languages have no listed directions. The article names Chinese-speaking and English-speaking hosts only.
The article also includes a "Future Expansion" line: "We are committed to broadening our language support to include additional languages" (BIGO article, 2025-04-18, updated 2026-02-04). That's a commitment, not a dated release, and BIGO's product update page shows no later translation entry (BIGO Product Update page, checked 2026-11-07). So I'm not treating any new language as live.
Flip it around: what can you, the viewer, read?
The official page is written from the host's side ("for hosts speaking Chinese…"). But you're watching, not hosting. So I turned the two lists around into a viewer-side view. Same data, just sorted by the language you read.
Original Buffget graphic: viewer-side regrouping of the two official language lists in BIGO's real-time translation article (published 2025-04-18, updated 2026-02-04; fetched 2026-11-07).
Here's the same thing as a table:
| Viewer language | Chinese host | English host |
|---|---|---|
| French, Indonesian, Vietnamese, Japanese, German, Thai | Listed | Listed |
| Korean, Portuguese, Russian | Listed | Not listed in official directions |
| Arabic, Spanish, Malay | Not listed in official directions | Listed |
| English | Listed | Same language |
| Chinese | Same language | Listed |
- Shows only officially listed directions; viewers outside the list can manually activate translation (official wording) — the output language is not specified.
- No translation directions are listed for hosts speaking languages other than Chinese or English.
Source: both lists from the BIGO article, 2025-04-18, updated 2026-02-04. The regrouping is Buffget's own.
Quick counts from the official lists
These numbers are my own tally of the two official lists (BIGO article, 2025-04-18, updated 2026-02-04):
| Group | Languages | How many |
|---|---|---|
| On both lists | French, Indonesian, Vietnamese, Japanese, German, Thai | 6 |
| Chinese-host list only | English, Korean, Portuguese, Russian | 4 |
| English-host list only | Arabic, Chinese, Malay, Spanish | 4 |
| Distinct target languages across both lists | All of the above | 14 |
Notice that English shows up only on the Chinese-host list and Chinese only on the English-host list. That's simply because a host's own language isn't a translation target for that host.
Real examples of how gate 3 plays out
| You read | Host speaks | Is this direction listed? | What the article says next |
|---|---|---|---|
| Japanese | Chinese | Listed | Subtitles display by default if the other gates are open |
| Japanese | English | Listed | Subtitles display by default if the other gates are open |
| Korean | English | Not listed | You "can manually activate the translation feature"; output language not specified |
| Spanish | Chinese | Not listed | Same manual-activation wording; output language not specified |
| Arabic | English | Listed | Subtitles display by default if the other gates are open |
| Any language | A language other than Chinese or English | No directions listed for this host language | The article doesn't cover this host language |
All rows derived from the BIGO article, 2025-04-18, updated 2026-02-04.
Default subtitles vs. manual activation
The article's "Viewer Experience" section has three sentences. Each one does a different job, so I'm quoting them separately (BIGO article, 2025-04-18, updated 2026-02-04).
Sentence 1, the option: "When a host's live stream supports real-time translation, viewers will have the option to enable translated subtitles."
Sentence 2, the default: "If the viewer's language differs from the host's and is among the supported translation languages, subtitles will display by default."
Sentence 3, the exception: "In cases where the viewer's language is not in the supported list, they can manually activate the translation feature to enjoy the translated content."
Read sentence 3 carefully. It says manual activation exists for viewers outside the list. It does not say which language the subtitles will then appear in, and it does not describe where the switch is. I'm not going to fill those gaps with guesses, and you shouldn't trust anyone who does without showing a source.
| Your situation | Official behaviour | What the article leaves open |
|---|---|---|
| Your language = the host's language | No translation needed (same language) | Nothing; there's nothing to translate |
| Your language differs and is on the list | "subtitles will display by default" | Nothing about the default; it's stated |
| Your language is not on the list | "they can manually activate the translation feature" | Output language and where the control sits |
Source: BIGO article, 2025-04-18, updated 2026-02-04.
One more note on sentence 2. The article says "the viewer's language" and, in its intro, "the viewer's preferred language". It doesn't say which setting defines that. That's exactly why I keep app interface language in its own box above; the article never links the two.
Gate 4: your app version
The last gate is the one you can actually fix in ten seconds. The "Platform Availability" section of the article says (BIGO article, 2025-04-18, updated 2026-02-04):
| Platform | Minimum version (official) |
|---|---|
| iOS | "Available starting from version 6.28" |
| Android | "Available starting from version 6.29" |
Those are minimums from the original rollout. They are not the latest versions. For reference only, here is what the stores showed when I checked:
| Store | Current version shown | Release date shown | "What's new" text | Source |
|---|---|---|---|---|
| Apple App Store | 6.56.0 | 2026-11-05 | "The lastest version contains bug fixes and performance improvements" | App Store listing, checked 2026-11-07 |
| Google Play | 6.55.2 | 2026-11-03 | "The lastest version contains bug fixes and performance improvements" | Google Play listing, checked 2026-11-07 |
The "lastest" typo is BIGO's own, quoted as shown. Both notes mention only bug fixes and performance, so there's no basis for saying anything about translation changed in November 2026 (App Store and Google Play listings, checked 2026-11-07).
Keep the two tables apart in your head. The first tells you the floor. The second tells you what's in the store today. If your app sits at or above the floor for your platform, gate 4 is open.
How to check your version (generic steps)
- Open your phone's app store and search for BIGO LIVE.
- If you see an "Update" button, update. If you see "Open", you're on the store's current build.
- Compare against the floor: iOS 6.28 or later, Android 6.29 or later (BIGO article, 2025-04-18, updated 2026-02-04).
A viewer's step-by-step check when one stream has subtitles and another doesn't
Here's the order I'd run through, from the gate you can see most easily to the one you can't see at all.
- Confirm what's missing. Are you expecting the host's speech as subtitles? If you're actually looking at typed comments or menu text, that's a different system (see the three-way table above).
- Check your app version. iOS 6.28+ or Android 6.29+ per the official article (2025-04-18, updated 2026-02-04). Update if you're below.
- Look at the room. One host, or several people on seats? Only single-host room types are listed (same source).
- Identify the host's spoken language. Chinese or English? Hosts speaking other languages have no listed directions (same source).
- Find your language in the viewer table. Is it "Listed" under that host's column? If yes, the article says subtitles show by default (same source).
- If your language isn't listed, the article's only statement is that you "can manually activate the translation feature". It doesn't specify the output language (same source).
- If everything above checks out and there are still no subtitles, the remaining official gate is the host UID whitelist, which viewers can't verify from outside (same source).
Side-by-side: why stream A has subtitles and stream B doesn't
| Check | Stream A (subtitles show) | Stream B (no subtitles) | Gate that differs |
|---|---|---|---|
| Host UID on whitelist | Yes | Unknown to you | Gate 1, possibly |
| Room type | Single video room | Multi-guest room | Gate 2 |
| Host language | English | English | Same |
| Your language | Thai (listed for English hosts) | Thai | Same |
| Your app | Android 6.55.2 | Android 6.55.2 | Same |
This is an illustration built on the official rules (BIGO article, 2025-04-18, updated 2026-02-04), not a report about a specific account. In this example, the room type is the visible difference. Swap that variable and you could see a different result, but only if the host's UID is also on the list.
More "same app, different result" patterns
| Pattern | Likely gate | Why (official basis) |
|---|---|---|
| Same host, solo yesterday, panel with guests today | Room type | Only single-host room types are listed |
| Two English hosts, same room type, only one shows captions | Host whitelist | Eligibility is per host UID |
| Chinese host shows captions for your Korean-speaking friend but you read Spanish | Language direction | Spanish isn't on the Chinese-host list; Korean is |
| Your old spare phone never shows captions anywhere | App version | Minimums are iOS 6.28 / Android 6.29 |
| Host speaks a third language | Language direction | Only Chinese- and English-speaking hosts have listed directions |
All patterns reasoned from the BIGO article, 2025-04-18, updated 2026-02-04. They're possibilities to check, not diagnoses.
If you're the host: what the article tells you
Hosts read these guides too, so here's the host-side summary, again strictly from the official page (BIGO article, 2025-04-18, updated 2026-02-04).
| Host question | Official answer |
|---|---|
| Can every host use it? | No. It's "available to hosts whose User ID (UID) is included in our designated whitelist" |
| Which rooms? | Single video, single audio, single rooms integrated via channels, single rooms engaged in cross-room connections |
| Which spoken languages? | Chinese (10 target languages) and English (10 target languages) |
| What gets translated? | "the broadcaster's spoken content", shown as subtitles |
| Minimum app? | iOS 6.28, Android 6.29 |
A practical takeaway for hosts on the list: if you want viewers in other languages to follow you through subtitles, the official article's conditions point to a single-host room and speaking Chinese or English. Switching to a multi-guest panel takes you outside the listed room types.
Timeline: what's dated and what isn't
Dates get garbled fast on this topic, so here they are in one place.
| Date | What happened | Source |
|---|---|---|
| 2025-04-18 | Real-time translation article published (create date on the page) | BIGO article |
| 2025-10-15 | Program List article on the Product Update page (unrelated to translation) | BIGO Product Update page, checked 2026-11-07 |
| 2025-11-12 | Room PK System article on the Product Update page (unrelated to translation) | Same page, checked 2026-11-07 |
| 2026-02-04 | Translation article shows an update date; changes aren't described | BIGO article |
| 2026-11-03 | Google Play shows version 6.55.2, bug fixes and performance | Google Play, checked 2026-11-07 |
| 2026-11-05 | App Store shows version 6.56.0, bug fixes and performance | App Store, checked 2026-11-07 |
The Product Update page held three entries when I checked on 2026-11-07, and translation appears only in the 2025-04-18 article (BIGO Product Update page). So the rules in this guide are the ones from that article; there's no newer translation changelog on that page to override them.
What I'm deliberately not claiming
A guide like this is only useful if it's honest about its edges. Here's what stays out, and why.
| Claim you may see elsewhere | Why it's not in this guide |
|---|---|
| "Subtitles work in every language pair" | The article lists two fixed host-language lists, 10 targets each (2025-04-18, updated 2026-02-04) |
| "Manual activation translates into your language" | The article says viewers "can manually activate the translation feature" but doesn't name the output language |
| "BIGO expanded translation in February 2026" | The page shows an update date of 2026-02-04 without describing changes |
| "The November 2026 update changed subtitles" | Both store notes (2026-11-03 and 2026-11-05) mention only bug fixes and performance |
| "Buy diamonds or VIP to unlock subtitles" | None of the four official conditions involves a purchase |
| "Multi-guest rooms definitely can't ever have it" | The article says "currently available in single-host rooms"; multi-guest rooms are simply not listed |
| "Lots of users are reporting broken subtitles" | This is a rules check, not a complaints round-up; I'm not quoting reports I can't source |
Where diamonds actually fit in
Let's be crystal clear: diamonds don't switch subtitles on. The four gates above are the whole official list (BIGO article, 2025-04-18, updated 2026-02-04).
Where diamonds come in is afterwards. Once subtitles let you actually follow a host you couldn't understand before, you might want to send a gift the normal way. If that's you, you can top up Bigo Live diamonds on Buffget using your BIGO ID, then gift as usual inside the stream.
Just keep the two things separate in your head: subtitles depend on BIGO's conditions; gifts are a choice you make after you've understood the stream.
Cheat sheet
| If you see… | Check this gate | Official reference point |
|---|---|---|
| No subtitles anywhere, on any host | Gate 4: app version | iOS 6.28+ / Android 6.29+ |
| No subtitles in a room with several people | Gate 2: room type | Single-host rooms only are listed |
| No subtitles for a host who speaks neither Chinese nor English | Gate 3: language | Only Chinese and English hosts have listed directions |
| Subtitles on one Chinese host but not with your language on another | Gate 3: language | Check your language against that host's list |
| Everything matches, still nothing | Gate 1: host whitelist | Eligibility is per host UID |
Source for every row: BIGO article, 2025-04-18, updated 2026-02-04.
FAQ
Does BIGO LIVE translate the host's voice or the chat?
The official article describes translating "the broadcaster's spoken content" and "displaying translated subtitles" (2025-04-18, updated 2026-02-04). It doesn't describe chat text, so treat chat translation as a separate topic.
Can every BIGO host turn on real-time translation?
No. Per the official article, it's "available to hosts whose User ID (UID) is included in our designated whitelist" (2025-04-18, updated 2026-02-04).
Does it work in multi-guest rooms?
Multi-guest rooms are not among the listed room types. The article says it's "currently available in single-host rooms" and lists single video, single audio, single rooms integrated via channels, and single rooms engaged in cross-room connections (2025-04-18, updated 2026-02-04).
Which languages can a Chinese-speaking host be translated into?
English, Korean, Japanese, Vietnamese, Indonesian, Thai, German, French, Portuguese and Russian (official article, 2025-04-18, updated 2026-02-04).
Which languages can an English-speaking host be translated into?
Arabic, French, Indonesian, Vietnamese, Japanese, Chinese, German, Malay, Thai and Spanish (official article, 2025-04-18, updated 2026-02-04).
My language isn't on the list. Can I still get subtitles?
The official article says: "they can manually activate the translation feature to enjoy the translated content" (2025-04-18, updated 2026-02-04). It doesn't say which language those subtitles appear in.
Do subtitles turn on automatically?
If your language differs from the host's and is on the supported list, the article says "subtitles will display by default" (2025-04-18, updated 2026-02-04).
What app version do I need?
iOS from 6.28, Android from 6.29 (official article, 2025-04-18, updated 2026-02-04). For context, the stores showed 6.56.0 (App Store, 2026-11-05) and 6.55.2 (Google Play, 2026-11-03) when checked on 2026-11-07.
Did the November 2026 update change translation?
Both store notes say only that "The lastest version contains bug fixes and performance improvements" (App Store 2026-11-05, Google Play 2026-11-03; checked 2026-11-07). There's no translation change mentioned.
Does buying diamonds or VIP unlock subtitles?
The four official conditions are host whitelist, room type, language direction and app version; none involves a purchase (official article, 2025-04-18, updated 2026-02-04). If you want to gift a host after you can follow them, that's where Bigo Live diamonds come in.
Sources
- BIGO LIVE: "Bigo Live Introduces Real-Time Translation for Global Users", published 2025-04-18, page update date 2026-02-04, fetched 2026-11-07.
- BIGO LIVE Product Update page, three entries (2025-11-12, 2025-10-15, 2025-04-18), checked 2026-11-07.
- BIGO LIVE on the Apple App Store, version 6.56.0 dated 2026-11-05, checked 2026-11-07.
- BIGO LIVE on Google Play, version 6.55.2 dated 2026-11-03, checked 2026-11-07.