Every marathon runner reaches the same wall eventually, and it isn't the one at mile 20.
It's the volume wall. You want a bigger aerobic engine — more VO2max, more capillary density, a heart that moves more blood per beat — because that engine is what actually determines your marathon time. So the instinct is to run more. But your legs have a ceiling on how much pounding they can absorb before something breaks down: a stress reaction, a tendon that won't settle, a hip that aches on every run instead of just the long ones. Runners hit this wall at wildly different mileages, but almost everyone hits it.
Cycling is how you keep building the engine after your legs have said no to more running.
This isn't a replacement for running — nothing replaces running if you're training for a marathon. It's an addition that lets you accumulate aerobic training load your legs couldn't otherwise handle, because the mechanism that builds fitness on a bike doesn't require your feet to hit the ground three times a body weight, seventy-plus times a minute, for however long the ride lasts. Here's the physiology behind why that works, and exactly how to fit it into a training week without messing up the running that actually prepares you to race 26.2 miles.
The engine and the chassis are different problems
Think of your body as two separate systems that happen to share the same skin.
There's the engine — your cardiovascular and metabolic system. Heart size and stroke volume, blood plasma volume, mitochondrial density in your muscle fibres, your capacity to shuttle oxygen from lungs to working muscle and turn it into ATP. This is what VO2max measures, and it's the single strongest predictor of endurance performance across almost every sport that requires sustained aerobic output.
Then there's the chassis — the specific muscles, tendons, and neuromuscular patterns that let you actually run. Running economy (how efficiently you convert oxygen into forward motion at a given pace), the stiffness and elasticity of your Achilles and calf complex, the coordination pattern your nervous system has drilled into your stride after years of practice. This is sport-specific in a way the engine isn't.
The engine adapts centrally. When you do sustained aerobic work — running, cycling, rowing, doesn't matter — your heart gets bigger and pumps more blood per beat, your blood plasma volume expands, your muscles grow more mitochondria and capillaries. None of that machinery cares what movement produced the training stimulus. A stronger heart is a stronger heart whether it was built pedalling or running.
The chassis adapts locally and specifically. Running economy is partly about learning to recycle elastic energy through your tendons with each stride, and partly about the exact recruitment pattern your nervous system uses at your specific running cadence and mechanics. Cycling uses your legs, but in a completely different movement pattern, at a different joint range, with no impact and no elastic loading through the Achilles. It will not make you a more economical runner. It isn't supposed to.
This is the concept to hold onto through everything below: trained engine, fresh chassis. You're aiming for a strong cardiovascular system paired with legs that haven't taken on more impact than they can currently handle. Cycling builds the first without touching the second.
What the research actually shows
The idea that fitness transfers between running and cycling isn't new, but the evidence has firmed up considerably. A 2026 systematic review by Menges and colleagues, published in Frontiers in Sports and Active Living, pulled together the cross-training literature and confirmed meaningful VO2max transfer between the two sports — trained runners who added structured cycling saw aerobic capacity gains that showed up in their running fitness, not just their cycling fitness.
The mechanism lines up exactly with the engine-versus-chassis model. The central adaptations — the ones that drive VO2max — transferred. The peripheral, sport-specific qualities did not transfer to the same degree, and the review was consistent with the older cross-training literature on this point: swapping some running volume for cycling volume maintains or improves aerobic fitness while measurably reducing the impact load your musculoskeletal system absorbs.
None of this means cycling is equivalent to running for marathon preparation. It means cycling is a legitimate tool for building the aerobic component of marathon fitness when your legs need a break from the mechanical stress of doing that same building through running alone. The marathon-specific qualities — economy at goal pace, the durability of your stride mechanics over three-plus hours, glycogen management, the mental skill of holding pace when everything hurts — those still have to come from running. This is an addition to your running program, not a substitute for the running that makes you race-ready.
The intensity question: conversation pace, and mean it
Here's where people undo the benefit before they even get on the bike: they ride too hard.
The cycling sessions that support marathon training are easy. Conversation pace. If you can't hold a full sentence without gasping partway through, you're riding harder than this session calls for, and you're starting to create the kind of fatigue and muscular stress that bleeds into your next run — which defeats the entire purpose of doing this instead of just running more.
A useful number: cycling heart rate runs 5-10 bpm lower than running heart rate at an equivalent level of effort. This is a real physiological difference, not a coaching approximation — a smaller amount of muscle mass is engaged per pedal stroke compared to a running stride, and you're not fighting gravity and impact the same way, so your heart doesn't have to work as hard to deliver the same aerobic stimulus. If you try to hit your running Zone 2 heart rate numbers on the bike, you'll end up riding harder than you should. Ride by feel and let the lower numbers be lower numbers. The session is doing its job at an effort that will initially feel almost too easy.
Aim for 60-90 minutes. Cadence doesn't need to be technical — somewhere in the 80-95 rpm range is comfortable and sustainable for most people without much of a learning curve. This is not a structured intervals session and it's not meant to feel productive in the way a hard run feels productive. It's meant to feel easy, because building the aerobic engine at this level of training is a volume game, not an intensity game.
Which runs to replace, and which you never touch
This is the part that actually matters for your marathon build, because get this wrong and you lose more than you gain.
Never replace these with cycling:
The long run. This is the single most marathon-specific session in your entire program. It trains fuel utilisation and glycogen management at race-relevant duration, teaches your musculoskeletal system to tolerate the accumulated impact of running for two-plus hours, and builds the mental capacity to hold pace and form when you're deeply fatigued. Nothing about a bike ride replicates the specific demand of being on your feet, absorbing impact, for three hours. This session stays running, always.
Tempo runs. Tempo work trains your body to sustain effort at or near lactate threshold while running — the specific neuromuscular and metabolic skill of holding a hard-but-sustainable running pace. That skill is trained by running at that pace, not by producing a similar heart rate on a bike.
Race-specific intervals. Any session built around marathon pace, or paces faster than marathon pace, is teaching your body the exact movement pattern and energy system demand of the race itself. This is where running economy gets sharpened. A bike cannot substitute for pace-specific running work, however fit the ride makes you.
Freely swap these:
Easy runs and recovery runs. These sessions exist primarily to add aerobic volume and support recovery between harder efforts. A 60-90 minute easy run and a 60-90 minute conversation-pace bike ride are doing largely the same aerobic job — building the engine — without meaningfully different demands on your running-specific chassis. This is the easiest swap to make in the entire plan.
The second run on double-run days. If your program has you running twice in a day — a common approach in higher-mileage marathon blocks — the second easy run is a strong candidate to become a bike session instead. You still get two aerobic sessions that day, but only one of them loads your legs with impact.
A rough rule: if the session's purpose could be described as "just add aerobic volume," it's a candidate for cycling. If the session's purpose requires running mechanics, running-specific fatigue, or race-pace practice, it stays running. When in doubt, keep it as a run — you can always add cycling on top as a plus-one session rather than a straight swap.
Timing it around your week
Placement matters as much as the swap decision itself.
Ride the day after a hard running session — a long run, a tempo run, an interval day — not the day before one. Easy cycling the day after a hard effort supports blood flow to fatigued muscle and helps clear the accumulated fatigue from the session before, without adding the kind of mechanical stress that slows recovery. This is active recovery doing what active recovery is supposed to do.
What you want to avoid is riding hard, or even riding easy but for too long, the day before a key running session. Your legs need to walk into tempo runs, long runs, and interval days reasonably fresh. A cycling session the day before one of those sessions — even an easy one — is competing for the same recovery window your legs need for the session that actually matters more to your marathon fitness.
A simple weekly shape for a runner adding one cycling session: hard running session, then easy bike the next day, then a lower-key running day, building back toward the next hard effort. The bike session sits in the recovery window, doing useful aerobic work while your legs get a break from ground contact.
What this looks like in practice
Take a runner doing five running days a week during a marathon build: a long run, a tempo run, an interval session, and two easy runs.
Swap one of the two easy runs for a 75-minute conversation-pace bike ride, placed the day after the tempo or interval session. The long run, tempo, and intervals stay exactly as programmed — untouched, because those sessions are doing jobs cycling can't do. What changes is that one running day becomes a cycling day, which means one day's worth of impact stress simply doesn't happen that week, while the aerobic stimulus from that session still lands.
Over a 12-16 week marathon build, that's somewhere between 12 and 16 running sessions' worth of impact removed from legs that are absorbing a long run, a tempo run, and an interval session every single week regardless. That's not a small trade. It's very often the difference between a runner who arrives at race week with legs that feel fresh and one who's managing a nagging ache through the taper.
A second scenario worth naming: the higher-mileage runner, someone running six days a week and 50-plus miles, who's already carrying a niggle — a tight calf, an ache in the shin, something that hasn't become an injury yet but is clearly asking for less running rather than more. This is exactly the runner cycling helps most, because the alternative to cycling isn't "run at the same volume, just smarter" — it's usually "keep running through the warning sign until it becomes a stress reaction, then stop running altogether for six weeks." Replacing two easy running days with two cycling days lets this runner hold their overall aerobic volume, keep the niggle from progressing, and often train straight through what would otherwise have become a forced break. This is where cycling stops being a nice-to-have and starts being the difference between finishing a training block and not.
Equipment: keep this simple
You don't need a serious bike to get the benefit here — a decent hybrid, an old road bike, or a turbo trainer with whatever bike you already own all work for conversation-pace aerobic riding. What matters more than the equipment is consistency: the same 60-90 minute session, once or twice a week, for the length of your training block.
Indoors on a turbo trainer is the easier environment to control intensity in — no hills tempting you to push, no traffic to deal with while your legs are meant to be doing nothing strenuous. Outdoors works fine too and adds a change of scenery that some runners find mentally useful during a long build, provided you pick flat, quiet routes and resist the urge to chase anyone. Either way, a basic heart rate monitor is worth having so you can actually confirm you're riding at conversation pace rather than guessing.
The takeaway
Cycling doesn't make you a better runner in the way another run would. It builds the engine — VO2max, cardiac output, plasma volume — that transfers to running because those adaptations are systemic, not sport-specific, and the 2026 Menges review is the clearest confirmation yet that this transfer is real and worth planning around.
What it doesn't build is running economy or stride-specific durability, which is exactly why the long run, tempo runs, and race-specific intervals stay non-negotiable. Everything else — the easy volume, the second run on a double day — is fair game to move to the bike, ridden at conversation pace, timed the day after your hard efforts rather than before them.
Trained engine, fresh chassis. That's the whole idea, and it's a useful lever for any marathon runner whose legs are telling them they've found the ceiling on running volume alone.
If you want help building a training week that actually balances this — running load, cycling volume, and recovery — that's exactly the kind of structure we work through inside the Roadman community.