A hosted overlay is a web page that OBS loads as a Browser Source. The provider serves the page and may let you personalize it in a portal; OBS displays it inside a scene. Before choosing one, look at the editing workflow, how access is maintained, and how the source fits your canvas.
01 / OWNERSHIP & UPKEEP
Check the maintenance tradeoff
Start by asking what you can customize and where that work happens. A portal-based service may let you update channel text or select a scene without editing files. You still need to learn the provider’s controls, create a source, and check it in your own OBS scene. Read the provider’s guide so you know what is included before joining.
Some hosted offers use recurring membership terms and limit access to a verified eligible period. Local files may avoid a hosted-access renewal, but you maintain the files and replace or edit them yourself. Self-hosting gives you control over the page and deployment, while leaving hosting, updates, and availability to you. Compare the total recurring cost with the time and upkeep you are willing to take on; there is no universal lower-cost choice.
For FWG Studio, Regular includes 9 themes and Premium includes all 23. Each included theme has four hosted Browser Source states at 1920 × 1080: Starting Soon, Be Right Back, Stream Ending, and Currently Offline. Review FWG’s About page and membership terms for the current service details and eligibility.
- Starting Soon
- Be Right Back
- Stream Ending
- Currently Offline
02 / ACCESS
Confirm access and connection needs
A hosted source needs an internet connection when OBS loads the page. Check what happens when access expires, a payment is pending, or the service cannot be reached. A saved URL by itself does not establish that you currently have access.
FWG hosted sources require internet access and an eligible, verified access period. For current eligibility and service-specific details, use FWG Studio’s official OBS setup guide, About page, or terms. Those pages are the source for current membership conditions.
03 / SOURCE PRIVACY
Treat your Browser Source URL as private
Use the URL created in your own authenticated FWG Studio portal. Do not copy a customer-specific URL from a post, screenshot, or someone else’s scene. Keep your private URL out of public materials; if it is exposed, revoke it in the portal, create a replacement, and update the OBS source.
Radarclips does not publish or generate private FWG source URLs, membership keys, or credentials. Sign in to your own FWG portal to create and copy your URL.
04 / SCENE FIT
Match the source viewport to the overlay
Browser Source Width and Height set the browser page’s viewport. Match them to the overlay’s design dimensions and your OBS canvas so elements have room to render. OBS documents 800 × 600 as the default, not a recommended universal size. FWG’s hosted scenes are 1920 × 1080, so use those dimensions for those full-canvas scenes; another overlay may need a different size.
Check your OBS base canvas resolution in Settings → Video → Base (Canvas) Resolution. Add the source to the scene where you need it, then position and layer it so the overlay does not cover content you want viewers to see.
OBS’s Local file option loads a page from your computer instead of loading a URL. For a hosted page, leave Local file off and enter the URL from your own provider account.
05 / PERFORMANCE
Test the page in your real scene
Browser Source embeds a web page in OBS. How much work it adds depends on the page, animations, frame-rate settings, and your system. Test the overlay in the scene you will stream, with your other active sources enabled. If performance is a concern, simplify or close sources you do not need and test again before going live.
OBS offers Shutdown source when not visible. When enabled, it unloads a page while its source is hidden or its scene is inactive. That can reduce inactive browser work, but the page must load again when shown, so test it with your connection and scene-switching workflow.
06 / QUICK SETUP
Add a hosted Browser Source in OBS
These steps apply to a hosted page. For FWG-specific account and source instructions, follow the FWG Studio setup guide.
- Select a scene. Choose the OBS scene where the overlay belongs.
- Add a Browser Source. In the Sources panel, add Browser to that scene.
- Keep Local file off. A hosted page is loaded by URL, not from a local file.
- Paste your own provider URL. Create and copy your private URL in your authenticated provider portal, then enter it in the URL field.
- Set Width and Height. Match the overlay design and canvas. For FWG’s hosted full-canvas scenes, use 1920 × 1080; do not apply that size to every overlay.
- Preview the scene. Check placement, visibility, connection, and source order before streaming.
What the other Browser Source settings do
- Page permissions default to read access to OBS status information.
- Shutdown source when not visible, when enabled, unloads a hidden source or one in an inactive scene.
- Default custom CSS makes the page background transparent, removes body margins, and hides scrollbars.
See the official OBS Browser Source documentation for the complete property reference.
07 / RADARCLIPS CATALOGS
Check the live listings, and keep checkout separate
See current Radarclips streaming plan prices, terms, and availability on the streaming plans page. Browse the overlay catalog for each pack’s current details and availability. A listed overlay pack is not necessarily a hosted Browser Source; check the individual listing for what it includes and how it is delivered.
Radarclips checkout does not create or activate an FWG Studio membership and does not provision an FWG private source URL. FWG membership access and Radarclips purchases are separate.