Minimax vs. Alpha-Beta Pruning

Last Updated July 20, 2026

Minimax evaluates every branch in the searched tree. Alpha-Beta uses running bounds to skip branches that cannot change the same final result.

  • Use Minimax when a small tree must be traced completely and every evaluated node needs to remain visible.
  • Use Alpha-Beta Pruning when the same minimax result is required but unnecessary branch evaluations must be reduced.
Same result; Alpha-Beta can reach it with fewer evaluations.

Head-to-Head Showdown

Branch Coverage

Minimax: Full searched tree

Alpha-Beta Pruning: Bound-pruned tree

The Implication: Minimax evaluates every branch included in the search, while Alpha-Beta skips branches already proven unable to change the final result. This allows Alpha-Beta to return the same minimax value with fewer node evaluations when cutoffs occur.

Move Ordering Effect

Minimax: Node count unchanged

Alpha-Beta Pruning: Pruning amount changes

The Implication: Reordering children does not reduce plain Minimax's search because it still evaluates every branch. Strong ordering gives Alpha-Beta earlier cutoffs, while poor ordering can leave its work close to Minimax's O(bd)O(b^d) search.

Pruning State

Minimax: No pruning bounds

Alpha-Beta Pruning: α\alpha and β\beta

The Implication: Minimax must finish the required child evaluations before backing up a node's value. Alpha-Beta carries running bounds and stops a subtree once αβ\alpha \ge \beta proves that further values cannot affect the ancestor's decision.

Selection Criteria

Scenario:Debugging a custom evaluation function on a small tree where every terminal score must be inspected and logged.

Choose Minimax:Minimax evaluates every leaf in the searched tree, so the complete scoring trace remains visible. Alpha-Beta may skip branches that cannot change the result, making it unsuitable when every raw evaluation must be inspected.

Scenario:Building a time-limited chess search where move ordering can expose cutoffs and every avoided node allows more positions to be explored.

Choose Alpha-Beta Pruning:Alpha-Beta can skip branches that cannot change the minimax result, allowing deeper search within the same time budget when ordering produces useful cutoffs. Minimax evaluates the full searched tree regardless of move order, so it spends time on branches Alpha-Beta may safely avoid.

Scenario:Completing a classroom hand-trace that requires every leaf evaluation and every MIN/MAX backup to be written explicitly.

Choose Minimax:Minimax keeps every branch visible, so each backed-up value can be shown in sequence. Alpha-Beta may prune branches whose leaf calculations the exercise explicitly requires.

Side By Side Trace

A depth-2 MAX node RR has two MIN children, BB and CC. BB's leaves are L1=3L1=3 and L2=5L2=5. CC's leaves are L3=2L3=2 and L4=9L4=9. Children are examined left to right: BB before CC, and within each, the left leaf before the right leaf.

R (MAX)
B (MIN)
C (MIN)
3
5
2
9

Step 1: Evaluating L1

Minimax

Descends to BB's first child, L1L1, and evaluates it to 33. No bound is stored since Minimax only compares raw values at BB.

Alpha-Beta Pruning

Descends to BB's first child, L1L1, carrying α=\alpha = -\infty, β=\beta = \infty from RR. Evaluates L1=3L1 = 3; no comparison is possible yet since BB has seen only one child.

Step 2: Evaluating L2 and Closing Out B

Minimax

Evaluates L2=5L2 = 5. BB is a MIN node, so it computes min(3,5)=3\min(3, 5) = 3 and returns 33 up to RR. RR records 33 as its current best.

Alpha-Beta Pruning

Evaluates L2=5L2 = 5. BB computes min(3,5)=3\min(3, 5) = 3 and returns 33 to RR. RR updates α=3\alpha = 3 since RR is a MAX node and 33 exceeds its prior -\infty.

Step 3: Point of Divergence

Minimax

Descends to CC's first child, L3L3, and evaluates it to 22. No bound exists to compare against, so L4L4 is scheduled for evaluation next regardless of this value.

Alpha-Beta Pruning

Descends to CC carrying α=3\alpha = 3 from RR, β=\beta = \infty. Evaluates L3=2L3 = 2; CC updates β=min(,2)=2\beta = \min(\infty, 2) = 2. Checks αβ\alpha \ge \beta: 323 \ge 2 holds, so L4L4 is pruned without being visited.

Step 4: Closing Out C and Returning to R

Minimax

Evaluates L4=9L4 = 9. CC computes min(2,9)=2\min(2, 9) = 2 and returns 22 to RR. RR compares its two children, 33 from BB and 22 from CC, and selects max(3,2)=3\max(3, 2) = 3.

