Pace Calculator

What pace means and how it relates to speed

Pace is time per unit of distance, usually written as minutes and seconds per kilometer or per mile, such as 5:00/km. Speed is the same relationship flipped around, distance per unit of time, such as 12 km/h. The two describe identical effort, just phrased for different questions: speed answers “how far in an hour”, while pace answers “how long for one kilometer”, which is the question most runners actually check against a mile marker or a GPS watch mid-run.

Worked example. A runner completes a 10 kilometer race in 50 minutes. Converting 50 minutes to seconds gives 3000 seconds, and dividing by 10 kilometers gives 300 seconds per kilometer, which is exactly 5 minutes per kilometer, or 5:00/km. The same 10K at the same pace covers each kilometer in exactly 5 minutes, so the runner would pass the 5 km mark at 25:00 and finish at 50:00.

A lot of visitors arrive already knowing exactly what they want to know: “how long does it take to run a mile”, “how many minutes to a mile”, or “how many minutes is a mile”, at their own pace rather than someone else's. There is no single official average mile time, age, sex, terrain and fitness level all move it a lot, so instead of asserting one, this calculator answers the personal version of the same question directly: enter any pace you have actually run, and the mile row of the table below shows your own average time to run a mile, effectively your own average mile run time or average 1 mile run time, without borrowing a stranger's average mile time as a stand-in for yours.

Predicting a race time with the pace calculator, and the other two directions

All three panels on this page rearrange the same relationship: time equals pace multiplied by distance, so any two of {distance, time, pace} determine the third. Which panel to use depends on which two numbers you already know.

Find my pace, worked example. A walker covers 5 kilometers in 1 hour flat. Entering 5 km and 1:00:00 into the “Find my pace” tab divides 3600 seconds by 5 kilometers to get 720 seconds per kilometer, shown as 12:00/km. That pace number is useful on its own, as a way to compare two different walks of different lengths on equal footing.

Find my time, worked example. A runner has trained at 5:30/km and wants to predict a finish time for an upcoming 10 kilometer race. Entering 10 km and a pace of 5:30/km into the “Find my time” tab multiplies 10 kilometers by 330 seconds per kilometer to get 3300 seconds, shown as 55:00. If that pace holds for the whole race, the predicted finish time is 55 minutes.

Find my distance, worked example. A runner has 40 minutes available for a run and wants to know how far a comfortable 4:45/km pace would carry them. Entering 40:00 and a pace of 4:45/km into the “Find my distance” tab divides 2400 seconds by 285 seconds per kilometer to get about 8.42 kilometers, the distance that pace and time combination covers.

Kilometers versus miles

The distance unit toggle above the tabs switches every panel between kilometers and miles at once, using the standard conversion of 1 mile equals 1.60934 kilometers. A pace of 5:00/km is roughly 8:03/mile, since a mile is the longer unit, so covering one takes longer than covering one kilometer at the same underlying speed. Switching the toggle changes the unit a number is read in, it does not convert an already-typed number, so re-enter values after switching if you want the same real-world distance expressed in the other unit.

The race-time table, and the other four calculators on this page

Whichever of the three tabs above produces a pace, the table underneath it projects that same pace across every standard race distance at once, 400m, 1K, 1 mile, 3K, 3 miles, 5K, 10K, 10 miles, half-marathon and marathon, so a training pace turns directly into “what would this pace mean for race day” without retyping the same number nine times. A 5:00/km training pace, for instance, works out to a 25:00 5K and a 3:30:59 marathon on that table, read straight off the same pace already calculated above it. The same table doubles as a running pace chart, or simply a pace chart, for anyone comparing paces across distances rather than typing one in at a time, and the 10K row already works as a pace chart 10km lookup on its own; a training pace converted from a minute miles to miles per hour reading works the same way. If your target is a specific marathon pace instead of a 5K one, the exact same table already lists it, and the “1 mile” and “3 miles” rows answer how long is 1 mile and how long is 3 miles at that same pace directly; the “Find my time” tab handles any other distance, such as how long is 2 miles, just as easily.

Below the main calculator sit four more independent tools. The Multipoint Pace Calculator takes up to 12 cumulative distance/time checkpoints, mile-marker splits, and reports the pace for every segment in between, which is the only way to see whether a run actually sped up, slowed down, or held even; the main calculator only ever sees one distance/time pair, so it can only report a single overall number. The Pace Converter takes one pace in minutes per kilometer and shows it instantly in minutes per mile, km/h and mph, useful when a training plan, a treadmill display and a GPS watch all report speed in different units. The Finish Time Calculator projects a finish for a longer target distance from real progress already made, distance and time actually covered so far, rather than from a pace typed in on faith, which is what sets it apart from the “Find my time” tab above. And the reference table at the very bottom lists typical world-record paces by distance, for men and women, so a training pace has some real-world elite context to sit alongside it.

Training through pace and heart rate

Pace measures output, how fast a given effort actually moved a runner over the ground, while heart rate measures the internal effort behind that output. That output number is sometimes searched for as runner average speed rather than pace, but they describe the same thing from opposite directions: speed in km/h or mph, versus pace in minutes per kilometer or mile. The two usually move together, but not always in lockstep: heat, fatigue, altitude and simple day-to-day variation can all push heart rate higher for the exact same pace, which is part of why many training plans prescribe effort by heart-rate zone as well as, or instead of, pace alone.

Heart-rate zones are commonly expressed as a percentage of maximum heart rate (MHR), and the most widely used rough estimate for MHR is 220 - age, for example roughly 185 beats per minute for a 35-year-old. This formula is a population-average approximation, not a lab measurement, and can be meaningfully off for any one individual, so treat a heart-rate zone built on it as a useful planning range rather than an exact physiological boundary.

Training below roughly 70 to 80 percent of MHR is generally aerobic, effort the body can fuel largely with oxygen and sustain for a long time, the zone most easy, base-building running sits in. Pushing further, toward and beyond roughly 80 to 90 percent of MHR, shifts increasingly toward anaerobic effort, where the body leans more on energy pathways that do not depend on oxygen delivery keeping pace with demand, effort that can only be sustained briefly. The anaerobic threshold, sometimes called the lactate threshold, is the intensity at which the body starts producing lactate faster than it can clear it, and training that specifically targets an intensity right around that threshold is a common, deliberate way distance runners try to raise the pace they can sustain aerobically before crossing into that steeper, harder-to-sustain effort.

Using pace and heart rate together, not one instead of the other

Neither number tells the whole story alone. Pace is precise and directly tied to performance, exactly what a race clock measures, but it says nothing about how hard the body is actually working to hold it on a given day. Heart rate reflects that internal effort directly, but the same heart rate can correspond to a meaningfully different pace depending on heat, hydration, sleep, or accumulated fatigue from recent training. A runner who notices their heart rate running noticeably higher than usual at what should be an easy, conversational pace is picking up a real signal, often recovery-related, before it would otherwise show up as a slower time on the clock.

In practice, many training plans use pace as the primary target for a workout on paper, a specific number to aim for, while using heart-rate zones as a live check during the run itself, a way to notice early that today's effort is costing more than the same pace normally would. Used together rather than as competing systems, the two numbers catch different kinds of problems: pace catches whether a session hit its goal, heart rate catches whether hitting that goal came at an unusually high physiological cost that might be worth paying attention to before the next hard session.