Why Your Twitch New Follower Notification Arrives but the Alert Stays Silent in OBS
Twitch notifications and OBS alerts travel different paths
A new follower message in the Twitch dashboard, chat, or a bot means only one thing: the platform has registered the event. The sound alert goes through a separate chain. Twitch passes the follower to the alert service, the service sends the event to the browser widget, the Browser Source loads that widget, and OBS adds its audio to the broadcast.
A notification from Twitch doesn't confirm that the sound reached the stream. The failure can be in the event settings, the widget itself, the browser source, the mixer, the audio track, or local monitoring.
There's no need to change every scene or reinstall OBS right away. First you need to determine whether the alert appears on screen, whether OBS sees its audio, and whether that audio reaches the stream track.
Separate an event error from an audio error
Run a test specifically for the "new follower" event in the alert service. Open the scene that's actually used on the broadcast and watch the preview and the OBS audio mixer at the same time.
- The alert image appears but there's no sound — the widget received the event, but the problem is in the Browser Source audio, the mixer, or routing.
- There's neither image nor sound — check the widget URL, the active scene, the source visibility, and the Twitch connection to the alert service.
- The test works but a real follower doesn't trigger the alert — check the connected account, filters, and authorization.
The test is useful but doesn't fully replace a real event. Its drawback is that some services may not apply filtering rules, repeat limits, or suspicious activity protection to the test.
Check the sound in the follower alert settings
Open the settings for the specific event, not just the general design section. Make sure follower alerts are enabled, an audio file is attached to them, and the event volume isn't lowered to zero. If you use different profiles, themes, or widgets, check the variant whose URL is pasted into OBS.
- Check the master alert toggle and the separate follower toggle.
- Compare the follower volume with the overall widget volume.
- Make sure the audio file plays in the service panel.
- Temporarily assign a different default sound and repeat the test.
- Check the rules that hide repeat or filtered events.
Replacing the audio file helps rule out an error in the file itself. The drawback of this method is that it won't fix a source that isn't passing audio to OBS.
Make sure the Browser Source is working on the broadcast scene
In the working scene, find the Browser Source with the widget and compare its URL with the address from the alert service. Scene collections often keep old copies: one widget is visible in the frame, while another source is set up for audio or points to an outdated page.
Check whether the Browser Source is inside a hidden nested scene or group. Also look at the setting that disables the source when it's hidden. It reduces the load on OBS, but the widget may stop loading events until the scene appears in the frame.
If the source was changed, refresh its page or restart OBS. The browser widget cache sometimes keeps old audio and design settings.
Check the Browser Source level in the audio mixer
During the follower test, the level indicator in the Browser Source row should move. This means OBS is receiving audio from the widget. If the indicator is still, check the URL, the alert settings, and the browser source parameters themselves.
If the indicator moves, make sure the source isn't muted and its volume slider isn't lowered. When old and new sources have similar names, temporarily rename the working Browser Source. Otherwise it's easy to configure the wrong widget.

