5K pace example
Input: 5 km in 25:00
Output: Pace per km, pace per mile, and split table.
Estimate and plan
Pace Calculator
Use this Pace Calculator as an online run pace, split pace, and finish time tool to solve the pace triangle for distance, time, or pace per mile or per kilometer.
Health & FitnessPublished Mar 13, 2026Last reviewed Mar 13, 2026
Loading tool…
How to use Pace Calculator
- 1
Choose whether you want pace, time, or distance
The solve-for toggle keeps the form focused on the two values you already know instead of forcing you to fill every field at once.
- 2
Enter distance plus time or pace in the supported time format
The route accepts mm:ss or hh:mm:ss input for time-based fields. That keeps running pace entry flexible without letting malformed time strings slip through silently.
- 3
Review pace per km, pace per mile, finish time, and the split table together
The result card gives the main pace outputs first, then the split table so you can skim the core number before checking how it maps across the race or run.
Workflow
Use Pace Calculator when you want straightforward running math without extra training-model noise
Pace Calculator is designed for a practical runner question: if I know two sides of the pace triangle, what does the third side look like, and what does that mean for per-kilometer, per-mile, or 400-meter splits? That is a clean online workflow for race planning, tempo checks, or simple training communication.
The scope is deliberately small. The page does not estimate elevation impact, weather, fatigue, terrain, or GPS drift. It keeps the job to distance, time, pace, and split math, which is exactly why the output stays easy to audit and easy to trust for basic running calculations.
How it works
The calculator solves the pace triangle first and then builds a deterministic split table
Every solve mode routes into the same underlying relationship between distance and time. Once the total distance and total time are known, the page derives pace per kilometer and pace per mile, rounds them consistently, and then builds the split table from the chosen segment size. The split table is not a separate calculator with different rules; it is a formatted view of the same solved result.
That consistency matters most for 400-meter splits and partial final segments. The table keeps one deterministic rounding path so the cumulative times remain predictable even when the total distance does not divide perfectly into equal split units.
Limits
This run pace result stays focused on simple training math only
Pace Calculator does not claim to be a coaching system, a performance predictor, or a terrain-aware race model. It does not estimate how hills, heat, surface, fatigue, or GPS drift will change your real run. That makes the page narrower, but it also keeps the result honest.
Use the output when the decision is mostly arithmetic: what pace matches this finish time, what finish time matches this pace, or how far does this pace-and-time combination travel? Use something more specialized when physiology or course conditions are the real source of uncertainty.
Use cases
Practical running cases where pace per mile, pace per km, and splits help
The page is useful before a 5K or 10K when you want to translate a finish-time goal into per-kilometer or per-mile pace. It is also useful for interval communication because the 400-meter split option makes track-style pacing much easier to skim at a glance.
It is equally practical in reverse. If you know the pace you can hold and the distance you plan to cover, the time mode gives a quick finish-time estimate. If you know the time and pace instead, the distance mode gives a simple projection. Use the route when the math itself is the question.
Example scenarios
Finish time example
Input: 10 km at 5:00 per km
Output: Estimated finish time and split rows.
Frequently asked questions
What time formats does this Pace Calculator accept?
The page accepts mm:ss and hh:mm:ss for time-based fields. It rejects malformed input instead of guessing what a broken time string means, which helps keep the split math and pace math more dependable.
Can it solve for finish time and distance too?
Yes. Pace mode solves from distance plus time, time mode solves from distance plus pace, and distance mode solves from time plus pace. All three modes flow into the same pace-per-km, pace-per-mile, and split table result structure.
Why are 400 m splits included?
400 m splits are useful for track-style pacing and interval communication. Including them next to 1 km and 1 mile makes the tool more useful for runners who switch between road and track contexts without changing calculators.
Does this account for hills or GPS drift?
No. The page stays focused on simple running math only. Elevation, terrain, heat, and GPS drift can all matter in real training or racing, but those variables are outside the scope of this calculator.
When should I not use this tool?
Do not use it as though it were a performance predictor or a terrain-aware model. It is best when the real job is pure pace arithmetic, not when the answer depends mostly on physiology, course profile, or environmental conditions.