Split names into random teams
Drop in your roster, pick the number of teams, and get an even split with cryptographic randomness. Re-shuffle as many times as you want until the lineup feels right.
- Eve
- Grace
- David
- Bob
- Carol
- Frank
- Alice
- Henry
How to make teams
The picker shuffles names with crypto randomness, then deals them round-robin into N team buckets — so sizes are as balanced as integer math allows.
- 01
Paste roster
One name per line — blank lines are ignored.
Inputs are treated as UTF-8 throughout the pipeline and validated client-side as you type — nothing dispatches until the value is well-formed.
inpututf-8client-sidevalidatedinput · textnames · setAlice Bob Carol Dave
loaded · parsedclient-side - 02
Pick team count
Slide between 2 and 10. The split is even within ±1.
Each toggle re-computes through a memoised hook, so flipping options never resets your input and the UI stays snappy on large inputs.
countoptionslivememoisedtogglesteams · memoised2 · livesplit into 2
options set · memoisedlive - 03
Shuffle
Crypto random shuffles the order; round-robin deal balances sizes.
Randomness — where used — comes from
crypto.getRandomValues, neverMath.random. Heavy work sits inuseMemo.shufflecomputeinstantlocaldeterministicshuffle · instanteven · computedA · C → Red B · D → Blue
computed · instantinstant - 04
Re-shuffle or copy
Don't like the lineup? Shuffle again. Copy or download the text summary.
Copy writes through
navigator.clipboardand downloads use aBlob— zero network traffic. Same input plus same options always yield the same bytes.exportcopydownloadzero-networkreproducibleok · copiedready · copiedCopied
shipped · ready to shipsuccess
Pro tips for everyday utilities
Reach for crypto.getRandomValues
Cryptographically random for IDs, tokens, salts. Math.random is for animation and games, not security.
Mock data with seeds
Faker-style libraries can be seeded so tests are reproducible. Embed the seed in the fixture file.
Reference cards beat memory
Cheatsheets for Vim, Git, Docker, Linux signals are faster than man pages when you’re mid-flow.
Browser APIs vary
Touch events, gamepads, and clipboard differ across vendors. Feature-detect before use.
Persist in the right place
localStorage for user preferences, sessionStorage for transient state, IndexedDB for structured data.
When to pick teams
Sports, classrooms, hackathons, retros.
Pickup games
Fair team draft without playground politics. Random values come from crypto.getRandomValues — cryptographically secure for tokens, salts, and session IDs. Math.random is deterministic enough for animations but predictable enough to be a security bug.
CSPRNG-backedClassroom groups
Project teams chosen without picking favorites. Pair with hashids, ULID, or UUID v7 when you need both random and sortable — useful for primary keys, public-facing IDs, and event log ordering without a sequence column.
reproducibleHackathons
Mix attendees into balanced project squads. Output is deterministic given the same seed, so fixtures and tests stay reproducible across CI runs and contributor machines. Embed the seed in the fixture file for full replay.
snappyCode reviews
Rotate reviewers across sprints randomly. Heavy work runs through useMemo so the UI stays snappy on large inputs. Same input + same options yields identical bytes — the kind of stability snapshot tests rely on.
feature-detectedRetros
Random breakout pairs for retrospectives. Storage tools persist to the right backend: localStorage for user preferences, sessionStorage for transient state, IndexedDB for structured data. Pick the right shelf and quota worries disappear.
deterministicTravel groups
Split a tour into shuttle vans by chance. Browser feature detection: clipboard, fullscreen, gamepad, and Web Bluetooth APIs gracefully fall back when unavailable. No surprise white screens on Safari or older Firefox.
production-readyFrequently asked questions
Something missing?
Tell us what you need. We ship the top requests every two weeks.