Temporary Hit Points 5e: Why They Never Stack, Even From the Same Spell Twice

The bard casts Heroism at the start of the fight, and the fighter picks up 10 temporary hit points. Two rounds later, a warlock drops Armor of Agathys on the same fighter for another 5. Someone at the table does the math out loud: fifteen temp HP, right? Wrong, and this is one of those D&D 5e rules that feels like it should work differently than it actually does.

Temporary hit points 5e don't stack. Not when they come from two different spells, and not when the same spell gets cast on the same character twice. The rule is short, it's been the same since 2014, and it still catches tables off guard almost every session someone stacks a buff, because "two separate sources" feels like it should mean "two separate pools."

Temporary Hit Points 5e: The One Rule That Covers Everything

Here's the entire mechanic, with no exceptions tucked into a sidebar.

When you gain temporary hit points while you already have some, you don't add the new amount to what you're holding. You compare the two numbers and choose: keep what you currently have, or replace it with the new grant. Either way, you end up with one number, never a sum of both.

That's it. That's the whole rule, and it applies the same way whether the second grant is a bigger number, a smaller number, or comes from a completely unrelated source.

Why "Two Different Sources" Doesn't Change Anything

This is the exact point where most tables go wrong. The instinct is that stacking rules only block the same buff from doubling up, the way two castings of Bless on the same creature don't give two separate bonus dice. This rule goes further than that. It doesn't matter whether the second grant is the same spell, a different spell, or a class feature entirely unrelated to the first. The rule doesn't ask where the extra hit points came from. It only asks how many you have now versus how many you're being offered.

So in the bard-then-warlock example above, the fighter doesn't end up with 15. They had 10 from Heroism, then got offered 5 from Armor of Agathys, and since 10 is bigger than 5, the sensible choice is to keep the 10 and decline the smaller grant entirely. If the order had been reversed, 5 first and then 10, the player would drop the 5 and take the 10. Either way, the fighter finishes with one number: the larger of the two, never both added together.

This holds even in the stranger case of the exact same spell cast twice on the same target. Two different bards both cast Heroism on the same fighter in the same round. That's not a pool of 20. It's whichever single casting grants the higher amount, with the other effectively wasted on a target who already had a better offer on the table.

