All guides

Stream features

Chat Text-to-Speech

SheekBot can read your chat out loud on stream. Viewers type !tts with a message, or you can have it read every chat message automatically. Your TTS settings decide who can use it and what gets read.

Two Ways to Use It

  • !tts <message> — a viewer asks for their message to be read, e.g. !tts hello stream!. Works in Kick and Twitch chat.
  • Auto-read — reads every normal chat message (not commands). Works in Kick chat.

You can use either, or both. With auto-read off, !tts still works.

Prerequisites

  • A SheekBot account with Kick or Twitch connected
  • OBS or Meld for the TTS browser source
  • Free browser voices work on every plan. Premium voices (realistic AI voices) are part of Pro, up to a monthly character limit.

Step 1: Add the TTS Browser Source

  1. Go to Dashboard → TTS Queue → Settings
  2. Copy the browser source URL shown there
  3. In OBS: Sources → + → Browser, paste the URL, set the size to 800×200 and click OK. It shows each message on screen while it's read. In Meld, add a Browser layer with the same URL.
  4. Make sure the source isn't muted in your audio mixer

Keep the source loaded while you stream. Messages waiting more than 10 minutes are skipped, so a source added late doesn't read out an old backlog.

Step 2: Choose Your Settings

In Dashboard → TTS Queue → Settings:

  • Enable TTS — the main switch for all TTS
  • Auto Read — read every chat message (Kick)
  • Voice — browser voices, or Premium voices on Pro, plus volume, speed and pitch
  • Read Username — say "name says: …" before the message
  • Moderators Only / Subscribers Only — who can be read (moderators also pass "subscribers only")
  • Max Characters and Max Word Length — longer messages are skipped
  • User Cooldown, Global Cooldown and Delay Between Messages — how often one viewer, or anyone, can be read

These settings apply to !tts and auto-read alike.

What Viewers See

When !tts works, the message is simply read out — SheekBot doesn't reply, to keep chat clean. It does reply when:

  • the message is missing ("usage: !tts ")
  • TTS is turned off
  • TTS is limited to subscribers or moderators
  • the message is too long

Messages sent during a cooldown are skipped quietly.

Troubleshooting

  • Nothing is read out — check the browser source is in your scene, loaded and not muted, and that Enable TTS is on. Test with a plain chat message if auto-read is on.
  • Some messages are skipped — they hit a limit: length, cooldown, or the subscribers/moderators setting.
  • It reads old messages — it won't read anything older than 10 minutes; anything newer is read in order.
  • The voice suddenly sounds different — if a Premium voice can't be used (for example, the monthly character limit was reached), SheekBot reads the message with a browser voice instead. The limit resets each month.

Need Help?

See also: Viewer Entrances