Skip to content
Tools.Town
290+ free online tools

Real-world workflow

Use Case

Shuffle List as a Random Picker

Shuffle options and take the first line as the pick — or split into rounds.

14 August 2026 By Tools.Town Team 5 min read

The problem

You have a list of options and need one picked at random: which teammate presents first, which idea gets prototyped, which restaurant wins lunch, which comment gets the giveaway. Scrolling and “eeny-meeny” is not random, and spinning up a spreadsheet formula is overkill. A shuffle solves it directly — randomise the order once, then read from the top.

Who this is for

Anyone who needs a quick, defensible random choice: standup facilitators rotating who speaks, teachers cold-calling fairly, community managers running a light giveaway, or a team breaking a tie without arguing about method.

Before and after

Start with your candidates, one per line:

Priya
Marco
Ada
Wei
Sofia

After one shuffle you might get:

Wei
Sofia
Priya
Ada
Marco

Wei is the pick. Need three? Take the top three: Wei, Sofia, Priya.

Steps

  1. Open Shuffle List.
  2. Paste your options, one item per line. Random shuffle mode is already selected.
  3. Read the top line — that is your random pick.
  4. For several picks, take the top N lines instead of just the first.
  5. Copy the result if you want to paste it into chat, a doc, or a ticket as a record of what was drawn.

Running multiple rounds

If you want to process the whole list in fair, random batches — say, review submissions in random order across three sessions — shuffle first, then split. Take your shuffled output and paste it into Split List into Chunks with N set to your round size. Each chunk becomes one round, and because you shuffled before splitting, the batches are randomised rather than in whatever order the list arrived.

How to verify the result

A correct shuffle keeps every original item exactly once — nothing added, nothing dropped. Confirm the output line count matches the input line count. If the tool removed blank lines (it strips empties by default), the count can be lower by exactly the number of blank lines you pasted, which is expected. If you suspect the order is not changing, click re-shuffle before you commit and watch the top line move.

Edge cases and common mistakes

  • Duplicates stay duplicates. Shuffling does not dedupe. If the same name appears twice, it has two chances to be picked. Run Remove Duplicates from List first if each option should be unique.
  • Blank lines. Empty lines are removed by default, so they can not be “picked” as a silent winner.
  • Re-shuffling to fish for an outcome. Re-rolling until you like the top line is not random any more. For a genuine pick, shuffle once.
  • Weighting. A plain shuffle gives every line equal odds. If you need weighted chances (e.g. one entrant has five tickets), add that entrant on five lines before shuffling.

Weighting the odds fairly

A plain shuffle gives every line exactly equal odds, which is the point for a neutral pick. Sometimes you want unequal odds — a raffle where longer-tenured staff hold more tickets, or a giveaway where each qualifying action earns another entry. The simplest honest way to do this is to list each option once per “ticket” before shuffling. If Ada earns three entries and Marco earns one, Ada appears on three lines and Marco on one; after the shuffle, Ada is three times as likely to reach the top. Avoid trying to fake weighting by re-shuffling until a favoured name appears — that is not weighting, it is rigging.

Making the pick auditable

For anything others will care about, capture the outcome so it can be checked. Run the shuffle on a shared screen, then copy the shuffled list into the channel or doc where the decision lives. Because a shuffle is lossless, anyone can see that every candidate was present and that the winner sat at the top of a single draw — not cherry-picked from several attempts.

Privacy and scope caveats

Shuffle List is client-side, so your list never leaves the browser. But be honest about the randomness: it is Math.random-based (pseudo-random), suitable for internal, casual, and low-stakes picks. It is not appropriate for security-sensitive lotteries or anything with legal or monetary stakes, where a verifiable, cryptographically secure or independently audited draw is required.

Frequently Asked Questions

How do I turn a shuffle into a single pick?

Shuffle the whole list once, then read the top line. Because every item had an equal chance of landing first, the first line is your random pick — no separate 'pick one' step needed.

Can I pick more than one winner?

Yes. After a single shuffle, take the top N lines. That gives you N distinct picks without repeats, which is what you usually want for 'pick 3 names'.

Is the shuffle truly random?

It uses a Fisher-Yates shuffle driven by Math.random, which is pseudo-random. That is fine for casual picks and internal draws, but it is not cryptographically secure.

Should I keep re-shuffling until I like the result?

For a fun or low-stakes pick, re-shuffling is harmless. For anything that decides a winner, re-shuffling after you have seen the outcome quietly biases the result — shuffle once and commit.

Does my list get uploaded?

No. Shuffle List runs in your browser, so your entries stay on your device.