What Temporary Hit Points Actually Are (and Aren't)

Part of why the stacking instinct is so persistent is that temporary hit points look a lot like a second health bar, and a second health bar feels like something you'd want to grow, not swap out. It helps to be precise about what the pool actually does.

It's a buffer layered on top of your real hit points. When you take damage, it comes off the buffer first, in full, before your actual hit points take any of it. A fighter at 20 real hit points with a 10-point buffer who takes 12 damage loses all 10 temp HP and then 2 real hit points, landing at 18, not 20.

It isn't real hit points, and it doesn't heal anything. If a character is down to 5 hit points out of a 40 maximum and picks up a 10-point buffer, they're still at 5 real hit points once the temp HP is gone. Nothing about the buffer restores lost health. A character sitting at 5 hit points with 10 temp HP on top is in a very different position than a character actually healed up to 15.

It can push a character above their hit point maximum. Because it's a separate pool, not an addition to your real total, there's no upper limit tied to your stated maximum. A barbarian with a 45 hit point maximum sitting at full health plus a 10-point buffer is genuinely harder to drop than that same barbarian at full health alone.

It doesn't affect bloodied status or death saves the way real hit points do. Whether a creature counts as below half health for the purposes of features that key off that is based on real hit points, not the buffer sitting on top. And the buffer offers no protection once a character is already unconscious: it doesn't revive anyone, and once it's gone, damage goes straight to real hit points as normal.

Losing the whole buffer at once doesn't carry negative consequences on its own. Going from a 10-point buffer to 0 in one hit isn't the same as taking 10 damage to your actual pool for purposes like exhaustion-adjacent effects that trigger off taking damage; it's simply the buffer being spent as intended.

The "They're From a Class Feature, Surely That's Different" Trap

A second, closely related version of the same confusion shows up with class features rather than spells. A paladin's aura, a cleric's channel divinity option, a warlock invocation, and a bard's Heroism all technically grant the buffer through different mechanical routes. None of that matters to the stacking rule. The rule reads the result, not the mechanism. If the end state is "this character now has some amount of temporary hit points," every source that produces that end state plays by the exact same comparison: keep the higher number, drop the lower one.

This is also why "I'll just cast it again next turn to top up my temp HP" doesn't work the way refreshing a buff duration does. Recasting the same spell for the same amount doesn't add anything if the character still has an equal or higher amount left from the first casting. It only matters once the current pool has dropped below what a fresh casting would grant.

Temporary Hit Points vs. Healing: Two Different Jobs

It's worth separating these cleanly, because the overlap in how they're described, both "give a character more hit points," is exactly what makes stacking feel intuitive even though the mechanics don't work the same way.

Healing spells and effects restore lost hit points, up to a character's maximum, and enough healing can bring an unconscious character back up. Healing effects from different sources genuinely do add together in the sense that matters: a character healed by two separate spells in the same round recovers the combined total, capped at their maximum.

The buffer works on a completely different axis. It doesn't restore anything that's been lost, it doesn't have a maximum tied to the character's real hit point total, and it explicitly does not combine across sources the way healing does. Treating a Heroism cast and a Cure Wounds cast as the same kind of resource, just because both effects use the words "hit points," is where a lot of the stacking confusion starts.

Did the 2024 Rules Change This?

No. Tables sometimes assume a recent rulebook quietly loosened the no-stacking rule the way some other mechanics got reworded, but this one carried over unchanged. The 2024 core rules keep the same comparison-not-addition logic: gaining more while you already have some means choosing the higher amount, full stop. If a table is arguing about whether two castings of the same buff should add up, that argument predates the current rulebook by a decade, not something a recent edition introduced or removed.

Where an AI Game Master Actually Helps With This Rule

This rule rarely fails because someone can't understand it once it's explained. It fails because a live table is tracking several numbers for several characters at once, who has a buffer, how much, from which effect, and whether a fresh grant this round is actually an upgrade, and doing that math correctly under time pressure for four or five characters is genuinely easy to get wrong.

That bookkeeping is exactly the kind of thing StoryRoll's AI Game Master handles without anyone having to flag it. When a character would gain more while already holding some, the narration resolves the comparison automatically. Nobody has to remember whether the warlock's Armor of Agathys was cast before or after the bard's Heroism, or do mental math mid-combat to figure out which number survives. The pool updates to whichever amount actually applies, and play keeps moving.

That doesn't take any decision away from the table. A player still chooses when to cast the buff, still chooses whether it's worth casting at all if an ally already has a bigger pool going. What disappears is the five minutes of "wait, does that add up or not" that used to interrupt the fight to settle.

Frequently Asked Questions

Do temporary hit points stack in D&D 5e?

No. If you already have temporary hit points and gain more, you don't add the two amounts together. You choose to either keep your current temporary hit points or replace them with the new amount, whichever you'd rather have.

What happens if you already have temporary hit points and gain more from the same spell?

The source doesn't matter. Whether the second grant comes from the same spell, a different spell, or a class feature, the rule is identical: compare the two amounts and keep the higher one. You never end up with both added together.

Can temporary hit points exceed your hit point maximum?

Yes. Temporary hit points are a separate pool layered on top of your real hit points, so a character can sit well above their stated maximum while they last. They aren't real hit points, just a buffer that absorbs damage first.

Do temporary hit points stop you from dying or being knocked unconscious?

Not by themselves. Temporary hit points absorb damage before your real hit points take any, which can prevent you from dropping to 0 in the first place. But once they're gone, damage hits your actual hit points normally, and temporary hit points never revive an unconscious character or heal lost hit points.

Did the 2024 D&D rules change how temporary hit points work?

No. The no-stacking rule is unchanged from the 2014 rules: multiple sources of temporary hit points never combine, and a new grant means choosing between what you have and what you're being offered.

What's the difference between temporary hit points and healing?

Healing restores lost hit points up to your maximum and can bring an unconscious character back up with enough points. Temporary hit points are an entirely separate pool added on top of your current total; they don't restore anything you've lost, they just absorb damage before your real hit points do.

Temporary hit points show up constantly alongside the other binary, easy-to-misjudge mechanics in combat: advantage and disadvantage work the same way, a flat state rather than a stacking bonus, and death saves, concentration checks, and knowing whether your party needs a dedicated healer all get easier once the hit point math at the table stops being a point of debate.