QUICK ANSWER
The host’s short version
- An all-in player can win only the amount matched from each opponent.
- Build a main pot for chips matched by every remaining player, then one side pot for each additional matched layer.
- When no further betting is possible, every live hand in the main and side pots is tabled without delay.
- Award side pots separately, then the main pot, using the eligible hands for each.
An all-in wager is limited by the shortest stack
A player cannot win more from an opponent than that player put at risk against them. If Player A is all-in for 1,000 and Players B and C each continue for 3,000, only 1,000 from B and 1,000 from C can join A’s 1,000 in the main pot.
The unmatched layers belong in a side pot contested only by the players who contributed to that layer. Keeping the layers separate is the core idea behind every side-pot calculation.
Worked three-player side-pot example
Player A is all-in for 1,000. Player B is all-in for 3,000. Player C covers both players and calls 3,000. Ignore blinds already included in those totals for this simple example.
Award the 4,000 side pot using only B and C’s hands. Then award the 3,000 main pot using A, B and C’s hands. Player A can win the main pot but has no claim on the side pot.
| Pot | Calculation | Amount | Eligible players |
|---|---|---|---|
| Main pot | 1,000 × 3 players | 3,000 | A, B and C |
| Side pot | 2,000 × 2 players | 4,000 | B and C |
| Total | 7,000 |
When should all cards be turned face up?
If at least one player is all-in and every other player in the hand has completed all betting action, all live hands must be tabled immediately. Do not wait for the remaining community cards or for the pots to be awarded.
If two larger stacks still have chips and can bet later streets, their cards stay down because further action remains possible. Once their betting is also complete, table every live hand—including the short stack playing only for the main pot.
A reliable method for building the pots
First, leave all wagers in front of the players so the amounts remain visible. Identify the smallest total, multiply it by the number of contributing players, and move that layer to the main pot. Then repeat with the next-smallest unmatched amount to create the first side pot.
Do not mix side pots together before awarding them. Announce the amount and eligible players for each pot. If the table is confused, write the layers down or use distinct physical areas on the felt.
- Return any completely uncalled amount before building pots.
- Include folded players’ contributed chips, but folded hands are not eligible to win.
- Resolve the final side pot first, then work back to the main pot.
- Split tied pots separately and apply the published odd-chip rule.
Prevent the common side-pot errors
The most common mistake is sweeping every chip into one pile before confirming contributions. The second is allowing the all-in player to muck without showing after all action is complete. The third is comparing a short stack’s hand for a side pot they did not fund.
PokerTimer Next should eventually add a guided side-pot calculator to the live director. Until then, keep the rules desk and a written layer calculation beside the tournament clock.
KEEP THE FIELD STATE VISIBLE
Open the tournament desk
Track the remaining field and live event while the dealer resolves each pot.Use the free toolCOMMON QUESTIONS
Frequently asked questions
Can an all-in player win a side pot?
Only if the player contributed to that side-pot layer. The shortest stack is normally eligible for the main pot but not later side pots funded by larger stacks.
Do all players have to show in an all-in?
In a tournament, all live hands are tabled once at least one player is all-in and all betting action by every other player is complete.
Which pot should be awarded first?
A practical dealing procedure is to award the final side pot first and work back toward the main pot, keeping each pot and its eligible players separate.
SOURCES & METHOD
How this guide was prepared
This is original practical guidance for home and community tournament hosts. Examples are planning ranges, not promises. We review the product workflow, current tournament references, and the operational questions hosts repeatedly need to answer.