Exhaustion 5e: The Condition Nobody at the Table Tracks

Exhaustion 5e is the condition every Dungeon Master reaches for during a desert crossing, a blizzard, or a three-day march through goblin territory, and then quietly forgets exists by session four. Not because the rule is unclear. Because it's the one condition in the entire game that asks a table to keep score, and most tables don't have anywhere to write the number down.

That's the real story here. Every other condition in the Player's Handbook is a light switch. You're Poisoned or you aren't. You're Prone or you aren't. Exhaustion is the one dial, six cumulative levels, each one stacking its penalty on top of everything below it, and it's also the only condition that can kill a character outright with no monster involved. It deserves more respect than it usually gets, and it gets less than almost anything else in the rulebook.

Exhaustion 5e Is the Only Condition That Stacks

This is the detail that separates exhaustion 5e from every other status effect in the game.

Blinded, Charmed, Frightened, Grappled, Paralyzed, all of them are on or off. A creature can be Blinded and Poisoned and Restrained at the same time, sure, but each of those conditions is still a single flat state. It doesn't work like that. It has six levels, and a character carries every level up to and including their current one.

That means a character at exhaustion level 3 isn't just suffering the level 3 penalty. They're also carrying levels 1 and 2 on top of it. The condition is cumulative by design, which is exactly why it feels so punishing once it actually shows up at the table, and exactly why groups that only half-track it end up with characters who are quietly far weaker than anyone realizes.

Exhaustion 5e Gets Ignored Because Nobody Has a Place to Write It

Here's the part that doesn't show up in the rulebook: the actual reason it disappears from most campaigns has almost nothing to do with the mechanics and almost everything to do with bookkeeping.

Look at a standard character sheet. There's a box for hit points. There's a box for armor class. There's a line for conditions, usually blank, usually the first thing that gets forgotten when combat starts moving fast. Exhaustion doesn't even get that much. It's a rule that lives in an appendix, applies over the span of days rather than the span of a single die roll, and only actually costs the player anything the next time someone remembers to check it. A GM calls for a Constitution save against exhaustion during a forced march, somebody fails, and then three sessions later nobody at the table can say with confidence whether that character is still carrying the penalty.

That's not a player being careless. It's a rule that was built to represent long-term wear on a character, running on a table that mostly tracks short-term state. Concentration gets attention because it breaks the moment a spell drops. Death saves get attention because everyone stops breathing while they happen. It asks a table to remember something across an entire in-game week, and most groups just aren't built to do that without a dedicated place to keep the number.

The frustrating part is that exhaustion 5e is doing real design work when it's actually enforced. It's the mechanic that makes "how much food and water do we have" matter. It's the mechanic that makes a forced march through the mountains feel different from a leisurely walk down a market road. Skip it consistently, and every environmental hazard in the game quietly loses its teeth.

Exhaustion 5e Levels, One by One

Worth walking through the full ladder, because most confusion comes from people remembering roughly what each level does instead of exactly what it does.

Level 1: Disadvantage on ability checks. This is the level most groups can shrug off, which is part of why it's also the level most groups forget to apply. It hits Strength checks to force a door, Perception checks to spot an ambush, Persuasion checks to talk down a guard. Small tax. Real tax.

Level 2: Speed halved. Now it's visible on the map. A character who was covering 30 feet a turn is covering 15. Chases get harder to win. Retreats get harder to pull off. This is usually the level where a party finally notices something is wrong, because it changes tactical positioning instead of just a hidden number behind the screen.

Level 3: Disadvantage on attack rolls and saving throws. This is where exhaustion 5e stops being an inconvenience and starts being dangerous. Every attack roll suffers. Every saving throw suffers, including the ones against poison, fear, and worse exhaustion. A character stacking level 3 exhaustion into a fight is playing at a real, measurable disadvantage in the one place disadvantage costs the most.

Level 4: Hit point maximum halved. Not current hit points, maximum hit points. A Fighter with a 60 hit point max is suddenly capped at 30, and if their current total was already above that new cap, it drops immediately. This level turns a character who felt sturdy into a character who can be dropped by half the damage.

Level 5: Speed reduced to 0. The character can't move under their own power anymore. Allies have to carry them, drag them, or leave them behind. Combined with everything from levels 1 through 4, this is close to a character being taken out of the story without a single monster attack landing.

