Chess engines are usually configured with either a depth or a node limit. The two settings sound similar and are often used as if they mean the same thing. They do not. Understanding the difference makes analysis faster and credit estimates more honest.
What depth means
Depth is measured in plies. Depth 18 means the engine has completed a principal variation of about 18 half-moves. It does not mean every line has been searched to exactly 18 plies. Pruning means some branches are abandoned early and others are extended.
Depth is a useful target because it is stable across positions. It is also a target, not a guarantee: a forced mate may be found at depth 12, while a quiet middlegame at depth 18 may still be unresolved.
What nodes mean
A node is one position visited by the search. Nodes measure work, so they are the fairest way to bill engine time. Two positions searched to the same depth can use wildly different node counts. A tactical position with many checks may need far more nodes than a locked pawn structure.
This is why node-based pricing is common: it charges for the computation actually performed rather than the label on the search.
Why use both?
If you ask for depth 25 with no other limit, a difficult position can run for minutes. If you ask for a fixed number of nodes, the search may stop before it reaches the depth you wanted. A practical review uses both: a target depth and a conservative node ceiling. The engine stops at whichever comes first.
On ChessUrge, game reviews ask for a target depth and apply a per-depth node cap. The maximum cost is shown before the review starts. If the engine finishes below the cap, the unused nodes are refunded.
A rough guide
- Depth 10–12: quick blunder check, opening ideas, simple tactics.
- Depth 14–18: useful club-level review and most position analysis.
- Depth 19–22: deeper middlegame work, tougher positional decisions.
- Depth 23+: specialist analysis, endgame study and long-running reviews.
These are targets, not guarantees. The position always decides how much work is required. If you only remember one thing, remember this: depth tells the engine where to aim; nodes tell it when to stop.
Try both settings on the analysis board and compare the lines at the same position.
Frequently asked
Is higher depth always stronger?
Usually, but not always. A deeper search can still choose a practically difficult move, and some positions are decided by tablebase knowledge or opening theory rather than raw depth.
Why did my depth-20 search stop at depth 17?
A node cap or a time limit stopped it early. The engine reports the depth actually reached, not the depth requested.
See the whole game, not just the blunder.
Choose a review depth, see the maximum cost, and get move-by-move accuracy with blunder, mistake and inaccuracy markers.