Blog / Fifth edition rules

Death saving throws: what actually happens at 0 hit points

31 July 2026

When your hit points reach 0 in fifth edition you are unconscious and dying, not dead. On each of your turns you roll a bare d20. Ten or higher is a success, nine or lower is a failure, and you are racing two counters: three successes and you are stable, three failures and you die. Nothing you do influences the roll, and nothing on your character sheet is added to it.

That is the ordinary case. There is also a way to skip it entirely.

Dropping to 0 versus dying outright

Two different things happen at 0 hit points depending on how much damage arrived.

Dropping to 0. Damage reduces you to exactly 0. You fall unconscious, you go prone, and you start making death saving throws on your turns. Any excess damage beyond what was needed to reach 0 is discarded; you never go negative.

Instant death from massive damage. If the leftover damage - what remains after taking you to 0 - equals or exceeds your hit point maximum, you die. No saves, no counter, no chance to be revived by a healing spell that only restores hit points.

The maths trips people up because the comparison uses the leftover, not the total. A character at 3 hit points with a maximum of 15, hit for 20: three of that damage takes them to 0, leaving 17, and 17 is more than 15, so they die outright. The same character at full health takes the same 20 damage and lives, dying, with five leftover. Being nearly dead is genuinely more dangerous than being fresh, which is the rule's whole point.

The three-and-three track

Roll d20 at the start of each of your turns while you are at 0 hit points. No ability modifier. No proficiency bonus. No Bless, no Guidance, no inspiration in most readings. Just the die.

• 10 or higher: one success. Exactly 10 succeeds.
• 9 or lower: one failure.
• Three successes: you are stable. You stop rolling. You are still unconscious and still at 0 hit points.
• Three failures: you die.

Successes and failures accumulate independently, so a run of two successes and two failures is entirely normal and decides nothing. The counters are the only thing that matters; the order they arrived in does not.

Natural 1 and natural 20

The two ends of the die break the pattern.

• Natural 1 counts as two failures. Two of them, on their own, kill you.
• Natural 20 puts you back on your feet: you regain 1 hit point immediately and you are conscious again. Not stable-but-out, conscious, on your turn, able to act (you are still prone until you stand).

A natural 20 on a death save is the single largest swing on any d20 in the game, and it is the reason a downed character is never a settled question.

Damage while you are down

Taking damage at 0 hit points causes an automatic death save failure, on top of any you have already rolled. If that damage came from a critical hit, it is two failures instead.

Here is the part that gets missed at almost every table: any attack that hits an unconscious creature from within 5 feet is automatically a critical hit. So a monster that walks up and stabs your unconscious fighter deals two failures per hit, not one. A pair of hits from a multiattack is your entire death track in a single monster turn. This is why standing over a downed ally matters, and why "we will get to them in a round or two" is usually a decision to let them die.

If the damage taken at 0 also meets the massive-damage threshold above, you die instantly, as normal.

Getting somebody back up

Three ways out, and they are not equivalent.

1. Three successes. You become stable: no longer rolling, still unconscious at 0 hit points. A stable creature regains 1 hit point on its own after 1d4 x 10 minutes.
2. A Medicine check. Another creature can use its action to make a DC 10 Wisdom (Medicine) check to stabilise you. Success makes you stable, exactly as three successes would. Using a healer's kit removes the need to roll at all - it just works, and expends one of the kit's ten uses.
3. Healing. Any healing at all ends the dying state, wakes you up, and clears both counters.

Stable is not safe. A stable creature that takes any damage is dying again and back to rolling.

The counters reset

When you regain hit points, your successes and failures both go back to zero. They do not carry across a fight, a rest or a campaign. The character who went down twice in one dungeon and rolled two failures each time starts the third episode clean.

This is worth saying because the opposite intuition is common, and because it changes how the risk feels: each time you go down, the full three-failure runway is there again. What does not reset is the thing actually killing parties, which is a healer who is out of spell slots.

The misreadings worth naming

"Healing brings you back at 1 hit point." Not quite. Healing at 0 puts you at the amount healed - a Cure Wounds for 7 leaves you at 7 hit points, not 1. The only routes that give you exactly 1 are a natural 20 and waking up naturally after being stable. Spare the Dying is the exception in the other direction: it stabilises without healing, so you stay unconscious at 0.

"You add your Constitution modifier." You do not. It is a saving throw in name only, and the fact that no bonus applies is what makes it feel so grim.

"Monsters make them too." They do not, as standard. Monsters and most NPCs die at 0 hit points. If you want a villain to survive being downed, that is the GM choosing it, not the rules producing it.

"You have to kill them." When you reduce a creature to 0 with a melee attack you may choose to knock it out instead. It is stable and unconscious, and that choice is free.

What this looks like when something tracks it for you

Death saves are the most consequential bookkeeping in D&D 5e and among the easiest to lose track of. The failure from being hit while down is applied outside your turn, by somebody else's action, and is exactly the sort of thing that gets narrated past in the noise of a boss fight. So is the second failure from the critical. A table that misses those two is playing a materially safer game than the one in the book, and will never notice.

On Rolegend the counters live on the character record rather than in the conversation. Keystone Engine rolls the d20, applies the natural 1 as two failures and the natural 20 as a return to 1 hit point, adds the automatic failures when you are hit at 0 (two for a critical), computes the leftover-damage instant death, and clears the track the moment you regain a hit point. ROWAN is handed the outcome and writes it. It never rolls the save and never decides the number, so it cannot decide that you should probably survive this.

The point is not that the software is harsher. It is that the third failure means something, because the first two were really counted. Which of the fifth edition rules Rolegend enforces, and which it leaves to narration, is published rule by rule at /rules-coverage.