How many moves ahead should I try to calculate, and how do I build that up?
These answers restate the rules implemented by our open-source engine, which follows the WXF laws and is regression-tested against the official 110-diagram repetition casebook. Where an answer refers to a specific position, that position lives on the linked reference page, where the build verifies it against the engine before publishing.
Direct answer
Fewer moves than most players assume, but with far more accuracy. Calculating two or three moves correctly, checking every reasonable reply at each step, beats calculating six moves with gaps in the middle. Build depth gradually: verify short forced sequences completely before stretching into longer, less forcing ones.
Why depth without accuracy is worthless
A ten-move calculation that skips your opponent's best defence at move three is not actually a ten-move calculation, it is a three-move calculation with seven moves of wishful thinking attached. Strong players are not necessarily calculating further than weaker ones; they are far more reliably checking the opponent's best response at every branch rather than only the reply that suits their plan.
A concrete way to build the skill
Practise with forced sequences first, positions where checks or captures leave little choice, since these are easiest to calculate accurately and give clear feedback when you get them wrong. Once short forcing lines feel reliable, extend into quieter positions with more branches, accepting that your accuracy will naturally drop as the tree gets wider, and keep verifying rather than trusting a plausible-looking line.
Related questions
Should I calculate every move this carefully?
No, reserve full calculation for genuinely critical moments; routine moves do not need the same depth of checking.
Does calculation depth matter more than pattern recognition?
They work together; recognising a pattern often shortens how far you actually need to calculate to confirm it.
.