Dead Ball Rules in Cricket: When Does Play Stop?

The phrase "dead ball" appears frequently in cricket commentary, yet it is one of the concepts that casual fans most consistently misunderstand. A dead ball is not just a ball that has stopped moving — it is a specific legal state under the Laws of Cricket that suspends all scoring, all dismissal possibilities, and all other match events.

When the ball is dead, nothing that happens matters. A batsman can be stumped by the wicketkeeper while the ball is dead and it counts for nothing. The fielding side can celebrate a catch during a dead ball situation — and the batsman walks back out.

This guide explains exactly when the ball becomes dead, who can call it dead, what it means for dismissals and scoring, and how T20 cricket's unique pace interacts with dead ball provisions.

---

What is a Dead Ball?

A dead ball is a state in cricket where the ball is no longer in play. During a dead ball, no runs can be scored (except penalty runs), no wickets can be taken, and no other match events (apart from umpire signals for extras or penalties) have any effect.

The ball alternates between two states throughout a match:

• Live (in play): From the moment the bowler begins their delivery stride until the ball becomes dead
• Dead: The period between deliveries and during any interruptions defined by the Laws

Understanding when the ball is live and when it is dead is foundational to understanding cricket. Almost every major rule about scoring, dismissals, and play hinges on whether the ball was live at the time the relevant event occurred.

---

When is the Ball Automatically Dead?

Law 20 of the Laws of Cricket specifies a number of conditions under which the ball becomes dead automatically, without any umpire call. The most important of these are:

1. The ball is finally settled in the wicketkeeper's hands or the bowler's hands. After a delivery has been played, once the wicketkeeper or bowler has the ball settled in their gloves or hand — and play is obviously over — the ball is dead. This is the most common end to each delivery.

2. A boundary is scored. The moment the ball crosses or touches the boundary, the ball is dead. Any runs attempted during the ball that results in a boundary are cancelled — the boundary four or six is awarded instead.

3. A batsman is dismissed. The ball becomes dead when a batsman is dismissed — but critically, it becomes dead after the dismissal is complete, not before. So a batsman can be caught and then the fielder can drop the ball — but only if the ball was dead at the point of the drop. If the batsman was genuinely caught and then the fielder dropped it while celebrating, that does not un-do the dismissal because the catch itself completed the dismissal.

4. A penalty is incurred for ball tampering or other specific offences. The ball becomes dead when certain penalty situations arise.

5. An umpire calls "Over." The ball is dead at the end of each over.

---

When Can an Umpire Call Dead Ball?

Beyond the automatic dead ball situations, the on-field umpire can call the ball dead in specific circumstances. These are situations where play must stop immediately to protect a player, prevent unfairness, or deal with an unusual event:

Distraction from outside the field. If a person, animal, or object enters the field and distracts or affects play — a spectator running on, a dog wandering onto the pitch — the umpire can call dead ball to stop play.

Serious injury. If a player is seriously injured during a delivery, the umpire calls dead ball to stop play.

Batsman not ready. If the umpire judges that the batsman had not completed their preparation to receive the ball when the bowler delivered it — for example, the batsman was tying their shoelace — the umpire can call dead ball.

Unfair play. The umpire has general authority to call dead ball when an unfair event occurs that needs to be addressed.

Ball lodged in a fielder's clothing. If the ball becomes lodged in a fielder's clothing or equipment, the umpire calls dead ball.

Ball bouncing off the umpire or a helmet. If the ball strikes the umpire or a fielding team's helmet (on the ground), specific rules about penalty runs and dead ball apply. In the case of the ball hitting the helmet on the ground, five penalty runs are awarded and the ball is immediately called dead.

---

Dead Ball and No-Ball Interaction

The interaction between dead ball and no-ball is important in practice, particularly in T20 cricket.

A no-ball is called by the umpire during the delivery. Until the ball becomes dead — which happens as described above — a no-ball delivery is still live and all running, scoring, and (for limited modes of dismissal including run out) dismissal possibilities remain open.

A key scenario: the bowler delivers a no-ball, the batsman hits it for what appears to be a six over the boundary. The moment the ball crosses the boundary, it is dead. The runs scored are four or six (depending on whether the ball cleared the rope), and the no-ball penalty of one run is also added. The ball being a no-ball does not make it dead earlier — it only becomes dead at the boundary like any other delivery.

The free hit that follows a no-ball in limited-overs cricket also interacts with dead ball in the same way: the free hit delivery is live until the ball becomes dead through the normal mechanisms.

---

Dead Ball Scenarios in Practice

Fielder retrieves ball and throws toward stumps — throw goes wide and reaches the boundary. The delivery is still live during the running and the throw. If the throw goes to the boundary, the ball is dead at the boundary. The batting side receives overthrow runs. If the batsmen had completed three runs before the ball reached the boundary, they get four runs total (three runs plus the boundary overthrow).

Batsman is stumped, but the ball is simultaneously called dead. If a umpire has called dead ball — for example, because a player outside the field distracted play — at the moment before the stumping is completed, the stumping does not count. The dead ball declaration takes priority.

Umpire calls dead ball while the batsmen are mid-run. All run attempts are cancelled. No runs are scored from that delivery (unless there was a no-ball penalty already called, in which case that penalty run still applies). The batsmen return to their respective ends.

Ball lodges in the wicketkeeper's pads. The umpire calls dead ball. Any runs the batsmen have completed up to that point may or may not be credited — the umpire uses judgment about what would have happened had the ball remained in play. In practice, the umpire typically awards any runs already completed before the ball became lodged.

---

Does a Dead Ball Cancel a Dismissal?

This is one of the most contested questions in dead ball law. The answer depends on the sequence of events.

