From Road to Trail: What Actually Changes

A coach's guide to moving from road to trail running: why your pace collapses, how to measure effort on hills, what to change in your training week, and the gear that genuinely matters.

Gianluca Belloni 7 min read

The short answer

Moving from road to trail means abandoning pace as your primary metric and training by time and effort instead. Expect to run 20-50% slower per kilometre on technical terrain, add vertical gain as a tracked variable, build downhill tolerance deliberately, and shorten your stride while raising cadence. Aerobic fitness transfers almost entirely; pacing intuition and tissue tolerance do not.

Key takeaways

  • Pace becomes meaningless on trails. Switch to time on feet and perceived effort as your primary units.
  • Your aerobic fitness transfers almost completely. Your ankles, quads, and descending skill do not.
  • Power hiking is a trained skill, not a failure. Above roughly 15-20% gradient it beats running on cost and often on speed.
  • Expect the first six to eight weeks to feel clumsy and slow. Coordination adapts faster than you think, tendons slower.
  • One or two trail runs a week is enough to start. You do not need to abandon the roads.

The first time a strong road marathoner runs a mountain trail, they usually have the same two reactions in the same order. First: this is much harder than I expected. Second, quietly, on the descent: I have no idea what I am doing with my feet.

Both are normal, and both fix themselves faster than you would guess. But the transition goes better if you know in advance which parts of your road fitness come with you and which parts you are starting from scratch on.

What transfers, and what doesn't

Comes with you, essentially intact:

  • Aerobic capacity. Your heart, lungs, capillary density, and mitochondria do not care what surface you are on.
  • Fat oxidation and general endurance.
  • The habit of consistent weekly training - which is honestly the biggest one.

Does not transfer:

  • Pace intuition. Completely useless in the mountains, and actively misleading.
  • Descending skill and quadriceps tolerance for eccentric loading.
  • Ankle, foot, and hip stability on uneven ground.
  • Fueling over durations longer than about three hours.
  • Navigation, self-sufficiency, and kit management.

The gap between those two lists is why a 3:00 marathoner can be comprehensively humbled by a 25 km mountain race, and also why they will improve very quickly once they start training the second list.

Stop looking at pace

This is the change that matters most, and the one people resist longest.

On a technical climb, a runner who holds 4:30/km on the road might be moving at 9:00/km. On a steep descent they might be at 7:00/km while working harder than they do on a road tempo. Neither number tells you anything useful about how hard you are working or how the session is going.

Replace it with two things:

  1. Time. Plan and log sessions in minutes and hours. "90 minutes easy" is a real instruction. "15 km easy" is not, once terrain enters the picture.
  2. Effort. Breathing rate and the talk test are more reliable on hills than either pace or heart rate. Easy means you can speak in full sentences. If you can only manage three or four words, you are no longer running easy, whatever the watch says.

Heart rate is a reasonable third input with two caveats: it lags by 30-60 seconds when the gradient changes, so it is always describing the climb you were on rather than the one you are on, and it drifts upward through long efforts even at constant work. Use it as a ceiling to stay under, not a target to chase.

If you want a number that behaves consistently on varied terrain, running power is the closest thing available - a given power output means roughly the same physiological cost uphill, downhill, or flat. It is not perfect, and it is not necessary, but it solves the specific problem that pace cannot.

Add vertical gain to your training log

On the road, weekly volume is one number. On trails you need two: time (or distance) and elevation gain.

Gain is a load in its own right. A 20 km run with 200 m of climbing and a 20 km run with 1,400 m of climbing are different sessions in every way that matters - different duration, different muscle recruitment, different recovery cost. Log both, and progress both, and do not progress both at once.

A reasonable starting rule: add either volume or vertical in a given week, not both, and hold each increase to roughly 10-15%.

Learn to power hike on purpose

Walking is not what happens when trail running goes wrong. It is a technique, and in the mountains it is often the correct one.

Somewhere around 15-20% gradient, most runners cross a point where hiking costs meaningfully less energy than running for a nearly identical speed. Above 25% almost nobody should be running, and the elite fields at steep mountain races are hiking too - just extremely well.

Good power hiking looks like this: hands driving down on the thighs just above the knee on each step, a forward lean from the ankles rather than the waist, a shorter and more frequent step than feels natural, and a rhythm you can hold for twenty minutes rather than two. Practise it as a session, not just as a fallback. Twenty minutes of steep hiking with hands on quads, repeated weekly, produces a noticeably different runner within a month.

Descending is the real skill

Climbing is mostly fitness. Descending is mostly technique and tissue tolerance, and it is where road runners lose the most time and take the most damage.

Three things to change immediately:

  • Shorten your stride and raise your cadence. Long reaching steps mean landing on your heel out in front of your body, which is both a brake and a shock. Small quick steps let you react.
  • Land under your hips. Lean slightly down the hill rather than sitting back. Sitting back feels safer and is the main cause of both slipping and quad destruction.
  • Look four to six metres ahead, not at your feet. Your feet know where to go if your eyes have already been there. Staring at your shoes is the single most common technical error I see.

