Multiplayer Spin Wheel: Spin Together, Online

A normal spin wheel lives on one screen. A multiplayer spin wheel lives on everyone's. The host creates a room, shares a code or a link, and each guest opens the same wheel in their own browser. When the host spins, every screen animates together and stops on the same name. That turns a solo random picker into a live wheel spinner a whole group can watch, whether the group is a class on Google Meet, a team on Microsoft Teams, a Discord server, or a Twitch chat.

The point is trust as much as convenience. When a raffle winner is drawn on a screen only the host can see, the audience takes the result on faith. When the same realtime spinner runs on their own device, they watched it happen. That is why remote giveaways, classroom picks and team decisions all get easier with a shared spinner instead of a screenshot.

Traditional wheel tools require the host to share their screen over Zoom, Meet or Discord. That introduces latency, video compression, and a wheel squeezed into whatever corner of the call the platform gives it. Anyone on a phone sees a blur, anyone with a slow connection sees the result a few seconds late, and nobody can read the entries.

Multiplayer Spin Wheel lets every participant open the same room directly in their own browser, so everyone watches the same synchronized animation at full resolution on their own device. The host still controls the spin. The difference is that guests are looking at the wheel itself, not a video of it, which is why the result reads as fair and why it works alongside any meeting or streaming tool rather than depending on one.

The wheel is not streamed. When the host clicks Spin, the winner is chosen on the host's device with a cryptographically secure random number, and the room record is updated with the target slice, a random animation seed and the spin duration. Every guest's browser is listening to that record in real time. The moment it changes, each browser animates its own copy of the wheel using the same seed, so the easing, the overshoot and the final rest are identical everywhere.

Because only a few numbers travel over the network, sync is fast and cheap. Network latency can shift the first frame by a fraction of a second between devices, but the destination cannot differ: the seed drives the animation, and the target slice was fixed before any wheel moved. A guest who joins mid-spin gets the same record and lands on the same winner.

Each browser renders the wheel independently, so it is fair to ask how they can agree. The answer is that the winner is never derived from the animation. The host's device picks the winning slice first, then the animation is built to land there. Guests receive the slice index, not a video, so a dropped frame or a throttled background tab on one phone cannot change who won on that phone.

The seed matters only for cosmetics: it makes every screen show the same number of revolutions and the same flourish at the end. It cannot select a winner, which means an invite link, which contains the code, cannot be used to predict or influence a draw.

Joining is free for everyone; hosting needs a free account, which can host a limited number of rooms, each open for 24 hours. One click hosts it, it runs on its own page with a short code, guests join with nothing but the link, roles cover host, participant and spectator, entrants can add themselves to the wheel, the page reconnects on its own, every spin lands in an append-only event log, and the server commits to each spin before the wheel moves. It suits classrooms, standups, game nights and small giveaways.

Every room a Premium host runs also has the event capabilities: room locking once entries close, member removal, co-hosts who can keep spinning if the host drops, several winners drawn in one session, CSV export of the results, and a standing room that never expires. The server enforces every one of these, not the browser.

Use the ordinary wheel when you are the only one who needs to see it: picking a restaurant, choosing a task, drawing a name in a physical classroom where everyone can see your projector. It is instant, works offline once loaded, and never touches a server.

Use the multiplayer wheel when the audience is somewhere else. Remote classes, distributed teams, online communities and livestreams all benefit from a collaborative decision wheel that each person watches on their own screen. The wheel, the entries and the spin are identical; the room is what changes.

Add the class list to the wheel before the lesson, click Host room, name the room after the activity ("Who reads next?", "Exit ticket order") and paste the invite link into the Meet, Zoom or Teams chat. Students open it on their own devices while you keep the wheel on the projector or in your shared screen for anyone who prefers it.

Spin from your device only; students cannot spin or edit, so nobody can skip a turn or remove a name. Emoji reactions let the class respond without unmuting. When the lesson ends, close the tab: the room cleans itself up within a day, and your class list stays saved in your browser for next time.

For a remote giveaway, load the entrant names or ticket numbers, host a room, and share the link where the entrants already are: the Discord announcement channel, the stream chat, the Zoom sidebar. Entrants watch the draw on their own screens, which removes the usual "was that really random?" reply.

For prizes people care about, use the Premium room capabilities. Lock the room once entries close, promote a co-host as a backup, draw the number of winners you need in one go, and keep the event log as your record of who was in and who won.

The room works the same on every meeting platform because it never plugs into the platform. Paste the invite link into the meeting chat, and each attendee opens it in a browser tab beside the call. On Zoom, the link is clickable in chat on desktop and mobile. On Google Meet, it opens in a new tab next to the meeting tab. On Microsoft Teams, drop it in the meeting chat or the channel; attendees on the Teams desktop app open it in their default browser.

If some attendees cannot open a second tab, share your screen as a fallback for them and let everyone else watch in their own browser. The result is the same for both groups because the winner is fixed before the wheel moves.

On Twitch, add the wheel as a browser source in OBS so it appears on stream, and post the room link in chat so viewers can also open the shared spinner directly. Viewers who open the room see the spin in real time, without the stream delay, and can react with emoji that appear on the host's screen too.

On Discord, post the invite link in a text channel while people are in the voice channel. Nobody needs a bot or a screen share; members open the link and watch the same wheel on their own device. Community game nights, giveaway draws and "who goes first" decisions all run this way, and the host can retitle the room between rounds.

Every room gets a random 8-character code from an alphabet that leaves out easily confused characters, so a code read aloud on a stream or written on a whiteboard still types correctly. Opening the invite link shows an invite card first: who is hosting, what the wheel is for, and who is already in. Guests confirm a display name and they are in. Older rooms used 6-character codes, and those links and codes still work.

Codes are random rather than sequential, so nobody can guess a live room by trying neighbours. A Premium account can additionally reserve a permanent alias for its rooms, so a community can reuse the same link every week.

Rooms are temporary on purpose. The host picks a lifetime when creating the room, from a couple of hours to a day, and when it lapses the room is deleted and any guest still connected drops back to their own local wheel. A standing room that never expires, for a recurring event, comes with Premium.

Nothing about a room is needed after the event. Your wheel and entries remain in your own browser, and a guest who wants the wheel gets a copy with one tap after the spin. Cleanup keeps expired codes from accumulating and keeps old entry lists from lingering on a server.

In a shared wheel, the temptation to poke it is universal. If every guest could spin, a live giveaway would become a race, and a classroom pick would become a game of who clicks first. Making the host the only person who can spin, edit entries or change settings keeps the event orderly and the result meaningful.

It also keeps the result honest. Because the room record only accepts spins from the host, a guest cannot inject a spin that lands on their own name. The server checks the host's authority on every action, so even a tampered browser cannot claim powers it was not given.

Sharing the code before the entries are final, so early guests see a half-built wheel. Hosting from a device that will go to sleep or lose signal with no co-host as a backup. Posting a room link publicly for a draw that should have been limited to entrants. Spinning before everyone has joined, when the point was for people to watch.

Each has a simple fix: finish the wheel first, host from a stable device or promote a co-host (Premium), treat the link like a ticket, and check the presence list before you spin. A multiplayer random picker is only as convincing as the moment everyone sees together.