Dice notation min and max calculator

What dice-notation min and max mean and what the response contains

The response echoes the original notation string, a normalized form without spaces and with explicit counts, the integer min_total and max_total, the arithmetic range max minus min, possible_totals as range plus one (the count of integer values from floor to ceiling when every intermediate total is reachable under additive fair dice), the total dice_count across terms, the net constant, term_count, a structured terms array with kind, sign, count or value, sides when applicable, and each term’s own min and max, plus a short formula reminder. Rejected cases are different from extreme but valid totals: missing notation, empty strings after trim, unsupported keep-highest or exploding operators, zero or one-sided dice, bare constants without a die, leading zeros, and values above the published dice or sides ceilings produce invalid_input so a bad form cell never becomes a silent wrong band.

How notation is read, normalized, and kept reproducible

Whitespace around plus and minus signs is stripped; the die letter is accepted as lowercase or uppercase d; a missing count before d means one die, so d8 is the same as 1d8; and d% is accepted as a percentile die with one hundred faces. Multiple dice terms and constants may be chained with + and −, for example 1d20+1d4+3 or 4d6−2. The engine rejects advanced operators that change the extreme model in ways that are not a simple sum of independent face ranges—keep highest, drop lowest, explode, multiply, and divide—so the published min and max stay honest for the classic additive reading. The normalized string rewrites implicit ones and drops spaces so two clients that send 2D6 + 3 and 2d6+3 compare equal after normalization. The preferred field is notation for the full expression string, with aliases expression, dice, formula, expr, input, and text so spreadsheets, query strings, and typed forms can reuse the same contract without a rename layer. Dice count per term and total dice across the expression are capped by the documented maxima, and sides per die are capped likewise, which keeps browser and Worker paths inside a predictable budget. Pair the free browser run on this page with the priced API when you need the identical mathematical envelope inside an automated pipeline without re-implementing dice tokenization yourself. Failed validation is not charged, and nothing is stored after the response returns.

Where min–max dice ranges fit in play, design, and software

Players meet range questions when a weapon card prints 2d6+4 damage and they want to know whether a lucky swing can one-shot a foe or whether the floor still fails to crack light armor. Game masters and homebrew designers use the same numbers when tuning encounter budgets, critical-hit riders, and treasure tables so the table never sees a dead zone of impossible totals or an accidental ceiling that trivializes a boss. Teachers introduce sample spaces by first showing the envelope of two six-siders before counting the ways for each intermediate sum. Contest and homework drills need a fast offline source of exact bounds so students can check work without opaque calculator apps that silently treat d% differently or allow illegal zero-sided dice. On this page the work runs entirely in your browser; through the API each successful lookup costs $0.002. That split—free interactive exploration and a priced, identical API—matches the rest of the KIT tier-A catalog and lets you move from a classroom demo to an automated pipeline without changing the mathematical result. Pair it with dice probability endpoints when you need the full distribution inside the band, and with other hobby math helpers when you are building a small lab of free, deterministic tools for games and study.