From builder to scene
in three steps.
The overlay is a standard web source. The mock uses archived sample data; the production architecture refreshes its payload without replacing the URL in your scene.
1 · Copy the browser-source URL
Choose a utility and filters in the builder. Preview empty and delayed-data states before copying.
Open builder →2 · Add it to your scene
In OBS, add a Browser source, paste the URL, and use your canvas size so placement remains intuitive.
3 · Place the safe area
Drag the utility to a corner or lower third. Keep important game HUD elements outside its footprint.
Suggested concept settings
| Canvas | match your scene |
| Custom CSS | none required |
| Refresh | payload every 60s |
| Shutdown source | leave off |
What happens when data changes
New campaign
The next valid payload replaces the previous reward facts; the browser-source URL stays put.
No campaign
The utility switches to a deliberate empty state or hides, depending on its saved configuration.
Refresh fails
The shell retains the last good response instead of flashing blank or surfacing a server error.
Delayed over 3h
A visible data-delayed chip tells the broadcaster the snapshot may be stale.
Common questions
Does the source know a viewer's personal Drops progress?
No. A public broadcast overlay only shows campaign facts such as rewards, requirements and deadlines. Personal claim progress remains on the official platform.
Where do viewers find eligible channels and claim steps?
Those details live on StreamDrops. StreamOverlays links to that source page instead of duplicating a campaign directory.
Does channel auto-sync work in this mock?
No. The production mode requires a verified Twitch OAuth channel claim; this static concept intentionally does not simulate authentication.