Mountain Marathon Training: Preparing for a Course With Vert

A mountain marathon is not a marathon with a few hills. Once the course profile shows 800 metres of climbing or more, every number you plan with shifts: pace becomes secondary, vertical gain becomes the yardstick, and the second half of the race is decided not on the climbs but on the descents. Athletes who understand this early in their preparation run a controlled mountain marathon. Those who ignore it pay on the final ten kilometres with a time they never planned for.

Why a mountain marathon is a different race

The distance is still 42.195 kilometres, but the work per kilometre rises sharply. In climbing, 100 metres of vertical gain costs roughly as much energy as a kilometre on the flat — with 1,200 metres of race climbing, that works out to an additional twelve kilometres of load. This is exactly why mountain marathon times are not comparable to flat times: a runner who clocks 3:15 on the flat is realistically 45 to 75 minutes slower on a profile course with 1,500 metres of climbing.

The second difference is mechanical. Uphill, impact force drops because the flight phase shortens — but the work per step rises. Downhill it is the reverse: landing forces multiply and the muscles work eccentrically, braking under lengthening. After a mountain race, most runners do not feel the climbs, they feel the descents. That is not weakness of will, it is measurable muscle damage — and it can be trained.

Third, the terrain. Forest floor, gravel and roots already cost three to eight seconds per kilometre compared with asphalt, because the surface returns no energy. On a mountain course, steepness, turns and aid stations add to that. Anyone who never runs on natural surfaces loses time there without any training metric telling them so.

The three factors that set your pace in the mountains

• Vertical gain: It is the single most important metric. Allow roughly 6 to 9 minutes of extra time per 100 metres of climbing — more on steep sections or technical ground. For race planning, add the climbs to your flat time instead of expecting a target pace.
• Steepness and length of the climbs: Short ramps at 15 % run very differently from long climbs at 6 %. Ramps demand anaerobic surges, long climbs demand strength endurance. Your training has to mirror the distribution of the race profile, not just the total.
• Gradient on the descents: Descents steeper than 8 % on hard ground are the most taxing passage of the whole race. They determine how much you have left by kilometre 32 — or how much you have already lost.

The 16-week build at a glance

Preparation follows the same periodisation as a flat marathon, only with different emphasis. In the build phase (weeks 1–6) you increase volume and vertical gain in parallel, in the specific phase (weeks 7–12) hard hill repeats and long mountain runs come in, and at the peak (weeks 13–14) you run a simulation over half the race's climbing. The final two weeks stay as tapering.

Four rules carry through the whole block: increase weekly vertical gain by no more than 15 % per week, never every weekend. After any week above 1,000 metres of climbing, insert a down week at half the load. Start downhill training in week three instead of leaving it to the specific phase — musculature needs the longest adaptation window. And keep 80 % of your volume easy, even when the sessions are hilly; mountains are not a licence for constant intensity.

Training uphill: the sessions that matter

• Long mountain runs (strength endurance): 90 to 180 minutes with 400 to 800 metres of climbing, at easy aerobic pace. This is the most important session of the whole build — muscle endurance and mountain running economy are built here, not in interval work. How to dose such long efforts is covered in the article on the long run.
• Hill repeats of 3 to 8 minutes (threshold): 4 to 6 repetitions on an even climb, effort at threshold, jogging recovery downhill. These sessions replace the flat threshold run and put less stress on tendons and joints than intervals on the track.
• Hill sprints at the end of easy runs: 8 to 10 repetitions of 10 to 15 seconds on steep ramps, full recovery walking. They improve muscle fibre recruitment and cost almost no reserves because the effort is too short for cardiovascular fatigue.
• Hiking as training: Not every race section is runnable. Brisk hiking with active arms is more economical than slow jogging above roughly 20 % gradient, and hiking muscles are different from running muscles. Practise hiking sections deliberately instead of treating them as defeat.

Details on controlling and dosing hill intervals are in the article Hill training: why climbs make you faster — it also covers steepness limits and typical effort durations for each repeat format.

Training downhill: the underestimated lever

Eccentric load on descents causes microscopic damage in the muscle fibres and leaves the legs sensitive for one to two weeks. But that same stimulus is also the adaptation: after two or three properly dosed descent sessions the same hill hurts far less, the muscles absorb better and you can run downhill faster without burning through your reserves. The adaptation is faster than for almost any other training stimulus.

In practice: start with 5 to 10 minutes of controlled downhill running in week three — no sprint sections, no full throttle. Progress to 25 to 40 minutes per session by week ten. For the simulation, run a long descent off the back of your planned climbs, exactly as it happens in the race, on tired legs. Cadence and body tension matter: shorter steps, higher step frequency, arms balanced behind you. Runners who overstride downhill land with a longer step and brake on the heel — that costs time and loads knees and quads maximally.

