Concentration Rules for Spells

Concentration is one of the most tactically significant mechanics in fifth edition Dungeons & Dragons, shaping how spellcasters build their turns, manage damage, and support their allies. A single concentration slot governs the most powerful ongoing effects in the game — from Bless to Hold Monster to Wall of Force — and understanding exactly how it works separates a functional spellcaster from a frustrating one. These rules pull directly from the Player's Handbook (5th edition, Chapter 10).

Definition and scope

Concentration, as defined in the Player's Handbook (5e, p. 203), is the mental effort required to maintain certain ongoing spell effects. Spells that require concentration say so explicitly in their Duration entry — for example, "Concentration, up to 1 minute." A caster can maintain exactly 1 concentration spell at a time. Casting a second concentration spell ends the first immediately, with no saving throw and no negotiation.

This matters because the most battlefield-shaping spells in the game are concentration spells. Hypnotic Pattern, Fly, Conjure Animals, Polymorph, Banishment — the heaviest hitters on the spellcaster's toolkit are all gated behind this single shared resource. The design is intentional: it prevents a single caster from stacking three or four controlling effects simultaneously and reducing an encounter to a formality.

Spells that don't require concentration — Mage Armor, Spiritual Weapon, Fire Shield — run independently and stack freely. That distinction is worth understanding clearly, because players often assume a spell is concentration when it isn't, or vice versa. The Duration line in the spell description is always the authoritative check. For a broader map of how spell mechanics interconnect, the Key Dimensions and Scopes of DnD page provides useful framing.

How it works

When a caster takes damage while concentrating on a spell, they must make a Constitution saving throw to maintain concentration. The DC is either 10 or half the damage taken, whichever is higher. A caster hit for 30 damage, for instance, rolls against DC 15. This roll uses the standard d20 + Constitution modifier + proficiency bonus if the caster has proficiency in Constitution saves (Wizards generally don't; War Clerics often do).

Concentration also breaks automatically under three specific conditions:

  1. Casting another concentration spell — the new spell immediately replaces the old one.
  2. Incapacitation or death — being knocked unconscious, stunned, paralyzed, or killed ends concentration instantly.
  3. Environmental interference — the Dungeon Master may call for a saving throw when the caster is subjected to extreme environmental disturbance, such as a ship capsizing or a cliff face collapsing (Player's Handbook, p. 203).

Notably, a caster can voluntarily drop concentration at any time, on their turn, with no action required. That flexibility is easy to overlook and occasionally useful — ending a Hypnotic Pattern deliberately to let allies act freely, for instance.

The War Caster feat (Player's Handbook, p. 170) grants advantage on Constitution saving throws to maintain concentration, and the Resilient (Constitution) feat adds proficiency to Constitution saves for characters who lack it. These two options, separately or combined, dramatically reduce the odds of losing concentration under fire. A Wizard with a +3 Constitution modifier and War Caster has roughly a 73% chance of maintaining concentration against a DC 15 check — compared to about 55% without the feat.

Common scenarios

The scenarios where concentration rules most often create table friction tend to cluster around a few recurring situations.

Multiple casters, one target: Two spellcasters can each have a different concentration spell active simultaneously — concentration is per-caster, not per-target. A Druid concentrating on Entangle and a Sorcerer concentrating on Slow can both affect the same group of enemies at once.

Readied spells: A spell cast using the Ready action maintains concentration from the moment it's cast, not from when it's released. If the trigger never occurs, the caster spent their concentration slot on a spell that did nothing. This is a meaningful cost that frequently surprises newer players.

Multiclassing: A character who is both a Paladin and a Sorcerer still has one concentration slot. Paladin auras do not require concentration, but Divine Favor does. Juggling two spell lists against one slot is a central challenge of many multiclass builds. The DnD Frequently Asked Questions page addresses several common multiclass rule questions.

Decision boundaries

The concentration rule creates a consistent design question during play: which spell is worth concentrating on right now, given what this particular encounter demands?

The most practically useful way to think about it is a three-part decision frame:

  1. Duration vs. impact: A spell with a 10-round maximum duration is only as valuable as the caster's ability to maintain it. A 10th-level Fighter in the party throwing three attacks per round may force multiple DC 15+ saves before the spell's effect resolves. Short-duration concentration spells like Thunderwave are not concentration for exactly this reason.

  2. Action economy trade-off: Dropping one concentration spell to cast a better one for a specific moment is almost always correct. Newer players treat concentration as a "set and forget" resource; experienced players treat it as a real-time decision.

  3. Non-concentration alternatives: When a situation is uncertain, non-concentration spells carry zero maintenance risk. A caster positioned behind allies with a stable concentration spell running should consider whether a cantrip or non-concentration option handles the moment more safely than spending a slot on something that might immediately break.

For those still building familiarity with how the broader rule system fits together, the How It Works section maps the foundational mechanics that make decisions like these legible. The How to Get Help for DnD page is also a useful starting point for resolving edge cases at the table.

References