Run TRPG checks in two taps
- 1) Add a label and numbers. Name the check (for example Attack or Perception), choose d20 or d100, set your modifier and an optional DC.
- 2) Choose roll over or roll under. Use the checkbox to switch between “total ≥ DC” and “total ≤ DC” style checks.
- 3) Roll and share with your table. Tap Roll to see the total and outcome, then copy text, PNG, or a prefilled URL for chat or overlays.
- 1) Set XdY+Z. Choose N dice, S sides, and an optional modifier Z (for example 8d6+3 for damage).
- 2) Roll once for a quick total. Tap Roll to see the total and a compact list of individual dice.
- 3) Share totals for combat and stats. Use the result for damage rolls, HP or ability generation, and copy it as text or PNG.
- 1) Choose N and S. For example, 10 dice with 10 sides for a 10d10 pool.
- 2) Set the success threshold. If 8+ counts as a success, set T to 8.
- 3) Read and share successes. Check the total successes and a compact roll summary, then share as text or PNG.
Result
Result
—
—
Shows your d20 check total and whether it meets the DC.
Share & copy
History
How to use this tool effectively
This guide helps you use TRPG dice check in a repeatable way: define a baseline, change one variable at a time, and interpret outputs with explicit assumptions before you share or act on results.
How it works
The page applies deterministic logic to your inputs and shows rounded output for readability. Treat it as a comparison workflow: run one baseline case, adjust a single parameter, and measure both absolute and percentage deltas. If a result seems off, verify units, time basis, and sign conventions before drawing conclusions. This approach keeps your analysis reproducible across teammates and sessions.
When to use
Use this page when you need a fast estimate, a classroom check, or a practical what-if comparison. It works best for planning and prioritization steps where you need direction and magnitude quickly before investing in deeper modeling, manual spreadsheets, or formal external review.
Common mistakes to avoid
- Changing multiple parameters at once, which hides the true cause of output movement.
- Mixing units (percent vs decimal, monthly vs yearly, gross vs net) across scenarios.
- Comparing with another tool without aligning defaults, constants, and rounding rules.
- Using rounded display values as exact downstream inputs without re-checking precision.
Interpretation and worked example
Run a baseline scenario and keep that result visible. Next, modify one assumption to reflect your realistic alternative and compare direction plus size of change. If the direction matches your domain expectation and the size is plausible, your setup is usually coherent. If not, check hidden defaults, boundary conditions, and interpretation notes before deciding which scenario to adopt.
See also
How to use & FAQ
Keep everything local, read totals at a glance, and share clean logs as text, PNG, or URL while playing or streaming.
What can I do with this TRPG dice check tool?
You can run d20 checks with advantage or disadvantage, compare totals against a DC, and roll dice pools that count how many results meet a success threshold. Everything runs in your browser, with optional labels and a local history for logging your sessions.
How can I share my rolls with my group?
Use Copy text for chat logs, Copy PNG or Download PNG for visual cards, and Copy URL to share a prefilled link with the same inputs. Everything runs in your browser, and neither your inputs nor rolls are uploaded to a server.
What should I do first on this page?
Start with the minimum required inputs or the first action shown near the primary button. Keep optional settings at defaults for a baseline run, then change one setting at a time so you can explain what caused each output change.
Why does this page differ from another tool?
Different pages often use different defaults, units, rounding rules, or assumptions. Align those settings before comparing outputs. If differences remain, compare each intermediate step rather than only the final number.
How reliable are the displayed values?
Values are computed in the browser and rounded for display. They are good for planning and educational checks, but for regulated or high-stakes decisions you should validate assumptions with official guidance or professional review.