Alpha-Beta Pruning

Skips L4L4 entirely. CC returns its bound value 22 to RR without needing L4L4, since the pruning condition already guarantees CC's true value cannot exceed 22 and therefore cannot beat RR's existing α=3\alpha = 3. RR keeps 33 as its final value.

Final Solved Trees

Minimax

Final utility: 3

R (MAX) [3]
B (MIN) [3]
C (MIN) [2]
3
5
2
9

Alpha-Beta Pruning

Final utility: 3

α:-∞3
β:
R (MAX)
α:-∞
β:3
B (MIN) [3]
α:3
β:2
C (MIN) [2]
3
5
2
9 [PRUNED]

Final Result

Minimax:Minimax returns utility 33 after evaluating all 44 leaves: L1L1, L2L2, L3L3, and L4L4.

Alpha-Beta Pruning:Alpha-Beta returns the identical utility 33 after evaluating only 33 leaves, pruning L4L4 once αβ\alpha \ge \beta held at node CC. The saved evaluation is exactly the branch whose value could not have changed RR's decision.

Common Pitfalls & Exam Mistakes

  • Thinking Alpha-Beta can return a better result than Minimax.

    The Mistake: Students assume that because Alpha-Beta skips branches, it may discover a better move than Minimax or trade accuracy for speed.

    Why It's Wrong: Alpha-Beta returns the same optimal root value as Minimax because it prunes only branches proven unable to change the final decision. With the same depth, evaluation function, legal moves, and tie-breaking policy, both also select the same move; only the evaluated work changes.

  • Treating O(bd/2)O(b^{d/2}) as Alpha-Beta's complexity for every move ordering.

    The Mistake: Students write O(bd/2)O(b^{d/2}) for Alpha-Beta without checking whether the question assumes strong move ordering, random ordering, or worst-case ordering.

    Why It's Wrong: The O(bd/2)O(b^{d/2}) time complexity describes the best case, where strong move ordering causes early cutoffs. With worst-case ordering, Alpha-Beta performs no useful pruning and remains O(bd)O(b^d), matching Minimax's worst-case search cost.

  • Updating α\alpha at MIN nodes and β\beta at MAX nodes.

    The Mistake: Students reverse the bounds during a hand-trace, causing cutoffs at nodes where Alpha-Beta would continue searching.

    Why It's Wrong: α\alpha is updated at MAX nodes because it tracks MAX's best guaranteed value. β\beta is updated at MIN nodes because it tracks MIN's best guaranteed value. A cutoff occurs when αβ\alpha \ge \beta; swapping the updates produces an invalid trace.

Comparative Analysis

AttributeMinimaxAlpha-Beta Pruning
Stored BoundsNoneα\alpha and β\beta
Branch CoverageFull searched treeCutoff-dependent
Cutoff ConditionNoneαβ\alpha \ge \beta
Move Ordering EffectNode count unchangedPruning efficiency changes
Best-Case TimeO(bd)O(b^d)O(bd/2)O(b^{d/2})
Search StyleExhaustive evaluationExact bound pruning

Common Questions & Edge Cases

  • Does Alpha-Beta Pruning return the same result as Minimax?

    Yes. Alpha-Beta Pruning skips only branches proven unable to change the minimax value. With the same depth, evaluation function, legal moves, and tie-breaking policy, both return the same result and selected move.

  • Do Minimax and Alpha-Beta Pruning have the same space complexity?

    Yes. Both commonly use depth-first search storage proportional to the current path and pending successors, often written as O(bd)O(bd) in textbook analysis. Alpha-Beta carries α\alpha and β\beta bounds but does not change the asymptotic space class.

  • Do Minimax and Alpha-Beta Pruning always evaluate the same number of leaf nodes?

    No. Minimax evaluates the full searched tree, while Alpha-Beta may skip subtrees once αβ\alpha \ge \beta proves they cannot affect the result. Under worst-case move ordering, Alpha-Beta performs no useful pruning and evaluates the same leaves as Minimax.

  • Can Alpha-Beta Pruning remove the optimal move that Minimax would select?

    No. A branch is pruned only after current α\alpha and β\beta bounds prove that its remaining values cannot improve the decision at the relevant ancestor. Different selected moves indicate different tie-breaking, depth limits, evaluation functions, legal moves, or an incorrect implementation.

Explore the Algorithms in Action

Open the theory pages or try the interactive solvers for the algorithms compared above.