Facing the London System: When Your Opponent Plays Nh5

ECO D02 564 games Stockfish +0.32

The London System is famous for being solid and hard to attack. So when your opponent plays 3...Nh5, chasing your bishop, it can feel tempting to grab space or lash out. But here's the truth: Stockfish gives this position +0.32, a small edge for White. That means you are slightly worse if you don't know what you're doing. The good news? In the 564 real games played from this exact spot, Black actually scores 45.2% – nearly even. The difference comes down to one decision: whether you know the right square for your knight, or fall into the most common trap. Jump into the drill below to test yourself before your next game.

Practice playing against the London System: Nh5

Free, no signup — you play black, the engine adapts to your level.

Ready to put this knowledge into practice? Fire up the board and drill the position after 1.d4 d5 2.Nf3 Nf6 3.Bf4 Nh5 4.Bc1. Try the engine's top choice: retreat with Nf6 and reach a comfortable middlegame.

Create a free account →

The Big Idea: Don't Chase, Develop

The move 3...Nh5 looks aggressive – you're attacking White's unguarded bishop on f4. But White simply retreats with 4.Bc1, and now your knight is stuck on the rim. A knight on h5 is out of play: it attacks nothing important, controls no central squares, and can be kicked away at any time. Your job now is to admit the plan didn't work and bring the knight back to useful territory. The database shows that players who stubbornly keep the knight on the rim (or develop badly around it) score significantly worse than those who retreat immediately.

The Engine's Recommendation: Bite the Bullet

Stockfish's top move here is Nf6, returning the knight to its original square. Yes, you just moved it twice – but the engine values central control over tempo. After Nf6, White's most dangerous follow-up is c4 dxc4 e3, aiming to recapture on c4 with the bishop and build a strong centre. In the 70 games where Black played this retreat, White scored only 41.4% – the second-lowest White score among all main continuations. That's a huge practical success rate for Black. Retreating is not cowardly; it's the most principled way to reach a comfortable middlegame.

Avoid the Biggest Mistake: Bg4

The most common natural-looking move here is Bg4, pinning White's knight on f3 against the queen. But according to Stockfish, Bg4 is a clear mistake – it loses roughly 1.0 pawns in evaluation. Why? Because White can respond with c4, h3, and later d5, breaking open the centre with your knight misplaced and your bishop vulnerable. Across 85 games, White scores 44.7% with Bg4 – better than against Nf6, but not great for Black. The move that was better (the engine says) was ...Nf6. So when you feel the urge to pin, ask yourself: is my knight doing anything useful on h5? If not, bring it back first.

The Database Tells the Story — Which Moves Work?

Across 564 Lichess games from this exact position, the most-played response is Nc6 (129 games, White scores 43.4%) – developing a piece while leaving the h5 knight in place. Second is e6 (100 games, White scores 48.0%), which keeps things solid. The engine's favourite Nf6 appears in 70 games with White scoring only 41.4% – the second-lowest White score in the dataset. Bg4 (85 games, White scores 44.7%) is played almost as often as Nf6 but is the engine's top mistake pick. Rounding out the data: g6 (52 games, White 51.9%) and Bf5 (43 games, White 51.2%) both give White a small edge. The clear pattern: immediately returning the knight with Nf6 gives Black the best practical results in this sample.

Your Practical Takeaway for the Board

When you face the Anti-Nimzo-Indian with 3...Nh5, your main job is to bring your knight back or develop quickly enough that the knight's absence doesn't hurt. If you play Nf6 immediately, you will reach a comfortable position where your opponent spent two tempi (Bf4 and Bc1) just to get pushed. That's a small win for you. If you prefer a wider approach, Nc6 and e6 both score respectably, but you must be ready to retreat the knight later if attacked. The one move to avoid is Bg4, which the engine marks as a clear error. Practise the retreat, keep your head, and watch your opponent overreach.

Results across 564 Lichess games

48.4%
6.4%
45.2%
■ White 48.4% ■ Draw 6.4% ■ Black 45.2%
Most-played continuationGamesWhite wins
Nc612943.4%
e610048.0%
Bg48544.7%
Nf67041.4%
g65251.9%
Bf54351.2%

Frequently asked questions

Is Nh5 a bad move for Black in the London System?

Not necessarily — it is a well-known line. The problem comes after White retreats to Bc1. Your knight is now misplaced on the rim. To score well, you need to handle the follow-up correctly. The engine recommends returning to Nf6 immediately, which actually gives Black a comfortable position. If you do not know the right plan, you can quickly fall into trouble.

Why does the engine suggest Nf6 even though Black just moved the knight twice?

Tempo is important, but piece quality matters more. A knight on h5 attacks nothing and can be pushed away at any moment. Returning to f6 puts the knight back on its best central square, controlling e4 and d5. In this specific position, the engine values central control over tempo. It is the most principled way to reach a good middlegame.

What is White's best reply if I play Nf6?

The engine's best move after Nf6 is c4, attacking the centre immediately. The line continues c4 dxc4 e3, with White aiming to recapture on c4 with the bishop and build a strong centre. You should be ready for this central break. Black's position remains solid, but you need to know how to handle the pressure.

What should I do if White plays c4 before I retreat my knight?

If White plays c4 while your knight is still on h5, you should consider whether to retreat now or capture on c4. Generally, if White attacks the knight with g3 later, you will have wasted more time. The safest approach remains bringing the knight back to f6, even if White has already played c4. You will reach a normal Queen's Gambit position where your opponent has misused a tempo.