STREAMING GUIDE / STREAM TOOLS

OBS alerts have no sound: test the event, source, and output

A visible alert does not prove its sound reached the stream. Separate provider playback, OBS capture, local monitoring, and the audience mix.

START HERE

Run one provider test alert and watch the browser source in OBS. If the provider preview is silent, fix that event and its sound asset. If OBS receives audio, check its output mute and track routing. Enable local monitoring only if you also need to hear the alert yourself.

1. Identify who cannot hear the alert

Use a local recording as the reference. An alert can reach the audience while remaining absent from your headphones, or reach your headphones without being assigned to the saved mix. Those are different routes.

This guide covers web-based Streamlabs and StreamElements alerts loaded into OBS Studio. It does not assume Streamlabs Desktop or the SE.Live plugin is installed (if your whole Streamlabs Desktop mix is silent, start with the Streamlabs Desktop audio guide). The test should be a provider-generated sample, not a real purchase or donation. Keep your public stream offline while changing the routing.

2. Confirm that the event contains sound

  1. Open the alert provider's editor and select the exact event type that fails, such as a follow or subscription.
  2. Preview the selected audio asset, check its volume, and save any change. Confirm you are editing the overlay used by OBS.
  3. Test both the ordinary alert and any variation that matches the failing event. A custom variation may use a different sound or no sound.
  4. For StreamElements, check whether the Activity Feed has alerts muted or paused. Trigger one sample and allow it to finish.

If only one event type fails, keep troubleshooting that event. Rebuilding every OBS source is unlikely to fix an asset missing from one provider variation.

3. Give the alert one identifiable OBS audio route

Open the alert browser source's properties and enable Control audio via OBS when you want the alert managed as its own mixer source. Trigger the same sample and locate that source's meter. StreamElements documents this per-source audio path; the browser-source approach also applies without SE.Live.

If the meter does not respond, compare the provider preview again and refresh that source once. Confirm the URL belongs to the saved overlay containing the alert. Keep the overlay URL private: provider links can contain account-specific tokens. Do not paste one into a support screenshot or this site's tools.

Close extra alert preview windows when evaluating the recording. Otherwise a preview playing through desktop capture can appear to fix the route while the actual browser source remains silent.

4. Separate audience output from monitoring

On OBS versions with the redesigned mixer, the output mute and headphone monitor controls are independent. Leave the alert unmuted for the audience and enable monitoring only if you want a local copy. OBS 32.2 removed the old redundant monitor-only choice; the current mixer guide explains the controls. Older installations may show the legacy monitoring dropdown instead.

Check that the source belongs to the track your stream uses. If you maintain separate recording or VOD mixes, confirm those deliberately rather than selecting every track indiscriminately. A sound present in one recording track may be absent from another by design.

For local listening, choose your actual headphones as the monitoring destination. If that destination is also captured as desktop sound, the alert can enter the broadcast twice. Start with monitoring off, prove the direct source works, and then add monitoring while checking for duplication.

5. Compare one change at a time

Use the first failing stage
ObservationNext check
Provider preview is silentEvent sound, variation, volume, and provider save state.
Provider works; OBS meter is stillCorrect overlay source and its audio control setting.
Meter responds; recording is silentOutput mute, fader, and source-to-track assignment.
Recording works; headphones are silentLocal monitor button and monitoring device.

If several unrelated browser sources fail together, use the browser-source isolation checklist before replacing every alert. If you hear two copies, follow the duplicate-alert guide.

Verify an entire scene change

Record a sample alert in your starting scene, move to gameplay, and trigger another. Listen for exactly one sound each time and check the intended tracks. Repeat with the provider preview closed. This proves the active production route works instead of accidentally recording an editor preview.

If the alert works live and you want a clean local copy, follow the live-only browser alert setup. It includes a check for alert audio leaking back through Desktop Audio.

Finally compare alert volume with actual speech. A clear sound effect can still obscure a sentence. Keep the verified source as your baseline and record its routing before rebuilding the rest of the layout.

Sources & version notes

Documentation checked November 18, 2026. Use the platform and version notes in this guide when comparing settings. The troubleshooting checks are intended for your own setup; this review date does not represent hardware testing.