b2KIT

Team Randomizer

Randomly split a list of players into balanced teams for sports, games, or group work.

Tested tool guide Tested browser tools Checked August 16, 2026

What Team Randomizer does, with a checked example

Type or paste a roster - players for a game, coworkers for a project - choose how many teams you want, and the tool deals everyone into teams of equal size with a fresh random draw on every click. The split is unbiased: no captain's picks, no alphabetical clustering, no friend groups voting themselves together. The thing people most often get wrong: random does not mean fair-looking. The tool guarantees team sizes balance, but the same two stars can still land on one team by chance, and rerunning is the correct response, not a sign that anything is broken.

Worked example

A concrete input and expected output from the current implementation.

Input

Maya, Leo, Ada, Kai, Zoe, Sam, Ivy, Max, Ana, Ben, Eli, Nia

Expected output

Team 1 (4): Maya, Leo, Ada, Kai
Team 2 (4): Zoe, Sam, Ivy, Max
Team 3 (4): Ana, Ben, Eli, Nia

Twelve players split into three teams forces teams of exactly four, because 12 / 3 = 4 with nothing left over. The arrangement shown is one of 5,775 equally likely layouts (12! / (4!^3 x 3!)), so any draw that keeps four players per team is a correct result, and the names will usually land differently when you run it.

How the result is produced

1

How the draw works

On each click, the tool reorders your full list so that every arrangement of the names is equally likely, then assigns them to the number of teams you requested. Because the draw is fresh every time, rerunning almost always changes the split, and the order in which you typed the players has no influence on who ends up together.

2

Leftovers and team size

Team sizes are fixed by arithmetic before anyone is named. When the count does not divide evenly, teams differ by at most one member: eleven players across three teams is always 4-4-3, with the extra player going to one team. The randomness decides who sits where, never how many sit on each team.

Good uses

  • A coach pastes the 14 names from a pickup-basketball sign-up sheet and gets two even sides for the scrimmage, with no captain picking last.
  • Planning pub quiz night for the office: 16 coworkers become 4 teams of 4 in one click, so friend groups do not silently cluster into stacked teams.
  • A teacher assigns group projects: 28 students split into 7 groups of 4, giving a defensible, unbiased grouping and skipping the usual 'who is left over' negotiation.

Limits and checks

  • A fair draw can still look unfair. The same two strongest players can land on one team, and a pairing you wanted separated can recur; both are normal outcomes of independent draws. Rerun for a fresh chance rather than reading intent into the result.
  • Balanced means equal headcount, not equal strength. The tool evens the number per team but has no information about anyone's skill, so a numerically even game can still be one-sided. If competitive balance matters, sort players yourself before running.
  • Small rosters leave little room for randomness. With four players and three teams the result must be 2-1-1, and the order of names within a team is arbitrary - the first name listed is not its captain or best player.

Common questions

Why did the same two friends end up on the same team again after I reran?

Coincidence, not a bug. Each run is an independent draw that does not remember previous runs, so no pairing is ever excluded in advance. With small rosters the chance is higher than people expect: with 12 players in three teams of 4 there are 5,775 possible layouts, so any specific repeat is a 1-in-5,775 event per rerun. Rerun, or move one player manually.

Can I make the randomizer spread my best players across different teams?

The names you enter carry no skill information, so the tool balances team size and leaves strength to chance. The reliable way to get skill-spread teams is to rank players yourself and assign them alternately in snake order - strongest to team A, second to team B, and so on - or rerun until a layout looks competitive.

References and verification

The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.

Related Tools