Photo by Mikhail Nilov on Pexels
You’ve probably seen “strides x4” written into a training plan and skipped over it, assuming it’s something for faster runners. Or you’ve done them without really knowing why — just a few quick bursts at the end of a run because someone told you to. Either way, strides are one of the most underused and misunderstood tools in everyday running training.
They’re not a sprint session. They’re not tempo intervals. They take about six minutes total, they don’t add meaningful fatigue, and they genuinely do make you faster if you use them consistently. This article explains exactly what strides are, how to run them correctly, and where they fit into a real training week — whether you’re building toward a 5K or grinding through marathon prep.
If your running has felt stale, or you’ve been doing easy miles without any sense of sharpness or speed, strides might be the simplest addition you can make right now.
What strides actually are
A stride is a short, controlled acceleration — typically 20 to 30 seconds — where you gradually build to about 90% of your maximum effort, hold it briefly, and then ease off. That’s it. You’re not sprinting flat-out. You’re not trying to hit a specific pace. You’re just running fast, smoothly, and with control.
The full sequence looks like this: 5 seconds building up, 15–20 seconds at close to full speed, 5 seconds winding back down. You then walk or jog for 60–90 seconds before the next one. Most runners do 4 strides per session, which takes roughly 8–10 minutes including the recoveries.
One important distinction: strides are a neuromuscular drill, not a cardiovascular workout. The goal isn’t to raise your heart rate or accumulate fatigue. It’s to remind your legs what fast running feels like — to practise efficient mechanics at speed without the stress of a full interval session.
Why bother if you’re not trying to race fast?
Even if your goal is just to finish a half marathon or run parkrun without stopping, strides are worth doing. Here’s why.
Most recreational runners spend nearly all their time at one pace — slow to moderate. Over time, your legs adapt to that pace and only that pace. Your stride length shortens, your cadence drops slightly, and fast running starts to feel genuinely alien. The first time you try to run faster in a race, your form falls apart because you simply haven’t practised it.
Strides solve this by keeping the fast-running pathway open. They maintain leg turnover, improve your running economy (how efficiently your body uses oxygen at a given pace), and subtly reinforce better form — particularly a more powerful toe-off and upright posture. Research into running economy consistently shows it’s one of the key variables separating faster runners from slower ones, even at the same level of aerobic fitness.
And because strides don’t add meaningful training stress, you can include them almost any week, even a recovery week.
How to run strides correctly
The mechanics matter more than the pace. Here’s what good stride technique looks like:
- Build gradually: don’t launch straight into full speed. The first 5 seconds should feel like you’re shifting through gears.
- Stay relaxed: your shoulders should be down, your hands loose. Tension is the enemy of fast running.
- Run tall: hips forward, slight forward lean from the ankles — not a hunch at the waist.
- Foot strike under your hips: don’t reach forward with your foot. Let it land beneath your centre of mass.
- Wind down smoothly: don’t brake suddenly. Ease off over the last few seconds.
If you’re thinking about cadence during strides, that’s actually useful practice — fast running naturally encourages a quicker turnover. If you’re working on improving your running cadence, strides are one of the most practical ways to feel what a higher cadence actually means for your body.
Don’t worry about tracking the exact pace. Run by feel — “fast but controlled” is the right internal cue. If you finish a stride completely breathless and your form fell apart, you went too hard.
When to do strides in your training week
Strides fit into several different contexts. Here’s a clear breakdown:
| When | Why it works |
|---|---|
| End of an easy run (2–3 times/week) | Adds neuromuscular stimulus without fatiguing you for the next session |
| Before a speed session or race | Activates fast-twitch fibres and primes your legs for hard effort |
| During base-building phases | Keeps fast running familiar when volume is high and intensity is low |
| Recovery weeks | Maintains leg sharpness without adding cardiovascular stress |
| After a long run (occasionally) | Practises running with good form under fatigue — but only do this if you’re feeling strong |
The most common and most useful placement is at the end of an easy run — say your 45-minute Tuesday run. You finish the easy portion, walk for a minute, then run 4 strides with 60–90 seconds jog recovery between each. Done in under 10 minutes.
What you want to avoid: doing strides the day before a long run or a hard interval session if you’re not well-rested. And don’t do them when you’re carrying a niggle — strides put a quick mechanical load through your Achilles, calf, and hamstring, so if anything’s already complaining, hold off.
Where strides fit into specific training plans
If you’re following a structured plan for a 5K or 10K, strides often appear 2–3 times per week. In a marathon plan, they tend to show up 1–2 times per week, mostly to maintain leg speed during high-mileage phases.
For a 5K-focused runner, strides are particularly valuable in the final 4 weeks of sharpening. Running 4 × 25-second strides after your easy runs 3 times per week during that phase genuinely translates to race-day leg speed. The 5K personal best training plan on this site builds them in from week one for exactly this reason.
For marathon runners, the purpose is different. You’re not trying to get faster over 400m — you’re trying to prevent your legs from forgetting what quick turnover feels like after weeks of slow long runs. Adding 4 strides twice a week during your base phase costs almost nothing but keeps the neuromuscular edge sharp.
If you’re a complete beginner who’s still building up to running continuously, strides can wait. Get your easy running base solid first. Once you can run 20–30 minutes without stopping, strides become genuinely useful. Building that aerobic base is the prerequisite — strides are an addition to a foundation, not a replacement for one.
Common mistakes runners make with strides
Going too fast: strides should be 90%, not 100%. If you’re running them at full sprint, you’re adding unnecessary injury risk and defeating the purpose. Think “controlled fast”, not “all-out”.
Skipping the recovery: some runners jog straight into the next stride without recovering. The 60–90 second walk or slow jog between strides isn’t optional — it allows your legs to reset so each stride is mechanically clean.
Counting them as speedwork: strides don’t replace intervals. They complement them. If your plan has a track session on Thursday, doing strides Tuesday doesn’t get you off the hook for Thursday.
Doing too many: 4 strides is the standard. Some runners do up to 6 occasionally. Doing 10 strides turns it into a workout — which is fine if that’s your intention, but it’s no longer the same tool.
Doing them when you’re already tired: strides require a small amount of sharpness. If you’re on your 5th consecutive day of running and your legs feel dead, skip them. They’ll do more harm than good when your form is compromised by fatigue. Running every day has its trade-offs, and strides are one of the things worth pulling back on when recovery is lagging.
How quickly will you notice a difference?
Honestly, most runners feel a difference within 2–3 weeks of adding strides consistently — not in race times yet, but in how easy running feels. Your legs feel livelier at the start of runs. Your natural pace on easy days tends to creep up slightly without extra effort. Turnover feels less forced when you pick it up.
Measurable race-day improvement takes longer — typically 6–8 weeks of consistent use before it shows in a time trial or race. Running science from institutions like the British Journal of Sports Medicine consistently points to neuromuscular adaptations requiring 6–10 weeks to fully consolidate, even when the sessions themselves are short.
If you do strides once in a while and forget them for weeks, you’ll get little benefit. Consistency is what makes them work — but given how short they are, “consistent” means 8–10 minutes tacked onto an easy run, a couple of times a week.
The honest takeaway
- Strides are 20–30 seconds of controlled fast running at about 90% effort, followed by 60–90 seconds recovery. Do 4 per session.
- They’re not speedwork — they don’t replace intervals or tempo runs, but they do keep your legs sharp between harder sessions.
- The best time to add them is at the end of 2–3 easy runs per week, or before a race as a warm-up tool. They add almost no fatigue.
- Good form matters more than pace: relaxed, tall, building gradually — not flat-out sprinting with your arms flailing.
- Give it 6–8 weeks of consistency before judging whether they’re working. Two strides done once won’t tell you anything.
Next read: How to run faster: speed work for recreational runners