How Peerful works
One shared screen, one phone per player, and no server in the middle.
Most party games ask you to buy controllers, install an app or sign in. Peerful asks for a screen and the phones already in people's pockets.
The screen and the phones
Open Peerful on the biggest screen in the room: a laptop, a TV with a browser, a tablet propped against a chair. That device becomes the shared screen. It shows the game, the room code and — during a round — the information everybody is allowed to see.
Every other device is a controller. It shows only what that player needs: their hand, their buttons, their secret answer. Nothing private is ever painted on the shared screen, which is why people can sit next to each other and still keep a secret.
The framework also supports shapes without a shared screen: in a screenless match the phones hold the whole game, and in a single device match everybody takes turns on one tablet or laptop. Category Clash, the first shipped game, is shared-screen only, and each game's page lists the shapes it supports.
Joining a room
The host creates a room and the shared screen shows a five-character code and a QR code. Everyone else opens the same game, chooses Join, and types the code or scans it. Names are optional guest names — there is no account to create, and nothing to verify.
Who runs the game
One device is the authority for the match: it owns the timer, the scores and the rules. Usually that is the shared screen, because it has the most stable connection and the biggest display. Everyone else sends their moves to it and receives the public state back.
If the authority device closes or loses its connection, another player device can take over hosting and continue the match. The original screen can reclaim hosting when it comes back, so its player picks up their phone again instead of being stuck as a spectator.
What the network actually does
The first step is discovery: devices need a way to find each other, so they exchange connection offers through public signaling relays. Once two devices have met, game traffic goes directly between them over WebRTC.
That has two practical consequences:
- No game server stores your session. Nobody can read the answers from a database afterwards, because there is no database.
- A network that blocks direct connections (some offices and schools do) may need a TURN relay to pass traffic. Peerful treats that as an optional extra rather than a requirement.
A poor connection is handled rather than hidden: the game shows the measured latency, batches updates, and can compress large messages. The host can also pick a lighter network profile before the match starts.
Privacy in one paragraph
There are no accounts, no analytics profiles and no match history. The only things stored on a device are preferences: language, chosen theme, sound volume and the last guest name, all in the browser's local storage. The privacy article explains what the relays can and cannot see.
Where to go next
- Play Category Clash, the first game built on this setup.
- Read the FAQ for player counts, broken connections and hosting your own copy.
- Accessibility statement for themes, keyboard use and known gaps.