Cricket Bowling Action: How to Fix a No-Ball and Stay Legal

A no-ball is one of the most expensive mistakes a bowler can make in limited-overs cricket. It concedes a free hit, costs a legal delivery, and — when it becomes habitual — signals a fundamental flaw in the delivery stride. Most bowlers who bowl no-balls consistently are not making a mental error; they are making a biomechanical one.

Why No-Balls Happen: The Root Causes

There are two types of no-balls in cricket: the front-foot no-ball (the most common) and the back-foot no-ball (rare, but relevant for fast bowlers). This guide focuses on the front-foot variety, which accounts for over 95% of all no-balls at every level of the game.

A front-foot no-ball occurs when any part of the front foot lands beyond the popping crease at the moment of delivery. The key phrase is "at the moment of delivery" — the foot can land behind the crease and slide forward after release, which is legal. The issue is when the stride is so long that the foot is already over the crease on landing.

The three root causes are:

1. Inconsistent run-up length — the bowler's stride pattern changes from delivery to delivery, making the front-foot landing position unpredictable.
2. Overstriding — the bowler is trying to generate extra pace by lengthening the final stride, which pushes the front foot over the crease.
3. Back-foot landing position — if the back foot lands too close to the crease, the bowler has less room to plant the front foot legally.

The Delivery Stride: What Good Mechanics Look Like

The delivery stride is the final stride before release. In a legal delivery, the sequence is:

1. Back foot lands parallel to (or slightly behind) the return crease — this is the pivot point of the action.
2. Front foot lands behind the popping crease — with the heel, toe, or any part of the foot behind the line.
3. Release — the ball is released as the front foot plants.

The distance between the back-foot landing and the front-foot landing is the delivery stride length. For most pace bowlers, this is between 1.2 and 1.6 metres. Spin bowlers typically have a shorter delivery stride of 0.8 to 1.2 metres.

How to Measure and Fix Your No-Ball Problem

Step 1: Mark Your Run-Up Precisely

The most effective fix for habitual no-balls is a precisely marked run-up. Use a tape measure to establish your run-up length from a fixed point (the bowling crease) to your starting position. Mark the starting position with a cone or chalk.

Run up to the crease 10 times without bowling. Have a partner watch where your front foot lands each time. If it lands consistently in the same spot, your run-up is consistent. If it varies by more than 15 cm, your run-up needs recalibrating.

Step 2: Video Your Action from the Side

Set up a camera at stump height, side-on to the bowling crease. Bowl 10 deliveries at match pace. Review the footage frame by frame at the moment of front-foot landing. You should be able to see clearly whether the foot is behind or over the crease.

What to look for:

• Is the heel of the front foot behind the popping crease line?
• Is the front knee bent (good) or locked straight (bad — this causes overstriding)?
• Is the back foot parallel to the return crease, or is it angled toward the batsman (which causes the body to rotate early and pull the front foot forward)?

Step 3: Shorten the Run-Up by Half a Step

If you are bowling no-balls consistently, shorten your run-up by half a step (approximately 30-45 cm). This is counterintuitive — most bowlers fear losing pace — but the reality is that a legal delivery at 85% effort is more effective than a no-ball at 100%.

Bowl 20 deliveries at the new run-up length in the nets. If the no-balls stop, you have found your legal run-up. If they continue, shorten by another half step.

Step 4: Fix the Front-Knee Collapse

A common cause of overstriding is front-knee collapse — the front knee bends excessively at the moment of landing, which allows the body to continue moving forward and pulls the front foot over the crease.

The fix is to strengthen the front leg and focus on a braced front leg at the moment of delivery. The front knee should be slightly bent (not locked straight, which causes back injury) but firm enough to act as a pivot point. Think of the front leg as a post that the rest of the body rotates around.

Drill: Bowl off a shortened run-up (3-4 steps) focusing only on the front-leg brace. Exaggerate the firmness. Once the feeling is established, gradually extend the run-up back to full length.

The Back-Foot No-Ball: A Note for Fast Bowlers

The back-foot no-ball occurs when the back foot lands on or outside the return crease. This is rare but happens to bowlers with a wide delivery stride or those who run in at an angle.

The fix is to adjust the run-up angle so that it approaches the crease more directly (closer to straight-on). A run-up that approaches at more than 15 degrees from straight will naturally push the back foot toward the return crease.

Using Video Analysis to Monitor Progress

The most effective way to eliminate no-balls is to review footage after every net session. The human eye cannot reliably judge front-foot position in real time — even experienced coaches miss no-balls at full pace. Video analysis removes the guesswork.

Set up a fixed camera position for every net session so that comparisons between sessions are valid. After each session, review 5-10 deliveries and check the front-foot landing position. Track progress over time.

SportsReflector's frame-by-frame analysis mode is particularly useful for this — you can scrub through the delivery stride one frame at a time and see exactly where the foot lands relative to the crease.

Key Takeaways

• Most no-balls are caused by an inconsistent run-up or overstriding, not by poor intent.
• Video analysis from a side-on camera at stump height is the most reliable diagnostic tool.
• Shortening the run-up by half a step is the fastest fix for habitual no-balls.
• A braced (not locked) front leg prevents the body from sliding over the crease.
• Review footage after every net session to monitor progress and prevent regression.