Why Your Jackbox Game Won't Show Up on the TV
Most connection problems between your phone and the TV screen in Jackbox games come down to one thing: everyone is not on the same local network, even when it looks like they are. The host game runs on your computer or console and broadcasts a room code. Players join from their phones by entering that code at jackbox.tv. That sounds straightforward until someone has a guest WiFi network enabled, a smart TV is connected to a separate IoT VLAN, or the router is isolating devices from each other. Start by checking the basics before you do anything complicated. Make sure the TV or device running the Jackbox game is actually outputting video to the screen you think it is. I spent an entire party once troubleshooting a "connection issue" that turned out to be my friend using an HDMI capture card for streaming while also trying to play Jackbox. The game was running fine, but nobody could see it because the display output was switched to the wrong source. Check the input. Seriously. It happens more often than you would think. Once you confirm everyone can see the game screen, move to the network side. All devices need to be on the same subnet. If your router has a guest network feature enabled, make sure nobody connected their phone to that. Guest networks commonly have client isolation turned on, which blocks devices from communicating with each other even though they share the same SSID. I had a situation where three out of five players kept getting connection errors, and it turned out the host's phone was on the 5GHz band while the others were on 2.4GHz, and the router had AP isolation enabled between bands. Switching everything to the 2.4GHz band resolved it immediately.
If you are playing through Steam or a PC app, check your firewall settings. Windows Defender Firewall and third-party antivirus suites sometimes block the local discovery protocol that Jackbox uses. I encountered this with a player who had ESET installed. The game would load, the room code worked, but phone controllers would connect and then immediately disconnect. Turning off ESET's HTTP scan module fixed it without touching the firewall rules. If you do need to adjust firewall settings, allow both inbound and outbound traffic for the Jackbox host application on private networks only. Console players face a different set of issues. If you are using an Xbox or PlayStation, the console needs a stable connection to the internet for license verification, but the actual game communication between phone and console happens locally. Some routers use symmetric NAT or CGNAT, which can interfere. If players report that they can enter the room code but the game never recognizes their phone, try toggling the NAT type on the console to open. On Xbox this is done through network settings, and on PlayStation through connection test followed by port forwarding if needed. Port forwarding for Jackbox typically involves UDP ports 27000 through 27030, but the exact range can vary by game. Smart TV apps are the most unreliable way to play Jackbox, and I will be blunt about this. The Samsung Tizen and LG webOS versions of Jackbox apps have been problematic for years. They often fail to receive controller connections properly, and the UI is not designed for the fast-paced nature of most Jackbox games. If your TV is an older model or runs one of these platforms, consider casting from a phone or tablet instead. Chromecast, AirPlay, or even a simple HDMI cable will give you a dramatically more stable experience. I once watched a group struggle with a Samsung TV app for forty-five minutes before someone suggested just casting from a phone, and the game started working within two minutes of doing so.
Another common pitfall is browser-based play on the TV itself. Some people try to load jackbox.tv directly in a smart TV browser to act as the host screen. This rarely works well because smart TV browsers are slow, lack proper WebSocket support, and often crash under the load of multiple simultaneous connections. If you must use a TV without a console or PC, use a dedicated streaming device like a Fire Stick or Roku instead. These handle the browser workload much better and have been tested more thoroughly by the Jackbox team. Mobile devices themselves can cause issues. If a player's phone is in low power mode or has background app refresh disabled for the browser, the connection to the host can drop intermittently. This is especially common with iPhones on iOS 17 and later. Turn off low power mode for the duration of the game. Also make sure the browser being used is one of the supported ones. Chrome and Safari work reliably. Firefox on Android has had occasional issues with the WebRTC connections that Jackbox depends on. If a player is using Firefox, suggest they switch to Chrome or the Samsung Internet browser. Network congestion is another factor that people overlook. If ten phones are all connecting to the same router simultaneously while the host PC is also downloading a game update, the router's buffer can fill up and cause packet loss. This typically manifests as delayed or missing responses when players submit answers. Playing on a wired Ethernet connection for the host, if possible, eliminates this variable entirely. Wireless hosts are fine for small groups of two to four players, but once you get into larger parties, the difference becomes noticeable.
Get the Full Details
There is also the issue of router QoS settings. Some routers allow you to prioritize certain types of traffic, and if Jackbox's traffic is not recognized, it may get deprioritized in favor of video streaming or large downloads on other devices. Check your router's Quality of Service settings and make sure no other applications are monopolizing bandwidth during gameplay. Disabling QoS temporarily during a Jackbox session is often the quickest way to test whether it is the culprit. When all else fails, restart the router. Not just power cycle the modem or the console, but the actual router. DHCP lease renewals, NAT table resets, and DNS cache clears that happen during a full router reboot often resolve issues that no amount of individual device restarting will fix. This took me from about twenty minutes of troubleshooting down to about thirty seconds in multiple instances over the years. One last thing worth noting: Jackbox games do not have a built-in server infrastructure for matchmaking. Every session is peer-to-peer between the host and the players' phones. This means there is no central point of failure on Jackbox's side that you can blame, but it also means your local network environment is entirely responsible for connection quality. There is no cloud relay, no CDN, no fallback server. If your local network is the problem, the problem is your local network, and the solutions above are the actual solutions. Understanding this fundamentally changes how you approach any connection issue you encounter.
