Random Pair Generator

Paste names or items, generate randomized pairs, and leave one unpaired item when the list size is odd.

Names / items — one per line

Random/decision tools run locally. Secure tools use browser Web Crypto randomness and rejection sampling; the seeded generator is deliberately deterministic and is labeled separately.

No-repeat round-robin pairing audit

Generate deterministic rounds from the current participant list, handle a bye and prove duplicate-pair coverage.

Pairing evidence

Round to preview

Round	Pair A	Pair B

Core random, wheel & group workflows

Use the broad picker, number, wheel, name, team or dice workflow first. Move to a specialist only when the probability model or output structure genuinely changes.

All 35 random tools

Random Number GeneratorSecure integer draws & unique mode Random PickerPick names or items from a list Spin the WheelVisual choice wheel & winner history Random Name GeneratorGenerate names in local batches Random Team GeneratorSplit a roster into teams Dice RollerCustom dice count & sides Yes or No WheelBinary decision with visible odds Weighted WheelCustom non-negative probability weights

Fairness and randomness boundaries

Random selection can make equal-probability choices from the entered pool, but it cannot prove that the input list itself is appropriate or unbiased. Visual wheel/dice animations are presentation only. Seeded tools remain reproducible pseudo-random workflows rather than cryptographic randomness, and rating-balanced teams use a transparent heuristic rather than an optimal or human-judgment model.

Pairs are without replacement

Each entered row is shuffled once into pairs. With an odd number of rows exactly one row remains unpaired; duplicate visible names are still separate rows unless cleaned first.

Practical guide and verification

Decide whether one draw or a full schedule is the goal

A one-time random pairing only needs an unbiased shuffle, while repeated rounds need memory of earlier pairs to reduce repeats. Use the round-robin audit when fairness over many sessions matters rather than judging one random draw.

Odd participant counts require a visible policy

With an odd list, one participant must receive a bye or join a group of three. Decide the rule before generating rounds and rotate the exception over time so one person is not repeatedly left unmatched.

Duplicates should represent real separate participants only

Two identical names are ambiguous in a pairing list. Add initials or identifiers if they are different people; otherwise remove accidental duplicates so the generator does not create a meaningless same-name pair.

Random order does not guarantee social or skill balance

A fair shuffle ignores experience, conflicts, accessibility needs and team history unless those constraints are explicitly modeled. Use random pairs when randomness is the objective, then review practical constraints before publishing assignments.

Keep the schedule evidence for repeated rounds

Export or copy the generated schedule when avoiding repeats matters. Comparing later rounds with the recorded pair history is more reliable than trying to remember previous combinations or regenerating until a preferred outcome appears.