The most common mistake is the simulation run three weeks before the race, followed by two weeks off with soreness. Overdo the first descent deliberately: your quads will feel heavy for 48 to 72 hours afterwards, which is normal and intended. What follows are easy days, not another hard session.

Fueling: what is different in a mountain marathon

Mountain marathons take four to six hours, often longer than a flat marathon. That moves fueling from plan to strategy. The carbohydrate target of 60 to 90 grams per hour stays the same, but absorption gets harder: at high intensity the gut receives less blood flow, and undigested food then sits in the stomach instead of reaching the muscles. That is why gut training is mandatory in this build — rehearse fueling on the long mountain runs exactly as in the race, with the same brand, the same bars, the same gels.

The second shift concerns sodium. If you run four to six hours in the heat and lose two to three litres of sweat, a large share of that loss is sodium rather than water. 500 to 800 milligrams of sodium per litre of drink is a realistic starting point, more if you sweat heavily. Electrolyte capsules are practical but only worthwhile if you have tested them beforehand. The basics are covered in electrolytes for running.

The race-day plan follows the same pattern as other long-distance events: a full breakfast three hours before the start, a bar about 45 minutes before the gun, then solid food from kilometre 30 onwards during the hiking sections — the stomach is calmer there than on a descent. Gels in the final 90 minutes, when swallowing is easier and every gram you no longer carry counts.

Pacing: by vertical gain, not by pace

The most common mistake in a mountain marathon is applying a flat-marathon pace expectation. Anyone who tries to hold their planned split on a climb overreaches and destroys the second half. Correct pacing follows two measures: first effort, meaning perceived exertion and if needed heart rate, then vertical gain. The article on marathon pacing strategy explains even pace and negative splits; for profile courses the addition is that even pace does not mean even speed, but even effort.

In practice: run climbs of 4 to 8 % at a steady threshold heart rate, hike ramps steeper than that — briskly, not slowly, with a shortened step and active arm drive. Run descents technically clean and controlled fast, but not at the limit. And aim for constant relative effort rather than a pace. If your heart rate stays steady on a climb, that is the correct performance information, even if pace drops to a slow jog.

Common mistakes in mountain marathon preparation

• Training only uphill. Descents cause more load and are the limiting factor. Runners who never train downhill do not fade on the climbs in the race, they fade on the descents.
• Too much vertical gain added per week. Jumps from 500 to 1,500 metres of climbing in one week overload the Achilles tendon and quads. Cap it at 15 % per week, with a down week every third week.
• Confusing hills with hill intervals. High vertical rates per hour in interval format are not the same as a long mountain run. Both are necessary, but in different blocks.
• Testing fueling for the first time in the race. Four to six hours with an unknown drink and unknown gels, followed by stomach trouble — the most common reason for dropping out of ultras and mountain marathons. Test everything in training, never on race day.
• Fearing the hiking sections. Walking breaks are part of race strategy, not a sign of weakness. Jogging needlessly on steep passages costs more time than hiking in an organised way.
• Keeping the final weeks hilly. In the taper, reduce vertical gain more sharply than flat volume, because quads need longer to recover.

How Peakora handles a mountain marathon

In the Peakora engine, it is not just distance that counts but work: a mountain run with 700 metres of climbing loads you differently from the same distance on the flat, and the engine folds that into the Training Stress Score via intensity and duration. Load management then follows automatically: weeks with high vertical gain land in the plan exactly where your form allows, and the recovery monitor shows whether your quads can handle the next descent session.

When you set a race with a profile as your goal, planning weighs it accordingly: long runs are dosed by vertical gain, and when freshness is missing the engine shifts sessions instead of deleting them. The build stays linear instead of tipping into overload. How the plan reacts to such profiles is described in adjusting your training plan.

Frequently asked questions about mountain marathons

How much vertical gain do I need in training for a mountain marathon?

As a rule of thumb, build the same vertical distance the race demands during your peak weeks, spread across two to three sessions per week. For a race with 4,000 feet of climbing that means roughly 3,300 to 4,600 feet weekly — not in one run, but as long mountain runs plus hill repeats.

How long should mountain marathon preparation take?

Twelve to 16 weeks if you already know the marathon distance. The difference from a flat marathon is not the distance but the extra eccentric load: your downhill muscles need four to six weeks to adapt, which is why descents belong early in the build.

Why should I train downhill if I want to be fast uphill?

Because downhill your muscles brake eccentrically and take microscopic damage — the cause of the soreness after mountain races. Controlled downhill training makes that protection durable. Without descent stimuli in training, the second half of the race costs you a lot of time.

What should I eat during a mountain marathon?

More than in a flat race: for four to six hours of effort you need 60 to 90 grams of carbohydrate per hour plus 500 to 800 milligrams of sodium per litre of drink. Solid bars early in the race, gels later, and drink at every aid station rather than waiting for thirst.