#Text-to-Speech (TTS)

TTS reads chat messages and events aloud during your stream. The audio plays through your overlay, so your viewers hear it in your broadcast through the OBS Browser Source.

#How it works

When a viewer (or you) triggers TTS with the chat command, the message is queued, synthesized into speech using your chosen voice, and played back through the overlay. Multiple requests are spoken in order.

#Enabling TTS

TTS has two separate enable switches, and both must be on for TTS to fire from chat:

1. Widget enabled - Turn the TTS widget on in its dashboard settings.
2. Command enabled - Turn the TTS chat command (for example !tts) on in your Commands settings.

If only the widget is enabled but the command is off, chat triggers do nothing. If you have tested TTS from the dashboard and it works, but TTS never fires when someone types the command in chat, check that the command itself is enabled. The dashboard test button bypasses the command switch, so a working test does not prove the chat path is on.

#Choosing a voice

Voices come from TTS providers (such as Inworld). In the TTS settings, pick the voice you want messages spoken in. The selected voice applies to TTS playback.

Settings apply live. After you change the voice or other options, the next message is spoken with the new settings - no restart needed.

#Testing from the dashboard

Use the test (demo) button in the TTS settings to play a sample through your overlay. This confirms the voice and audio path are working.

Remember: the test bypasses the command switch. It only confirms the widget and your overlay audio are set up correctly - it does not confirm that the chat command is enabled.

#Audio requires Browser Source audio

TTS plays through the overlay, so OBS must be allowed to output audio from the Browser Source. If the test plays but you hear nothing in your stream, the Browser Source likely has audio muted or disabled. See Audio Issues to fix it.