Bloket Code: Complete Guide to Game Codes on Blooket

A Bloket code is the small string of digits that turns a hosted game into something students can actually join. Everything else on the platform, the modes, the blooks, the reports, all sit behind this one number. Get the code wrong and the game does not exist for the player trying to reach it.

This guide covers what a Bloket code actually is, where to find it as a host, how to enter it as a player, why codes fail, and the small tricks experienced teachers use to keep the code-sharing part of a class session smooth. It also covers class codes, which are different from game codes and cause a fair amount of confusion when people mix them up.

Codes are short, single-use, and case-insensitive. That combination makes them fast to share out loud but also easy to type wrong.

What a Bloket code actually is

A Bloket code is a short numeric identifier, usually six or seven digits, that connects a live game host to the players joining the game. The host generates the code the moment they launch a game, and players type it on the join page at play.blooket.com to enter the same session.

Codes are session-specific. Each hosted game has its own code, generated fresh at launch. When the game ends, the code retires and no longer works for any new join attempts.

Class codes are not the same as game codes

This is the single biggest source of confusion around Bloket codes. Class codes and game codes are two different things and serve two different purposes.

A game code is temporary and lets students join one specific live game. Once the game ends, the code is dead. A class code is permanent and lets students join a teacher’s Blooket class, which is a longer-term grouping for tracking performance across many games.

Students who type a class code into the game join page get an error. Students who type a game code into the class join screen also get an error. Knowing which one is being asked for is the first check on any code problem.

Why the codes are short and numeric

The short numeric format is intentional. Long alphanumeric codes would be harder to type on the phones and Chromebooks students use in class, and they would slow down every session.

Numeric codes also work well when read out loud, which teachers do when the projector is off or the class does not have a shared screen. A six or seven digit number is easy to say and easy to type.

The trade-off is that similar-looking digits sometimes cause errors. A one and a lowercase L look alike in some fonts, though Blooket codes are pure numbers, which sidesteps most character-confusion problems.

How to get a Bloket code as a host

The Bloket code appears automatically the moment a host launches a game. The host does not need to configure it, generate it, or copy it manually. Blooket handles the code creation and displays it prominently.

The steps below cover the standard flow from picking a set to seeing the code on the host screen.

Launching a game and finding the code

The full flow from dashboard to visible code takes about thirty seconds on a normal connection.

1. Sign into blooket.com and open the dashboard.
2. Click the question set to host.
3. Click the Host button on the set’s action bar.
4. Pick a mode from the list.
5. Configure the mode settings, if the mode has any.
6. Click Start on the settings screen to launch the game.
7. Read the game code at the top of the host screen.

The code stays visible on the host screen for the whole lobby period. Players joining will need to see or hear it clearly.

Some modes show the code alongside a QR code that students can scan on a phone. This works well when students are on phones anyway, though it adds no benefit for students on laptops.

Sharing the code with a live class

Getting thirty students to type the same code correctly is where classroom management meets tech. A few approaches work well.

Projecting the host screen on a shared display is the fastest and most reliable. Every student sees the same code from every seat, and no one has to remember it while typing. The code stays visible for the whole join window.

Reading the code out loud works when a projector is not available. Reading the digits in pairs is easier for students to type correctly than reading each digit one at a time.

Writing the code on a whiteboard is the middle option. It stays visible for a longer time than a spoken code and does not need a projector.

Sharing the code for remote or hybrid classes

For classes that mix in-person and remote students, dropping the code or the join link into a class chat is the fastest option. Most learning management systems support pasting links directly into announcements or chats.

Some hosts share a full join URL with the code already appended, which lets students click through instead of typing. This form of link looks something like play.blooket.com/play with a game ID parameter, and it takes remote students directly to the nickname entry step.

Sharing the code by email works too but adds delay because students need to check their inbox. For a live session this is slower than a chat drop.

How Bloket codes work under the hood

The Bloket code is the identifier that links a host session to the players connecting to it. When a player types the code, Blooket looks up the matching live game and puts the player in the correct lobby.

The mechanics below are useful to understand for teachers and students who have run into confusing code behavior.

