Can You Have a Translated Video Call in Arabic?
Last updated: September 2026 · 8 min read
If you have tried to set up a translated call between English and Arabic, you have probably run into the same wall twice: the platforms already on your phone either do not cover Arabic at all, or they will only show it to you as text. This is a straight answer to what works today, what does not, and why Arabic is genuinely harder than Spanish for this particular problem.
The short version
FaceTime does not translate Arabic. Apple's Live Translation in FaceTime is a captions feature, delivered through Live Captions: translated text appears on screen while the other person talks. It is one-to-one, it needs Apple Intelligence on recent hardware, and it runs on about ten languages — English, French, German, Italian, Portuguese, Spanish, Chinese, Japanese and Korean. Arabic is not among them, and there is no Android side to it at all.
Google Meet captions Arabic but will not speak it. This distinction decides the whole question, and most articles on the subject get it wrong — we got it wrong on this site once, and had to correct it. Meet ships two different things that both get called translation. Its translated captions have been there for years, cover around 70 languages, and Arabic is one of them. Its speech translation — the newer feature, the one that produces an actual voice — covers English paired with Spanish, French, German, Portuguese and Italian. Arabic is not on that second list. So in Meet you can read Arabic. You cannot hear it. Both features sit behind a paid Google plan.
Google's own Translate app does speak Arabic, and it is free. Google has put its Gemini 3.5 Live Translate model into the Google Translate app on Android and iOS: more than 70 languages including Arabic, spoken out loud, through headphones or the phone's speaker. The same model is in private preview inside Meet for enterprise Workspace accounts. If what you need is spoken English–Arabic translation and you do not need to see anyone's face, this is the best free option available, and we would rather tell you that than pretend it does not exist. What it is not is a video call — it is built around one phone and two people taking turns.
So if the point is to see your family while you talk to them in Arabic, none of the three does that today.
The options side by side
| Speaks Arabic | Video call | What they need | |
|---|---|---|---|
| FaceTime | No — no Arabic | Yes, captions only | An Apple device with Apple Intelligence |
| Google Meet | No — captions only | Yes | A Google account; host on a paid plan |
| Google Translate app | Yes | No — one phone, in person | To be in the room with you |
| VivaLingua | Yes | Yes | A link, opened in any browser |
What people usually try instead
Propping a second phone next to the first. Google Translate on one device, the video call on the other. It works, in the sense that words get across. It falls apart the moment anyone talks over anyone, and you spend the call looking at a phone instead of a person.
Typing into a translator and pasting into chat. Reliable, and it kills the conversation completely. Fine for arranging a time. Useless for talking to your mother.
Caption-only apps. Several apps will transcribe a call and translate it into on-screen text. As a backup this is genuinely useful. As the main experience it means both of you spend the call reading instead of looking at each other, which is most of what a video call was for.
Dedicated translated-call apps. A small number of apps, ours included, carry Arabic as spoken audio in both directions on the call itself. The honest limitations of that are further down.
Why Arabic is harder than Spanish
This is the part most articles skip, and it is the part that sets your expectations correctly.
Arabic is not one spoken language
When a product says it "supports Arabic", the reasonable question is which Arabic. Modern Standard Arabic is the formal written register — news broadcasts, newspapers, official documents. Almost nobody speaks it at home. What people actually speak are regional varieties that differ substantially: Egyptian, the most widely understood after decades of Egyptian film and television; Levantine across Syria, Lebanon, Jordan and Palestine; Gulf across Saudi Arabia, the UAE, Kuwait and Qatar; Maghrebi, or Darija, across Morocco, Algeria and Tunisia; plus Iraqi, Sudanese, Yemeni and more.
These are not accents. Speakers from Morocco and Iraq can struggle to follow each other in their own dialects, and sometimes converge on Modern Standard to be sure. Speech recognition is trained disproportionately on Modern Standard and Egyptian, because that is where the recorded data is, and Maghrebi is consistently the hardest for these systems. The practical consequence: a tool that works well for an Egyptian speaker may be noticeably worse for someone from Algiers. Any product claiming uniform Arabic quality is worth a raised eyebrow.
The script runs right to left
Arabic is written right to left, and its letters change shape depending on where they sit in a word. For a translated call this lands squarely on captions: text direction has to be handled deliberately or the captions render as a mess. It is a solved problem, but it is one that has to be built rather than inherited, which is part of why Arabic tends to arrive late in these feature rollouts.
It is slower, and here is the honest reason
In our own testing, streaming speech recognition fragments Arabic sentences more than it does English or Spanish. A streaming model has to decide where a sentence ends while the audio is still arriving, and with Arabic it commits too early and splits thoughts in half.
Our fix was to stop streaming Arabic and process whole utterances instead. That is noticeably more accurate. It also adds a little under two seconds per turn compared with the streaming path we use for European languages. We would rather say that than claim Arabic performs identically to Spanish. It does not — in our product or anyone else's — and the reasons are structural rather than a matter of somebody not trying hard enough. We wrote up where the rest of the delay goes in our latency teardown.
What we built, and what it does not do
We make VivaLingua, an app for translated calls. Since this is our blog, here is the disclosure and the limitations in the same breath.
How it works. Each person picks their language. You speak normally and the other person hears it in theirs, out loud, both directions, while you stay on video. Captions are there as a backup rather than the main event. Arabic works with English and with any of the other 41 call languages directly, without routing through a third.
The other person does not need the app. You install VivaLingua to host. Whoever you are calling opens a link in their browser and waits a moment while you let them in — no app, no account, nothing to sign up for. A video call takes one guest that way; an in-person session takes up to three, and those three can be any mix of people using the app and people on a link. Only the host spends minutes; guests pay nothing. That matters more for this language pair than most, because asking a parent in Cairo or Casablanca to install an app, make an account and find the right setting is where these plans usually die. Opening a link is a much smaller thing to ask.
What it does not do. The translated audio is always a synthetic voice, never your recorded one. By default it is a standard voice; with AI Voice, which is optional and included at no extra cost, your family hears fluent Arabic in a voice that sounds like you, labelled as AI while it speaks. We ask which Arabic you speak, but we have not validated that signal against enough real recordings to make strong per-dialect claims; if you speak Maghrebi, expect it to be rougher than Egyptian. Arabic carries the extra latency described above. And VivaLingua hosts its own call rather than plugging into someone else's, so it will not add Arabic to a meeting already running in Meet, Zoom or Teams.
What we would actually recommend
If you are in the same room and free matters most, use Google Translate's live translate. It speaks Arabic, it costs nothing, and it works with headphones you already own.
If you are already living in Meet on a business plan, check whether Gemini Live Translate has reached your account yet. When it rolls out broadly it will be the most convenient option for people whose calls already happen there.
If you need a video call today, on a personal account, you need a dedicated app. Ours is one; here is the full English–Arabic page if you want the detail, and here is the same comparison without the Arabic focus. Whatever you pick, try it on a low-stakes call first — five minutes with someone patient tells you more than any review, this one included.
Whatever you use, test the dialect you actually speak, not the one the marketing page was demoed in. That is the single biggest variable in whether Arabic translation feels usable or exhausting.
If that sounds like the call you have been putting off, try VivaLingua — the person you are calling joins from a link, and pays nothing.