Running Pace Guide: How to Find, Train and Race Your Pace

Pace is time per unit of distance — minutes per kilometre or per mile. Speed is distance per unit of time — kilometres or miles per hour. They are the same information inverted, and which one feels natural depends mostly on your sport: runners think in pace, cyclists and treadmills in speed.

The relationship underpinning everything is simply pace = time ÷ distance. Fix any two and the third follows, which is why the Pace Calculator offers three modes: find your pace, find your finish time, or find the distance you covered.

Most training and racing revolves around a handful of fixed distances, two of which have famously untidy numbers.

Nearly everyone runs slower per kilometre as the race gets longer, and the reason is physiological rather than motivational. Short races draw substantially on anaerobic capacity, which is powerful but brief. Longer races are limited by how much work you can sustain aerobically without accumulating fatigue faster than you can clear it.

As a rough guide, expect to slow by around 15–20 seconds per kilometre moving from 5K to 10K, and a similar increment again from half marathon to marathon. Individual variation is wide — some runners hold pace remarkably well over distance, others fall away sharply.

This is why extrapolating a marathon goal from a 5K time usually produces something unachievable. Calculate for the distance you are actually running.

The most common race-day failure is going out at a pace that has never been sustained in training. A goal pace you have not held for at least half the race distance in a training run is a hypothesis, not a plan.

A reasonable process: take a recent race or hard training effort at a shorter distance, adjust for the longer distance, and then sanity-check it against your long runs. If the adjusted pace is one you have only ever held for 5 km, it will not survive 42 km.

Then plan the first few kilometres deliberately slower than goal pace. Starting conservatively costs seconds; starting too fast costs minutes, and the arithmetic of that trade is not close.

Most running in a well-structured plan should be comfortably slower than race pace. The classic mistake is running every session at a moderately hard effort — too fast to build aerobic base efficiently, too slow to develop speed.

Running the second half of a race at the same pace as the first (even splits) or slightly faster (negative splits) is how most personal bests are set. Positive splits — slowing in the second half — are the signature of going out too fast.

In the marathon specifically, glycogen depletion adds a hard physiological constraint. Muscle and liver glycogen stores hold roughly 90 to 120 minutes of hard running; beyond that, without fuelling, pace falls sharply. This is the origin of 'the wall', and it typically arrives somewhere around 30–35 km.

The countermeasures are unglamorous and effective: start conservatively, and take on carbohydrate during the race — commonly 30 to 60 g per hour — practised in training rather than improvised on the day.

A pace calculator assumes flat ground and good conditions. Reality rarely obliges. Hills cost more time on the ascent than they return on the descent, so a hilly course is slower than a flat one of the same distance even with equal elevation gain and loss.

Heat is the single biggest environmental factor. Performance declines measurably above roughly 15°C, and substantially above 20°C, because blood is diverted to the skin for cooling. Humidity compounds it by impairing evaporative cooling. Wind costs more into a headwind than it gives back with a tailwind.

Adjust expectations for conditions rather than treating a calculated pace as a commitment. Racing to effort in the heat and accepting a slower time is nearly always better than racing to a number.

Pace is the output; running economy is much of what determines it. Two runners with identical aerobic capacity can differ substantially in race times because one uses less energy at the same speed.

Cadence — steps per minute — is the most commonly discussed lever. The often-quoted target of 180 comes from observations of elite runners and is not a universal prescription, but many recreational runners do over-stride, landing with the foot well ahead of the body, which brakes on every step. Increasing cadence by around 5% usually reduces over-striding without any conscious change to form.

Beyond that, economy improves mostly through consistent mileage over months, some faster running, and enough strength work to tolerate the load. There is no shortcut, and chasing a specific form cue rarely produces one.

Most running injuries come from doing too much too soon. The widely cited guideline is to increase weekly mileage by no more than about 10% at a time, with an easier week every third or fourth week.

It is a rule of thumb rather than a law — very low mileage can be increased faster, and very high mileage should be increased more slowly — but the underlying principle is sound: connective tissue adapts more slowly than the cardiovascular system, so your fitness will often outpace your resilience.

Pair pace work with the Target Heart Rate Calculator to check that your easy runs really are easy. If your easy pace is pushing you into zone 3, it is not an easy run, whatever the plan calls it.