Build the tolerance gradually. Downhill running causes genuine muscle damage through eccentric loading, and the soreness two days after your first proper descent is real. The compensating good news is the repeated-bout effect: after two or three exposures, the same descent causes dramatically less damage, and that protection lasts for weeks.

What changes in your training week

You do not need to rebuild everything. For a road runner adding trails, a sensible first eight weeks looks like:

DayBeforeAfter
Easy runsRoad, by distanceTwo stay on road, one moves to soft trail, by time
Quality sessionTrack or road intervalsUphill intervals, 6-10 x 2 min hard
Long runRoad, by distanceTrail, by time, with real climbing
StrengthOptionalTwo 30-min sessions, non-negotiable

Keep some road running. It is the cheapest way to hold aerobic volume, it is easier to recover from, and there is nothing virtuous about doing every run on rocks.

The strength work is not optional if you are going to trails. Single-leg strength, calf work through full range, and hip stability are what stop your ankles from being the limiting factor. Split squats, step-ups and step-downs, straight-and-bent-knee calf raises, and anti-rotation trunk work, twice a week.

Gear: what matters, in order

Most trail gear is a preference. Three things are not.

  1. Shoes with real outsole lugs. Road shoes on wet rock or mud are a genuine hazard, not just slower. Lug depth of 4-5 mm covers most terrain. Rock plates matter if your local trails are sharp and rocky; a broad, stable platform matters more than cushioning depth.
  2. A way to carry fluid and food. A vest with soft flasks for anything over an hour. Handhelds are fine for short runs. You cannot run a three-hour mountain long run on a single 500 ml bottle and expect the second half to go well.
  3. A layer and a phone with a downloaded map. Weather in the mountains changes faster than your ability to get back down. This is not gear enthusiasm, it is basic risk management.

Poles are worth considering once you are running races with sustained climbing, but they are a skill of their own and not a week-one purchase.

Expect six to eight awkward weeks

There is an adaptation curve, and it has an unflattering middle. In the first few weeks you will feel uncoordinated, your ankles will be tired in a way you have not felt before, and your average pace will look catastrophic. Around week four the footwork starts to feel automatic. Around week eight, descents stop being frightening.

Tendons and connective tissue adapt more slowly than muscle or the cardiovascular system - months, not weeks. This mismatch is why enthusiastic road runners get hurt when they switch: the engine is ready for far more than the structure. Hold your increases conservative for the first two months even when you feel fine, especially on vertical.

A first month, concretely

Weeks 1-2: Replace one easy run and your long run with trail. Keep the trail runs on non-technical, rolling ground. Log time, not distance. Add two strength sessions.

Weeks 3-4: Add a second trail run midweek with sustained climbing. Introduce 15-20 minutes of deliberate descending in the long run. Start practising power hiking on anything steep.

Weeks 5-8: Move the quality session to uphill intervals. Extend the long run by 15-20 minutes every second week. Take a genuine recovery week every fourth week - the trail load is higher than the volume number suggests.

After that you are not a road runner adapting to trails any more. You are a trail runner, and the next question is which race.

Where to go next

If you are eyeing a first ultra, the 16-week first 50K framework picks up exactly where this leaves off. If descending is your weak point - it usually is - the downhill running guide goes deeper on technique and the specific sessions that build tolerance.

And if you want the transition managed rather than improvised, coaching is where I do that.

Frequently asked questions

How much slower is trail running than road running?
Typically 20-50% slower per kilometre, and far more on steep or technical terrain. A runner holding 5:00/km on the road may be at 7:00-9:00/km on a mountain trail and working harder. This is why trail training is planned in time rather than distance.
Do I need trail shoes to start trail running?
For dry, smooth paths, road shoes are fine. For wet rock, mud, roots, or loose ground, trail shoes with 4-5 mm lugs are a safety item rather than a performance upgrade. Grip is the feature that matters most; cushioning depth matters least.
Should I stop road running when I switch to trails?
No. Road running is an efficient way to hold aerobic volume with lower recovery cost and lower injury risk from uneven ground. Most trail runners I coach keep one or two road runs a week year-round, including through ultra builds.
Is it normal to walk during a trail run?
Yes, and it is often correct. Above roughly 15-20% gradient, power hiking uses less energy than running at a similar speed, and above 25% nearly everyone hikes, including elite mountain racers. Treat hiking as a technique to train, not a concession.
How long does it take to adapt to trail running?
Coordination and footwork improve noticeably within four to eight weeks. Muscular tolerance for descending adapts within two or three exposures. Tendons and connective tissue take months, which is why the first eight weeks should progress conservatively even when your fitness feels ready for more.

About the author

Gianluca Belloni - Level 1 Trail Running Coach (CONI-recognised), based in Lecco, Italy.

I coach trail and ultra runners from first 50Ks to hundred-mile finishes, and I write these guides the way I'd explain them to an athlete. More about me.

Want this applied to your training?

Articles give you the framework. Coaching bends it around your week, your terrain, and your race. The intro call is free and low-pressure.