DnD Dice Roller has had its biggest update since it launched. Your dice lines can live on an account instead of in one browser, the save button is gone because the site saves as you go, and you can see, and choose, where your random numbers come from.
Here is what changed and how to use it.
Your dice lines can follow you now
The roller has always remembered your lines. The catch: it remembered them in one browser. Set up your character on a laptop and your phone knew nothing about it.
There is now an optional account. Sign in and your dice lines save to it, so the same setup waits on any browser you sign in from.
You get up to 10 named lists. Enough for a list per character, plus a few for the monsters you run.
| To do this | Do this |
|---|---|
| Name or rename a list | Type in the box at the top of the roller |
| Switch lists | Click the arrow at the right edge of that box |
| Start a new, empty list | Press + |
| Throw a list away | Remove its last line (see below) |
There is also an entry called Local Browser. That is the old behaviour, kept: lines stored in the browser you are using and never sent anywhere. It works signed in or not, stays separate from your account lists, and does not count toward the 10.
One thing to know about Local Browser: it belongs to the browser, not the computer. Chrome and Safari on the same laptop keep separate lines. That is why it is not called "this device".
The save button is gone
There is nothing to press any more. Change a line and it is saved. Rename a list and it is saved. Nothing announces it and nothing asks you to confirm.
This was the most common thing people got wrong: a carefully built set of lines, a closed tab, and no idea a button somewhere needed pressing first.
Autosave: because the only thing that should vanish without warning is your hit points.
If you would rather nothing was saved at all, open the site in a private or incognito window. Everything works the same, and it is all forgotten when you close the window. That is the cleanest way to use the roller on a shared or borrowed computer.
Backup & Transfer on the Settings page exports your dice lines, backgrounds and other settings to a file, and imports them again. Use it to move between browsers, or to keep a copy of a setup you spent an evening on.
Deleting a list
There is no delete button either, and that is deliberate. A list with nothing in it is not a list, so removing its last line is how you throw one away. The roller asks first, and names the list it is about to remove.
Where your random numbers come from
Every dice roller gets its randomness from somewhere, and most never tell you where. (Your lucky d20 won't tell you either. It just knows.) This one does, and lets you choose.
| Secure Enclave (default) | Public randomness beacon | |
|---|---|---|
| Where the numbers come from | Your browser's cryptographic generator, crypto.getRandomValues |
NIST's Randomness Beacon, or drand if NIST is down |
| Speed | Instant, works offline | Needs a connection |
| What each roll can show you | Nothing to check: there is no public record | The signed public record it came from, with a link |
| Cost | Free | Free for everyone since September 2026. Switch it on in Settings |
Secure Enclave is the default and the name in Settings. It uses the browser's own cryptographic random number generator, the one built for security work, which MDN describes as producing "cryptographically strong random values" [1]. It is also an upgrade on what this roller used before: Math.random, which MDN calls a "non-cryptographic" source [1]. For rolling a d20, it is more than good enough.
The beacon is the other option. NIST, the US National Institute of Standards and Technology, publishes a fresh 512-bit random value about once a minute, time-stamped, signed and chained to the value before it [2][3]. drand, run by a group of independent organisations called the League of Entropy, publishes a signed round every 30 seconds [4]. Your dice ask NIST first; if NIST goes quiet, drand takes over without you doing anything.
Roll on the beacon and the roll log names the pulse or round behind each roll, links to the beacon's own copy, and opens a certificate page that fetches that record from the beacon and checks it matches.
The difference is not that one is "more random". It is what you can check. You can confirm, afterwards and without asking us, that the record behind your roll is genuine, signed by someone who is not us, and published at that moment. What the check does not prove is the number itself: we mix the public value with a private key, so nobody can predict your next roll by watching the beacon. The certificate page shows each step of that working.
Whichever you pick, the roller tells you which one produced the number in front of you. If the beacon cannot be reached, the roll still happens on your device, and the status line says so. It never swaps sources silently.
Switch between them on the Settings page, under Dice Randomness.
Smaller things
- Appearance settings follow your account: colour scheme, custom theme, day or night mode, log shadow and dice sound arrive with you. Backgrounds stay on each device, because a phone wallpaper is not a desktop one.
- Long list names are capped so they cannot spill out of the box.
- The roll log and the roller sit where they always have. Nothing to relearn.
Nothing was taken away
Everything the roller did before, it still does. No sign-in is needed to roll, nothing that was free moved behind an account, and the free roller is the same free roller. The account is there if keeping your lines is useful to you. Ignoring it costs you nothing.
Want to put the new lists to work? Start with 10 useful dice presets you can save, or take them to the 3D table.
Roll well.
Table Talk
Rohan: The browser generator is cryptographically strong. Why would anyone pay for a beacon?
Arthur: Not for more random. For a receipt. The beacon roll links to a signed public record you can check without asking us.
Rohan: Nobody at my table has ever asked to audit a d20.
Arthur: Nobody at your table has ever lost a character to a roll the whole group watched.
Rohan: Fair. Still default Secure Enclave. Instant, works offline, free.
Arthur: Default for me too. The beacon is for the night a roll has to be beyond argument.
Rohan: The feature I actually care about: no save button. People lost whole setups to a closed tab.
Arthur: Tip for anyone on a borrowed laptop: private window. Everything works, nothing stays.
Rohan: And export with Backup & Transfer before you switch browsers. Chrome and Safari don't share.
References
- MDN Web Docs. "Crypto: getRandomValues() method." Mozilla, accessed 28 September 2026. https://developer.mozilla.org/en-US/docs/Web/API/Crypto/getRandomValues
- Kelsey, John, Luís T. A. N. Brandão, René Peralta, and Harold Booth. A Reference for Randomness Beacons: Format and Protocol Version 2. NIST Interagency Report 8213 (initial public draft), May 2019. https://doi.org/10.6028/NIST.IR.8213-draft
- NIST Computer Security Resource Center. "Interoperable Randomness Beacons." Accessed 28 September 2026. https://csrc.nist.gov/projects/interoperable-randomness-beacons
- drand / League of Entropy. Mainnet chain information (period: 30 seconds). https://api.drand.sh/info
