streamoverlays.app
Creator utility reward-aware · one browser source

Overlays that know
what viewers can earn.

Pick a game—or, later, follow a claimed channel—and turn reward data from StreamDrops into an OBS browser source. Requirements and campaign windows stay attached to the source instead of becoming another scene you have to maintain.

4Reward utilities
60sProduction refresh target
1Browser-source URL
Last goodStale-data behavior

See the reward layer

archived snapshot · not current campaign data
1920 × 1080 preview Interactive concept · archived sample
Rewards · Dead by Daylight Archived sample
Camper's Shelter BadgeCampaign reward Watch 1h
Slasher's Mask CharmCampaign reward Watch 3h
Red Omen BannerCampaign reward Watch 6h
No active reward campaign for this game.
Ended Jun 25, 2026 ● data delayed Data: streamdrops.app
Interactive concept The Dead by Daylight sample was captured June 24, 2026 and ended June 25. It demonstrates the broadcast surface, not a live campaign. Campaign details and claim guidance belong on StreamDrops →

Reward utilities

facts first · no theme-pack marketplace
Marquee delivery mode

Switch games.
Keep the same source.

A claimed-channel source can follow the broadcaster's current category and switch the reward utility automatically. The URL stays in OBS; only the graph query changes.

No OBS pluginCategory-awareEmpty-state safe

Channel claim comes later

This mock does not invent a sign-in flow. Production channel mode requires a verified Twitch OAuth claim and stores the overlay configuration against that channel.

/channel/claimed-login/reward-list
→ current category
→ reward facts from StreamDrops

Build the browser source

sample config · URL semantics preserved

Configure facts, not decoration packs

Choose a utility, decide which reward types appear, preview empty and delayed-data states, then paste the generated URL into OBS.

drops=watch,event hidedrops=subs theme=glass
Open builder →
🎁 Dead by Daylight campaign dataeligibility, campaign history and claim steps live on StreamDrops streamdrops.app → Chatbot companions!drops · !reward · !claim responses from the same graph see commands →

Three steps to air

standard browser source
01

Choose the data

Fixed game for the concept; claimed-channel auto-sync in production.

02

Shape the utility

List, rotator, countdown or badge window—with safe empty states.

03

Paste into OBS

Add one browser source and keep that URL through future campaigns.

Freshness is part of the UI

Static shell

The OBS document stays cacheable and lightweight; campaign facts are a separate payload.

60-second polling

Conditional requests use an ETag so unchanged reward data stays cheap.

Last-good fallback

A failed refresh keeps the last valid payload. After three hours, a data-delayed chip appears.

Authority links

Campaign details route to StreamDrops; badge acquisition details route to StreamBadges.