Code generation and length

Each code is generated at game launch time and is unique across every active game on the platform. The length is usually six or seven digits, which gives enough combinations that the same code is not reused across two active sessions.

The generation is instant. There is no delay between clicking Start and seeing the code. Teachers who have run games where the code took a moment to appear were likely on a slow network, not waiting for code creation.

Codes are not memorable on purpose. A random number keeps students from guessing codes and jumping into games they were not invited to.

Code expiration

Codes stay valid for as long as the host game session is active. The moment the host ends the game or closes the game window, the code expires.

Some modes have a rolling join window that closes at a certain point in the game. In those modes, the code stops accepting new players after the join window closes, even though the game itself is still running.

Expired codes show a clear “code not found” or “game not found” message on the join page. Students who see this message need a fresh code from the host, not troubleshooting on their own device.

What happens when a wrong code is entered

Typing a wrong code that does not match any active game shows a “no game found” error. The player stays on the join page and can try again.

Typing a code that matches an active but full game shows a different error, usually a “game is full” message. Blooket has generous player limits per game, so this is rare in a normal class setting.

Typing a code that matches a game the host has locked shows a “game locked” message. Some hosts lock a game after a certain number of players join, which prevents late arrivals.

The role of the join URL

The join URL, play.blooket.com, is where the code entry happens. The URL itself does not carry the code by default. Players need to type or paste the code after loading the page.

Some hosts share a URL with the code embedded as a parameter. This form of link takes the player past the code entry step and directly into the nickname entry. It saves a few seconds of typing per player.

Blooket does not require the embedded-code URL. The plain join page with a manual code entry works exactly the same way.

Case sensitivity and formatting

Since Blooket game codes are numeric, case sensitivity does not apply in the standard flow. There are no letters that could be entered in the wrong case.

Spaces are stripped automatically. Some students paste a code with a leading or trailing space from a chat message, which used to cause errors in older versions of the join page but now gets cleaned up before the lookup.

Dashes and other separators are not supported. Some hosts write the code with a dash in the middle for readability, like “123-4567,” but students should type only the digits.

How multiple codes can exist at once

A teacher hosting one game has one code. A teacher hosting two games in two different browser tabs would have two codes, one for each. Blooket supports multiple simultaneous hosted games on the same account.

This matters for teachers running back-to-back class sessions with different periods. Instead of ending the game between periods, some teachers keep the same game open and share the same code with each period. This is a valid approach, though it mixes the reports across periods.

For most classroom setups, one game code at a time is enough. Running multiple concurrent games from the same account is a niche use case.

Using Bloket codes on different devices

The Bloket code entry works the same way on any device. What changes is the input method and the small details around screen size.

The overview below covers the practical differences between device types.

Codes on laptops and desktops

Typing a code on a full keyboard is fastest. The code field on the join page accepts input directly, so no click is needed before typing.

Copying and pasting a code from a chat message also works cleanly on laptops. This is how most remote students get into a game when the host shares the code in a class chat.

Enter or the arrow button on the field submits the code. Both work the same way, and there is no submit-on-blur behavior that would let a player accidentally leave the field with a partial code.

Codes on phones

Phones use an on-screen keyboard for code entry. Because Blooket sets the code field to numeric input, the keyboard opens in number mode by default, which speeds up typing.

Autofill does not usually work for game codes because each code is single-use and never repeats. Copy-paste from a chat message is still the fastest way to enter a code on a phone.

Very long codes are rare, but a fumbled tap on a small screen is not. Reading the entered code back before hitting Enter catches typos.

Codes on tablets

Tablets sit between phones and laptops. The larger screen makes the on-screen keyboard easier to use, and the code field is bigger and easier to tap into.

Split-screen mode helps for students who want to keep the class chat visible while typing the code. This works especially well for hybrid classes where the code arrives in a message.

Codes on Chromebooks

Chromebooks handle code entry the same as any other Chrome browser. Speed and reliability match a desktop experience.

School Chromebooks with content filtering sometimes block the play.blooket.com URL, which stops the code entry from happening at all. If the code page does not load, the network is the problem, not the code itself.

