OBS Browser Source Troubleshooting for Alerts, TTS, and Upload Corner

The URL is not the setup

The most common OBS mistake is pasting an alert URL into Browser Source and assuming the job is done. The URL is only the feed. The source still needs a deliberate width, height, position, audio behavior, refresh behavior, and a place in the scene stack.

This is where a lot of streamer tools feel worse than they are. The alert service may be fine, but the source is 800 by 600 in a 1920 by 1080 scene, sitting under the gameplay capture, muted in the audio mixer, or stuck with yesterday's cached state.

A good browser-source setup is boring to look at in OBS. The box has the same size every time. It sits where it cannot cover the face cam or game UI. It can be tested without going live. If it breaks, a moderator or producer can describe the problem in one sentence.

The bugs usually look like timing bugs

Alert and TTS bugs often show up as timing problems. The first alert works, the second one does not. Audio plays when the source is hidden. A viewer upload appears in the wrong scene. The browser source only refreshes after the streamer clicks properties.

Treat those as lifecycle issues. Browser content has to load, become visible, receive events, play audio, and clean itself up when scenes change. OBS gives streamers enough controls to make that sane, but those controls need to be chosen on purpose.

• If the alert never appears, check source size, URL, layer order, and whether the page needs login cookies.
• If the alert appears behind the stream, move the source higher in the scene stack.
• If old alerts keep replaying, test refresh behavior and cache settings.
• If TTS is silent, check OBS audio mixer routing before blaming the TTS provider.
• If uploads cover important content, fix the source rectangle instead of asking viewers to behave differently.

My pre-stream browser-source test

Before I would trust any paid alert on a real stream, I would run the boring version of the test. Send a small test tip, a long username, a long TTS message, a rejected message, and an approved image. Change scenes while each one is pending. Then watch the recording back on a phone-sized player.

That last step catches more problems than people expect. Tiny alert text, bad contrast, misplaced Upload Corner images, and loud TTS are easier to notice when you stop looking at the OBS canvas and start looking like a viewer.

• Test over the actual gameplay, camera, and chat layout.
• Use the longest names and messages you realistically allow.
• Confirm the source survives scene switches.
• Record locally and watch the test back before launch.
• Write down the one reset step a moderator should try first.