What pace actually tells you
Pace is speed turned upside down. Instead of asking how much ground you cover in an hour, it asks how long one unit of ground costs you — nine minutes for this mile, five and a half for that kilometer. That inversion is the whole reason runners use it. A race is a fixed distance, so a number expressed per unit of distance multiplies straight into a finish time in your head. At 8:00 per mile a half marathon takes a shade over 1:44, and you can work that out on the start line without a calculator.
Speed in miles per hour does not behave that way. It is the natural unit when the distance is open-ended and the clock is what is fixed — a treadmill session, a cycling commute, a lap swim. Both describe the same motion; they just answer different questions. This page carries both, and every calculator on it will hand you either.
The other thing pace gives you is a fair comparison across efforts of different length. Total time says nothing on its own: a 52-minute run tells you nothing until you know whether it covered four miles or seven. Pace normalizes the two so a Tuesday recovery jog and a Sunday long run sit on the same scale.
The formula behind the calculator
There is no hidden model here. Three quantities are locked together by one relationship, and giving the calculator any two of them pins down the third:
time = pace × distance
distance = time ÷ pace
The only real work is in the units. Everything is converted to seconds and meters first, the arithmetic happens there, and the answer is converted back out to whatever you asked for. The conversion constants used throughout are one mile as 1,609.35 meters, one yard as 0.9144 meters, and one kilometer as 1,000 meters.
Worked through with the values this page loads with: 6 miles in 47 minutes 30 seconds is 2,850 seconds over 9,656.1 meters, which is 0.29515 seconds for every meter. Multiply by 1,609.35 and you have 475 seconds per mile — 7 minutes 55 seconds. Multiply the same figure by 1,000 instead and you get 295.15 seconds per kilometer, or 4:55.15. Divide 3,600 by the seconds-per-mile figure and the speed falls out as 7.58 miles per hour.
The race-distance table applies that per-unit cost to each standard distance, and the splits table applies it to each whole kilometer and each whole mile you would pass. Both are the same multiplication repeated, which is why they agree with each other by construction.
Pace, time, distance: which one to solve for
The three buttons at the top of the form change which box the calculator fills in rather than changing the maths.
- Pace is the one to use after a run. You know the distance and you know what the watch said, and you want to know how fast that actually was.
- Time is the planning mode. You have a distance in mind and a pace you believe you can hold, and you want the finish time that combination produces. This is how you check whether a goal is arithmetically possible before you build a training block around it.
- Distance is for a fixed window. You have forty minutes before you need to be somewhere and you know roughly how fast you run — how far does that get you?
The event dropdown next to the distance box fills in the standard distances so you do not have to remember that a marathon is 42.195 kilometers or that a half is 21.0975. Choosing an event overwrites whatever is in the distance field, which is the intended behavior, not a bug.
Times are forgiving to type. Placeholder zeros are optional, so a pace of five minutes three seconds can be entered as 5:3 rather than 00:05:03, and the calculator reads the fields from the right: the last number is always seconds, the one before it minutes, the one before that hours.
Splits, and why they beat an average
An average pace is a summary, and like all summaries it hides its own variance. Two runners can finish a 10K in exactly the same time, one having held a metronomic 5:00 per kilometer and the other having gone out at 4:30 and staggered home at 5:40. The average is identical. The races were not.
The splits panel lists the elapsed time you would show at each kilometer marker and each mile marker if you held the pace exactly. Read as a target it is a pacing plan; read against your actual watch data after the fact it is a diagnosis. The gap between the two is where the race was won or lost.
Two terms worth knowing. An even split means the second half of the race takes the same time as the first. A negative split means the second half is faster, which sounds harder than it is — starting a touch conservatively usually costs less than the blow-up that follows starting too fast. The splits table gives you the even-split reference; running the numbers a second time at a slightly slower opening pace shows you what the negative-split version would look like.
The table appears once the distance clears two kilometers, since below that there is not much of a sequence to lay out.
Minutes per mile, minutes per kilometer, miles per hour
Runners in the United States mostly think in minutes per mile; almost everywhere else, and in track and road racing internationally, minutes per kilometer is standard. Treadmills and bike computers add a third convention by showing speed instead. None of these is more correct than the others, and switching between them is a frequent source of confusion — a 5:00 kilometer and a 5:00 mile are wildly different efforts.
Because a mile is roughly 1.609 kilometers, a per-mile pace is always the larger number. The rough mental conversion is to add about 60 percent: a 5:00 kilometer is close to 8:03 per mile. Going the other way, take about five-eighths of the per-mile figure. The Pace Converter tab does the exact version, including the speed units, so you never have to trust the shortcut when it matters.
One practical use for it: gym treadmills are almost always calibrated in miles per hour, so if your training plan is written in minutes per kilometer, the converter tells you which button to hold down.
Finding the leg where you slowed down
The Multipoint Pace Calculator tab exists for the run where the average tells you nothing useful. You take the clock at intermittent points — each lap of a track, each aid station, the top and bottom of a hill — and enter the running totals. It reconstructs each leg by subtracting one row from the row above, then reports the pace for that leg alongside the pace for everything up to that point.
Two things fall out of that pair of columns. The segment column shows the shape of the effort: whether you faded, whether one climb cost far more than it looked like it did, whether your track intervals are drifting slower as the session goes on. The accumulated column shows how much any single bad leg is dragging on the whole, which is often less than it feels at the time.
Each row must be larger than the one above it in both distance and time, because the entries are cumulative rather than per-leg. Rows can each carry their own unit, so a route measured partly in miles and partly in kilometers still works.
Pace, effort and heart rate
Pace measures the output; heart rate measures what that output is costing you. They correlate, but not tightly enough to be interchangeable, and the gap between them is where most of the useful training information lives. The same pace on a cold flat morning and on a humid hilly evening will show up as two very different heart rates, and heart rate is the one telling the truth about the effort.
The most-quoted estimate of maximum heart rate is simply 220 minus your age. It is a population average with a wide spread around it — individuals of the same age routinely differ by twenty beats or more — so treat the zones below as a starting frame rather than a personal prescription. A graded exercise test is the accurate way to establish the real number.
| Zone | Share of max | Age 20 | Age 30 | Age 40 | Age 50 | Age 60 | Age 70 |
|---|---|---|---|---|---|---|---|
| Very light Warm-up, cool-down, recovery | 50–60% | 100–120 | 95–114 | 90–108 | 85–102 | 80–96 | 75–90 |
| Light Easy aerobic running | 60–70% | 120–140 | 114–133 | 108–126 | 102–119 | 96–112 | 90–105 |
| Moderate Steady endurance work | 70–80% | 140–160 | 133–152 | 126–144 | 119–136 | 112–128 | 105–120 |
| Hard Threshold and tempo | 80–90% | 160–180 | 152–171 | 144–162 | 136–153 | 128–144 | 120–135 |
| Maximum Short intervals | 90–100% | 180–200 | 171–190 | 162–180 | 153–170 | 144–160 | 135–150 |
Beats per minute, from the 220-minus-age estimate. Individual maximums vary widely around it, so read these as a starting frame rather than personal targets.
The pace you can hold for about an hour of hard running sits near what coaches call threshold — the point above which lactate accumulates faster than the body clears it. Below it, effort is sustainable for hours. Above it, the clock starts running out. Knowing roughly where that line falls for you turns a pace number into a decision about how long you can hold it.
What this calculator cannot see
Everything on this page assumes a constant pace over flat, uninterrupted ground. Real running rarely obliges. The projections do not account for:
- Terrain and elevation. A climb costs far more than the equivalent descent gives back, so an out-and-back route is slower than its flat twin even though the net elevation change is zero.
- Fatigue. The finish-time projection multiplies your current pace across the remaining distance. Early in a long race that is optimistic, because holding 10K pace for a marathon is not something the projection knows you cannot do.
- Heat, humidity and wind. All three move achievable pace substantially, and heat in particular compounds over the length of a race rather than applying evenly.
- Course measurement. GPS watches and certified courses disagree, usually with the watch reading long, because a GPS trace cuts corners and adds noise.
- Surface. Track, road, treadmill and trail are not equivalent, and the differences are large enough to swamp the precision the numbers here are printed to.
Use the output as a plan and a reference point rather than a promise. The arithmetic is exact; the assumption that you will hold one pace is the part that bends.
Frequently asked questions
How do I calculate my running pace?
Divide your total time by the distance you covered. Forty-seven minutes thirty seconds over six miles is 2,850 seconds divided by 6, which is 475 seconds — 7 minutes 55 seconds per mile. Converting the time to seconds first avoids the mistake of treating minutes as if they were decimal.
What is a good running pace per mile?
There is no single answer, because it depends on distance, age, terrain and how long you have been running. A useful personal benchmark is your easy pace: the speed at which you could still hold a conversation. Most recreational runners find that sits somewhere between 9 and 12 minutes per mile, and it is meant to feel comfortable rather than impressive.
How do I convert minutes per mile to minutes per kilometer?
Divide the per-mile figure by 1.60935. An 8:00 mile is 480 seconds, and 480 divided by 1.60935 is about 298 seconds, or 4:58 per kilometer. The Pace Converter on this page does it exactly, in both directions and across speed units too.
What pace do I need for a sub-2:00 half marathon?
Just under 9:09 per mile, or about 5:41 per kilometer. Switch to the Time tab, enter that pace with a distance of 13.1 miles, and the calculator shows the finish time it produces — then read the splits panel for the checkpoints to hit along the way.
Are splits the same thing as pace?
No. Pace is a rate; a split is the elapsed time at a specific point. The splits table converts one into the other, showing what the clock should read at each kilometer and mile marker if you hold the pace you entered.
Why does my GPS watch show a different pace?
Two reasons. Watches report instantaneous or recently-smoothed pace, which fluctuates constantly, while this page computes a single average across the whole distance. And GPS traces tend to measure long against a certified course, which makes the watch pace look slightly quicker than the official result.
What is a negative split?
Running the second half of a race faster than the first. It is widely regarded as the more reliable way to race distances from 5K upwards, because the alternative — going out fast and slowing — usually loses more time at the end than it gained at the start.
Can I use this for walking, cycling or swimming?
Yes. The relationship between pace, time and distance does not care what activity produced it. Cyclists usually prefer the speed units and swimmers typically think in time per 100 meters, which you can get by entering the distance in meters and reading the per-kilometer figure.
This calculator is provided for general fitness and planning purposes and is not medical advice. Estimates such as the 220-minus-age maximum heart rate are population averages with wide individual variation. If you are starting or significantly changing an exercise program, or have a heart, respiratory or other health condition, speak to a qualified healthcare professional first. Learn more about how we build these tools or read our privacy policy.