Back to Help Center

First Steps

Get SoundSlap ready before your first stream

Use this page when you are setting up SoundSlap for the first time or checking a channel before going live. It covers Twitch auth, extension activation, OBS, mobile, and the first real test.

Checklist

Get live with your first slap

This is the safest setup order because each step confirms one part of the chain before you move to the next one. Do not start with a paid Twitch test until the dashboard test can play audio through OBS.

  1. Open the SoundSlap dashboard and log in with the Twitch account that owns the channel.
  2. Confirm the dashboard shows your channel name and that the panel is not paused or muted.
  3. Add one short sound to your library. Keep the name short and set a low test volume first.
  4. Copy the OBS overlay URL from the dashboard and add it as a browser source.
  5. Use the dashboard Test Slap button. Confirm the alert appears visually and plays through OBS.
  6. Activate the Twitch extension panel and check the viewer panel from a logged-in Twitch account.

If any step fails, fix that layer before continuing. For example, if the dashboard test does not play in OBS, do not troubleshoot Bits yet - the overlay path must work first.

Twitch

Activate the Twitch extension panel

SoundSlap uses the Twitch extension panel for viewer-triggered sounds. The panel must be activated on the channel before viewers can see or spend on sounds.

  1. Go to your Twitch Creator Dashboard and open the Extensions area.
  2. Find SoundSlap in your installed extensions and activate it as a panel extension.
  3. Enable Subscription Status for SoundSlap if you plan to use the Subscribers only setting.
  4. Set the panel title to something clear, such as SoundSlap Alerts or Play a Sound.
  5. Open your Twitch channel page as a viewer and confirm the panel loads below the stream.
  6. If the panel says offline, open the SoundSlap dashboard and check whether the panel is paused, Twitch auth expired, or no sounds are enabled.

For a clean launch, enable only a few sounds at first. Viewers understand the panel faster when the first version is focused and easy to scan. If Subscribers only is enabled, test from a subscribed Twitch account and from a non-subscribed account so the lock message is clear.

Testing

Run the first full test

A full test means the alert is visible in OBS, audible in the stream mix, visible in the extension panel, and trackable from the dashboard history.

  1. Run a dashboard test and watch the overlay browser source in OBS.
  2. Watch the OBS audio mixer. You should see the browser source or desktop audio meter move when the sound plays.
  3. Open the extension panel and confirm the test sound has the expected price and GIF thumbnail.
  4. If using Channel Points, redeem the test reward from Twitch and confirm the dashboard logs the event.
  5. If using Bits, test with the Twitch developer flow or a low-cost sound only after the overlay test succeeds.

After the first successful test, raise the volume slowly. Alerts that sound fine in your headphones can be too loud inside a live stream mix.

Mobile

Check the mobile panel

Many viewers interact from the Twitch mobile app, so your sound names and GIF thumbnails should be readable on a narrow screen.

  • Keep sound names short enough to read at thumbnail size.
  • Use GIFs with one obvious subject instead of tiny text or busy scenes.
  • Preview a few sounds at low volume so mobile users can understand what they are about to trigger.
  • Use reasonable cooldowns for loud sounds so the mobile panel does not become a spam button.

If a sound looks good on desktop but confusing on mobile, rename it or pick a clearer GIF before sending viewers to the panel.