Get a quick yes or no
Ask any question, hit Decide, and let chance break the tie. The result is drawn from cryptographic randomness in your browser.
Type the question for context — only you see it. Hit Decide to roll a 50/50 outcome.
How to break a tie
When two options look the same on paper, sometimes a coin flip is the most honest answer. This tool gives a deterministic 50/50 verdict from cryptographic randomness.
- 01
Type the question
The text stays local — it just frames the decision for you.
Inputs are treated as UTF-8 throughout the pipeline and validated client-side as you type — nothing dispatches until the value is well-formed.
questioninpututf-8client-sidevalidatedinput · texttext · setShip on Friday?
loaded · parsedclient-side - 02
Hit decide
The button rolls a single random bit and reveals YES or NO.
Each toggle re-computes through a memoised hook, so flipping options never resets your input and the UI stays snappy on large inputs.
rolloptionslivememoisedtogglesroll · memoisedbit · live1 → YES
options set · memoisedlive - 03
Read the verdict
Green YES or red NO appears beneath the question.
Randomness — where used — comes from
crypto.getRandomValues, neverMath.random. Heavy work sits inuseMemo.verdictcomputeinstantlocaldeterministicout · instantyes/no · computedYES
computed · instantinstant - 04
Roll again
Tap Decide as many times as you need — every roll is independent.
Copy writes through
navigator.clipboardand downloads use aBlob— zero network traffic. Same input plus same options always yield the same bytes.repeatcopydownloadzero-networkreproducibleok · copiedhistory · copiedYES · NO · YES
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 flip yes/no
Tiebreakers, prompts, group decisions.
Tiebreaker
Two options, equal weight — let chance decide. 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-backedDaily routines
Run or rest? Coffee or tea? Quick verdict. 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.
reproducibleWriter prompts
Roll for plot branches when stuck on the page. 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.
snappyStandup volunteer
Decide who demos first without picking favorites. 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-detectedWorkouts
Heavy lift or cardio? Yes/no makes the call. 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 pick
Beach vs mountains? Hit Decide and pack. 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.