Skip to content
Rules5 min

The Dead Ball Law: When the Ball Goes Out of Play

Law 20 of cricket — what constitutes a dead ball, the difference between the ball becoming dead naturally (end of delivery action) and being called dead by an umpire (injury, obstruction, lost ball), which dismissals are valid when the ball is dead, and how the dead ball law interacts with run-outs, overthrows, and wides.

Written by GeoCric EditorialUpdated Invalid Date
ShareShareWhatsAppFacebook

What the Dead Ball Law Covers

Law 20 of the Laws of Cricket defines when the ball is 'in play' versus 'dead' — the distinction that determines whether any action taken during or after the delivery has legal effect. When the ball is in play, runs can be scored, wickets can be taken, and fielders can complete run-outs. When the ball is dead, none of these outcomes are valid — the delivery's consequences freeze at the point the ball became dead.

The ball becomes dead automatically after each delivery in several ways: when it is finally settled in the wicketkeeper's or bowler's hands; when it crosses or pitches over the boundary; when a batsman is dismissed; when the ball lodges in a fielder's clothing or equipment; or when the umpire calls 'over' or 'time'. In all these cases, no deliberate umpire intervention is needed — the ball simply becomes dead by the completion of the natural delivery action.

When an Umpire Calls Dead Ball

An umpire actively calls dead ball (using the appropriate signal — both arms crossed at waist height) in specific circumstances where continuing play would be unfair or unsafe: if the ball lodges in the wicketkeeper's pads; if a fielder's cap or helmet makes contact with the ball in the outfield; if a batsman is distracted by movement or noise from the fielding team; if a significant injury occurs to any player that requires immediate attention; if a dog or other animal enters the field; or if any other interference occurs that was not anticipated by the Laws.

The umpire may also call dead ball if the batsman is not ready and has not left their crease (in the case where a bowler delivers without the batsman being set — though this can also result in a no-ball). The key principle behind umpire-called dead ball is fairness: if an external circumstance has unfairly disadvantaged either team, calling dead ball resets the delivery without penalty.

Overthrows and the Dead Ball Timing Issue

One of the most practically significant applications of the dead ball law involves overthrows — when a fielder's throw at the stumps misses and runs away toward (or over) the boundary. Runs scored from overthrows count as long as the ball is in play. If an overthrow goes to the boundary, the batting team receives 4 runs plus any completed runs the batsmen were making at the moment the fielder released the throw. The dead ball law determines the cutoff: runs in progress at the moment the ball becomes dead (or the moment the overthrow bounces the boundary) are counted; any further running is not.

The 2019 World Cup final overthrow controversy: England's Ben Stokes hit a deflection off his bat during the final over that went for a boundary overthrow, giving England 6 runs total (2 completed + 4 boundary). The fielder's throw hit Stokes's bat unintentionally, but under the Laws of Cricket at the time, all runs counted. The ball was live throughout. After the final, the MCC reviewed the Law and clarified in 2022 (Law 19.8) that where a deflection off the body (not the bat) occurs, only the runs completed before the fielder released the throw should count — a nuanced clarification arising directly from this match.

Dismissals and the Dead Ball

No dismissal can stand if the ball is dead at the moment the wicket-taking event occurs. If the ball becomes dead (e.g., the bowler has already been notified 'over' by the umpire) and a fielder then hits the stumps, the run-out does not count. This creates some edge cases: if a batsman is run out attempting a run and the ball then hits the stumps, but the umpire had already signalled dead ball due to a prior event in the same delivery, the run-out is invalid. The ball's status at the exact moment of the wicket-taking event is determinative.

Frequently asked questions

What happens if the ball hits a fielder's helmet left on the ground?

Under Law 28, if a ball in play hits a fielder's helmet that has been placed on the ground by the fielding team (not on the fielder's head), the batting team is awarded 5 penalty runs in addition to any runs already completed. The ball is NOT called dead at this point — it remains in play after the helmet contact, and runs scored from the field after the helmet contact count normally. The 5 penalty runs are an addition, not a reset.

Can a run-out happen when the ball is dead?

No — a dismissal of any kind (run-out, stumping, caught, bowled, LBW) requires the ball to be in play at the moment the dismissal occurs. If the ball is dead when the stumps are hit, any batting attempt to run is irrelevant — the batsman cannot be given out. This is why fielders appeal immediately after a run-out attempt: the umpire must confirm the ball was still in play at the moment the stumps were broken.

Does a wide ball remain in play?

Yes — a wide ball is in play from the moment it is bowled until it becomes dead in the normal way (reaching the wicketkeeper, crossing the boundary, or the umpire calling dead ball). If a batsman edges a wide into the outfield and runs, those runs plus the wide extra are all counted. The wide call penalises the bowling team with an extra run but does not remove the ball from play — fielding, running, and dismissals can all occur from the moment a wide is called to the moment the ball becomes dead.