Knight vs Pawn

A lone knight draws against a lone pawn far more often than beginners expect: it does not need to capture the pawn, only to control one square on its path, and its checks constantly steal tempi from the escorting king. The knight holds every pawn that has not yet reached the seventh rank, and even stops most pawns on the seventh with the blockade dance shown below. The single systematic exception is the rook pawn on the seventh: at the edge of the board the knight's wheel breaks down, and only a precisely timed corner sacrifice — which works only when the defending king is close enough — saves the game. Every one of these results is tablebase-verified.

This little ending decides real games constantly, because it is the residue of every pawn race in a knight endgame: one side promotes or wins the last pawn, the other side's knight must cope with the survivor. Knowing exactly which cases draw tells you, many moves earlier, which races you can afford to enter.

The Catching Rules

The bishop stops a distant passer by aiming at it; the knight must physically get there, so its catching arithmetic is stricter — but more generous than it looks, for two reasons.

First, the knight does not need to catch the pawn; it needs to reach any square on the pawn's remaining path, or a square controlling one. A knight sitting on the pawn's path is immovable by the king alone in front of a non-rook pawn: chase it, and it hops to another square that keeps control. So when you count, count to the path, not to the pawn. Unlike the king with its square rule, the knight has no tidy geometric shortcut — you count hops — but the target being a whole file of squares rather than one running pawn is what makes the knight's reach surprisingly long.

Second, checks are free tempi. A knight that arrives "too late" by raw counting often arrives exactly on time because the escorting king had to waste moves stepping out of checks or shielding its pawn. Watch a knight on g8 — the far corner of the board — hold an a-pawn already on its fifth rank, escorted by its king:

1...Ne7! 2.a6 Nc8! and the knight has already done it — from c8 it guards a7, so the pawn cannot advance. Now watch the ladder work: 3.Kc6 Kg2 4.Kb7 (finally evicting the knight) 4...Nd6+! 5.Kc7 Nb5+! 6.Kb6 Nd6, and if White ever plays 7.a7, then 7...Nc8+! — a check that is simultaneously a fork of king and pawn — wins the runner outright. The white king can never escape the wheel of checks and shepherd the pawn at the same time; that double duty is precisely the tempo the knight keeps stealing. This dance around an advanced pawn, checking and returning, is the signature knight resource, and it is why "the knight is two moves away, the pawn queens" is so often a miscount.

The Blockade Dance on the Seventh

Even a pawn one step from promotion, king at its side, cannot break a well-placed knight — as long as the pawn is not a rook pawn. White: Kf7, pawn e7. Black: Ne8, Kh1 — the defending king might as well be on the moon. Black to move, and the tablebase confirms the draw:

1...Nd6+! 2.Ke6 Ne8! 3.Kf7 Nd6+ 4.Kf6 Ne8+! 5.Kf7 Nd6+ and the position repeats forever. The mechanism deserves a close look: the knight uses exactly two squares, d6 and e8, one of which is the blockade square and the other of which attacks the king whenever it approaches. Every time the white king touches the knight, the knight either checks or reoccupies e8, and the king can never cover both squares at once. Every pawn from the b-file to the g-file is held by some version of this defense — near the edge the details shift toward check-and-fork tricks rather than the pure shuttle, but the verdict stands — which is the precise sense in which a lone knight "stops any pawn on the seventh except the rook pawn."

The Rook-Pawn Corner Problem

Now put the pawn on a7 and watch the same machinery seize up. The squares from which a knight can guard a8 are b6 and c7 — both adjacent to the pawn, both instantly coverable by the escorting king, and the board edge has amputated the far half of the knight's wheel, so there is no second shuttle square. White: Kb7, pawn a7. Black: Nb6, Kh1. Black to move loses:

The knight's best try is the corner sacrifice 1...Na8!, hoping for imprisonment tricks — but with the black king a continent away, White simply plays 2.Kxa8 Kg2 3.Kb8 Kf3 4.a8=Q and promotes by unburying the king. Note that White must be slightly careful even here: the king that captures on a8 stands in front of its own pawn, and needs a tempo to step out — which is exactly the crack the defense exploits when the black king is closer.

How much closer? Two files closer is enough. Same position, but the black king on d7 instead of h1 — and now the sacrifice saves the game. Black to move draws:

1...Na8! 2.Kxa8 Kc7! and White is stalemated on the spot — the king's only squares, b8 and b7, are both covered, and the pawn cannot move with its own king on a8. Declining the capture does not help: after 2.Ka6 the knight escapes with 2...Nc7+ and returns to its duties. The precise boundary, then: against a rook pawn on the seventh, the knight alone loses; knight plus a defending king near the c7/c8 corner-cage squares draws. When you are the defender heading into this ending, that one fact should steer your king several moves in advance — and when you are the attacker, it tells you to push the a-pawn to the seventh before the enemy king crosses into range, and to keep your own king off a8 until the coast is clear.

For completeness: a rook pawn that has only reached the sixth is still held by the knight alone (also tablebase-verified — the knight has time to set up the a7 net and start the ladder), so the corner problem is genuinely a seventh-rank phenomenon.

From One Pawn to the Full Knight Ending

Keep this page's results filed as the endpoints of bigger fights. Add a knight for the attacker and you get knight and pawn vs knight, where these same catching rules decide whether the defender may simply give his knight for the pawn. Add pawns for both sides and you are in the world of knight endgames proper, where every race calculation silently assumes you know which lone-knight-versus-pawn positions hold. And the strange corner behavior of knights near rook pawns echoes in one more classic spot: the famous two knights vs king ending, where — in the theory built around the Troitsky line — an enemy pawn's existence is precisely what makes mate possible. The knight is the strangest piece in chess; endings like these are where its strangeness becomes exact science.

Frequently Asked Questions

Can a knight stop a passed pawn by itself?

Yes, in most positions. The knight only needs to control one square on the pawn's path, and it holds any pawn that has not reached the seventh rank, plus every non-rook pawn on the seventh via the two-square blockade dance. The lone exception is a rook pawn on the seventh supported by its king.

Why is the rook pawn on the seventh special?

A knight guards the corner promotion square only from two squares, both adjacent to the pawn and easily covered by the escorting king, and the board edge removes the knight's alternative squares. The central-pawn shuttle between the blockade square and a checking square simply does not exist in the corner.

When does the corner sacrifice Na8 save the draw?

When the defending king is close enough to build the stalemate cage — in the standard position, close enough to reach c7 right after the enemy king captures on a8. The attacking king then has no legal move: its pawn blocks a7-a8 and the defending king covers b7 and b8. With the defending king far away, the attacker just captures, steps out, and promotes.

How do knight checks gain tempi against a passed pawn?

The escorting king must simultaneously shield its pawn and escape the checks, and those two jobs constantly conflict. Each check either drives the king off its best square or lures it onto a square where the next check forks king and pawn. That stolen time is why knights catch pawns that raw move-counting says are uncatchable.

Is there a square rule for knights like the one for kings?

No — the king's square rule works because king distance is simple geometry, while knight distance is irregular. You have to count actual knight moves, remembering that the target is any square on the pawn's path and that every check along the way effectively subtracts a tempo from the pawn's count.

Does the knight draw these endings even with its own king far away?

Against any pawn up to the sixth rank, and against non-rook pawns on the seventh: yes, completely alone. The defending king's proximity only becomes the deciding factor in the rook-pawn-on-the-seventh case, where the corner sacrifice needs the king's help to become a stalemate.