How to run game night over a video call

When a video-call game night falls apart, it's usually not the game that was the problem. It's the small annoying stuff: you send the link to the wrong chat, nobody knows who's keeping time, or one person's audio arrives half a second behind everyone else. Twenty minutes in, you're still troubleshooting and nobody has played anything.

All of it is fixable before anyone joins the call. Here's what I do each time to help make sure my remote sessions are smooth.

The five-minute host checklist

1. Open the call and the game before everyone arrives. If the game needs a lobby, create it before. Keep the join link somewhere you can paste again (and again).
2. Pick one host and one timekeeper. The host (probably you) handles rules and restarts and debugging. The timekeeper keeps everyone in line, still useful even when the game shows its own clock.
3. Send the link in a new chat for the call. A link posted to the group chat gets lost fast. Make a new chat for this specific call and put the link in.
4. Run a five-second audio test. Count down and have everyone clap on zero. If one person arrives late, have them close extra tabs or turn off a camera. If that doesn't help, you can also let that person control timing for the night.
5. Keep a fallback game ready. This way, if the game lobby gets broken, you can switch games instead of making eight people watch you troubleshoot.

Pick a game that fits the vibe

The best remote games have one shared source of truth. Usually that's a browser lobby, but a clearly named host works just as well, and so does a single screens-shared document everyone can see.

If you're itching and want to start immediately, use our free remote-games list:

• Gartic Phone is the easiest large-group game. Just share one browser link and let the final slideshow do the hosting.
• Fishbowl works when the group wants teams and more interactivity/talking. Use the browser version instead of physical paper.
• Spaceteam is for a smaller, louder group with phones. Everybody talking at once is the joke, which also makes it less forgiving of lag.
• Spyfall is the slower bluffing pick. Use the browser version when the group would rather study each answer than draw or shout.

Treat latency as a game rule

If even one person is running half a second behind, every shared "go" and every reveal can become a dispute. So decide before the first round whose screen or voice is the authority:

• For turn-based games, the host calls the end of each turn.
• For timed games, open one shared timer for the room. The timekeeper's "stop" wins, even when another screen disagrees.

Teach it with one practice turn

Rules explanations feel longer over video because you can't lean over and point at the table. Instead, you should give the goal, play one practice turn, and let edge cases wait until they actually come up. A sixty-second demonstration beats five minutes of instructions. (There's a whole guide on teaching a party game if you want our advice on how to best do it; when you're teaching over video, trim that down to the shortest version of it.)

For a browser lobby, screen-share the join screen until everyone is in. Makes it easy to call out those who aren't in yet :)

Have a backup

Choose the backup before you need it. Ours is usually Fishbowl online: it needs no account and has worked consistently for us. Keep that fallback game link handy before you even start the main game. And set a limit! If the first game isn't running after five minutes, switch over.

I know all of this isn't the most exciting advice, and we didn't learn it in an exciting way. I once pasted a lobby link into the wrong group chat and started without half the people who were supposed to be there. So do the five minutes of prep. The alternative is forty-five minutes of people asking "wait, I'm not in the game!?"