← All languages

Arabic Text to Speech: Free, In-Browser, Nothing Uploaded

Arabic gets both neural tiers and a working step-down — but the thing that actually decides output quality is your text, not the engine. Paste Arabic text, press play, and the audio is generated on your own device — no account, no upload, no character limit. This page is the honest version: which engines really speak Arabic (العربية), which ones silently do not, and what each one costs you.

Which engines actually speak Arabic

Quick TTS ships four TTS engines and lets you switch between them from one dropdown — but not all four cover every language, and the gaps are not the ones you would guess from the marketing.

EngineArabic?What that means
Web Speech APIYesYour operating system's built-in Arabic voices. No download, works on every device including iPhone and Android.
Piper (WebAssembly)YesVoice ar_JO-kareem-medium. Runs without a GPU after a one-time model download.
Kokoro-82M (WebGPU)NoEnglish only. Hidden on every other language, because a voice you cannot select is not an option.
Supertonic HD (WebGPU)Yes44.1kHz studio-grade Arabic, one of fifteen mapped languages. WebGPU-only, ~380MB cached once.

Arabic is better covered here than in most browser TTS tools, which tend to ship English and a handful of European languages:

The bigger factor for Arabic is not which engine you pick — it is diacritics. Arabic is normally written without short-vowel marks, and every TTS engine has to infer the vowelling from context. Getting it wrong changes the word, not just the sound of it. If a passage matters, text with tashkīl will be read noticeably more accurately by every engine here, and text stripped of it will trip all of them in the same places.

The honest limits

Arabic is one of only five languages with a working smaller Piper tier — English, Spanish, Polish, Dutch and Arabic. A device that cannot allocate ar_JO-kareem-medium steps down to ar_JO-kareem-low — a step-down model chosen automatically, never listed in the voice dropdown — rather than dropping to the system voice, and devices reporting 4GB of RAM or less start on the smaller model deliberately.

Supertonic HD's cost is WebGPU with no WebAssembly fallback and a one-time ~380MB cached download. One practical note specific to Arabic: the Web Speech API tier depends entirely on whether your operating system has an Arabic voice installed. iOS and macOS do; a default Windows install often does not, and the browser will simply have nothing to speak with. On those machines Piper is not the compromise option, it is the only one that works without a GPU — which is the inverse of the usual advice.

The app's Arabic interface is right-to-left throughout, and the reader controls, the segment display and the file-import flow are mirrored rather than bolted onto a left-to-right layout. Mixed Arabic-and-English text — a paragraph with a product name or a citation in Latin script — is handled by Supertonic's "Auto language" mode, which is the toggle worth knowing about for anyone reading technical Arabic.

Nothing you paste is uploaded

This is the part that separates in-browser TTS from the cloud tools that look identical in a browser tab. A cloud tool sends your Arabic text to a server, synthesizes it there, and sends audio back — the page is a remote control. Quick TTS ships the engine to you instead and runs it on your CPU or GPU, so your text is never received by anyone. The test is simple: once the page and its model have loaded, the neural engines keep working with your network disconnected.

That matters most for the documents people actually want read aloud — a contract, a medical letter, coursework, an unpublished draft. It also means there is no "we phonemize non-English text on our server" asterisk, which is not true of every tool advertising local synthesis.

Reading Arabic documents, not just pasted text

PDF, DOCX, EPUB, ODT, RTF, HTML, TXT and Markdown are all parsed in the browser, so a whole Arabic EPUB or a long PDF opens and plays without a byte leaving your machine. A scanned PDF — a photo of text with no text layer — is handled by running OCR locally in WebAssembly rather than uploading the scan, which is precisely the case where local processing is worth the most.

Speed, volume and voice can all be changed mid-read and the current passage replays under the new settings without starting over. Switching the engine itself stops playback, so you press play once to start the new one — there is no mid-read handover of the remaining text between engines.

Frequently asked questions

Is Arabic text-to-speech free?

Yes. Quick TTS reads Arabic with no account, no character limit and no watermark. Synthesis runs in your browser on your own device, so there is no per-character server cost to meter and nothing to gate behind a sign-up.

Is my Arabic text uploaded anywhere?

No. The speech engine ships to your browser and runs locally, so the text you paste is turned into audio on your machine and never sent to a server. That is an architectural property, not a promise in a privacy policy — there is no server in the loop once the page has loaded.

What is the best Arabic TTS voice in the browser?

Supertonic HD is the highest-quality Arabic voice available here — 44.1kHz, running on WebGPU. If your machine has no usable GPU, Piper is the neural option that still runs. To get Arabic voices rather than English ones, open the app at quick-tts.com/ar/ — the neural voice list follows the page language.

Does it work on a phone?

The Web Speech API engine works on every modern phone with no download, and it is the default so the first play click always works. The neural engines are more demanding: Supertonic HD needs WebGPU and is effectively a desktop feature, and Piper runs more widely but can be slow on low-end hardware.

Can I download the Arabic audio?

Yes, as WAV or MP3, generated on your device. Anything longer than about 20,000 characters is packaged as a ZIP of audio parts so memory stays bounded on long documents.

Try it in Arabic — open the العربية app, not the English one

This is the one piece of setup worth knowing, because it is not obvious: the neural voice list follows the language of the page you are on. On the English homepage the Piper voices are the English ones, and Supertonic reads with the English language tag — so Arabic text pasted there will be pronounced as though it were English. Open the العربية version instead and the engine picks up Arabic voices, including ar_JO-kareem-medium, automatically.

The one exception is Supertonic's "Auto language" toggle, which switches generation to a language-agnostic mode that reads mixed-language text with the right pronunciation per language without tagging anything by hand. That works from any page — it is the right choice for a document that is part Arabic and part English.

Written in العربية

These are the Arabic-language write-ups on this site. They are authored in العربية rather than translated from the English, so they are the better read if العربية is the language you would rather be reading in:

Each of this language's Piper voices also has a page of its own, covering the quality tier, what happens when your device cannot load the model, and how it compares to the HD option: ar_JO-kareem-medium.

For the architecture behind all of this, see how in-browser text-to-speech works; for a tool-by-tool comparison with the other local TTS sites, see the comparison page.