How do I balance one powerful enemy against many weaker enemies in a tabletop RPG?

What action economy counts

Action economy is the number of useful things each side can do in a round. Keep three levels separate. A turn is one combatant's slot in the initiative order. An action is one choice made in that turn, such as attacking, casting or dashing. An attack is a single roll resolved inside an action, so an action that grants several attacks can partly fail and still partly succeed.

When judging a disabling effect, read its own wording rather than assuming it removes a whole turn. Note exactly which attacks or other actions it prevents, whether it also stops movement, bonus actions, reactions or off-turn abilities, and when it ends. Count an action as effective only if it can change the fight from the positions on the table: reach a target, impose a condition, protect an objective, or force the other side to spend an action in reply. Ten attacks that cannot reach anyone are not ten effective actions.

One powerful enemy against the party

A solo enemy concentrates its threat in one body. That shape has a clear strength and a predictable weakness:

• One activation carries the whole threat Against three player characters (PCs), the enemy has one activation while the party has three. The worked example below shows what happens in the round a stipulated effect prevents both of its attacks, and what the party paid to impose it.
• Focus fire and control land on one target Every PC can aim at the same creature, and there is nowhere for damage or conditions to spread. High hit points (HP) keep it in the fight longer, but they do not restore an activation in which it could not attack.
• How its damage is packaged matters One design gives the solo enemy a single heavy hit. That version is swingy: a miss does nothing and a critical hit can drop a character at once. A different design spreads similar total damage across several smaller attacks or an area ability. That version is steadier, can threaten more than one character, and keeps some output when one attack misses. Neither follows automatically from being a solo enemy, so judge the stat block you have, not the label.
• Initiative and the first round matter more If the party acts first and can deal heavy damage or land control before the enemy moves, the encounter may be decided early. Note where the enemy starts, whether it can be reached or targeted in round one, and what it can still do if it begins the fight restrained, prone or out of position.
• Ways to give a solo enemy a fair share of the fight Use only what your system actually allows: support creatures that draw fire and act on their own turns, a second objective the party must attend to, terrain that stops the whole party reaching the enemy at once, or defensive features and extra off-turn actions written into that creature's rules. Adding support changes this into the elite and support composition below, which is often the honest fix.

Many weaker opponents against the party

A group spreads its threat across several bodies and turns. Individually weak enemies can still be dangerous together:

• Many turns, many chances Eight weak enemies get eight turns. Several can aim at the same PC, surround a character to cut off retreat, or keep acting after one or two of them fall. Losing one member costs the group one turn out of eight, so its threat degrades gradually rather than vanishing in one round.
• Concentrated attacks add up Judge the group by a round of its attacks against one target, not by one attack in isolation. The worked example below does that sum for a specific character, because a foe that looks harmless alone may not be harmless as the fourth attacker.
• Area attacks and control cut the other way Grouped enemies are exposed to area of effect (AoE) spells and abilities, sweeping attacks and effects that frighten or hold several targets at once. One good area roll can remove several enemy turns at once. Spread the group out, use cover, or accept that exposure as the price of numbers, and tell the players what they can see about the group's formation.
• Morale and objectives keep numbers honest Ordinary opponents rarely fight to the last member. Set a visible point where they check, fall back, surrender or flee: after their leader falls, after half of them are down, or when the thing they were guarding is gone. That gives the party a way to end the fight by changing the situation, not only by removing every HP pool.
• Bookkeeping is a real cost Every separate enemy adds initiative, movement, target choice and HP tracking. If the group is large, share an initiative count for similar enemies, use average damage where your system permits it, or combine similar foes into one squad, as described in the related answer on combining enemies into a squad. Simplification should keep each enemy's position and losses clear enough for player choices to matter.

Why party size matters

The same enemy group is a different encounter against three PCs than against five. Three characters bring fewer actions per round, fewer spells and abilities in reserve, and less cover when one character is down, controlled or out of position. One PC unable to act removes about a third of the party's round. Against five PCs it removes about a fifth, and another character is more likely to have the healing, control or movement needed to answer the problem.

Composition matters as much as headcount. A party of three with an area spell, strong healing and a character who can hold a doorway handles a group differently from three single-target strikers with no healing. List what this party can actually do before you adjust any numbers: who can hit several enemies at once, who can stop an enemy acting, who can restore HP or remove a condition, and who is in trouble if several enemies choose them at once. For the wider question of signalling danger and avoiding a total party kill (TPK), see the related answer on balancing encounters without a TPK.

Encounter-design checklist

Work through these before initiative:

• Start from the encounter-building rules for your system and edition, and note which method you used if you write the encounter down for later.
• List turns per round for each side, then list the attacks, area abilities, reactions and off-turn actions inside those turns, and note what each one can reach.
• For the target each enemy is likely to choose, multiply hit chance by average damage on a hit and add the round up. Do this for several weak enemies aiming at one character as well as for a single powerful enemy.
• Estimate rounds to drop each body the party is likely to focus on, using damage against that body's defences. Re-check after the first likely casualty, area effect or diverted attack, rather than treating a group's combined HP as one pool.
• List the party's area attacks, control effects, healing and ways to remove conditions, and check whether one composition removes the only copy of something the party needs.
• Note terrain, starting positions and any objective besides defeating every enemy. Set a morale point or another way for the fight to end, plus an escape route the party can use if it goes badly.

Common mistakes

• Raising CR until a solo enemy feels strong enough A higher CR usually raises damage and defences on the same single activation. It does not add another body or activation when that enemy is prevented from attacking. Fix the composition or the situation before you fix the statistics.
• Treating the budget as a guarantee An encounter budget estimates statistical weight for an average party in an average position. It does not know that your wizard has one area spell left, that the fighter starts the fight already hurt, or that the enemy begins surrounded. Use the budget to shortlist, then run the action, damage and survival checks in the checklist above. For memorable boss fights as campaign payoffs, rather than balance alone, see the related answer on making a boss fight memorable.