Pace Calculator

Understanding the Pace Calculator

A pace calculator divides time by distance to tell you how long each mile or kilometre took. It's the number runners actually think in, because unlike speed it maps directly onto the effort of a single mile, and it's the figure every race plan and training session is built around.

How it actually works

Enter distance, hours, and minutes. The calculator divides total minutes by distance for pace per mile, converts to pace per kilometre using the 1.60934 conversion, and reports speed in miles per hour. Covering 3.1 miles in 28 minutes gives a pace of 9:02 per mile, 5:37 per kilometre, and a speed of 6.64 miles per hour.

The deeper context most people miss

A minute per mile sounds small and compounds substantially over distance: the gap between 9:00 and 10:00 pace is about three minutes over a 5K and thirteen minutes over a half marathon. This is why pace targets are set per mile rather than by finish time, and why holding pace in the early miles of a longer race matters more than any late effort can compensate for.

Why pace rather than speed, and what the two conversions represent

Speed in miles per hour is the standard measure almost everywhere except running, and there's a reason runners inverted it. Pace expresses time per unit distance, which matches how the effort is actually experienced and planned: a runner thinks about holding 9:00 miles, checks their watch at each mile marker against that figure, and knows immediately whether they're ahead or behind. Speed would require mental arithmetic at every checkpoint. Pace also scales linearly with race time in a way that's easy to project, since multiplying pace by distance gives finish time directly. The kilometre conversion matters because most of the world races in kilometres while much of the running culture in the US and UK still thinks in miles, and the two aren't intuitively interchangeable. A mile is 1.60934 kilometres, so a 9:02 mile pace is 5:37 per kilometre, and the shortcut some runners use of dividing mile pace by 1.6 works well enough for mental estimates. Standard race distances sit awkwardly across both systems: a 5K is 3.107 miles, a 10K is 6.214, a half marathon is 13.109, and a marathon is 26.219. This is why finish time predictions rarely come out as round numbers and why a runner targeting a specific time needs pace to a precision of seconds rather than a rounded figure.

A worked example: building a race plan from a target time

Suppose you want to break two hours in a half marathon. The distance is 13.109 miles, so the required pace is 120 minutes divided by 13.109, which is 9:09 per mile, or 5:41 per kilometre. That's the number to train around. Now consider what going out too fast costs. Running the first three miles at 8:40 pace banks about 87 seconds against target, which feels like insurance. But the energy cost of running faster than sustainable pace early is disproportionate, and the common result is a fade over the final third where pace drops to 9:45 or slower. Losing 36 seconds a mile across the last four miles costs about 144 seconds, wiping out the banked time and more. The pattern is well enough documented that negative splitting, running the second half slightly faster than the first, is the standard recommendation for distance races. The practical version of a two-hour plan is to run the first few miles a touch slower than 9:09, settle into target pace through the middle, and use whatever remains over the final miles. That approach feels harder early and easier late, which is the opposite of how most first-time attempts go.

Deciding what pace to train at

One of the more common training errors is running most sessions at roughly the same moderate effort, hard enough to be tiring but not hard enough to drive adaptation, and easy enough to accumulate fatigue without recovery. Most structured training distributes effort across distinct zones. Easy running, typically well slower than race pace and conversational, makes up the bulk of weekly volume in most endurance programmes and builds aerobic capacity while allowing recovery. Tempo or threshold running sits near the pace you could sustain for about an hour, comfortably hard rather than exhausting. Interval work runs faster than race pace with recovery between repetitions. Race pace itself appears in specific sessions to rehearse the target effort. The proportions vary by programme, but the general finding across endurance sports is that a large majority of training volume should be genuinely easy, with a smaller proportion genuinely hard, and comparatively little in the moderate middle. Runners who calculate their pace and then run every session at or near that figure typically plateau, because there's no easy running to build a base and no hard running to raise the ceiling.

Why pace varies with conditions, and how to account for it

A pace figure describes performance under the conditions it was achieved in, and several factors shift it enough to matter. Heat is the largest for most runners: performance degrades noticeably above roughly 15 degrees Celsius, and the effect compounds with humidity because evaporative cooling becomes less effective, so a pace comfortable on a cool morning can be unsustainable on a warm afternoon at the same effort. Elevation gain costs time that flat-course pace targets don't account for, and the time lost climbing is generally not fully recovered descending. Altitude reduces oxygen availability, with meaningful effects above roughly 1,500 metres that take weeks to partially adapt to. Wind costs more into a headwind than it gives back with a tailwind. Surface matters, with trail and soft ground slower than road at equal effort. The practical response is to run by effort rather than by pace when conditions are unusual, using perceived exertion or heart rate as the constant and letting pace fall where it falls. Runners who hold a pace target through a hot race frequently end up worse off than those who adjusted early, because the cost of overreaching in heat accumulates rather than being recoverable within the session.

Variations: race pace prediction, split pacing, and grade adjustment

Several extensions build on basic pace arithmetic. Race time prediction formulas estimate performance at one distance from a known result at another, with Riegel's formula being the most widely used, applying an exponent that accounts for pace slowing as distance increases. These are reasonable for adjacent distances and less reliable across large gaps, particularly predicting a marathon from a 5K, since endurance and speed are somewhat different capacities. Split pacing plans divide a race into segments with specific targets, whether even splits, negative splits, or a deliberate profile matching a course's terrain. Grade-adjusted pace, offered by several training platforms, estimates what your effort would have produced on flat ground, making hilly runs comparable to flat ones. Age-graded scoring compares a performance against the world best for your age and sex, which lets runners of different ages compare achievements meaningfully and gives a way to track whether performance is genuinely declining or simply reflecting age.

Using pace effectively

Calculate target pace from your goal finish time and the exact race distance, since standard distances aren't round numbers in either miles or kilometres and rounding introduces meaningful error over longer races. Plan to run the first portion slightly slower than target rather than banking time, since the energy cost of early overreaching typically exceeds what it saves. Distribute training across genuinely easy and genuinely hard sessions rather than running everything at moderate effort, which is the most common way training plateaus. Run by effort rather than pace in heat, wind, or on hills, since holding a pace target in adverse conditions costs more than it gains. And recalculate targets periodically as fitness changes, rather than training indefinitely toward a figure set months earlier.

What people get wrong

• Banking time by starting faster than target pace, when the energy cost of early overreaching typically produces a late fade that more than erases the gain.
• Running most training sessions at moderate effort, which is too hard to recover from and too easy to drive adaptation, and is the usual reason progress stalls.
• Holding a pace target through heat, wind, or hills, when running by effort and letting pace adjust produces better outcomes than forcing the number.
• Using rounded race distances, when a 5K is 3.107 miles and a half marathon 13.109, and the difference matters when targeting a specific finish time.

Where the math comes from

Pace per mile = Total Minutes / Distance in miles, where total minutes is (Hours × 60) + Minutes. Pace per kilometre = Total Minutes / (Distance × 1.60934). Speed in miles per hour = Distance / (Total Minutes / 60). Pace is displayed in minutes and seconds, with the seconds component derived from the fractional part of the decimal pace multiplied by 60.

Questions and answers

Related calculators

Pace Per Mile · VO2 Max Estimate · Workout Frequency · One-Rep Max · Heart Rate Zone