If the ball becomes dead before the dismissal is complete, the dismissal is cancelled. For example, if the umpire calls dead ball before the ball reaches the wicketkeeper's gloves (because a distraction occurred), and the wicketkeeper then takes the ball and breaks the stumps, the stumping does not count.

If the dismissal is complete before the ball becomes dead, the dismissal stands. A caught dismissal is complete the moment the fielder has the ball under complete control. At that precise moment, the ball becomes dead. Any subsequent dropping of the ball — during celebration, for instance — does not un-do the dismissal because the ball was dead from the moment the catch was completed.

Run outs have their own timing. A run out is complete when the stumps are broken with the ball while the batsman is short of the crease. If this occurs before the ball is called dead, the run out stands.

This sequencing — does the dismissal complete before or after the dead ball? — is sometimes genuinely ambiguous, and it is one reason why the third umpire's frame-by-frame review capability is so valuable in modern cricket.

---

Dead Ball in T20 and IPL

In T20 cricket and the IPL, the dead ball law has particular relevance in a few specific situations:

Wide balls called above waist height. In T20 cricket, balls above the batsman's waist on the full are called wide — and once the umpire signals wide, the delivery becomes dead and the batsman cannot be dismissed (other than in specific run out scenarios where the batsman was already running). The wide signalling effectively ends the delivery.

Free hit deliveries. On a free hit, the only dismissal available is run out. When the ball is hit to the boundary on a free hit, it becomes dead at the boundary exactly like any other delivery. The batsman cannot be run out once the ball is at the boundary.

Ball hitting LED stumps. The LED stumps used in IPL and many international matches in day-night conditions contain sensors that detect contact. When the ball hits an LED stump, it does not automatically make the ball dead — the ball is only dead when the dismissal (bowled, stumped, run out) is complete. If the ball clips the stumps but does not dislodge the bails, the ball is live and play continues.

Strategic timeouts and drinks breaks. These are not dead ball situations under the Laws — they are scheduled interruptions agreed to by the governing body. However, the practical effect is the same: play stops, the ball is not in play, and no match events occur during the break.

---

Law 20 Explained

Law 20 of the MCC Laws of Cricket is the governing law for dead ball. Its key provisions:

• The ball becomes dead when settled in the wicketkeeper's or bowler's hands at end of play
• The ball becomes dead on a boundary
• The ball becomes dead on the fall of a wicket
• An umpire can call dead ball in the circumstances described above
• The ball is not in play ("dead") at all times between the end of one delivery and the start of the next bowler's delivery stride

Law 20 also specifies that a dead ball cannot be called by a fielder or batsman — only by the umpire (or in the case of automatic dead ball situations, by the circumstances themselves).

---

Quick Reference Table

Scenario	Ball Status
Ball settled in keeper's or bowler's hands	Dead (automatic)
Ball reaches or crosses boundary	Dead (automatic)
Batsman dismissed	Dead (after dismissal is complete)
Umpire calls dead ball (distraction, injury, etc.)	Dead (from moment of call)
Ball hits LED stumps but bails not dislodged	Live — play continues
Ball lodged in fielder's clothing	Dead (umpire calls it)
Ball hits helmet left on field by fielding team	Dead — 5 penalty runs awarded
Drinks break or timeout	Not technically dead ball — scheduled interruption
Between deliveries (end of over, new batsman coming in)	Dead
Wide ball called	Dead for all dismissals except run out

---

Frequently Asked Questions

Can a batsman be run out during a wide ball? Yes. A wide ball is not dead simply because it is called wide. The delivery remains live for running purposes. A batsman can be run out during a wide delivery if they attempt a run and are short of their crease when the stumps are broken. The wide penalty of one run is also added regardless.

If the ball hits the umpire standing in the field, is it dead? No — not automatically. If the ball hits the on-field umpire during play, the ball remains live. However, if the umpire judges that the contact with their body or clothing significantly affected the course of the ball, they can call dead ball. The convention in cricket is that umpires try to stay out of the ball's path, and if they cannot, the situation is assessed case by case.

Does calling dead ball mean the delivery does not count? Not necessarily. The delivery counts (it was bowled). However, the results of that delivery — runs scored, wickets taken — are affected by the dead ball call. A no-ball that is called dead still counts as a no-ball (the penalty run is awarded), but any dismissal or runs from the subsequent play are not credited.

Can dead ball be reviewed via DRS? No. DRS is used to review dismissal decisions — caught, LBW, run out, stumping. Whether the ball was dead or live at a particular moment is a factual question that the third umpire can assess using video evidence, but it is not part of the formal DRS review process. The on-field umpires rule on dead ball calls, and the third umpire may assist if there is a dispute about timing.

In the IPL, can teams challenge a dead ball call? No. Dead ball calls are not challengeable via DRS in IPL or any other format. Teams can challenge dismissal decisions through DRS, but the administrative dead ball call itself — whether the ball was dead at a given moment — is a matter for the umpires.

---

Conclusion

Dead ball is one of cricket's most foundational concepts — the legal distinction between play being active and play being suspended. Every scoring opportunity, every dismissal, and every major match event hinges on whether the ball was live at the time. Understanding Law 20 gives you the framework to interpret dozens of match events that might otherwise seem ambiguous.

The next time a wicket is taken and the third umpire reviews whether the ball was truly dead at the moment of dismissal, you will understand exactly what is being assessed and why the sequence of events matters so much.

For more cricket rules explained clearly, browse our full cricket rules guide. You may also want to read about fielding restrictions and valid catch rules for other key areas of cricket law.

---

Sources:

• MCC Laws of Cricket — Law 20: Dead Ball
• ICC Playing Conditions
• ESPNcricinfo — Cricket laws explained