Browser Source Width and Height define the web page’s viewport. The scene transform then places that rendered source. Correct the page’s viewport and provider layout before trying to shrink missing content back into view.
Distinguish a web page rendered in the wrong viewport from an OBS transform crop, then test long labels and full alert animations.
In this guide
Before you start
- The widget provider’s intended dimensions or a known test layout.
- A duplicate scene and a harmless test event or long sample label.
Find whether the page or its scene placement is clipping
A widget can be missing content because the page rendered into a viewport that is too small, or because OBS cropped the resulting source. These failures may look similar in Preview but need different changes. Record the Browser Source dimensions and its current transform before touching either.
OBS defines Browser Source Width and Height as the web page viewport. Its default CSS also hides overflow. A label outside that viewport may therefore never become part of the rendered picture you are scaling. Making the scene box smaller does not recover content that was already outside the page view.
Start with the widget’s actual layout requirements
Check the dimensions supplied by the widget or overlay provider. Some designs expect a fixed canvas; others rearrange when the viewport changes. Use a provider test event with a long name, a multi-line message and the largest animation you plan to show.
Keep private widget URLs out of public screenshots and notes. When comparing two sources, label them by dimensions rather than copying secret URLs into a report. Leave any supplied custom CSS intact until you understand what it controls; replacing it wholesale can create a new layout problem.
Separate viewport and transform in the test
Remove the scene ambiguity
In a duplicate scene, inspect the Browser Source’s Edit Transform values and any crop. Note them, then use an uncropped test placement large enough to inspect the source.
Look for: You can see whether the page itself is missing content before the scene crops it.
Set the intended viewport
Open Browser Source properties and set Width and Height to the provider’s intended test dimensions. Trigger the same sample event again.
Look for: The page renders into the space its design expects, exposing whether viewport clipping was the cause.
Place the complete result
After the page is complete, resize and position its source in the actual layout. Record the entire event, including entry and exit motion.
Look for: The final composition keeps the whole required animation and readable text inside the visible area.
Test the content that stretches the design
Short sample names are forgiving. Try a long but permitted display name, several lines of text and the provider’s larger event variants. Watch whether an animation briefly leaves the visible region or whether its shadow gets clipped. Judge the full event, not just the middle frame.
If only one variant fails, inspect that variant in the provider’s editor. A global viewport change may make the others unnecessarily large. Keep the source’s scene scale and the provider layout in separate notes so the next person knows where each correction belongs.
Check readability after the clipping is gone
A complete widget can still be too small after you shrink it into the layout. Play the recording at the delivery size and read the longest label without pausing. If it fails, simplify the provider design or allocate more space rather than relying on a tiny complete rendering.
Return to performance checks only after the geometry is understood. Increasing the viewport far beyond the design’s needs is not a neutral fix. Keep the smallest dimensions that correctly render the intended content, then verify the widget still behaves properly when you leave and return to its scene.
Still stuck?
Shrinking the source does not reveal the missing text.
Inspect the page viewport and provider layout; the text may have been clipped before the scene transform was applied.
Sources & references
Based on the linked first-party OBS documentation checked on 4 November 2026. The exercises and acceptance checks are editorial workflows for you to run; no hands-on OBS session or hardware benchmark is claimed.
- OBS — Browser Source ↗Checked 2026-11-04
- OBS — Sources Guide ↗Checked 2026-11-04
Spotted something out of date? Let Alex know.
How we put our guides together ↗