Skip to Content
Platform.Ontology

Speech synthesis (text to speech)

Speaks text aloud with the device's voices; needs a prior interaction.

Does something on your deviceThings a page can doMedia outputWeb browsersWhile you use it

In one line

Can speak text out loud, after you have tapped on the page

Speaks text aloud with the device's voices; needs a prior interaction.

A site can read text out loud with built-in voices. The voice list differs by device, so it also hints at the OS, language packs and installed software.

What it can and can't do

What the user does: You tap Listen or Play aloud, or tap the page before it speaks.

It can

  • Speak text out loud using voices on your device
  • Pause, resume or stop the voice
  • Pick a voice from the ones on your device

It cannot

  • Speak the moment a page loads, before you have tapped or clicked
  • Record you or hear what you say
  • Use voices you do not have on your device

Browser support

BrowserStatusFirst versionReleasedNote
ChromeSupported332014-02-20None
EdgeSupported142016-08-02None
FirefoxSupported492016-09-20None
SafariSupported72013-10-22None
Safari on iPhoneSupported72013-09-18All iOS browsers use WebKit
Chrome on AndroidSupported332014-02-26None
Samsung InternetSupported3.02015-04-10None

How a site asks for it

APIspeechSynthesis.speak(new SpeechSynthesisUtterance(text)); getVoices()
Browser compat keysapi.SpeechSynthesis.speak
api.SpeechSynthesis.getVoices
How access is grantedgesture
What the user seesNo prompt (needs a click, tap or keypress)
Needs a secure context (HTTPS)No
Needs a user gestureYes
Activationsticky
How long it lastsVoices list fixed per OS; queue lasts for the page
How to take it backNothing to revoke (no permission is stored)
Inside an iframeCross-origin iframes need allow="autoplay"-like activation in that frame

Typical flow

  1. Person interacts with the page (sticky)
  2. Page calls speak()
  3. Device plays the voice

Data you get

Shape: none

No individual data fields. The signal is the access itself.

Technical limits

  • Chrome 71 requires user activation on the page before speak() produces sound
  • Utterance rate 0.1 to 10, pitch 0 to 2, volume 0 to 1
  • Network voices in Chrome (Google voices) historically stop after about 15 s of speech (known issue)
  • Cannot record the output or pick voices not installed
  • Voice list and default voice leak OS and language (fingerprint)

The story

What it is

A page can read text out loud with your device's voices.

For you

You tap a Listen button and a voice reads an article or a language lesson. The browser blocks a page from talking before you have touched it.

For makers

Makers use it for accessibility, language apps and hands free reading. It costs them nothing because the device does the voice work.

Where you see it

TypeExampleApps
educationA language app reads a Spanish word aloud so you can hear the accent.Duolingo, Google Translate
newsA news site offers a Listen to this article button.Medium
accessibilityA screen reading tool speaks page text for people with low vision or dyslexia.None named
gamesA browser game has a robot narrator reading dialog out loud.None named
productivityA web note app reads your note back to you while you cook.None named
kidsA children's reading site speaks each word as the child taps it.None named

Risks

  • Sudden noise
  • Voice list can identify a device

What the platform says

Good uses and abuse

Legitimate uses

  • Accessibility readers
  • Language learning
  • Audio notifications

Known abuse

  • Voice list fingerprinting
  • Unexpected audio

Scores

ScoreValueMeaning
Sensitivity1 of 5How revealing the data is
Utility3 of 5How useful it is to honest apps
Friction1 of 5How much the user has to do
Fingerprint bits3Rough identifying entropy, when known

History

  • 2016-04, Chrome 47: Remote voices exposed through getVoices
  • 2018-12, Chrome 71: speak() requires user activation

Sources

How well checked: Based on official documentation.

On this page