Running pace calculator

Pace vs speed

Runners talk in pace — minutes per kilometer or mile — while speed is distance per unit of time, like kilometers per hour. They're the same information turned upside down: a 5:00/km pace is 12 km/h, and a 4:00/km pace is 15 km/h. Pace wins out in training and racing because it maps directly onto the number that actually matters on race day: how long a given distance is going to take. Multiply pace by distance and you get a time; nobody does that arithmetic in their head with km/h mid-race. A GPS watch will happily show either number, but the pace display is the one you can act on without doing math while breathing hard.

The two aren't linearly related, which trips people up when they try to eyeball pace changes from a speed increase. Going from 10 km/h to 12 km/h looks like a 20% jump, but the pace change is bigger than that, because pace is the inverse of speed — 10 km/h is 6:00/km, 12 km/h is 5:00/km, a drop of a full minute per km. Small speed increases near the top of your range shave off more time per kilometer than the same speed increase would at an easy jog. That's part of why interval pace feels so much harder to hold than the numbers alone suggest.

Why even pacing beats going out fast

The fastest way to run a given distance slower than you're capable of is to run the first half faster than you can sustain. Going out too hard burns through glycogen and buffering capacity disproportionately. Running 10% faster than goal pace doesn't cost 10% more effort — it costs substantially more, because you pass the point where your body clears lactate as fast as you produce it. The result shows up as the back half of a run or race falling apart far more than the front half gained — a "positive split" that costs more time than the fast start bought.

Even or slightly negative splitting means running the second half at the same pace as the first, or a touch faster. It consistently produces better finishing times than an aggressive start — one of the more repeated findings in distance-running pacing research, from 5K to marathon. It's also just easier to execute: holding a pace you've already proven you can sustain requires less in-race judgment than trying to claw back a deficit after blowing up. A calculated, even pace isn't a conservative fallback — for most runners on most days, it's the fastest actual strategy available.

How race pace differs by distance

The same runner's pace gets slower as the distance gets longer, and not by a small amount. A runner capable of 20:00 for 5K (4:00/km) typically can't hold 4:00/km for a marathon. A pace you can sustain for 20 minutes and one you can sustain for two-plus hours rely on different energy systems. For most runners the gap runs somewhere around 45–75 seconds per kilometer — wider for less-trained runners, narrower for well-conditioned ones. This is why a single "pace" doesn't describe a runner — it only describes a runner at a specific distance.

That's also why this calculator solves per-distance rather than assuming one number covers everything. A 10K time gives you 10K pace; carrying that pace straight onto a marathon produces a target faster than what's sustainable over four times the distance. The training paces above apply a rough adjustment for exactly this reason — but they're still an approximation, not a substitute for a race result at the distance you actually care about.

What each training zone is for

Easy pace is the pace most training miles should be run at — slow enough to hold a conversation, built for accumulating aerobic volume without digging a fatigue hole that compromises the harder sessions later in the week. It's the zone runners are most likely to skip past too quickly, on the assumption that slower means wasted, when in fact most of the adaptation from a training block comes from the easy volume underneath the harder work, not instead of it.

Tempo pace sits at "comfortably hard" — sustainable in a continuous effort for something like 20 to 40 minutes, hard enough to raise the pace at which lactate starts accumulating faster than the body clears it. Marathon pace is its own distinct zone rather than just "moderate" — a steady effort meant to be held for hours, which trains fueling, pacing discipline, and the specific muscular endurance marathon day demands, separate from raw aerobic fitness. Interval pace is the fast end: short, hard repeats at faster than race effort with full recovery between them, aimed at raising the aerobic ceiling itself rather than the ability to sustain any particular pace for a long time. Each zone trains something the others don't, which is why a training week usually touches more than one of them rather than living entirely at any single pace.

The limits of predicting one distance from another

Every method for turning one race result into a prediction for another distance — this calculator's percentage-based training zones included — is fitting a general pattern to an individual runner, and individual runners deviate from that pattern in both directions. Endurance-leaning runners hold up better than the formula predicts as distance increases; speed-leaning runners fall off faster than it predicts. Training history matters too: someone who has run three marathons has muscular and fueling endurance a formula built from average outcomes can't see in a single 10K time.

The percentages above are a reasonable starting point, most reliable when the pace they're built from comes from a real recent effort in roughly the 5K-to-half-marathon range — hard enough to be honest, long enough to reflect endurance rather than pure speed. If you calculated straight from a marathon result, the marathon zone above is close to redundant with your input, and the others are a rougher estimate than usual, since you're extrapolating up in intensity rather than down. None of that makes the estimate useless — it's still a reasonable place to start a training block — but it's a starting point to test against how sessions actually feel, not a number to defend against how a run is going.

This calculator does arithmetic on the numbers you enter and applies a fixed set of percentages to derive training paces — it doesn't know your training history, injury risk, or how a session actually feels. Training zones and splits here are a planning starting point, not a coaching prescription; adjust based on how the effort feels, and check with a professional before training through pain or a medical condition.