Checkmate pattern
Arabian Mate: Rook and Knight in the Corner
Published Updated
The Arabian mate uses a knight and rook to cover one another around a cornered king. In the familiar h8 pattern, a knight on f6 protects a rook on h7 and covers g8; the rook checks along the h-file and controls g7. The name is traditional, but the useful part for calculation is this exact division of squares.
On this page
The anatomy of the pattern
The final picture uses two attacking pieces. The king sits on h8 and the rook on h7 gives check along the file. The knight on f6 does two jobs: it defends the rook, so Kxh7 is illegal, and covers g8. The rook also covers g7 along the rank. Rotate or reflect those relationships and the same geometry works in any corner.
A worked example
A common setup has a rook on the seventh rank and a knight able to check on f6. Below, after 1.Nf6+, Black chooses 1…Kh8 and 2.Rh7# completes the pattern. The alternative 1…Kf8 avoids mate in this position, so the first check does not force the corner.
Try it on the live board
Same position, your move. Play the knight check and the rook mate — and then try 1…Kf8 for Black instead of 1…Kh8 to see the defence in action.
How to set it up and spot it coming
- A rook on the seventh rank (or the enemy back rank) is the pattern’s engine — get it there first.
- Your knight needs a route to f6/f3 with check or with tempo; e4, g4, d5 and h5 are the usual launch squares.
- It works best against a king already pushed to the back rank corner — often after heavy pieces traded off the defender’s counterplay.
- The mirror version mates a queenside-cornered king (knight c6/c3, rook a7/a2) — the geometry is identical.
The defensive resource
In the example above, 1…Kf8 avoids the corner: White can trade the knight for the e8-rook with 2.Nxe8 rather than mate. Earlier defences include contesting the seventh rank, covering the rook’s entry square, exchanging the knight, or creating a safe flight square. In another position, the move away from the corner may be illegal or tactically worse, so calculate all checks and captures rather than treating Kf8 as a universal answer.