Hitting the Ball Twice in Cricket: Law 34 Explained
Law 34 lets a batter hit the ball twice only to defend the wicket. Do it for any other reason and you are out 'hit the ball twice'. Here is how the rule works.
A batter may lawfully hit the ball a second time only to defend their wicket — never to score runs. Striking the ball twice for any other purpose, such as steering it for runs, means the batter is out “hit the ball twice” under Law 34 of the MCC Laws of Cricket. It is one of the game’s rarest dismissals.
When a second hit is legal
Law 34 allows exactly one legitimate reason to strike the ball twice: to stop it from rolling onto your stumps. After playing or missing a delivery, if the ball is trickling back toward the wicket, the batter may use the bat (or any part of the body, though hand-on-bat rules apply) to push it away and protect the stumps.
This is purely defensive. The intention must be to guard the wicket, not to gain an advantage. A batter knocking the ball clear of the stumps is acting within the Laws and is not penalised.
When it’s a dismissal
The batter is out “hit the ball twice” if they wilfully strike the ball a second time for any reason other than protecting the wicket — most commonly to flick it away for a run. This is the dismissal in action, and the bowler does not get credit for it (it is recorded against the batter, not the bowler’s analysis).
Note that the first contact must be a legitimate stroke. A batter is not out under this Law if the second contact is to return the ball to a fielder, provided they have the fielding side’s consent.
Can you score runs?
In almost all cases, no. Runs cannot be scored off a deliberate second strike, even when the second hit was a legal act of defending the wicket. The intention of the Law is to remove any incentive to play the ball twice.
The one practical exception involves the boundary or the fielding side: if runs result from an overthrow, or from the act of a fielder after a lawful second strike, those runs may stand. Outside of these specific situations, the ball is effectively dead for run-scoring purposes once it is struck a second time.
| Scenario | Legal? | Outcome |
|---|---|---|
| Hits ball a second time to stop it hitting stumps | Yes | No dismissal, no runs |
| Hits ball a second time to push it away for a run | No | Out “hit the ball twice” |
| Second contact to return ball to fielder (with consent) | Yes | Not out, play continues |
| Runs from an overthrow after a lawful second strike | Yes | Those runs may stand |
How common is it
Extremely rare. “Hit the ball twice” is one of the least-seen dismissals in cricket, alongside “obstructing the field” and “timed out”. Because the only legal second hit is defensive — and umpires accept clear wicket-protection without penalty — instances of a batter being given out this way at the professional level are exceptional. Most players go an entire career without ever seeing it called.
Quick summary: Under Law 34, a batter can strike the ball twice only to defend the wicket. Doing it to score runs gets them out “hit the ball twice” (the same thing as a “double hit”), runs generally cannot be taken off a second strike except in overthrow cases, and the dismissal itself is one of cricket’s rarest.
Frequently asked questions
Can a batter ever legally hit the ball twice?+
Yes. Under Law 34 a batter may lawfully strike the ball a second time only to guard or protect their wicket, never to score runs.
Can you score runs after hitting the ball twice?+
Generally no. Runs cannot be scored off a deliberate second strike. The main exception is when the ball reaches the boundary or runs result from an overthrow or a fielder's act.
How is 'hit the ball twice' different from a 'double hit'?+
They describe the same situation. 'Double hit' is the informal name; 'hit the ball twice' is the official dismissal under Law 34 of the MCC Laws of Cricket.