Chessy
The Knight Fork
White's knight on d5 can leap to a single square that checks the king and attacks the rook at the same time — only one of them can be saved. Find it below.
Find the winning move, then play on against the engine
Free, no signup — you play white, the engine adapts to your level.
You just won the rook with a knight fork. Create a free Chessy account to keep drilling tactics against a real engine — with an AI coach that shows you every fork you missed.
Create a free account →The position: fork wins the rook
White to move. White knight on d5; Black king on g8, Black rook on e8. 1.Nf6+ is the fork. The knight checks the king on g8 and simultaneously attacks the rook on e8. Black must deal with the check — after 1...Kf8, White plays 2.Nxe8, winning the rook and entering a winning endgame. The knight attacked two pieces at once; Black could only protect one.
Why knight forks are so dangerous
The knight is the only piece that jumps over others and attacks in an L-shape. This makes its forks almost impossible to see coming until it's too late:
- The knight threatens squares that aren't on any file, rank, or diagonal — no line of sight gives it away.
- A knight that forks the king forces an immediate response, so the second piece is nearly always lost.
- Forks that include the king (called royal forks) are especially lethal: the check must be answered, and then the material drops.
How to spot a fork before you play it
Before moving your knight, run this quick check:
- Where can this knight land? List all squares it can reach in one or two hops.
- Which of those squares attacks two enemy pieces? A check + any other piece = likely free material.
- Can the opponent block, capture the knight, or interpose? If not, the fork works.
The key habit is visualising the knight's reach as a fixed pattern — the 8 squares it can land on — rather than chasing lines.
How to avoid being forked
Knight forks often land on outpost squares — squares the opponent can't challenge with pawns. Before developing pieces, ask:
- Is my king aligned with another major piece on a square the enemy knight can reach? King on g8, rook on e8 — both reachable from f6 and d7.
- Can I break the knight's outpost with a pawn push? Kicking it away eliminates the threat before the fork lands.
- After a check, does my forced king move put it in a fork on the very next move? Calculate one step further before moving.
Frequently asked questions
What is a knight fork?
A knight fork is a tactic where a single knight move attacks two or more enemy pieces simultaneously. Because only one can be saved, the other is usually captured for free.
What makes the royal fork especially strong?
A royal fork includes the king, which must move — leaving the other forked piece (often a rook or queen) completely undefended. The player being forked has no choice but to lose material.
How do you calculate knight forks?
Visualise all eight squares a knight can reach from its current position. Then do the same for any square it can reach in two hops. Wherever two enemy pieces land within that range, a fork may be possible.
Can a knight fork be defended against once it happens?
Rarely. If the fork checks the king, you must move the king first, and then the second piece falls. The best defence is to see the fork coming and reposition your pieces so they can't both be hit from the same square.