ReactFyre
ReactFyre is a hosted overlay and asset manager for streamers. You upload image, video, and audio assets, configure alerts for cheers, commands, custom actions, and channel point redemptions using six alert types, then copy an overlay URL into an OBS browser source. Live events arrive through a Streamer.bot websocket connection.
Platforms: Web, OBS browser source
Product page: desertice.tech/products/reactfyre
Who it’s for: Twitch streamers who want configurable browser-source overlays and alerts
Features
Section titled “Features”- Form-based overlay configuration with six alert types: Simple, Video, Sound, Thrown, Edge, and Slide
- Flat file manager for image, video, and audio assets with type filters and per-plan storage quotas
- OBS browser source via a copied overlay URL; saving is enough, there is no publish step
- Triggers for Twitch cheers, chat commands, Streamer.bot custom actions, and channel point redemptions
- Test alerts from the overlay editor without Streamer.bot
- Sign-in with Twitch via Clerk; entitlements via Clerk Billing, qualifying Twitch subscription, or Patreon
- Per-overlay slug URLs that can be regenerated
Requirements
Section titled “Requirements”- A Twitch account for sign-in
- An entitled account (Clerk Billing plan, qualifying Twitch channel subscription, or Patreon membership) or admin access to upload files and create overlays; other signed-in users have cleanup-only access to existing items
- OBS Studio for the browser source
- Streamer.bot 1.0.5 or newer (1.0.7+ recommended) with its WebSocket server enabled for live alerts
Install
Section titled “Install”- Open the React Fyre site and click Sign In, then authenticate with Twitch
- Connect Twitch (and Patreon if used) under Connections
- Open Files and upload images, video, or audio
- Open Overlays, click New, and name the overlay
- Configure cheers, commands, custom actions, and redemptions; pick an alert type and attach uploaded files
- Use Test Alert to preview a saved overlay
- Click Copy URL and paste it into an OBS Browser Source at canvas size
- Set the OBS Browser Source width and height to your canvas (e.g. 1920x1080)
- Set the browser source FPS to 60 or your stream FPS
- Enable “Shutdown source when not visible” and “Refresh browser when scene becomes active”
- On the stream PC, install Streamer.bot from streamer.bot, connect Twitch (and YouTube if used), and enable its WebSocket server on 127.0.0.1:8080 (port 8080, not 7474)
- The overlay browser source must be able to reach the Streamer.bot host (localhost when OBS and Streamer.bot share a PC)
Using it
Section titled “Using it”- Upload assets in Files; the list is flat with All / Images / Video / Audio filters and no folders
- Pick the alert type per trigger: Simple (image), Video (full motion), Sound (audio only), Thrown (physics toss), Edge (per-edge image lists), Slide (slide in from a screen edge)
- Keep start delays short, alert durations a few seconds, and volume below your bed music
- Regenerate a slug if you need a new browser-source URL, then update OBS
- Deleting a file used by an overlay is blocked until you remove those references
- Test alerts do not require Streamer.bot; live bits, commands, and redemptions do
Troubleshooting
Section titled “Troubleshooting”The OBS source is blank
Section titled “The OBS source is blank”Paste the overlay URL into a normal browser first, confirm the overlay still exists and the slug matches, refresh the browser source or restart OBS, and check that the referenced files still exist.
Alerts don’t fire live
Section titled “Alerts don’t fire live”Confirm Streamer.bot is running with its WebSocket server on 127.0.0.1:8080, you’re on Streamer.bot 1.0.5+ (1.0.7+ preferred) for the payload shape, and the overlay browser source can reach that host. Use Test Alert to separate media problems from event problems.
An upload fails
Section titled “An upload fails”Check the file size and type (image/, video/, audio/* are accepted) and retry; if a finished upload is missing, refresh the page.
I can’t delete a file
Section titled “I can’t delete a file”The file is still attached to an overlay. Remove the references from the overlay first.
Sign-in issues
Section titled “Sign-in issues”Sign-in is Twitch via Clerk. Try another browser or private window, clear site cookies, and remember that file and overlay writes need an entitled plan, qualifying Twitch sub, Patreon, or admin.
Is there a publish step for overlays?
Section titled “Is there a publish step for overlays?”No. Saving the overlay is enough; Copy URL always reflects the saved state.
Can I trigger alerts with a webhook or REST API?
Section titled “Can I trigger alerts with a webhook or REST API?”No. React Fyre reads cheers, commands, custom actions, and redemptions from Streamer.bot over a local WebSocket; there is no public alert REST API or webhook endpoint.
Are there folders in the file manager?
Section titled “Are there folders in the file manager?”No. The manager is a flat list with All / Images / Video / Audio filters, so use descriptive filenames.
Does React Fyre support YouTube live events?
Section titled “Does React Fyre support YouTube live events?”Only if Streamer.bot is connected to YouTube; React Fyre reads those events from Streamer.bot and does not OAuth YouTube itself.