How to use Rulixy with OBS Studio
Rulixy's current integration uses a dedicated web overlay and a temporary encrypted bridge. Keep the Control in your browser while OBS renders the wheel inside a Browser Source—no visible second Chrome window is required.
/overlay/. OBS no longer needs to share Chrome's local browser channel. The Overlay also runs without Analytics or the cookie banner.Quick setup
Recommended dimensions
🖥️ 16:9
1920 × 1080. For standard horizontal 1080p scenes.
📱 9:16
1080 × 1920. For vertical and mobile-first scenes.
⬜ 1:1
1080 × 1080. For a square area inside a custom layout.
🎯 Wheel only
700 × 700. Best when your scene already has titles, frames and branding.
Transparent background in OBS
The new /overlay/ page is transparent by design. The recommended setup is an OBS Browser Source, not a captured Chrome window.
- Select Transparent (OBS / Web source) in Rulixy.
- You do not need to keep a Chrome overlay window above OBS.
- If you use custom CSS, make sure it does not force a solid background.
Connection status
🟡 Waiting for Overlay
The URL is not open yet or the source is still starting.
🟢 Overlay connected
The source can receive tests and spins from the Control.
🔴 Connection error
Check your Internet connection and reload the source.
🔄 Regenerate link
Create a fresh session if the private URL was exposed or you want a clean setup.
Useful OBS Browser Source options
- URL: paste the complete Rulixy address, including the final
#k=fragment. - Width and height: match the Rulixy preset.
- Shutdown source when not visible: leave it off if you want the connection to stay ready while changing scenes.
- Refresh browser source when scene becomes active: usually leave it off; enable it only if you intentionally want a reload.
Test before going live
Test Overlay uses temporary demo data and restores your real list afterward. Check the pointer, transparency, final-result readability, Hype motion and spacing around your camera, chat and alerts.
If OBS does not receive the spin
/overlay/ does not load Google Analytics or the consent interface. Treat the Overlay URL as private.