Free Chrome extension for casino streamers: the slot you open, !slot requests, room chat and participants flow from hype.bet, Shuffle or Stake into your widgets.
Casino streamers run two windows all night: the casino, and the tools that put it on stream. Every time the game changes, someone has to type the new slot into the Current Slot widget; every !slot request in the casino's own room chat is a request the queue never sees.
The CasinoHub browser extension closes that gap. It runs in the casino tab, reads the game you have open and the room chat next to it, and sends both to your own CasinoHub account — the same widgets, overlays and request queue you already use, now fed from the casino instead of by hand.
It is free, it works on Chrome, Edge, Brave and any other Chromium browser, and it only ever runs on the supported casinos plus any site you switch on yourself.
Every function can be turned off on its own, and every site can be switched off on its own. Nothing is captured until you have pasted your pairing token.
Current slot
The game you open on the casino is matched against the slot database and pushed to the Current Slot widget with its cover, provider and RTP.
!slot requests
Viewers typing !slot in the casino's room chat land in the same request queue as Twitch, Kick and YouTube chat, with the requester's name.
Room chat
The casino's room chat is forwarded into the Unified Chat overlay next to your platform chats — username, avatar and message.
Participants
The room's participant list with balance and wagered feeds the Room Participants widget, updated as the table changes.
Tab audio
Mute the casino tab or boost it to 600 % from the popup. The sound is shaped inside your browser and never leaves your device.
Only to your account
Everything is sent with your own pairing token to casinohub.app and nowhere else. Revoke the token in the dashboard and it stops at once.
Sites with a built-in adapter are captured automatically once you are paired. Any other site can be switched on from the popup — Chrome asks for that one site and nothing else.
| Casino | Current slot | !slot requests | Room chat | Participants | Tab audio |
|---|---|---|---|---|---|
hype.bet | |||||
Shuffle | |||||
Stake | |||||
Casinobud | |||||
Any other site |
Missing your casino? Say so in the Discord and it goes on the list.
Chrome, Edge, Brave and other Chromium browsers. Installs unpacked from the dashboard today; the Chrome Web Store listing follows once approved.
The current slot, matched against the database
On hype.bet the extension reads the room's game badge; on Shuffle and Stake it reads the game from the page you have open. The title is matched against the CasinoHub slot database, so the widget shows the proper cover, the studio and the published RTP even when the casino shows none of that.
Stake's own games — dice, mines, plinko and the rest — are recognised and skipped, so the widget never shows a slot that is not one.
!slot requests from the casino's chat
A viewer who types !slot Wanted Dead or a Wild in the hype.bet room chat lands in your request queue exactly like a viewer on Twitch or Kick, with their name attached, so the request limits, the battle and the suggester board all apply.
On any other site you switch on, new chat lines are scanned for !slot and forwarded the same way.
Room chat and participants on the overlay
Forwarded room chat appears in the Unified Chat overlay under its own source, with the username and avatar the casino shows, once you turn on Show external in that widget. The room's participant table feeds the Room Participants widget with balance and wagered as they change.
Both are toggles: capture the chat without forwarding it, or forward it without the participants — each function and each site has its own switch in the popup.
Tab audio without a mixer
The popup mutes the casino tab or boosts it up to 600 %, per tab, so a quiet game is audible on stream without touching the site's own volume. The audio is shaped inside your browser and never leaves it.
At exactly 100 % the tab plays natively; anything else runs through a gain node the extension keeps in a hidden document while the tab is open.
Which casinos does the CasinoHub extension support?
hype.bet, Shuffle, Stake, Casinobud have built-in adapters and are captured automatically once you are paired. hype.bet supports room chat and the participant table as well as the current slot; Shuffle, Stake (all mirror domains) and Casinobud are single-player sites, so it is current-slot detection there. Any other site can be switched on from the popup for !slot requests.
Is the extension free?
Yes. It is part of the free CasinoHub account, like the widgets it feeds. There is no paid tier for the extension.
Which browsers does it work in?
Chrome, Edge, Brave and other Chromium browsers (Chrome 116 or newer). It installs unpacked from the dashboard today, with the Chrome Web Store listing to follow once approved.
What data does it send, and where?
Only what the toggles allow — the open slot, !slot requests, room chat and the participant list from the captured casino page — and only to your own CasinoHub account, identified by your pairing token. It does not read your browsing history, does not run on other pages, and tab audio never leaves your device. The privacy policy has a section on it.
Does it read every website I open?
No. It runs on the supported casinos listed in its permissions, plus any site you switch on yourself — Chrome asks for that one site when you do. Turning the site off removes the access again.
How does the current slot get its RTP and cover?
The title read from the casino is matched against the CasinoHub slot database, which carries the cover, the studio and the published RTP for thousands of slots. Casinos can run a lower RTP configuration of the same game, so the in-game value is the one that counts.
One free account carries the whole toolkit — nothing here is behind a separate plan.