To turn on Chrome Live Caption on Windows or Mac, open Chrome Settings > Accessibility > Live Caption, then play spoken audio in a Chrome tab. For another source language, add its language pack and choose it as your caption language. Google’s caption instructions give the paths for Linux and Chromebook too.
Live Caption produces text from speech. Live Translate translates that caption text. Start with captions you can understand, then test translation on public training material before deciding whether either feature fits your interpreting work.
Turn on Chrome Live Caption
Use the path for your computer in Google’s setup guide:
| Computer | Caption controls |
|---|---|
| Windows or Mac | Chrome menu > Settings > Accessibility > Live Caption |
| Linux | Chrome menu > Settings > Accessibility > Captions > Live Caption |
| Chromebook | Chrome menu > Settings > Accessibility > Manage accessibility features > Audio and captions > Live Caption |
- Open the caption controls using the path for your computer above. Turn Live Caption on.
- Play a public video with clear spoken audio in Chrome. Expect a caption bubble while speech plays. For an autoplay video, check its volume.
- On Windows, Mac, or Linux, use Manage languages > Add languages for another source language. Let the language pack download, then choose Preferred caption language. Choose the language the speaker uses, not the language you want a translation in. For Chromebook Plus, use the supported source-language controls described in the translation section below. See Google’s language controls.
- Compare a complete spoken sentence with its caption before moving to your intended audio source. If nothing appears, work through the checks below.
After setup, make the bubble readable: move it away from call controls, expand it for more visible text, and adjust Caption preferences if needed. Google documents these caption controls; font options can open your computer’s system preferences.
To stop captions, return to the same controls and switch Live Caption off.
Test captions before an interpreting shift
Use a public training video in a language you understand. Listen to a complete sentence before checking its caption. Try a passage with a name and a number so you can compare the text with what you heard.
For example, use this fictional practice sentence in your own non-sensitive training material: “The appointment is on May fifth at nine fifteen.” Look for a missed date or a change in the number. Do not put patient details into a test clip.
Next, try the browser-based audio source you expect to use, with permission and non-sensitive material. A successful video test does not establish that your softphone, microphone, or both sides of a call will reach the caption feature. Confirm what appears while each speaker talks.
For interpreters, the useful result is a readable backup that leaves your attention on the speaker. If you spend the test rearranging windows or correcting the text, change your setup before a shift. Our audio-routing guide can help you identify the source you are testing.
Chrome Live Caption not working: what to check
Work from a simple public video toward your intended audio source. These are diagnostic checks, not guaranteed fixes:
| Symptom | Check next |
|---|---|
| No text appears | Confirm Live Caption is on and the clip contains audible speech. Google’s caption tips say to turn up volume for autoplay videos. |
| Captions are in the wrong language | Compare the spoken language with the caption-language selection. Translation has a separate target-language control. |
| A training video works, but a call does not | Verify that the call audio plays in Chrome. Identify whether the missing speech comes from another app, your microphone, or the other participant. |
| Caption or language controls are missing | Follow the instructions for your operating system and check your Chrome version. Ask your organization’s IT contact about a managed browser; do not change its policies. |
| Names or numbers look wrong | Compare against the speaker, repeat the test with clearer audio, and use your clarification procedure on an assignment. Treat caption text as fallible. |
| The bubble covers a control | Move or collapse the bubble; check that it remains readable without hiding the control you need. |
For a missing feature, check Chrome menu > Help > About Google Chrome using Google’s update instructions. Save your work before applying an update or relaunching. On a managed device, follow your organization’s update process.
Do not reset Chrome, disable security extensions, or grant a new microphone permission as a routine caption fix. First establish which audio source fails. For a word you did not hear, use a slow-down or repetition request rather than guessing from the caption.
Chrome Live Caption vs Live Translate
Use Live Caption for speech-to-text and Live Translate for translated captions. For Windows or Mac, Google’s instructions put Live Translate under Chrome Settings > Accessibility; Linux adds the Captions submenu. Chromebook Plus uses system Settings > Accessibility > Audio and captions. Keep Live Caption on, turn Live Translate on there, then choose the target under Translate to or Translate captions to, depending on the device. Follow the device-specific translation instructions.
On Chromebook Plus, add your source language under Supported Live Caption languages before choosing the translation target. A regular Chromebook should not be assumed to have the same translation controls.
For a Spanish training clip with English captions, check two settings: Spanish as the source caption language and English as the translation target. That distinction is the first thing to check if a selected language does not give you the result you expected.
Choose from the languages your device offers. Avoid assuming that a Chromebook Plus language list applies to a Windows computer or that page translation also translates audio. Our Live Translate guide for interpreters discusses when translated captions fit an OPI workflow; this page covers setup and checks.
Short answer
Chrome Live Caption generates captions for audio in Chrome. Google says captions are processed locally, are not stored, and do not leave your device. Chrome also has Live Translate, which can send captions to Google for translation.
Interpreter provides transcripts, translation reference, speaker labels, Quick Lookup, notes, and custom terms. Check the current feature list and obtain authorization before using it on an assignment.
Use Chrome Live Caption as a free backup for browser audio. Use Interpreter when the transcript is part of your working process.
What Chrome Live Caption does well
It can caption videos, podcasts, streams, games, video calls, and other audio media in Chrome. Google’s help page describes the movable bubble and caption appearance controls.
For basic captions, Google says the audio and captions are processed locally, are never stored, and never leave the device. That is a strong privacy point for a free browser feature.
Live Translate sends captions to Google. Language options depend on the supported source and device; check Google’s current instructions for your setup.
If you are watching training material, checking a webinar, or trying to follow a single speaker in Chrome, Live Caption can help.
Why interpreters like it
You may keep a notepad, a glossary tab, and a medical abbreviation list open during a shift. A caption bubble can add a second view of speech without another workspace to learn.
If a presenter says a number too fast during a webinar, the caption bubble may catch it. If a YouTube training video has no captions, Chrome can give you enough text to follow along. If a browser-based call has clear one-speaker audio, it may provide a rough backup.
Before you use that backup, check which parts of the conversation it captures and whether you can keep listening while reading.
The OPI limits
Chrome Live Caption is not designed around interpreting.
It does not know who the provider is, who the patient is, or which language should be treated as source at any given moment. It does not provide an interpreter workspace. It does not give you quick term lookup, notes, custom term mappings, or medical/legal domain settings. It does not manage the back-and-forth rhythm of a bilingual call.
You may need to see a medication name, check a target-language rendering, keep a note about dosage, and track the next sentence. You may need the transcript organized by speaker, support for code-switching, or capture of audio outside Chrome. Test those requirements against your authorized setup rather than assuming a caption feature covers them.
Interpreter groups those call-support features in one workspace.
Translation and compliance
Chrome’s privacy story depends on which feature you use.
For Live Caption, Google says processing is local and not stored. For Live Translate, Google says captions can be sent to Google for automatic translation.
For casual media, that is fine. For healthcare or legal calls, it is a problem to examine carefully. A free consumer browser feature is not the same as a signed healthcare workflow with a business associate agreement.
For either tool, ask the organization to review permissions, data handling, and applicable contracts. A product claim or local caption setting cannot establish approval for your assignment.
If you are on medical calls, do not rely on vibes around privacy. Read the actual compliance requirements. Start with HIPAA for interpreters if you need a plain-language refresher.
Cost is not the whole decision
Chrome Live Caption is free.
That matters. Not every interpreter can add another subscription, and a free tool can be better than no support at all.
But the real cost in OPI is not always software price. It is cognitive load. It is interrupting the provider three times because you missed a number. It is losing a case ID, confusing a medication, or having three floating windows open when the caller is already upset.
Interpreter’s pricing page lists a base rate of $0.45 per active hour for Manual and Automatic modes, with bonus hours on larger packages. Both modes use the same balance.
Compare the work you need to do with what your tested setup can capture and display.
Feature comparison
| Need | Chrome Live Caption | Interpreter |
|---|---|---|
| Main fit | Captions for Chrome audio | OPI call support |
| Cost | Free | Both modes share one balance; see current pricing |
| Works outside Chrome | No | Yes, when audio is captured from your source |
| Speaker labels | No | Yes |
| Two-way translation workflow | No | Yes |
| Live Translate | Yes, sends captions to Google | Built into interpreter call view |
| Notes | No | Floating notes |
| Quick term lookup | No | Yes |
| Custom terms | No comparable glossary in Google’s documented controls | Up to 50 mappings, per the feature list |
| Sensitive assignments | Employer review required | Employer review required |
Choose Chrome Live Caption if
You need free captions for browser audio.
You are watching training videos, webinars, or single-speaker content.
You want a backup caption bubble, not your main interpreting workspace.
The content is low-risk and does not require a healthcare or legal compliance workflow.
Choose Interpreter if
You work live OPI calls.
You need a transcript organized around speakers and languages.
You need quick lookup, notes, custom terms, and domain-specific recognition.
You work with medical, legal, insurance, government, or other sensitive content.
You want one screen for the call instead of a loose caption bubble next to your real work.
The honest take
Set up the source language, test the exact audio source, and check names and numbers against what you hear. Choose Live Translate only when you need translated captions and have reviewed that workflow.
Keep Chrome captions for the tasks they handle in your test. If you need speaker-organized text, lookup, or notes beside a live assignment, compare the interpreter tools available and check authorization before using them.
Setup sources checked October 1, 2026: Google Chrome Live Caption and Live Translate help and Chrome update instructions. Device controls can change; use Google’s instructions for your computer if its labels differ.
Related reading:
