Should Your Foot Be Moving Backward When It Lands?
Should your foot be moving backward when it lands?
Yes. At the instant your foot touches down, it should already be moving backward relative to the ground rather than forward or straight down. This backward motion is often called "pawback," a term borrowed from sprint coaching. When the foot is moving rearward at contact, it meets the ground closer to the speed the ground is moving relative to you, which cuts the horizontal braking force you'd otherwise absorb with every step.
The opposite pattern — a foot still moving forward at touchdown — is the signature of overstriding, where the foot lands well ahead of your hips and center of mass. That forward-moving foot acts like a small brake on every stride.
What is pawback, and why does it matter for running economy?
Pawback describes the backward-and-down sweeping action of the foot in the last moments before ground contact, driven mainly by hip extensor activity that decelerates the swinging leg and reverses its direction. Sprint coaches have described this "claw-back" action for decades, and distance-running biomechanists use similar language to describe efficient touchdown mechanics.
Running economy is the amount of oxygen you burn to cover a given distance at a given pace — lower oxygen cost for the same speed means better economy. In theory, less braking at each landing means less work your muscles have to do to re-accelerate your center of mass forward afterward, which should show up as better economy. That said, the evidence directly linking pawback timing to measured running economy in distance runners is thinner than the sprint-coaching literature suggests; most support comes from biomechanical modeling and force-vector reasoning rather than large controlled trials. Treat it as a plausible, well-reasoned mechanism, not a proven economy hack.
How does backward foot motion reduce braking forces at landing?
Think of it in terms of relative velocity. Your foot's horizontal speed relative to the ground at touchdown is roughly your forward running speed minus the backward speed your leg is sweeping underneath you. If your leg swings backward fast enough to nearly cancel out your forward travel speed, the foot meets the ground with very little horizontal velocity relative to the surface — and a foot that isn't moving much relative to the ground can't generate much braking force against it.
If the foot is still moving forward when it lands (the overstriding pattern), the ground pushes back against that forward motion, decelerating your body with every single step. Over a 10K, that's thousands of small braking events stacking up.
What causes a foot to land moving forward instead of backward?
Overstriding is the main mechanical cause. It typically shows up when the lower leg reaches out ahead of the knee and hip at touchdown, often paired with a heel-first landing well in front of the body's center of mass. Contributing factors include:
- Low cadence relative to your natural stride mechanics — many runners land closer to the pawback pattern when cadence sits somewhere in the 165–180 steps-per-minute range, though this varies by height, leg length, and pace, so it's a general reference point rather than a rule.
- Downhill running, where gravity encourages reaching the foot further forward.
- Fatigue, which tends to shorten hip extension range and push the foot further out in front late in a run — see why your foot strike changes when you're tired for more on that drift.
- Trying to "stride out" for speed, a common but counterproductive instinct — reaching further forward with the lower leg doesn't add speed if it also adds braking.
Can you actually see backward foot motion on slow-motion video?
Partially, and it depends heavily on frame rate. The pattern — foot sweeping backward and down just before contact versus foot reaching forward and landing out front — is visible on decent slow-motion footage. The exact speed of that backward sweep, in centimeters per second, is not something a phone video can measure with confidence.
| Capture method | Typical frame rate | What you can reasonably see |
|---|---|---|
| Naked eye | N/A | General stride pattern only |
| Phone standard video | 30 fps | Foot strike position, overall cadence |
| Phone slow-motion | 120–240 fps | Approximate pawback pattern, foot path shape |
| Lab high-speed / motion capture | 1,000+ fps with markers | Precise foot velocity, ground contact time, joint angles |
A tool like StrideIQ, which scores form from a single phone video, can flag whether your foot appears to be reaching forward (overstriding) versus sweeping back before contact, and it measures cadence reliably since that's a simple count of steps over time. It cannot give you a lab-grade foot velocity number at touchdown — that still requires marker-based motion capture or force plates. Use it as a quick pattern check, not a biomechanics report.
Form analysis is also a separate question from foot strike type. A midfoot or forefoot landing (see is toe running bad for you?) often co-occurs with better pawback timing, but foot strike zone and foot velocity at contact are two different variables — you can heel strike with good pawback, and you can forefoot strike while still overstriding.
Does fixing pawback lower injury risk?
This is where you should be careful with confidence. Reducing overstriding and increasing cadence slightly has been shown to reduce loading rates at the knee in some studies, and lower loading rates are theorized to reduce injury risk over time. But foot strike and stride mechanics are only one part of a multifactorial injury picture that includes training load, recovery, footwear, and individual anatomy. If you've dealt with shin or stress-fracture concerns, foot strike and stress fractures covers what the evidence does and doesn't support — and it's mixed enough that no single cue, including pawback, should be treated as a guaranteed fix.
How do you train pawback without overhauling your whole stride?
Drills that emphasize a quick, active foot strike under the hips tend to reinforce the pattern indirectly, rather than by consciously "pulling" the foot back, which can create tension elsewhere.
- A-skips: 3 sets of 20 meters, focusing on a quick down-and-back foot action.
- B-skips: 3 sets of 20 meters, which specifically drill the claw-back motion before ground contact.
- Cadence drills: run 4–6 x 60 seconds at 5–10% above your normal cadence using a metronome or watch beep, then return to normal pace.
- Short downhill strides (gentle 2–3% grade): 4–6 x 20 seconds, which naturally encourage a faster leg cycle and discourage reaching the foot out front.
Most runners see these patterns shift gradually over 4–6 weeks of consistent drill work rather than overnight, and cadence itself can drift as a run goes on — cadence drift during a run is worth understanding if you're tracking this over long efforts rather than short clips.
What can video analysis NOT tell you about foot speed at landing?
A single phone-video clip, even at high frame rate, has real limits. It can't give you a precise foot velocity in cm/s, true joint angles, or ground-contact time with lab-level accuracy — those require high-speed multi-camera setups or force plates, the kind you'd find in a formal gait lab. A short clip also only captures a snapshot; it won't show how your pattern drifts over the back half of a long run, when fatigue is most likely to push your foot forward.
Form cues and drills are general guidance, not a treatment plan. If you're dealing with pain, a suspected stress fracture, or a nagging injury, see a physical therapist or sports medicine physician for an individualized assessment rather than relying on a cue or a video score. This article, and tools like StrideIQ, are meant for general technique feedback for healthy runners — not diagnosis.
Frequently Asked Questions
What is pawback in running?
Pawback is the backward-and-down sweeping motion of the foot in the moments just before it touches the ground. It's driven by the hip extensors decelerating and reversing the swinging leg, and it reduces how much the foot is moving forward relative to the ground at contact.
Do I need to consciously try to pull my foot back?
Not usually. Actively yanking the foot backward can create extra tension and disrupt your natural rhythm. Most coaches recommend training it indirectly through drills like A-skips and B-skips, and by nudging cadence up slightly, rather than consciously forcing the motion.
Is heel striking the same thing as landing with your foot moving forward?
No, they're related but not identical. Heel striking describes where on your foot you land; landing with the foot still moving forward describes overstriding. You can heel strike with decent pawback timing, and you can land on your midfoot while still reaching your leg out too far ahead of your hips.
Does cadence affect pawback?
Often, yes. Runners with a lower cadence tend to take longer strides and reach the foot further forward, which usually means the foot is still moving forward at contact. Increasing cadence slightly, without changing pace, tends to shorten stride length and bring the foot down closer to under the hips.
Can a phone video measure exactly how fast my foot is moving backward at landing?
Not precisely. A phone video, even at 120-240 fps, can show you the general pattern — whether your foot appears to sweep back or reach forward before touchdown — but it can't produce a lab-grade velocity number. That level of precision requires marker-based motion capture or force plates.
Sources
- Medicine & Science in Sports & Exercise — "Effects of Step Rate Manipulation on Joint Mechanics During Running (Heiderscheit et al., 2011)"
- Nature — "Foot Strike Patterns and Collision Forces in Habitually Barefoot Versus Shod Runners (Lieberman et al., 2010)"
- American Academy of Orthopaedic Surgeons — "OrthoInfo: Running and Overuse Injury Prevention"
- USA Track & Field — "Coaching Education Program: Sprint and Distance Running Mechanics"
- British Journal of Sports Medicine — "Running Retraining and Injury Risk in Recreational Runners"