Guide · Updated September 2026
Why was my move a mistake?
By Atulya GuptaA chess move is a mistake when it drops your evaluation compared with the best available move. In practice that happens in a few ways: you hang a piece or pawn, you miss a threat the opponent then carries out, you allow a tactic like a fork, pin or skewer, or you drift into a strategically worse position. To learn why a specific move was a mistake, look at what changed right after it - the engine’s evaluation swing, the opponent’s best reply (the refutation, which usually reveals the point), and the stronger move you had instead. Often the real error is a move or two earlier: the quiet move that left a piece undefended and made the blunder possible. A move explainer grounded in the engine states all of this in plain English so the reason matches the evaluation.
What "a mistake" actually means
Engines grade a move by how much it changes the evaluation compared with the best available move. A small drop is an inaccuracy, a larger one a mistake, a big one a blunder. So "why was it a mistake" really asks: what did the position lose, and what should I have played instead? The label is only the starting point.
Most mistakes fall into a few buckets: you hung a piece or pawn, you missed a threat the opponent then carried out, you allowed a tactic (a fork, pin or skewer), or you drifted into a strategically worse position. Naming which one it was is the actual lesson.
How to work it out yourself
When a move is flagged, first look at the opponent’s best reply - the refutation. That reply usually reveals the point: it grabs the hanging piece, lands the fork, or executes the threat you overlooked. Then look at the engine’s recommended move for you and ask what it does that yours did not. Often the real error is a move or two earlier - the quiet move that left a piece undefended and made the blunder possible.
Doing this by hand is slow, and it is easy to talk yourself into a wrong reason. That is where a grounded explanation helps.
A worked example
Say the engine flags your move 24, Rxd5, as a blunder that swings the evaluation from roughly level to clearly losing. The instinct is to note "do not take on d5" and move on - but that teaches you nothing reusable. Look at the refutation: the opponent replies with a knight fork on f5 that hits your king and the rook, winning the exchange. That is the concrete reason the move failed.
Now rewind. On move 22 you tucked a rook away with a passive Rc7, leaving your knight undefended and your king slightly airy - which is what made the fork possible two moves later. The real lesson is not "avoid Rxd5" but "don’t drift into passive moves that leave pieces undefended." Whenever a review shows a sharp eval drop, scroll back to where the position was still fine and find the quiet move that let the trouble in.
Get a plain-English, engine-grounded answer
The Audit Chess move explainer answers "why was this a mistake" for you in plain English: it runs the position through Stockfish, checks whether a piece is actually hanging with a static exchange evaluation, finds the concrete threat and the refuting line, and only then writes the explanation - so the words match the eval instead of guessing. You get the reason and the better move together, on top of the free move-by-move review.
Because the whole game history is analysed together, you also see whether the same kind of mistake keeps recurring - and you can drill those exact positions as puzzles built from your own blunders. Free, no account, in your browser.
Keep reading
Frequently asked questions
Why was my chess move a mistake?+
Because it dropped your evaluation compared with the best move - usually by hanging a piece, missing a threat, or allowing a tactic. Look at the opponent’s best reply to see what your move gave up.
How can I tell what I should have played instead?+
Compare your move with the engine’s recommended move and the refuting reply to yours. Audit Chess names the better move and explains, in plain English, what your move gave up - grounded in a real Stockfish read.
Is the mistake often earlier than the blunder?+
Yes. The flagged blunder is often where the game became obvious; the real error is a move or two earlier - the quiet move that left a piece undefended or weakened a key square.