Running Pace Calculator: Find Pace, Finish Time, and Race Splits

A training plan falls apart when the numbers are fuzzy. You know you want a 10K under 50 minutes, or a half marathon around 1:45, but the pace per kilometer, the equivalent per mile, and the implied speed never quite line up in your head. The Running Pace Calculator solves any one of pace, finish time, or distance when you know the other two, then shows speed in km/h and mph plus predicted finish times from 1 km through a full marathon.

Everything runs in the browser. There is no account, no upload, and no round-trip to a server, so you can check a workout on a phone at the track and keep the numbers private.

This guide walks through the three solve modes, the unit switch between kilometers and miles, how predicted splits are built, and practical ways to use the tool before a race, during training, or when converting a GPS watch readout.

Why Use the Running Pace Calculator?

• Three-way solver. Switch between Find Pace, Find Time, and Find Distance. The form hides the field you are solving for, so you only enter what you already know.
• Kilometers and miles together. Work in km or mi. Pace is shown per kilometer and per mile, so a 5:00/km plan is immediately comparable to an 8:03/mi watch setting.
• Speed without extra math. Every result includes km/h and mph. That is useful when a treadmill shows speed instead of pace, or when you want a sanity check against a bike computer or car odometer.
• Race split table. Once a pace is known, the tool predicts finish times for 11 common distances: 1 km, 1 mile, 5K, 10K, 15K, 10 miles, 20K, half marathon, 25K, 30K, and marathon.
• Copy-friendly times. Results use H:MM:SS and M:SS formatting, with a copy button on the main result so you can paste a target into a notes app or race plan.
• Private and offline. After the page loads, calculations stay on the device. Useful on a race-morning flight or a gym with spotty signal.

Key Features

The solver always needs two of the three inputs. Pace is entered as minutes and seconds per the selected unit (for example 5 minutes 0 seconds per km). Time is hours, minutes, and seconds, so a marathon goal of 3:30:00 is a first-class input, not a decimal hour.

Predicted splits assume even pacing. They are a planning table, not a course-adjusted forecast. Hills, weather, and aid-station stops still belong in your race strategy.

How to Use

1. Open the Running Pace Calculator and pick a mode: Find Pace, Find Time, or Find Distance.
2. Choose km or mi. If you are converting a Garmin or Apple Watch workout that stores miles, switch to mi before you type.
3. Enter the two values you know. For a 10 km in 50:00, use Find Pace, distance 10, unit km, time 0 hours, 50 minutes, 0 seconds.
4. Read the primary result, then the secondary line (the other unit, plus km/h and mph). Scroll to Predicted Finish Times to see what the same pace would do at 5K, half marathon, and marathon.
5. Copy the result if you need it elsewhere, or hit Reset and try a second scenario (easy run vs race pace) without reloading.

Example: 10 km in 50:00 is 5:00/km, about 8:03/mi, 12.0 km/h, and 7.5 mph. The split table then shows a 5K near 25:00 and a marathon near 3:31 if you held that pace the whole way — which most runners will not, but the table still makes the goal concrete.

Understanding Pace, Speed, and Splits

Pace and speed describe the same motion with inverted units. Pace is time per distance (min/km or min/mi). Speed is distance per time (km/h or mph). If you run 10 km in 50 minutes:

• Pace per km = 50 min ÷ 10 km = 5:00/km
• Pace per mile = 5:00/km × 1.609344 ≈ 8:03/mi
• Speed = 10 km ÷ (50/60) h = 12.0 km/h

The calculator uses the international mile of 1.609344 km. Race distances in the split table match common road-race definitions: 5K is 5.000 km, 10K is 10.000 km, half marathon is 21.0975 km, and marathon is 42.195 km. A “1 mi” row is the statute mile, not a rounded 1.6 km.

The three equations the tool solves are:

• Pace = time ÷ distance
• Time = pace × distance
• Distance = time ÷ pace