Level 6: Death. No save. No warning shot. A character who gains a level of exhaustion while already at level 6 dies. It's the only condition in D&D 5e that can end a character's life entirely on its own.

Exhaustion 5e Removal Rules Are Stricter Than People Think

This is where a lot of tables get the recovery math wrong, usually by assuming exhaustion clears the way fatigue does in real life: sleep it off and you're fine.

A long rest removes exactly one level of exhaustion, and only if the resting character had food and water available during it. That's it. One level, one long rest. A character sitting at exhaustion level 3 isn't clean after a single night's sleep. They need three separate long rests, on three separate nights, assuming nothing forces a new level onto them in between.

The only other fix in the core rules is the spell Greater Restoration, a 5th level spell that also removes exactly one level per casting. That's a real resource cost for a caster to spend, which is precisely the point. It's supposed to be a slow-burn consequence, not something a first level Cure Wounds waves away between fights.

This matters most on the exact trips where exhaustion is likely to come up in the first place: desert crossings, arctic treks, forced marches to reach a besieged town before it falls. It's worth deciding how your table handles travel and downtime before the trip starts, not mid-scene. If the party is racing the clock, they usually don't have three clean nights to spare, which means the condition and time pressure end up fighting the same story beat from opposite directions. That tension is the whole point of the rule.

Why Exhaustion 5e Actually Matters When Someone Remembers to Use It

None of this is an argument for punishing players constantly with it. It's an argument for using it on purpose instead of forgetting it exists.

Used well, exhaustion 5e is one of the few tools in 5e that makes travel, weather, and survival feel like they cost something without needing a full hunger-and-thirst tracking system bolted on top. A single Constitution save at the end of an eight-hour forced march does more narrative work than a page of ration math. It tells the party, correctly, that pushing past the group's limits has a price, and that price follows them into whatever fight is waiting at the end of the road.

It also does something useful for Barbarian players specifically. A Berserker who wants to Frenzy every round already knows the deal: extra bonus action attacks now, a level of exhaustion once the rage ends. That's a real, felt tradeoff precisely because the condition sticks around and stacks if the player keeps making the same choice fight after fight. If a table quietly stops tracking exhaustion, that whole risk-reward decision collapses into free damage, and the class feature stops meaning anything.

This is the kind of state that's easy for a human table to lose and easy for a persistent digital one to keep. In StoryRoll, conditions live in the same session state as hit points and armor class, not on a sticky note that gets left behind between sessions. A level of exhaustion applied during a desert crossing is still there three sessions later when the party finally gets a real rest, the same way the party's gold total or a locked door's status doesn't reset just because nobody mentioned it recently.

Frequently Asked Questions

What are the six levels of exhaustion in D&D 5e?

Level 1 gives disadvantage on ability checks. Level 2 halves your speed. Level 3 adds disadvantage on attack rolls and saving throws. Level 4 halves your maximum hit points. Level 5 drops your speed to 0. Level 6 kills you. Each level keeps every penalty from the levels below it.

How do you remove exhaustion in 5e?

A long rest removes one level of exhaustion, as long as the character has eaten and had access to water during that rest. Greater Restoration also removes one level per casting. There is no fast fix for multiple levels.

Can you die from exhaustion in D&D 5e?

Yes. A character who already has six levels of exhaustion and gains another level dies, with no save and no monster required.

Does exhaustion 5e stack with itself?

Yes. It's the only condition in D&D 5e with cumulative levels. Every other condition is a flat, binary state, but exhaustion has six stacking levels, and a new level adds on top of whatever level a character already has.

What causes exhaustion in D&D 5e?

Forced marches beyond eight hours of travel in a day, extreme heat or cold without proper protection, going without food or water, certain monster abilities and spells, and specific class features like a Barbarian's Frenzy can all cause exhaustion. A Game Master can also call for a Constitution save against it whenever a situation calls for it.

Why do so many D&D tables ignore exhaustion 5e?

Mostly bookkeeping. There's no dedicated box for it on the standard character sheet, the penalties only apply once someone remembers to check them, and clearing it takes multiple long rests instead of a single spell. Tables without an easy way to keep it visible tend to stop calling for it after the first session or two.