tts

This permission is for accessibility tools or any extension that needs to provide audio feedback.

Examples:

• A "read aloud" extension that reads the content of a web page to the user.
• An accessibility tool for visually impaired users.
• A language-learning extension that speaks words or phrases.
• An extension that gives spoken notifications.

No "tts" permission entry is needed. A minimal manifest looks like this:

{
  "name": "My Read Aloud Extension",
  "version": "1.0",
  "manifest_version": 3,
  "background": {
    "service_worker": "background.js"
  }
}

Why is it not risky?

This permission lets an extension convert text into spoken words, like having your computer read a webpage to you.

This is a very safe permission. The extension can only "speak," it cannot "listen" or access any of your personal data. The worst a malicious extension could do is be annoying by speaking at unexpected times.

This example says "Hello, world!" when the user clicks the extension's icon. It also includes a function to list available voices.

// background.js

chrome.action.onClicked.addListener(() => {
  speakHelloWorld();
});

function speakHelloWorld() {
  chrome.tts.speak('Hello, world!', {
    lang: 'en-US',
    rate: 1.0
  }, () => {
    if (chrome.runtime.lastError) {
      console.error('TTS Error:', chrome.runtime.lastError.message);
    }
  });
}

// You can also get a list of available voices
async function logVoices() {
  const voices = await chrome.tts.getVoices();
  console.log('Available TTS voices:', voices);
}

logVoices();