More club games are decided by a knight fork than any other tactic. It's the first one worth drilling until you see it without looking — both when it's yours and when it's coming at you. Four to solve are below.
A fork is one move that attacks two things at once. Any piece can do it, but the knight does it best, for two reasons worth understanding, not memorising.
First, the knight jumps to squares nothing else defends the same way — its eight targets are scattered in a ring, and a piece guarding one rarely guards another. Second, a knight check cannot be blocked: against a rook or bishop you can interpose, but against a knight there's nothing to put in the way. The king must move, and while it moves the knight takes whatever else it was hitting.
The most valuable version attacks the king and queen together — the royal fork. The mechanics are the same:
In a real middlegame, both sides developed, White to play — the knight has a square hitting the king on g8 and the queen on c8. Click the knight, then its square.
None of the other pieces mattered: the knight checked from a square the king couldn't answer, and the queen fell. Everything below is the same idea in different clothes.
The pattern isn't tied to one square. Here the king has castled to h8 and the knight jumps to f7 instead — and this time the queen isn't even defended, so it's won outright. White to play:
This is the more important habit. The fork you play is satisfying; the one you walk into loses the game. Train your eye to see it from the other side — here you are Black:
The defensive version saves rating: before you move, check whether your opponent has a knight that could fork your king and queen — or king and rook. Most players only look for their own forks; the stronger habit is looking for the opponent's.
Pair the king with a rook and the same move wins it. The queens are already traded here — the fork just needs two targets a knight's-move apart. White to play:
A fork is just one move attacking two things — neither has to be royal or on the back rank. The knight jumps to d5 and hits both black rooks on b6 and e7. White to play:
Forks aren't a tidied-up-endgame trick. Here's one in the thick of a middlegame: the knight lands on d6 and hits the rook on c8 and the rook on f5. Same idea, more furniture. White to play:
Two habits, in order of importance:
Every position above was checked by an engine: the fork is the single best move and clearly wins. That's the point of drilling clean examples — you learn the shape, then start seeing it in your own games, where nobody labels it for you.
The forks you miss are the same ones you never review. Rookbook reads your Chess.com history and finds the sharpest version of that gap — every forced checkmate you missed, replayable as a puzzle — so the blind spots that hide forks and mates stop being invisible.
Free, no account, and your games never leave your browser.
Find the tactics you missed on rookbook.net →What is a knight fork? One knight move that attacks two enemy pieces at once. Because a knight's targets can't be blocked and are rarely defended by the same piece, the opponent usually can't save both — and when one target is the king, the check forces it.
What is a royal fork? A knight fork that hits the king and queen together. The king must move out of check, and then the knight takes the queen.
How do I stop walking into them? Before each move, look at your own king and ask whether an enemy knight could reach a square that forks it with your queen or a rook. Checking for the opponent's fork matters more than finding your own.