STREAMING GUIDE / STREAM TOOLS

OBS browser source not showing: isolate the page and scene

Find whether the overlay page failed to load or simply sits outside the visible composition. Test a clean source before rebuilding the production scene.

START HERE

First test whether the source is visible, inside the canvas, and above covering layers. Then compare a known public web page with the actual overlay in a temporary scene. If only the overlay fails, investigate its URL and provider state; if both fail, investigate OBS browser support or rendering.

1. Decide whether blank is actually unexpected

An alert box may intentionally show nothing until an event occurs. A chat widget may have no retained messages after it starts. Trigger a provider test alert or send a test chat message from an account that is allowed to participate before treating an empty transparent source as broken.

These checks apply to the Browser source in OBS Studio, not a Window Capture aimed at your normal web browser. On Linux, confirm that your OBS package includes browser support; OBS documents support through its official packages. Do not install an unrelated legacy browser plugin simply because a tutorial names one.

2. Check the scene before the network

  1. Select the source and confirm its visibility is enabled.
  2. Move it temporarily above opaque backgrounds, game captures, and nested scenes that could cover it.
  3. Inspect its transform and crop. Reset an accidental crop, then fit the source to the canvas for a diagnostic view.
  4. If using Studio Mode, inspect the program view as well as preview. Editing a preview scene does not prove the outgoing scene changed.

Record the original transform before moving anything so you can restore the layout. If the overlay appears after these checks, the web page was loading successfully; changing the provider account or clearing every cache would address the wrong stage.

3. Verify the URL and browser viewport

Copy the provider's overlay or widget URL again and compare it with the browser source. An editor URL, dashboard address, and rendered overlay address serve different purposes. Keep account-specific URLs private when copying or sharing screenshots.

Use the dimensions expected by that overlay. Browser width and height define the page's viewport; resizing the source on the canvas is a separate transform. A widget positioned near the bottom of a 1080-pixel-tall layout can disappear when the browser viewport is only 600 pixels tall.

For a hosted overlay, make sure the source is loading a URL rather than a local file. For a local HTML widget, verify that the chosen file still exists after moving or extracting its folder. Refresh the individual source once after correcting the address, rather than repeatedly restarting OBS. If the missing widget is a YouTube live chat overlay from Slippy2 Desktop, check the Slippy2 YouTube chat setup guide to isolate authorization from browser-source rendering.

4. Compare a clean source with the failing overlay

Create a temporary scene and add a new browser source containing a harmless public page such as https://example.com/. Do not capture an account dashboard or private inbox for this test. Give the source enough visible canvas space to see its result.

  • The public page appears: OBS can render a simple page. Return to the overlay's saved configuration, event availability, custom CSS, and provider status.
  • The public page is blank too: verify the internet connection and OBS installation, then investigate the shared browser/rendering layer.
  • The overlay works only in the clean scene: compare transforms, layers, filters, and source properties with the production scene.

A page working in Chrome does not guarantee it will work in OBS's embedded browser. Browser sessions, stored logins, and supported features can differ.

5. Check reload behavior and rendering carefully

If the failure happens only after returning from a break scene, inspect whether the source unloads when hidden or refreshes when activated. Test those options individually. An overlay that needs time to reconnect may not be ready at the instant a transition starts.

For a rendering problem affecting clean sources too, StreamElements recommends testing the browser hardware-acceleration option in OBS's Advanced settings. Note the current value, change it once, restart OBS, and repeat the same comparison. Restore it if there is no improvement. Do this off stream because it affects browser sources beyond the one you are inspecting.

Leave browser page permissions at the least privilege the widget actually needs. Increasing Browser Source page permissions does not repair an incorrect address or off-screen crop.

Verify the actual production sequence

Test one alert, one chat message, a scene transition, and a return to the original scene. Confirm both the outgoing picture and any associated audio in a short recording. Remove the temporary diagnostic source afterward.

If the clean-page test still fails, collect OBS version, OS, installation type, source dimensions, and the smallest reproducing scene. Review logs and screenshots for private overlay URLs before sending them to OBS or the provider's official support channel.

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.