Rook against knight: holding the draw
Rook against knight is drawn when the defenders stay together — and lost surprisingly often when they do not. The knight is the awkward piece to defend with, because it is the one that can be trapped.
The position
White to move.
- 1.Rf5 Ne6 2.Kg3 Kg7.
Why does this work?
A knight separated from its king is in real danger: it moves slowly, it cannot lose a tempo, and a rook can take away its squares one at a time. Keeping it beside the king removes every one of those problems.
That is the difference from the bishop version. A bishop can defend itself from a distance along a diagonal; a knight has to be physically next to help, so the defence is more precise even though the verdict is the same.
Verified as a draw against the tablebase, with each move in the line checked to hold it. The practical lesson is the same as with the bishop: know which endings are drawn before you trade into them.
The same verdict, a harder defence
Rook against knight is drawn, like rook against bishop — but the defence takes more care, and it is lost in practice far more often. The difference is entirely about how the two minor pieces defend themselves.
A bishop can sit far from its king and still be safe along a diagonal. A knight has to be physically beside the king, because on its own it is slow, cannot lose a tempo, and can be cornered by a rook taking its squares one at a time.
What actually loses it
Almost every practical loss comes from the same mistake: the knight wanders. It goes to grab a square or block a check, the rook cuts it off from the king, and then it is trapped — not immediately, but inevitably.
The defensive rule is therefore blunt: keep the knight next to the king and move the king rather than the knight whenever there is a choice.
What the tablebase says about this position
All twenty-one of White’s first moves keep the draw, which is the point of the position: there is nothing to find. The line shown is also more relaxed than it looks. 1.Rf5 leaves the rook where the knight can take it, and 1...Nxf5 would simply be a draw too, since a king and knight cannot mate a bare king.
Of Black’s six legal replies, five hold. The one that loses is 1...Nh5, which sends the knight to the edge, away from its king. That is the whole ending in a single move: the knight leaves its king, and the rook starts taking its squares away.
Notice that even the king moves into the corner, 1...Kh7 and 1...Kh8, hold here, because the knight stays beside the king. In this ending the corner is not the main danger. The distance between king and knight is.
A grandmaster who lost it
Rook against knight is usually a draw, and the standard references name two exceptions: a knight separated from its king and trapped, and a king and knight that are badly placed to begin with. Gata Kamsky against Étienne Bacrot in 2006 shows the first. Bacrot underpromoted a pawn to a knight to avoid being mated, and later lost after letting the knight drift away from his king.
The defensive habit follows directly. Keep the knight within a move of the king, and answer checks with the king rather than by sending the knight out to block them.
What else was playable?
Checked against the tablebase:
- 1.Rf5 (the line shown): A draw, like every other first move. The rook can even be taken: 1...Nxf5 leaves king and knight against king.
- 1...Nh5: The only losing reply. The knight goes to the edge, away from its king.
- 1...Ne6, 1...Ne8, 1...Kh7 or 1...Kh8: All draws: each keeps the knight and king together.
What to take away
- The edge of the board is the knight’s worst place in this ending. 1...Nh5 is the only losing move here for exactly that reason.
- Keep the knight beside its king. Separated, it is the one minor piece a rook can actually trap.
- Prefer king moves to knight moves when both are available — the knight’s position is the thing worth preserving.
- The verdict is a draw, but unlike the bishop version it has to be defended accurately to stay one.
Want a looping version of a position like this? Create an animated chess GIF with the Chess GIF Maker.
Sources
- Syzygy endgame tablebases (via the Lichess tablebase API) — Proven draw, and every move in the line re-checked.
- Pawnless chess endgame — The two exceptions, and Kamsky–Bacrot 2006.
Read next: Rook against bishop: why it is a draw, The Philidor position: third-rank defense, The rule of the square and Minimal Social template.