Pace Calculator

Pace, Time, and Distance

These three are directly related: pace is time divided by distance, so knowing any two lets you calculate the third. Use "Find Pace" when you know how far and how long you ran and want your per-km or per-mile pace. Use "Find Time" when you know your target pace and distance and want to estimate a finish time, handy for planning a race strategy.

Common Mistakes When Calculating Pace

The most frequent manual error is treating minutes and seconds as a decimal, converting a 5:30 pace to 5.30 rather than correctly recognizing that the 30 represents 30 seconds, half of a minute, not thirty hundredths of one. This mistake produces a pace calculation that's consistently off in a way that compounds when comparing splits or predicting longer distances. Another common mistake is mixing units mid-calculation, comparing a pace measured in minutes per kilometer directly against a target expressed in minutes per mile without converting first, which understates or overstates actual performance by roughly 60%, since a mile is significantly longer than a kilometer. This calculator avoids both issues by working in raw seconds internally and converting cleanly between km and miles using a precise conversion factor.

About the Race Predictions

The predicted times table extrapolates your current pace across common race distances. Keep in mind that pace naturally varies with distance, most runners can't sustain their 5K pace for a full marathon, so treat these as a rough starting reference rather than a guaranteed finishing time, especially for much longer distances than the one you entered.

Worked Example

For a 5 km run completed in 25 minutes flat, the calculator divides total seconds (1,500) by distance (5) to get a pace of 300 seconds per km, displayed as 5:00 /km. Converting that to miles multiplies by 1.60934 (the number of km per mile), giving roughly 482.8 seconds per mile, displayed as 8:03 /mi. Speed in km/h comes from dividing 3,600 by the per-km pace in seconds: 3,600 ÷ 300 = 12.0 km/h. Extrapolating that same 5:00/km pace across standard race distances gives predicted times of 0:25:00 for a 5K, 0:50:00 for a 10K, 1:45:29 for a half marathon (21.0975 km), and 3:30:59 for a full marathon (42.195 km), each calculated by simply multiplying the per-km pace by the distance in kilometers.

Why the Official Race Distances Have Odd Numbers

A half marathon's official distance, 21.0975 km (13.1 miles), and a full marathon's official distance, 42.195 km (26.2 miles), look oddly specific rather than round numbers, and that's because they are historically fixed rather than mathematically convenient. The modern marathon distance traces back to the 1908 London Olympics, where the course was extended so the race could start at Windsor Castle and finish in front of the royal viewing box at the Olympic stadium, and that specific distance was later standardized internationally in 1921 rather than rounded to an even 42 km. The half marathon distance is simply defined as exactly half of that official marathon distance, which is why both figures carry the same seemingly arbitrary decimal precision.

Understanding Pace vs Speed

Pace and speed describe the same underlying quantity, how fast someone is moving, but expressed in inverted units, which is why they can feel confusing to convert between mentally. Pace is time per unit distance (minutes per km or per mile), a smaller pace number means faster movement, since less time is needed to cover the same distance. Speed is distance per unit time (km per hour or miles per hour), a larger speed number means faster movement. Runners and endurance athletes overwhelmingly think and talk in terms of pace, since it maps directly onto how race splits and training paces are typically communicated (a 5:00/km pace, an 8-minute mile), while speed in km/h or mph is more commonly used for cycling and driving contexts. This calculator shows both so the same result is usable regardless of which framing is more natural for the reader.

Reading the Alt-Unit and Speed Line

Below the main pace result, the calculator shows a secondary line converting your pace into the other distance unit plus an equivalent speed in km/h. This exists because different contexts call for different units, a race entry form might list pace requirements in min/mile while a training app displays min/km, and having both immediately visible avoids needing a separate unit converter. The km/h figure is included because some treadmills and fitness devices set target intensity directly as a speed rather than a pace, so having that conversion on hand makes it easier to translate a target race pace into a treadmill speed setting for indoor training.

Why Race Pace Isn't Constant Across Distances

Physiologically, the pace a runner can sustain drops as race distance increases, since longer efforts draw more heavily on aerobic energy systems and depend more on pacing discipline, fueling, and fatigue resistance rather than pure short-burst speed. This relationship is well documented enough that experienced coaches and race predictors use adjustment factors (sometimes called Riegel's formula or similar exponential models) to estimate a realistic longer-distance time from a shorter-distance result, factors that account for the expected slowdown rather than assuming a flat pace. This calculator's predictions table intentionally uses the simpler flat-pace method rather than one of these adjustment models, making the numbers easy to understand and reproduce by hand, but it also means the longer predictions, especially the marathon figure, should be treated as a best-case reference rather than a realistic goal time for anyone without specific endurance training for that distance.

Everyday Uses Beyond Racing

Pace calculations aren't only useful for competitive racing. Walkers and hikers use the same pace-time-distance relationship to estimate how long a planned route will take, especially useful when timing a hike against daylight hours or a return schedule. Cyclists sometimes switch between pace-style and speed-style thinking depending on context, road cycling conventionally uses speed (km/h or mph), while some structured training plans reference pace per kilometer similarly to running. Even everyday walking commutes benefit from this same math, knowing a typical walking pace lets you estimate arrival time for a known distance without needing to consult a map app, using nothing more than the same time-equals-pace-times-distance relationship this calculator is built around.

Using Pace Data to Plan a Race Strategy

Beyond simple curiosity, converting a known pace into predicted finish times is a common part of race planning. Runners often use a recent shorter race result (a 5K or 10K time trial, for instance) as an input here to get a rough sense of realistic longer-distance goal times before setting a specific race pace target. Because even splits (running at a consistent pace throughout) generally outperform positive splits (starting fast and slowing down) for most distance runners, having a calculated target pace on hand ahead of race day, and checking against it during training runs or race splits, is a common and effective pacing strategy across recreational and competitive distance running alike.

Frequently Asked Questions

Why does my pace show in both km and miles?

Different races and training plans use different units depending on region, showing both saves you from having to convert manually.

Should I train at my goal race pace?

Most training plans mix paces, easy runs slower than race pace, with some workouts at or faster than goal pace. This calculator gives you the numbers; how to structure training around them is worth researching separately or discussing with a coach.

Why do longer race predictions get less accurate?

The predictions simply multiply your entered pace by each race distance, assuming that pace holds constant the whole way. In reality, endurance, fueling, and pacing strategy all become more important the longer a race gets, so most runners naturally slow down somewhat as distance increases. A pace comfortably held for 5K is rarely sustainable unchanged across a full marathon, which is why the marathon and half marathon predictions should be read as optimistic upper bounds rather than realistic goal times.

How is speed in km/h calculated from pace?

Speed is the inverse of pace: dividing 3,600 (the number of seconds in an hour) by your pace in seconds per kilometer gives kilometers per hour. A pace of 5:00 per km (300 seconds) converts to 3,600 ÷ 300 = 12.0 km/h, since running that pace for a full hour would cover 12 kilometers.

Why does the km-to-mile conversion use 1.60934?

1.60934 is the standard, internationally defined number of kilometers in one mile, accurate to five decimal places. The calculator uses this figure to convert pace and distance between metric and imperial units so both figures describe the exact same underlying speed, just expressed in different units.

What's the difference between the Find Pace and Find Time tabs?

"Find Pace" works from a completed run, distance and time already known, to calculate the pace that was run. "Find Time" works in the opposite direction, starting from a target pace and a distance to estimate how long a run at that pace would take, useful for planning a race strategy or a training run before actually running it.