Frequently asked questions

Yes. Streamer Garden is free to use while the product and community grow. You can open the studio, connect it to OBS, and run interactive streams. There is no card or trial clock.

Not for Streamer Garden — its studio and viewer experience run in the browser and connect directly to OBS's built-in WebSocket. You do need OBS Studio (a free download) to capture, encode, and broadcast the stream.

Streamer Garden connects directly to OBS, so its overlays and phone controller go wherever OBS broadcasts, including Twitch, YouTube, or Kick. Native Streamer Garden stats, chat, and alert connections currently support Twitch and YouTube.

Open Studio, choose Connect to OBS, and use the connection details from OBS's built-in WebSocket server. Garden connects locally, sets up the overlay, and keeps your OBS scenes, sources, and live controls together in Studio.

No. Viewers scan the QR code on your overlay, which opens your viewer page in their phone's browser. There's no app to install and no account to create — they can vote, hype, ask, and draw right away.

From their phone's browser they can vote in live polls, charge a shared hype meter, submit questions for you to feature on screen, and draw doodles that appear on the broadcast after you approve them. Goal bars, a soundboard, and a BRB arcade round out the overlay.

No. You stay in control: questions and doodles only appear after you approve them, you decide when voting and hype are open, and a panic control can pause every interaction instantly.

Yes. The studio's Camera tab turns your phone into a webcam for the overlay: it connects peer-to-peer over WebRTC and shows up as a camera slot in your OBS browser source — no extra capture software.

Yes. Each scene stores a separate portrait (9:16) layout alongside the landscape one, so a vertical output gets a layout designed for it — you pick the orientation per OBS source on the overlay URL.

It's real-time by design. Votes, the hype meter, and the viewer count update live on the overlay over a websocket as your audience interacts — there's nothing to refresh. Any extra latency you see is just your normal stream encoding and platform delay.