Dice Roller — D&D and Tabletop Dice
Roll standard polyhedral dice with modifiers, advantage/disadvantage, and roll history.
How it works
- 1Configure your options above
- 2Click "Generate" — processing happens in your browser
- 3Copy or download the result
What to do next
About Dice Roller
Dice Roller is built for web and productivity utility jobs that fit cleanly into a browser tab. Roll standard polyhedral dice with modifiers, advantage/disadvantage, and roll history. The processing runs in the page itself, which is why the controls update instantly when you change settings and why a freshly loaded page is ready to do real work the moment it becomes interactive.
The processing pipeline is straightforward: your input is parsed by standard browser APIs, transformed according to the options you select, and serialised back into a downloadable result. The 0 MB per-file ceiling matches what a typical browser tab can handle without paging to disk.
Dice Roller is shaped around the recurring needs of two audiences: researchers gathering quick references, who use it as a quick utility between bigger tools, and site owners auditing pages, who use it as their primary way of getting the job done. Both groups get the same defaults and the same speed.
The browser sandbox isolates the page's JavaScript from the rest of the system, the same way it isolates every other tab you have open. Dice Roller works inside that sandbox: it reads the file you give it, processes it with standard browser APIs, and writes the result back. Nothing leaves the page's memory unless you choose to download or copy it.
Most people land on Dice Roller via a search at the moment they actually need the tool. That shapes the design: the page is a single screen with the input on one side, the controls in the middle, and the result on the other, so a first-time visitor can complete the job without reading documentation.
When the job finishes, Dice Roller hands you the result as a sensibly named file. Filenames are derived from your input where possible, so a quick batch of jobs leaves you with a tidy folder rather than a pile of generic "output (3)" files. Nothing is auto-saved on Favtoo's side because nothing was ever sent there.
Constraints worth knowing about: inputs are capped at 0 MB to keep memory usage in a sensible range, one input is processed per run, and the tool must be loaded over HTTPS for the in-browser engine to work. These are properties of the architecture.
Dice Roller fits naturally next to several adjacent tools. Common companions include Coin Flipper, Lottery Number Generator, Lucky Number Generator, and Prime Number Generator — combine them when the job needs more than one transformation. After running Dice Roller, many users move on to Coin Flipper and Lottery Number Generator. Each tool is a separate page so you can compose the exact pipeline you need.
Some notes on the design of Dice Roller. The page is intentionally narrow: one input, the controls relevant to the task, and one output. Adding unrelated features would make the common case slower for the majority of users, so the surface is held to what people actually use.
Dice Roller is structured around the idea that a useful tool should be its own page. Open the page, do the work, close the tab — the page is the entire product. There is no onboarding flow because there is nothing to onboard into.
Dice Roller runs as a regular web page, so there is no install step or permission grant before the first run. The page can be audited by viewing the source or by watching the developer-tools Network tab while a job runs.
Tips from users who reach for Dice Roller regularly: process one input first to confirm the settings produce what you expect before committing to a batch; treat the page as the working surface and avoid leaving large jobs running in a backgrounded tab where the browser may throttle JavaScript; and if a particular file fails, check whether the source is intact by opening it in its native viewer — most "tool errors" are actually input errors.
Common gotchas worth flagging: the supported formats are listed in the upload area. The 0 MB ceiling is per-file, not per-session; you can run as many separate jobs as you like, but a single oversized input will be rejected on load.
That is essentially everything Dice Roller does and how it does it. Open the tool above, drop in your input, and the work happens in the page. If you find yourself reaching for it often, bookmark the page — it loads quickly on subsequent visits, and your most-recent settings are remembered for the rest of the session.
How it works
- 1Land on the Dice Roller page. The tool is ready to use the moment the page renders.
- 2Drop a web utility file onto the upload area, or click to pick one from your device.
- 3Tweak the controls if the defaults are not quite right for your input. The options are kept short and labelled in plain language.
- 4Click to start the job. The engine (standard browser APIs) processes the input in the page; you can watch the progress indicator until it completes.
- 5Save the output when it is ready.
- 6Re-run with different settings as often as you want. Each run produces a fresh output and the original file on disk is never modified.
Common use cases
- Create a placeholder image for a wireframe using Dice Roller.
- Run a fast accessibility check before publishing.
- Audit a marketing page before launch.
- Preview how a result looks before deploying it.
- Run a one-off check during a meeting without context-switching.
- Plan content without paying for a SaaS dashboard.
- Sanity-check a webhook response while debugging.
- Validate a setting before circulating it to a team.
FAQ
Is it fair?
Uses crypto.getRandomValues when available for uniform rolls; falls back to Math.random otherwise.
Can I roll pools?
Yes — enter counts like 8d6 and add a flat modifier for weapon or spell damage totals.
What is advantage mode?
Rolls twice and keeps the higher (or lower for disadvantage) on a d20-style check.
Does it show history?
Recent rolls appear in a log with timestamps so the table can audit streaks.
Are rolls private?
Yes — random bytes are generated on-device; we do not broadcast your campaign rolls.
Which browsers are supported?
crypto.getRandomValues exists in Chrome, Firefox, Safari, and Edge for secure dice.
Can I use Dice Roller with formats other than the defaults?
The accepted formats are listed in the upload area on the tool itself. If your input is in a format that is not directly supported, convert it first using one of Favtoo's converter tools — every Favtoo converter outputs a file that is a clean input to the next tool in the chain.
Can I process multiple files at once with Dice Roller?
Dice Roller processes one input at a time by design — it keeps memory usage predictable on lower-end devices and makes results easier to verify. To handle a folder, run the tool once per file; the page stays loaded between runs and remembers your last-used settings, so the second run is essentially instant.
How do I know I am using the latest version of Dice Roller?
Dice Roller is updated whenever the underlying engine releases an improvement or a bug fix. Because the tool is delivered as a static page, every visit fetches the latest version automatically — there is no "version" to manage on your end. If a particular release ever changes default behaviour, the change is documented on Favtoo's changelog so you can confirm what shifted.
Can I trust the output of Dice Roller for important work?
Dice Roller is built on standard browser APIs, which is the same class of engine used by professional web and productivity utility pipelines. For deterministic operations, the output is byte-identical to what an equivalent CLI run would produce; for operations involving a codec or a model, the result is well within the range of what comparable tools generate. If you have a specific reference output you need to match, run a small test job first to confirm the configuration produces what you expect.
Is Dice Roller really free?
Dice Roller is free to use. The processing runs in your browser, which keeps the per-user cost low enough that the tool can be offered openly. The download is the same file the engine produced — you can use it for as many runs as you need.
How fast is Dice Roller?
Most jobs finish in seconds. Speed scales with input size and with how many CPU cycles your browser tab has available — the engine runs in your browser, so it shares resources with whatever else you have open. For inputs near the 0 MB ceiling, expect anywhere from a few seconds to roughly a minute on a typical laptop. Closing other heavy tabs noticeably speeds things up.
How many times per day can I use Dice Roller?
Inputs are capped at 0 MB per file, which keeps memory usage stable across phones, tablets and older laptops. You can run Dice Roller as often as you need; every run produces a full-quality result.
Does Favtoo keep a copy of files I process with Dice Roller?
Favtoo keeps no copy of your file because Favtoo never receives your file. Dice Roller runs entirely in your browser, the input is held only in your tab's memory, and closing the tab discards it. There is no opt-in cloud history, no "recent jobs" panel synced to an account, and no server-side retention to configure — the architecture simply has nowhere for your file to be stored.