A rook usually belongs behind a passed pawn because the open file grows as the pawn advances. Behind your own pawn, the rook supports every step toward promotion. Behind an enemy pawn, the rook attacks the runner without standing in its path. This guideline is known as the Tarrasch rule, but checks, captures, and immediate promotion threats still come first.
Use Back and Forward to replay the verified line. The current FEN is copyable at every step. When the geometry is clear, choose Endgame Student or Endgame Master and continue the exact starting position on the full board.
Interactive lesson
Advance with the rook behind the pawn
White to move: use the open file behind the pawn
The rook on e3 supports the e6-pawn from behind. After the pawn advances, the rook can protect it on the new square as long as the file stays clear.
7k/8/4PK2/8/8/4R3/8/7r w - - 0 1Play the rook endgame
Continue from the starting setup and calculate the game from the board in front of you. Choose an endgame opponent and play to the natural result.
What does rook behind a passed pawn mean?
For a White passed pawn, "behind" means a lower rank on the same file. If the pawn is on e6, a white rook on e3 is behind it. For a Black pawn moving toward rank 1, the direction reverses.
The same placement helps both sides for different reasons:
- Behind your own pawn: the rook protects the pawn on its current square while leaving the road to promotion open.
- Behind an enemy pawn: the rook attacks along the pawn's file and can keep contact as the pawn advances.
The lesson starts from 7k/8/4PK2/8/8/4R3/8/7r w - - 0 1. White has a king on f6, a rook on e3, and a pawn on e6. Black has a king on h8 and a rook on h1. The Syzygy tablebase classifies this five-piece position as a win for White.
The compact rule: behind, safe, active. Put the rook behind the passer, check that the square is tactically safe, then choose the most active move available.
Why rear support becomes stronger
At the start, the white rook sees e4, e5, and e6 before it reaches the pawn. After 1.e7!, another square opens between rook and pawn. The rook still protects the runner, but it also gains more working space on the file.
A rook in front of its own pawn has the opposite problem. The pawn cannot move until the rook leaves. Every advance may reduce the rook's space and expose it to attacks. A rook behind the pawn does not create that traffic jam.
Black answers 1...Rf1+, forcing White to deal with a check. White plays 2.Kg6. The king leaves the f-file and keeps the e-file clear between the rook on e3 and the pawn on e7. After 2...Re1 3.e8=Q#, the pawn promotes with checkmate.
The line does not prove that Black will choose these moves in practice. It shows one legal, tablebase-verified route that makes the geometry easy to see. The playable board begins from the original FEN, and the opponent may choose any legal continuation.
Common mistakes and important exceptions
Waiting when the pawn can advance
In the starting position, 1.Ke5? looks natural because the king approaches the centre. Syzygy classifies the resulting position as a draw. White spends a tempo while Black gains time to reorganize. The supported advance 1.e7! keeps the win.
Following the slogan without checking captures
The move 1.Re1?? keeps the white rook on the pawn's file, but Black can take it. Syzygy classifies the position after that move as winning for Black. A good square must also be safe. Before moving a rook behind a pawn, scan checks, captures, and threats.
Assuming a good setup decides the whole ending
Rear support does not replace king activity. In many rook endings, the king must protect the pawn, escape checks, or cut off the opposing king. The rook and pawn are a team, not a complete plan by themselves.
Ignoring positions where activity matters more
The Tarrasch rule is a default, not a law. A forcing check, a rook attack on an unprotected piece, or a promotion race may be more urgent. Some rook-pawn endings also need side checks or a special defensive setup. Calculate the concrete position before improving the rook.
Does the rook also go behind an enemy passed pawn?
Often, yes. A defending rook behind an enemy passer can attack the pawn along its file. If the pawn moves, the rook keeps the same line of attack. The defender may also gain checking chances against the supporting king.
But access matters. If the pawn is already far advanced, the rook may not have time to reach the rear. A check from the side, a blockade from the front, or a rook trade into a drawn pawn ending may be the only practical defence. This is why the memory rule ends with "active," not "automatic."
How to practise the Tarrasch rule
- Find every passed pawn on the board.
- Identify the square directly behind each passer.
- Check whether your rook can reach that file safely.
- Compare the move with forcing checks, captures, and pawn advances.
Replay the lesson until you can explain why 1.e7! is stronger than the waiting move 1.Ke5?. Then choose Endgame Student or Endgame Master. You play White from the exact starting position. Continue from the board in front of you and play to the natural result.
Do not expect the opponent to repeat ...Rf1+. Keep the rook active, answer the checks you actually receive, and recalculate after every move.
Behind, safe, active. A rook behind the passed pawn gains file space as the pawn advances, but the position must still pass a tactical check before you follow the rule.
What to study next
For the broader conversion plan, read the guide to playing rook endgames. When your king reaches the promotion square and checks become the main problem, continue with the Lucena bridge lesson. To learn the defender's waiting method, study the Philidor position.
You can also practise the exact setup and other rook endings in Endgame School.
How this article was checked: Olivers Grants wrote the lesson. Developer and ML researcher Uldis Briedis reviewed the technical implementation. Every SAN move and displayed FEN was replayed with chess.js. The starting position, the full lesson line, 1.Ke5?, and 1.Re1?? were checked with the five-piece Syzygy tablebase.