Poison Counters in MTG

A player who has ten or more poison counters loses the game. That number does not care how much life the player has left. A player can be sitting at 40 life in Commander and still lose immediately if they reach their tenth poison counter. That is what makes poison feel so threatening compared with ordinary combat damage.

Poison counters stay on the player until the game ends. They are not damage that wears off at end of turn, and they are not reduced by life gain. Once a player has four poison counters, they stay at four unless a card specifically says otherwise. This persistence makes every early poison hit matter, even if it looked small at the time.

Poison is not a side note to life totals. It is its own loss condition, just like commander damage is its own loss condition in Commander.

Players often mix up infect and toxic because both can lead to poison counters. Infect changes how damage works. A creature with infect dealing damage to a player causes that many poison counters instead of normal life loss. If a 3 power infect creature hits a player, that player gets three poison counters and does not lose 3 life from that combat damage.

Toxic works differently. A creature with toxic still deals ordinary combat damage, but when it connects with a player, that player also gets poison counters equal to the toxic value. So a 2 power creature with toxic 1 deals 2 combat damage and also gives 1 poison counter. Toxic does not replace the damage event the way infect does.

Then there is proliferate. Proliferate does not create poison counters from nothing. Instead, it adds another poison counter to players who already have one or more. That means a player at 9 poison can easily die to a single proliferate effect, even if no creature connected in combat that turn.

If your table is tracking both poison and combat-based threats, compare this guide with the commander damage rules guide. If you are building an infect or toxic deck and want to estimate how often you open a pressure piece, the hypergeometric calculator can help.

Commander begins at 40 life, so ordinary damage strategies often need time to close a game. Poison ignores that larger starting buffer because the loss threshold stays at ten counters. That is why even a few poison hits can change a pod's politics immediately. A player at 6 poison may still look healthy on life, but the whole table knows they are one or two clean attacks away from losing.

Poison also compresses decision-making. A player at 8 poison has to respect almost every proliferate effect, evasive infect creature, or toxic attack. The danger is not theoretical anymore. It is immediate. That pressure can force blocks, removal spells, or alliances that would not happen in an ordinary damage race.

At the same time, poison does not make life totals irrelevant. Toxic creatures still deal combat damage normally, and infect decks often need help from regular combat, pump spells, or proliferate to finish the job. The strongest poison decks usually win because they combine several small edges, not because every card says poison on it.

The simplest method is one dedicated poison counter for each player. Do not fold poison into life and do not try to remember it mentally. In Commander, poison kills at ten, so even moving from 2 to 4 changes how the table has to evaluate blocks and attacks. A visible counter prevents mistakes and makes threat assessment fairer.

It also helps to separate poison from other alternate loss conditions. A player can be at 14 life, 7 poison, and 16 commander damage from one source. Those are three different danger meters. Mixing them together leads to bad decisions. A good tracker keeps each one distinct so players can make the right combat and removal choices in the moment.

If you want the broader context for why Commander starts at 40 while poison still kills at ten, read the starting life totals guide. For actual gameplay, go back to the main MTG Commander tracker and record poison separately for each player.

Poison creates a different social pressure than normal combat damage. Players often ignore a few lost life points because they expect to recover later. They do not ignore six poison counters. Once someone is halfway to ten, every proliferate trigger and every evasive hit becomes a table-wide concern. That often changes who gets attacked, which removal spell gets used first, and which player becomes the political center of the pod.

This is one reason poison decks tend to draw attention even when they are not yet winning. The visible countdown is short, the counters do not go away, and the table knows one burst turn can end the game. Understanding that pressure helps both poison pilots and the players trying to defend against them.

Usually, no. Most games play out as if poison is permanent because very few cards remove poison counters from players. That scarcity is a big part of why poison matters so much. Once the counters are there, players generally have to stop the poison deck from connecting again instead of expecting to clean the total up later with ordinary resource recovery.

This is also why early poison hits are more valuable than many players realize. A single toxic creature that sneaks in twice may not look impressive at first, but it permanently changes the math for the rest of the table. Proliferate cards, evasive infect threats, and pump spells all get more dangerous once those first counters exist.

Poison usually feels fair when the table has time to interact before the count gets too high. A player at one or two poison still has a lot of room to answer the board, manage proliferate pieces, or redirect attacks politically. Problems start when the poison deck gets a burst turn and jumps a player from four to eight or from eight to lethal in one sequence.

That is why strong poison decks often mix several pressure tools instead of relying on just one big infect creature. Small toxic hits, one proliferate trigger, and a surprise combat pump can add up quickly. If your table wants cleaner games, track poison openly and treat the first few counters as an early warning, not as harmless chip damage.