You type in the code. You hit join. Nothing happens, or the error just stares back at you.
A Blooket code stops working for a handful of specific reasons: the game lobby is no longer open, the code was misread or mistyped, the host has not yet made the session joinable, the lobby reached its player cap, or a browser issue is blocking the request. Every one of those causes has a direct fix. This guide covers all of them, for students trying to join and for teachers whose students cannot get in.
Why is your Blooket code not working?
A Blooket code fails for one of five reasons: the game ended or was closed, the code was entered incorrectly, the host has not yet opened the lobby, the session reached its player limit, or a browser or network issue is preventing the join request from going through.
The game ended or the host closed the lobby
Blooket game codes are only active while the host’s lobby is open. Once a teacher ends the game or closes the browser tab, the code becomes invalid immediately. Students who try to join after that point will always get an error, even with a perfectly correct code.
This is the single most common cause. If the code was shared more than a few minutes ago, the game may simply be over.
The code was entered incorrectly
Blooket join codes are six-digit numbers. When a code is shared on a whiteboard, slide, or in a chat message, digits get misread. The most frequent source of confusion is the number 0 (zero) looking like the letter O, or the number 1 looking like a lowercase l or capital I.
Check the code character by character before concluding something is broken.
The host has not opened the lobby yet
Teachers often copy the code from the game setup screen and share it while they are still choosing a mode or adjusting settings. The lobby is not joinable until the host actively opens it. Students who try too early hit an error even with the correct code.
Waiting 60 seconds and trying again usually resolves this specific situation.
The session is at capacity
Blooket lobbies have a player limit. Free accounts support a certain number of concurrent players, and Blooket Plus raises that cap. If the lobby is already full when a student tries to join, the request is rejected. The fix here sits on the teacher’s side, not the student’s.
A browser or network issue is blocking the join
School networks sometimes filter the WebSocket connections Blooket uses to process join requests. An outdated browser or a conflicting extension can also stop the join page from communicating with Blooket’s servers correctly. If the same browser is also blocking you from signing in, this Blooket login issues fix troubleshooting guide is the right next step.
How to fix a Blooket code that is not working
Work through these steps from the top. The first two steps solve the problem for most students.
Step 1: Read the code again, digit by digit
Before changing any settings, look at the code one more time. Blooket codes are always six numeric digits. If the code came from a whiteboard photo, a slide, or a typed message, check whether any digit could be misread. Common errors are 0 versus O, 1 versus l, and 6 versus b in handwritten versions.
Type slowly, confirm each digit, then submit again.
Step 2: Confirm the game is still open
Ask the teacher directly whether the lobby is still accepting players. In class, this takes five seconds. If you are joining remotely, check whether the code was shared recently or whether the session may have already finished.
A code shared more than five minutes ago may belong to a game that is already in progress or done.
Step 3: Refresh the join page and enter the code fresh
Go to blooket.com/join, reload the page fully with Ctrl+R (Windows) or Cmd+R (Mac), and type the code again from scratch. Do not re-enter the code in a tab that has been sitting open for several minutes. A fresh page ensures the join request goes through cleanly.
This step resolves issues caused by stalled page loads and disconnected browser sessions.
Step 4: Clear your browser cache
A corrupted cache can cause Blooket’s join page to fail silently. Open browser settings, clear cached images and cookies, then try joining again. This takes under two minutes and rules out stored data conflicts as the cause.
If clearing cache does not help, move to the next step.
Step 5: Switch to Chrome or Edge
Blooket is built and tested on Chromium-based browsers. Chrome and Edge produce the fewest join errors. Firefox works acceptably. Safari on older Macs and iOS can interfere with Blooket’s real-time connection requests. For a deeper comparison that covers performance, audio, and privacy across every option, see this guide on the best browser for Blooket.
Switching browsers takes less than a minute and immediately rules out your current browser as the problem.
Step 6: Check your internet connection
Load another website quickly. If other pages are slow or failing, the issue is your connection, not the Blooket code. Reconnect to Wi-Fi, move closer to the router, or switch from a mobile hotspot to a proper network. If the connection holds long enough to join but keeps dropping mid-game, this Blooket disconnect problems complete fix guide covers what to try next.
Blooket join requests need a stable connection. A brief dropout at the wrong moment produces an error that looks identical to an invalid code message.
Step 7: Disable browser extensions temporarily
Ad blockers, VPN extensions, and content filters can intercept Blooket’s join requests and block them. Disable all extensions, reload blooket.com/join, and try the code again. If it works, re-enable extensions one by one to find the culprit.
Extensions are managed in Chrome at chrome://extensions.
Blooket code fixes for teachers when students cannot join
When students report a code is not working, the problem is almost always resolvable from the host side.
How to check whether your lobby is still joinable
While hosting, your game dashboard shows whether the lobby is in the waiting room or already running. If you have already started the game, most modes do not allow new players to join mid-session. Classic is more forgiving than Tower Defense in this regard.
If the game is still in the waiting room, confirm the code shown on your screen matches what you shared with students exactly.
What to do when students cannot join despite a correct code
If multiple students report the same error simultaneously, one of three things is happening: the player cap was reached, the lobby moved out of the waiting room, or a school network filter is blocking Blooket’s join endpoint.
For the first two, close the current game and reopen a fresh lobby with a new code. For a network filter, your IT administrator will need to whitelist Blooket’s connection endpoints.
Code error types and what each one means
The table below maps common Blooket join errors to their most likely cause and the fastest fix:
| Error or symptom | Most likely cause | Fix |
|---|---|---|
| “Game not found” | Game ended or lobby closed | Teacher reopens a fresh lobby |
| “Invalid code” | Typo or wrong code entered | Re-read and retype the code |
| Page loads but join fails silently | Browser or network issue | Clear cache, switch browser, check Wi-Fi |
| Join works but student is stuck loading | Device or bandwidth issue | Refresh, close other tabs, rejoin |
| “Lobby is full” | Player cap reached | Teacher raises limit or splits the class |
| Student joined then disconnected | Connection dropped | Rejoin with the same code while lobby is open |
Mistakes that cause Blooket codes to fail
These are the errors that come up most often and are completely avoidable once you know them.
Sharing the code before the lobby is open
Teachers frequently copy the code from the game setup screen and share it before clicking to open the lobby for joining. Students who attempt to join during that setup window see an error. The fix is to only share the code after the lobby is in the waiting room and actively accepting players.
If students are already in the room or on a call, tell them to wait for a verbal or written “join now” before entering the code.
Confusing digits when sharing by hand
Because Blooket codes are six numeric digits, handwritten or photographed codes create misreading opportunities. 0 looks like O, 1 looks like l or I, and 6 can look like b in some handwriting styles. Sharing codes digitally in typed form, directly in a chat message or as text on a slide, eliminates this problem entirely.
Writing a code on a whiteboard for a class of 30 students guarantees at least a few will read a digit wrong.
Using a code from a previous game session
Blooket generates a new code every time a lobby is opened. A code from a previous lesson will not work for a new session. Students who saved a code from last week’s review game need the fresh one for today.
Remind students not to save or bookmark game codes since they change with every session.
Joining from the wrong URL
Some students search “Blooket join” and land on unofficial or outdated pages that imitate the real join interface. The only correct join page is blooket.com/join. Any other URL will not process a valid code correctly. Bookmark blooket.com/join or type it manually to avoid this entirely.
Not noticing the lobby cap was hit
When a lobby fills up, later join attempts fail with an error that looks exactly like an invalid code message. Teachers may not notice the cap was reached, particularly in large classes. Check the player count in the lobby dashboard. If the limit is set lower than your class size, raise it before the game starts.
FAQs
Why does Blooket say “game not found” when I have the right code?
This error almost always means the game lobby ended or was closed by the teacher. The code is only valid while the lobby is open. Ask your teacher to reopen a fresh session and share the new code. If the game is finished, you will need to wait for the next one.
Can a Blooket code expire?
Yes. A Blooket code is only active for the duration of that specific lobby. Once the host ends the game or closes the browser tab, the code becomes permanently invalid. There is no time limit on joining while the lobby remains open, but the code has no use after the session ends.
Why can I load the join page but the code still fails?
The page loading and the join request are separate things. Your browser can reach Blooket’s website while a school firewall or browser extension blocks the real-time connection used to process the join. Clear your cache, disable extensions, and try Chrome or Edge. If the problem persists at school, it is likely a network filter.
What should a teacher do if every student gets the same code error at once?
If all students fail simultaneously, either the lobby closed, the player cap was hit, or Blooket’s servers are having a temporary issue. Close the current game, open a fresh lobby, and share the new code. If the problem continues for all students across different devices, check Blooket’s official channels for any reported outage.
Can duplicate player names cause a join error?
No. Blooket allows multiple players to use the same nickname in the same game. Name duplication does not cause join failures, though it creates confusion on the leaderboard. Join errors are always caused by connection, code, or lobby status issues rather than player names.
Does Blooket Plus give more stable or longer-lasting codes?
No. Blooket Plus is a paid subscription that adds gameplay and cosmetic features. It does not change how game codes are generated or how long they stay active. Code behavior is identical regardless of subscription tier.
Why does the join page keep reloading without letting me in?
A looping join page is almost always a browser cache or session issue. Close the tab entirely, open a fresh one, go to blooket.com/join manually, and enter the code again. If the loop continues, restart the browser completely before trying once more.
Conclusion
A Blooket code not working almost always comes down to one of four things: the game ended, the code has a typo, the lobby was not yet open when students tried to join, or a browser issue blocked the request. Checking the code digit by digit, refreshing the join page, and clearing the browser cache resolves the vast majority of cases.
For teachers, the fastest fix mid-class is closing the current session and reopening a fresh lobby with a new code, rather than troubleshooting the old one while 30 students wait. Students should bookmark blooket.com/join directly and always use a typed code rather than a handwritten one.
If the steps above do not resolve the issue, a school network filter is the remaining likely cause, and your IT team is the right next call.
Move from curious to confident with our step-by-step success framework.
