FaceTime Live Captions and Translation on Mac: What Works and What to Try Next

The short answer

Check FaceTime Live Captions and, where supported, Apple Intelligence Live Translation first. Availability is limited by Apple silicon, language, region, system version, and call type. A Mac-wide caption app may be an option when the built-in path does not fit, but only if the call’s incoming audio is actually available to the Mac audio capture path; verify with a short, agreed test.

Check FaceTime’s built-in captions first

FaceTime on Mac has its own Live Captions control. Apple says the feature transcribes conversations on screen and processes the audio on the Mac. Apple also says Live Captions requires Apple silicon and is not available in every language, country, or region. Availability and accuracy can vary, so check the current settings on the specific Mac rather than assuming that a feature shown in a guide is available on every device.

During a call, look for the More button in the FaceTime window and choose Live Captions. If the control is missing, check macOS version, Apple silicon, accessibility settings, language, and region. Apple’s current instructions also describe a Live Captions setting that can limit captions to FaceTime; otherwise macOS Live Captions can cover audio from other apps too.

Test the feature with a sentence that contains an ordinary name or a familiar phrase before you rely on it for a class, appointment, or work call. Confirm that captions are appearing in the FaceTime window and that their language matches the person speaking. If the feature is present but the text is incomplete, distinguish a setup issue from difficult audio: a quiet caller, several people speaking at once, or a rapidly changing topic can make any speech-recognition result harder to follow.

Know when FaceTime can translate the call

Apple documents Live Translation for one-to-one FaceTime calls when Apple Intelligence is enabled. The currently listed language options include English (U.K. and U.S.), French (France), German, Italian, Portuguese (Brazil), Spanish (Spain), Simplified and Traditional Chinese, Japanese, and Korean. Apple notes that macOS 27 features are not available in every language or region and that usage limits may apply.

That means a translation option may be absent even when ordinary captions work. Group calls, unsupported language pairs, regional availability, system requirements, and Apple Intelligence settings can all affect the built-in route. Check the FaceTime controls and Apple’s latest language availability before changing your workflow. Machine-generated captions and translations should be checked against important details.

Treat the source and reading languages as separate questions. First identify the language the other person will speak; then check whether the feature can show or translate that language into the one you want to read. A language appearing somewhere in Apple’s feature list does not necessarily establish support for every direction, call type, or region. For a high-stakes call, verify the exact pair in the current interface and agree on a fallback with the other participant.

Prepare for the call you actually have

Before choosing a caption method, note whether the call is one-to-one or a group, which language each participant expects to use, and whether you need source-language text or a translation. Confirm that the Mac you will use meets the selected feature’s requirements and that the correct system language resources are available. If the speaker will use headphones, an external monitor, or a Bluetooth output, include that device in your test; changing the output can change which audio is available to a separate Mac-wide workflow.

Keep one fallback ready. It may be FaceTime’s own captions, a language both participants share, a request to repeat or type a key phrase, or a different agreed call setup. A fallback makes it less tempting to treat an incomplete caption as a transcript of record.

When a Mac-wide caption workflow may help

If FaceTime’s own options do not meet your needs, Alison Workspace can listen to system audio playing through an accessible Mac audio path, recognize speech, and optionally translate it into a separately selected target language. It does not join the FaceTime call as a participant or read your FaceTime account. Whether a particular FaceTime call’s incoming audio is available to the app depends on the current Mac, audio route, permissions, and software behavior; do not assume compatibility without trying it.

Alison Workspace requires macOS 15 or later on an Apple silicon Mac (M1 or newer). Recognition and translation are separate settings, and translation availability depends on language resources available on that Mac. First-time use may require downloading a local recognition model or Apple language resources. Once prepared, the app’s current capture, recognition, and translation flow runs on the Mac. Local text history remains until you delete it; the app does not retain the original audio or screen frames.

Think of this as a separate caption layer, not a way to turn on a missing FaceTime control. The app receives only the Mac playback audio exposed through the selected route; it does not obtain separate participant tracks or guarantee that FaceTime audio will be exposed in every configuration. It also cannot make an unavailable Apple language pair available inside FaceTime. Test the exact combination of FaceTime, macOS, speaker output, and language before you plan around it.

Try a short, consented call before relying on captions

1. Check whether FaceTime’s Live Captions or Live Translation already supports your Mac and language pair.
2. If you want to try Alison Workspace, confirm that the incoming caller’s voice is audible through the Mac output you plan to use. Check Alison’s Screen & System Audio Recording permission if macOS asks for it.
3. Open Alison Workspace and choose the spoken language, or automatic recognition when the local model needed for that path is installed. Choose a translation language separately if you need one.
4. Start a brief test with the other person’s knowledge. Use a low-stakes sentence and confirm that captions follow the caller rather than your own microphone.
5. If the words do not appear, switch the call’s speaker/output route, check the app’s audio permission and recognition resources, and repeat once. If the audio remains unavailable, use FaceTime’s built-in feature or another agreed method.
6. Keep the original language visible when possible. Check names, numbers, and commitments with the caller instead of relying on an uncertain caption.

During the test, ask the other person to say one short sentence, pause, and then repeat it naturally. Check whether the text follows the incoming voice, whether source-language recognition is understandable, and whether the optional translation preserves the point. Do not judge the setup from a ringtone or silence: it needs actual speech in the selected language. If only your own voice appears, the call and microphone paths may be separate; do not assume that the other side is being captioned.

Choose the right path for your call

For a supported one-to-one language pair, FaceTime Live Translation is the simplest place to start. FaceTime Live Captions can help when you need the spoken words but not translation. A Mac-wide workflow can be useful if your selected language or call format is not covered by the built-in options and the incoming audio is accessible, but it adds a separate app and its own setup.

For a group call, do not infer Live Translation availability from one-to-one support. Check current FaceTime controls and test the desired setup with participants. Alison Workspace does not provide speaker identity verification or a guarantee that overlapping voices will be separated accurately.

Use the simplest route that meets the need. If built-in FaceTime captions provide readable source text, there may be no reason to add another app. If FaceTime’s own translation covers the pair and call type, start there. A separate Mac-wide caption layer is worth testing when you need another supported reading language or consistent text from Mac playback, but it brings its own permissions, resources, and audio-route dependency. If a short test fails, switch methods instead of spending the call troubleshooting.

Keep consent and private information in view

Captioning makes spoken content readable and can leave text history on the Mac. Tell the other participant before using a separate caption workflow, follow applicable recording and accessibility rules, and avoid sensitive calls unless everyone understands the setup. Delete local text history when you no longer need it. FaceTime’s built-in captions and Apple’s separate translation feature have their own behavior and settings, which Apple documents independently.

Troubleshoot missing or unreliable captions

• No Live Captions option: Check Apple silicon, macOS version, language and region availability, and FaceTime’s accessibility settings.
• Captions appear, but no translation control: Confirm Apple Intelligence eligibility and the exact one-to-one language pair in Apple’s current documentation.
• Alison shows no speech: Confirm the incoming voice is playing on the Mac, check system-audio permission and output device, then try a short test call.
• Only part of the conversation appears: The call may use a route not captured by the current setup, or speech may be quiet, overlapped, or outside the selected recognition language.
• Translation sounds wrong: Check the source language, target language, and installed resources. Verify important details with the caller.