Common Bloket code problems and how to fix them

Most Bloket code errors come from six recurring issues. Each has a fix that takes under a minute.

The list below covers what actually goes wrong, in rough order of frequency.

The code is expired

The most common code problem by far. A code from an earlier session almost never works for a new game.

The fix is to get a fresh code from the host. Codes stop working the moment the previous game ends, which is faster than most students expect. A code shared five minutes ago may already be dead.

Students who bookmark a join URL with a code baked in run into this a lot. The bookmark works for one session and then becomes useless.

The code has a typo

Typos happen when reading a projected code, especially in low light or from the back of the room. Digits like six and eight, or three and eight, look similar at a distance.

The fix is to double-check the entered code against the source. Reading the code back before hitting Enter takes two seconds and catches most typos.

For classes with recurring typo problems, sharing the code in a chat or making the projector text larger both help.

The code page will not load

If play.blooket.com does not open, the code cannot be typed at all. This is usually a school network filter blocking the domain.

The fix has to come from the school IT team. Whitelisting blooket.com and play.blooket.com solves it for good. Trying to work around the filter is against most school acceptable-use policies and does not fix the underlying block.

The code works but no game loads

Typing the correct code and getting no game screen usually means the host has not started the round yet, or the player was placed in the lobby and just needs to wait.

Waiting on the lobby screen is normal until the host clicks Start. If the wait extends past a couple of minutes, the host may have stepped away or opened a settings panel by accident.

Refreshing the lobby page sometimes drops the player out and requires a fresh join. Waiting is usually better than refreshing.

The code is being confused with a class code

Students who join a Blooket class using a class code sometimes try that same code as a game code later. It does not work, and the error is confusing because the code did work for something else.

Class codes join a class roster. Game codes join a live game. Two different codes for two different purposes. Teachers who use both types can help by labeling them clearly when shared.

Multiple codes on screen at once

Some teachers show a game code and a class code on the same slide during a class. Students glancing at the wrong one is a common source of “code not working” errors.

The fix on the teacher side is to only show the currently active code. Keeping unused codes off the projector during a live session removes the confusion.

The code entered is for a different platform

Some students confuse Blooket codes with codes from other platforms like Kahoot, Quizizz, or Gimkit. Every quiz platform has its own code format and its own join page, and codes are not portable between them.

If a code that came from a teacher is not working on play.blooket.com, checking whether the code is for a different platform is a fast diagnostic. A quick look at the last game the teacher ran usually clarifies it.

For teachers who switch between multiple platforms, being explicit about which platform a code belongs to when sharing it prevents this confusion.

The code was truncated or partially copied

Codes copied from messages sometimes lose a digit or two if the selection was made in a rush. A five-digit fragment of a six-digit code fails the lookup with the same error as a totally wrong code.

Comparing the entered code length to the expected code length catches this. Blooket codes are consistently six or seven digits, so anything shorter is a red flag.

Recopying the full code from the source message is the fix. On phones, tapping and holding to select the whole code without missing digits works better than trying to swipe-select.

Best practices for using Bloket codes in class

A few habits make the code-sharing part of a Bloket session smoother for everyone. Most take almost no time to set up.

The tips below come from patterns across experienced teacher workflows.

Show the code clearly during the join window

The code needs to be readable from every seat in the room. If the projector is small or dim, increasing the font size on the host device before starting the game helps.

Some teachers use browser zoom to make the host screen bigger. Ctrl+plus in most browsers zooms the interface, which makes the code more visible without changing the game itself.

Reading the code out loud once at the start of the join window catches students who cannot see the projector clearly.

Set a clear join deadline

The two minutes between the code appearing and the game starting can drag out without a time boundary. Setting a verbal deadline like “code is up, you have one minute to join” gives the class a clear window.

Deadlines also help identify which students consistently join late, which can point to a device or attention problem that is worth addressing separately.

Use the join link for hybrid classes

For classes with remote students, sharing the full join link in a chat is faster than sharing the code and asking students to type it. Remote students click through and are on the nickname screen without any typing.

The link also removes the risk of typos, which are more common in remote setups because the projector is not visible.

