What Does a Good Foot Strike Actually Look Like?

A good foot strike lands close to underneath your hips, not several inches out in front of your body, and the shin is close to vertical at the moment your foot touches down. Whether you land on your heel, midfoot, or forefoot matters far less than that one detail: where the foot lands relative to your center of mass.

This surprises a lot of runners who assume "good form" means switching to a forefoot strike. It doesn't. Research on strike patterns hasn't found one pattern that's clearly safer or more efficient across runners — what it has found is that overstriding (landing well ahead of the body with a straightened, braking leg) increases impact loading regardless of which part of the foot hits first.

Does heel, midfoot, or forefoot striking matter more than people think?

Less than the fitness industry has implied for the past 15 years. A widely cited retrospective study of collegiate cross-country runners (Daoud et al., 2012) found injury rates were high in both heel- and forefoot-striking groups, with no strike pattern showing a clear overall injury advantage. Roughly three-quarters of recreational runners land on their heel first, and that's not inherently a problem.

What changes with strike pattern is where forces show up, not whether they're dangerous. Heel striking with an overstride can spike braking forces at the knee. Forefoot and midfoot striking shift more load onto the calf and Achilles, which is one reason some runners who switch abruptly develop calf tightness or Achilles pain — see forefoot striking and calf pain if that's happened to you. Neither pattern is universally better; each redistributes load differently, and your job is to land well within whichever pattern your body naturally uses.

Why does landing under your center of mass matter more than strike pattern?

Because it's the landing position, not the foot part, that determines braking force. When your foot lands ahead of your hips, your lower leg acts like a brake — the ground reaction force has a large horizontal component pushing back against your forward motion. Landing under your center of mass (roughly under your hips, with your foot closer to beneath your knee than in front of it) redirects that force more vertically, which several biomechanics studies link to lower peak impact loading.

This is the core idea behind overstriding, a landing pattern where the foot contacts the ground well in front of the body's center of mass, usually with a straighter leg. It's one of the more consistently discussed risk factors in running injury literature, though it's a contributing factor among several, not a single cause. If you want the mechanics of fixing it, how to stop landing in front of your body walks through the adjustment in more detail.

What does a "level shin" at contact actually mean?

At the instant your foot touches down, a roughly vertical shin (not angled forward from ankle to knee) is a visual proxy for "not overstriding." If you freeze a side-view video at initial contact and draw a line through your shin, a near-vertical line generally means your foot landed close to under your hips. A shin angled forward, with your knee well behind your ankle, usually means the foot landed ahead of your body.

This is a useful visual check, but it's an approximation, not a joint-angle measurement. A phone video at 30 or 60 frames per second can show you the general shin angle at contact; it can't give you a precise degree measurement the way a motion-capture lab can. Use it as a directional signal — "is my shin roughly vertical or clearly angled forward" — rather than chasing a specific number.

How does cadence relate to a good landing?

Cadence — your step rate, counted in steps per minute (spm) from both feet — is the one biomechanical value a single phone video can measure with real confidence, because it's just a matter of counting foot contacts over time. Efficient landings often come packaged with a cadence somewhere in the 170-180 spm range, though this is a general tendency across runners, not a strict target everyone must hit.

The relationship works mechanically: a low cadence, especially under roughly 160 spm at an easy pace, tends to be paired with longer strides and more overstriding, because you're covering the same distance with fewer, bigger steps. Nudging cadence up by 5-10% often shortens stride length slightly and pulls the landing back under the hips without you consciously thinking about foot placement. That's why cadence is a common lever coaches use to fix overstriding indirectly, rather than telling a runner to consciously change their strike pattern.

Metric What a phone video measures well What it estimates roughly What it can't measure reliably
Cadence (spm) Yes — count contacts over time — —
Landing position (under body vs. ahead) — Yes — visual estimate from side view Precise distance in cm
Shin angle at contact — Yes — rough visual angle Exact degrees
Ground contact time — — Yes, needs high-speed/multi-camera capture
Vertical oscillation — — Yes, needs lab-grade motion capture

How can you assess your own foot strike on video?

Film yourself from the side, at true 90 degrees to your direction of travel, ideally at 60fps or higher, over a flat 15-20 meter stretch after a light warm-up (form on tired, cold legs looks different from form mid-run). Check three things frame by frame:

  1. Landing position — pause at initial contact. Is your foot roughly under your hip, or several inches ahead of it?
  2. Shin angle — at that same frame, is your shin close to vertical, or clearly angled forward from ankle to knee?
  3. Cadence — count total foot strikes (both feet) for 30 seconds and multiply by two, or use a metronome app during a short run.

If you hear a distinct slapping sound on contact, that's often a sign the foot is landing with poor control of ankle lowering, sometimes tied to overstriding or weak shin muscles — why does my foot slap when running covers that specifically. And if your legs feel unusually heavy or fatigued partway through easy runs, it's worth checking whether an inefficient landing pattern is part of it, alongside training load and recovery — see why do my legs feel heavy when running.

Apps built for this, including StrideIQ, can score cadence and give a rough visual read on landing position and shin angle from a single side-view clip — useful for a quick self-check between runs, but not a replacement for an in-person gait assessment if you're dealing with a persistent issue.

What can video analysis NOT tell you?

A phone video, however you analyze it, can't measure ground contact time, vertical oscillation, or precise joint angles with lab-grade accuracy — those require high-speed or multi-camera setups, force plates, or 3D motion capture, the kind of equipment found in a running gait lab or a sports medicine clinic. A single side-view clip also can't diagnose why a fault is happening; a slightly forward landing might trace back to weak glutes, ankle mobility limits, or just habit, and that distinction usually needs hands-on assessment.

The evidence on "correct" form is also genuinely mixed. No single strike pattern or cadence number has been shown to prevent injury across all runners, and changing your natural mechanics too quickly, especially strike pattern, carries its own injury risk during the adaptation period. Form feedback is a useful input, not a verdict.

If you have persistent pain, a suspected injury, or you're returning from one, video review is not a substitute for evaluation by a physical therapist or sports medicine physician, who can test strength, mobility, and load tolerance directly. Use video and cadence data to spot patterns worth asking a professional about, not to self-diagnose or self-treat.

Frequently Asked Questions

Is heel striking bad for your knees?

Not inherently. Heel striking is common — most recreational runners do it — and studies haven't shown it causes more injuries than midfoot or forefoot striking overall. What raises knee loading is landing with the foot well ahead of the body (overstriding), which can happen with any strike pattern, including heel strikes.

Should I switch to forefoot striking to run better?

Not necessarily. Switching strike patterns shifts load from the knee toward the calf and Achilles, and abrupt changes are linked to calf and Achilles overuse issues during the transition. There's no strong evidence forefoot striking is safer or more efficient for every runner, so it's not a change to make without a specific reason and a gradual approach.

What cadence should I aim for?

Many efficient runners land somewhere around 170-180 steps per minute, but this is a general tendency, not a universal rule. If your current cadence is well below 160 spm at easy pace, gradually increasing it by 5-10% is a common way to reduce overstriding without changing your strike pattern directly.

Can a phone video accurately measure my foot strike?

A phone video can reliably count cadence and give a reasonable visual estimate of landing position and shin angle at contact. It cannot measure ground contact time, vertical oscillation, or exact joint angles accurately — those need high-speed or multi-camera lab equipment.

Sources