Because time is stored internally in seconds, a 5:00/km pace is 300 seconds per kilometer. A 21.0975 km half marathon at that pace is 21.0975 × 300 ≈ 6329 seconds, or 1:45:29. That is why the split table can show seconds that look “off” compared with a mental 5:00 × 21 = 1:45:00 — the extra 97.5 meters matter.

Even splits are an assumption, not a prescription. Many plans use negative splits (second half faster) or a conservative first 5K. Use the table to set a ceiling (“do not go faster than 5:00/km early”) as often as a target (“average 5:00/km”).

When you toggle km and mi, remember that the pace fields are labeled for the active unit. A 5:00 entry in km mode is 5:00 per kilometer; the same digits in mi mode are 5:00 per mile, which is a much faster effort. Always glance at the /km or /mi suffix before you calculate a race time.

Practical Use Cases

Set a 5K or 10K race goal from a recent workout

You just ran 8 km in 42:00 on a flat loop. Switch to Find Pace, enter 8 km and 42:00, and read 5:15/km. Open the split table: the 5K row is your even-pace 5K prediction, and the 10K row is the extrapolation. If the 10K prediction is slower than the time you want on race day, you know the workout was not yet at goal pace — useful honesty before you write “sub-50 10K” on a start list.

Convert treadmill speed to running pace

Treadmills often display km/h or mph, not min/km. Suppose the console says 11.0 km/h. You can work backwards: Find Distance is not required if you already think in pace, but Find Time with 1 km and a guessed pace, then nudge until speed reads 11.0 km/h, is a fast way to land on ~5:27/km. Alternatively, enter a 1 km time of 5:27 in Find Pace to confirm the speed line. That mapping is what you want when a coach says “easy 5:40–6:00” and the gym belt only has a speed slider.

Plan a long run duration from a target pace

Long-run plans are often written as “90 minutes easy,” but you still need a distance for fueling and a route. Choose Find Distance, enter 1:30:00 and your easy pace (say 6:15/km). The tool returns how far that is in km and mi, plus the speed so you can compare with last week’s GPS file. If you instead have a 22 km loop you like, use Find Time with 22 km and 6:15/km to see whether you should start earlier to be home before dark.

Translate a marathon goal into km and mile watch alerts

A 3:30:00 marathon is 5:00/km on even splits (42.195 × 5:00 ≈ 3:30:58 — the even-split table will show the extra 58 seconds). Enter Find Time with 42.195 km and 5:00/km, or Find Pace with marathon distance and 3:30:00, then copy both /km and /mi. Set your watch to alert on 5:00/km or 8:03/mi so kilometer markers and mile markers agree. The half marathon row (~1:45:29) is the halfway check you can write on your wristband.

Best Practices

• Match the unit to the watch. If your device is in miles, calculate in miles first, then read the km equivalent. Mixing a km distance with a mile pace is the most common self-inflicted error.
• Use even splits as a baseline, then adjust. Add time for hills, heat, and crowded starts. The table is the flat, perfect-world number.
• Prefer recent race-like efforts over one easy jog. A recovery 5K is a poor predictor of 10K race pace. Use a tempo run or a recent 5K/10K result as the input.
• Sanity-check speed. 4:00/km is 15 km/h — elite territory for many amateurs. If km/h looks unbelievable, a digit is probably wrong.
• Copy the formatted time, not a screenshot. H:MM:SS pastes cleanly into spreadsheets and training logs.
• Recalculate after the race. Enter actual distance and finish time in Find Pace so your next cycle starts from data, not from the goal you missed or beat.

Ready to turn a vague “I want to run faster” into a number you can train against? Open the Running Pace Calculator, pick Find Pace or Find Time, and generate a split table you can actually use on race morning.

Related Tools You Might Like:

• Calorie Calculator — estimate workout energy burn alongside your pace plan
• Interval Timer — structure repeats and recoveries once the target pace is set
• Time Duration Calculator — add warm-up, long-run, and cooldown blocks into a single session length

Happy running — may your splits stay honest.