Comparison of code sharing methods

Most experienced teachers combine two of these. Projecting the code plus reading it out loud catches students who might miss one channel.

Rotate the code between periods for tracked classes

Teachers who use Blooket classes to track student performance benefit from ending the game between periods and starting a fresh one. The fresh code and fresh game keeps the reports separate for each class period.

Reusing one game across three class periods mixes all the data into one report, which makes it harder to analyze one class at a time. A quick relaunch between periods takes ten seconds and keeps the data clean.

Lock the game after the join window closes

Some modes support locking the game after a certain point, which prevents late arrivals from disrupting the round. Enabling the lock once every expected student is in keeps the session focused.

Locking also prevents random joiners in the rare case a code gets shared outside the intended class. Public code sharing is uncommon for classroom games, but the lock exists for the few times it happens.

Save the join link for repeat sessions

Teachers who host the same set for multiple sections in a day can save the host game and reuse the join link. The dashboard remembers recently hosted games and offers a quick relaunch option.

This is faster than clicking through the full host flow every period. The relaunch generates a fresh code and a fresh session, but keeps the mode and settings from the last launch.

Practice the code flow with a new class early

For a class that has not used Blooket before, running one throwaway session just to walk through the code flow saves confusion in every future session. A five-minute practice game on an easy topic gets every student through the code entry step at least once.

The practice run also catches devices that have network issues or filter problems. Discovering that three students cannot reach play.blooket.com is much better in a practice session than during a graded review.

For teachers new to hosting themselves, the same practice run is useful for building comfort with the host controls before doing it in front of a class.

Keep a code cheat sheet handy

Some experienced teachers keep a quick reference of the join URL, a sample code format, and the top three code errors printed near the classroom computer. When a student runs into a problem, the reference solves it in under a minute.

The cheat sheet works even better when it lives on the same wall as the classroom rules. Students can check it themselves without asking the teacher, which frees up class time.

FAQs

How long is a Bloket code?

Bloket codes are usually six or seven digits long. The length gives enough combinations that no two active games share a code at the same time. The short format is intentional so students can type the code quickly during the join window.

Where do I enter a Bloket code?

Codes are entered on the join page at play.blooket.com. The page opens straight to a code entry field with no menus in the way. The main blooket.com URL also works but adds an extra click. Bookmarking the direct URL saves time on every future session.

Why is my Bloket code not working?

The three most common causes are an expired code, a typo, and confusing a class code with a game code. Getting a fresh code from the host, reading it back character by character, and confirming the code type all fix the problem in most cases.

Can Bloket codes be reused?

No. Each code is single-use and expires when the game ends. A code from an earlier session cannot start or join a new game. The host generates a fresh code every time they launch a new game.

Do Bloket codes have letters?

Standard Blooket game codes are pure numbers. This makes them easier to type and read out loud than mixed alphanumeric codes would be. Class codes are separate and can look different, but the game code that students enter to join a live game is always numeric.

Can I share a Bloket code by link?

Yes. Blooket supports join links with the code embedded as a parameter. These links take students directly to the nickname entry step, past the code typing. This is the fastest way to share a code with remote students.

Are Bloket codes safe to share?

Sharing a code with intended players is safe. Sharing a code publicly on social media is not recommended because random people can join the game, disrupt the session, and use inappropriate nicknames. For class games, sharing the code only in the class environment keeps the game controlled.

What is the difference between a Bloket code and a class code?

A game code joins one live game and expires when the game ends. A class code joins a persistent Blooket class roster and stays active until the teacher archives the class. Both are used through Blooket, but they serve different purposes and go into different join fields.

Wrapping up the Bloket code basics

The Bloket code is the smallest but most important part of a live game session. Codes are short, single-use, and expire the moment the host ends the game. Class codes are different from game codes and cause most of the confusion in this space.

The one action to take now: bookmark play.blooket.com in the browser used most often for Blooket. That single bookmark cuts every future code-entry to a click and typing.

For a walkthrough of the full join process from code entry to gameplay, the join guide on this site covers every step in more detail.

Find your next great click inside our top picks—handpicked gems you’ll actually enjoy.