Movement on the mixer scale doesn't yet mean viewers can hear the alert. The audio may go only to the recording track, to local monitoring, or to a track that isn't selected for the broadcast.
Configure the Browser Source audio output
Open the Browser Source properties and check the audio output through OBS parameter, if it's available in your version of the program. After changing it, run the test again: the corresponding row in the audio mixer should appear or start moving for the source.
Some widgets pass audio directly through the Browser Source. In this case you shouldn't try to capture them via "Desktop Audio." Other setup variants may output browser audio to a playback device, and then the route depends on system audio. These schemes shouldn't be mixed without need: you can end up with a double alert, an echo, or sound only in your headphones.
Recreating the Browser Source with the current URL helps with a corrupted cache or old settings. The drawback of the method is that you'll have to set the size, position, cropping, filters, and layer order again.
Assign the Browser Source to the broadcast track
Open the advanced audio properties in OBS. The Browser Source must have the track checked that's selected for the stream in the OBS output settings. Usually the check starts with track 1, but you should go by the actual broadcast track in your profile, not the familiar number.
A typical mistake: the Browser Source is checked only on another track, while track 1 is selected in the broadcast settings. The mixer shows a level, the streamer may hear the alert through monitoring, but it doesn't get into the audio sent to Twitch.
- Check the track number selected for the broadcast in the OBS output settings.
- Open the advanced audio properties and enable the same number on the Browser Source.
- Check whether the source is assigned only to the recording track or a separate mix.
- Do a short broadcast test or check the audio from the viewer's side.
Recording doesn't always repeat the broadcast routing: different tracks may be selected for it. That's why recording is convenient for an initial check but doesn't confirm the audio on the broadcast.
Separate monitoring for yourself from audio for viewers
Monitoring is needed to hear the alert locally in headphones or on another device. It's configured in the advanced audio properties of the source and depends on the monitoring device selected in the OBS settings.
Monitoring and the stream track work independently. The "monitor only" mode lets the streamer hear the alert but doesn't send it to viewers. A mode with output to the broadcast won't help if the Browser Source isn't assigned to the right track.
If you hear the alert but chat doesn't, look at the tracks first. If viewers hear the alert but you don't, check the monitoring device: OBS may be sending audio to the speakers while you're listening through the headphones of an audio interface.
Don't confuse the Browser Source with desktop audio capture
"Desktop Audio" captures everything playing on the selected system device: browser, game, music, and notifications. This variant can pass the alert to the broadcast if the widget plays through the browser and that device. But it creates extra risks: system sounds get into the stream, audio may be duplicated, and the capture disappears when the device changes.
If the Browser Source already sends audio directly to the OBS mixer, desktop capture is usually not needed for it. If the alert is audible only to you through the system browser but not to viewers, check whether OBS is capturing the exact output device the browser sends audio to.
The drawback of desktop capture is that it's harder to control by source. For alerts, a separate Browser Source row is more convenient: it's easier to assign volume, monitoring, and the right track to it.
Check authorization if the test passes but followers don't come through
When the test alert plays and is visible but a real new follower doesn't trigger the event, check the Twitch account in the alert service. An error is possible after a password change, signing in again under a different profile, permission changes, or transferring settings between channels.
Before reconnecting, save the widget URL and important alert rules. Then disconnect the integration, sign out of the wrong Twitch account in the browser, and connect the right channel. The drawback of reconnecting is that the service may request permissions again or reset some related settings.
Follower alert checklist from event to track
- Run a test of the "new follower" event in the alert service.
- Check whether the widget appears on the scene that goes to the broadcast.
- Make sure sound is enabled for the follower and its volume isn't lowered.
- Compare the Browser Source URL with the current widget address.
- During the test, watch whether the Browser Source level moves in the OBS mixer.
- Check mute, volume, and audio output parameters on the browser source.
- In the advanced audio properties, enable the broadcast track on the Browser Source.
- Compare it with the track selected in the OBS output settings, especially track 1.
- Check monitoring separately if the alert is inaudible only to you.
- Check desktop audio capture only if the widget audio goes through the system device.
- Reconnect Twitch to the alert service if the test works but real followers don't come through.
Last Articles
What has changed in design and functionality We have updated the website to make working with it faster and more convenient. The main changes affect ..
Good afternoon, I've collected all the news during this time.: 1. The main news is that prices for twitch viewers have been greatly reduced, while Tw..
1. Use promo code "December2025" for a 15% discount for all our viewers2. We have reduced the base prices for our configurator and the most affordable..
Twitch services are working stably, so we are ready to cooperate with squads, resellers, service owners, bot owners, and many others.Individual te..
We have completely updated our Twitch viewer services, and they are now working stably. We only use high-quality IP addresses for the viewers.The ..
Hello everyone! Today, we are announcing a new feature—"Twitch Viewer Configurator". Now, you can customize any plan for your Twitch channel. Choo..
Greetings, I have compiled a guide for streamers, which will be very relevant at the moment. Now YouTube and twitch have disabled monetization from vi..
We have finally developed the APINow it will be more convenient for our partner sites to work with us.To update the maximum tariffs for YouTube, an up..
Due to the huge popularity of the partnership services and referral program, we have made a cooperation table. The essence is very simple: more live a..
Our Services for Streamers
Our Services for Content Creators










