Pace Calculator Online — Free Pace Calculator Tool
CodexFuse Team · 2026-11-02T18:15:05.998Z · 9 min read min read
Free pace calculator: enter distance and finish time to get pace per km, pace per mile, and average speed — with a worked 10K example.
A pace calculator turns a run you have already done — or one you are planning — into a single, usable number: how long each kilometre or mile should take. Enter a distance and a finish time, and it returns your pace per kilometre, your pace per mile, and your average speed, so you can train, race, and set targets without mental arithmetic on the side of the road.
Most runners do not fail because they lack effort. They fail because they start too fast, fade in the second half, and finish wondering what went wrong. A pace calculator removes that guesswork before you lace up, and it gives you a number you can actually hold for the whole distance.
What is a pace calculator?
A pace calculator is a free online tool that divides your total running time by the distance you covered, giving your average pace per kilometre and per mile plus your average speed in kilometres per hour. You enter the distance in kilometres and your finish time in hours, minutes, and seconds, then it does the division and the kilometre-to-mile conversion for you.
The maths behind it is simple, which is exactly why it is worth getting right. Pace is time divided by distance. Run 10 km in 50 minutes and your pace is 50 divided by 10, or 5:00 per kilometre. That same effort is 8:03 per mile at 12.0 km/h — the tool on CodexFuse shows all three figures at once, so you never have to convert between them yourself.
How to use the CodexFuse pace calculator
The tool asks for only two inputs, and it works in four short steps:
- Enter your distance: type the distance you ran, or plan to run, in kilometres.
- Enter your finish time: add the time in hours, minutes, and seconds — for example, 0 hours, 50 minutes, 0 seconds for a 50-minute 10K.
- Click Calculate Pace: the tool divides time by distance and converts the result.
- Read and copy your result: you get pace per kilometre, pace per mile, and average speed in km/h, with a copy button for saving or sharing the result.
Check your result against the page default: 10 km in 50:00 gives 5:00 per kilometre.
Time a training run with a stopwatch first, then feed the exact time into the pace calculator. A rounded "about 45 minutes" can shift your pace by 10–15 seconds per kilometre, which is enough to wreck a race plan.
A worked example: Amna's 10K target
Amna runs with a local club twice a week and has signed up for her first 10K race in six weeks. Her most recent timed run gives her a solid starting point, and the calculator turns it into a race plan she can actually follow.
Here is her real input and output, step by step:
- What she ran: 8 km on a flat park loop, timed from start to finish.
- Her finish time: 42 minutes and 36 seconds, or 42.6 minutes in decimal form.
- Pace per kilometre: 42.6 divided by 8 equals 5.325 minutes, which is 5:20 per kilometre (rounded to the nearest second).
- Pace per mile: 5.325 multiplied by 1.60934 equals 8.57 minutes, or 8:34 per mile.
- Average speed: 8 km divided by 0.71 hours equals around 11.3 km/h.
| Figure | Amna's result | What it means for her race |
|---|---|---|
| Current pace | 5:20 per km | The pace she can already hold for 8 km |
| 10K at the same pace | 53:15 | 5.325 minutes × 10 km — a realistic first target |
| Stretch target | 52:00 | Needs 5:12 per km — a small, honest step up |
| Too ambitious | 48:00 | Needs 4:48 per km — far beyond her current fitness |
Amna's plan writes itself from that table. She trains at 5:20 per kilometre for her long runs, adds one session a week slightly faster than that pace, and goes into race day aiming for 53:15 with 52:00 as a stretch goal if conditions are good. She is not guessing, and she is not chasing a 48-minute finish her training has not earned yet. That is the difference a two-minute calculation makes.
You can run the same check on your own numbers in the pace calculator — enter your last timed run, note the pace, then multiply it by your race distance to see what finish time your current fitness actually supports.
Your pace on a flat, cool morning will not match your pace on hills, in heat, or into a headwind. Treat the calculator's result as your baseline for good conditions, then add 10–20 seconds per kilometre on hilly or hot days rather than forcing the number and blowing up halfway.
Common pace mistakes that cost runners minutes
The calculator itself is simple, so most errors happen before anyone opens it. Watch for these:
- Using a guessed distance: a "roughly 5K" loop measured by a car odometer or a vague map estimate can be 200–300 metres out, which skews every pace figure that follows.
- Rounding the time: "about 30 minutes" instead of 29:41 hides real progress and makes week-to-week comparisons meaningless.
- Chasing someone else's pace: a training partner's 4:30 per kilometre is irrelevant if your current fitness supports 5:20 — run your own number.
- Ignoring the second half: an even pace beats a fast start and a slow finish almost every time, because the fade always costs more than the early gain.
A precise tool helps here too: time your run with an online stopwatch, set intervals with an online timer, and only then calculate the pace. Clean inputs give clean outputs.
Just as a pace calculator turns a vague goal into a number you can hold, CodexFuse turns scattered IT — hosting, email, security, backups — into one fully managed platform on credits, so the people running your club or business stop babysitting servers and get back to the work that matters.
Get Started with CodexFuseHow do you convert pace per km to pace per mile?
To convert pace per kilometre to pace per mile, multiply your per-kilometre pace by 1.60934, the exact number of kilometres in a mile. A 5:00 per kilometre pace becomes 8:03 per mile, and a 6:00 per kilometre pace becomes 9:39 per mile, because each mile is longer than each kilometre.
Can a pace calculator plan your whole race?
A pace calculator can set your target pace and predict a realistic finish time, but it cannot plan your whole race on its own. It does not know about hills, heat, wind, crowds at the start, or how your fitness changes over a training block, so its answer is a baseline to adjust, not a promise.
That is also where the tool's honest limits sit, and they are worth knowing before you rely on it. The CodexFuse pace calculator solves for pace only: it takes a distance and a time and returns pace and speed. It does not solve for time or distance, it has no race-distance presets, and both inputs must be above zero — negative values are rejected. If you want to work backwards from a target pace to a finish time, multiply the pace by the distance yourself, as in Amna's example above. For strength work that supports your running, a one-rep max calculator can set sensible gym loads without the same guesswork.
Pair your pace work with precise timing: read how an online stopwatch removes timing errors from training runs before you calculate anything.
Frequently Asked Questions
How do I calculate my running pace?
Divide your total running time by the distance you covered. Run 10 km in 50 minutes and your pace is 5:00 per kilometre. Multiply by 1.60934 for pace per mile — in this case 8:03 per mile at 12.0 km/h. The CodexFuse pace calculator does both conversions automatically.
What pace do I need to run a 5K in 25 minutes?
You need 5:00 per kilometre, which is 8:03 per mile at 12.0 km/h. For a 5K in 30 minutes the pace is 6:00 per kilometre, 9:39 per mile, at 10.0 km/h. Enter 5 km and your target time in the tool to check any other goal.
How do I work out my marathon pace?
Divide your goal time by 42.195 km. A 4-hour marathon needs 5:41 per kilometre, 9:09 per mile, at around 10.55 km/h. A half marathon in 1:45:00 needs 4:59 per kilometre, 8:01 per mile, at around 12.06 km/h.
Does the pace calculator work for walking or cycling?
The maths works for any distance and time, so you can use it for a walk, a hike, or a cycle ride — but the labels are running-focused, and the result is an average pace, not a measure of effort on hills or rough ground. For mixed terrain, treat the figure as a rough guide.
Why does my race pace differ from my training pace?
Race-day adrenaline, crowds, course profile, weather, and accumulated fatigue all shift your pace, often by 10–30 seconds per kilometre. Your calculator pace is your trained baseline; adjust it for conditions on the day rather than assuming the number will hold exactly.
What does this pace calculator not do?
It calculates pace from the distance and time you enter only. There are no race-distance presets and no solve-for-time or solve-for-distance mode, and distance and time must both be above zero. Use the multiplication method in the worked example above to turn a target pace back into a finish time.
Run your number, then run your race
Your next run does not need a new watch, a new app, or a new training philosophy. It needs one timed effort, one honest calculation, and a target pace you can actually hold. Enter your last run in the pace calculator, write down the pace, and build your next six weeks around that number — not around a guess, and not around someone else's.
And if you run a club, a coaching business, or any small organisation whose website, registrations, and email eat up the hours you should spend coaching, stop babysitting that infrastructure too. Move your hosting, business email, security, and backups to CodexFuse today: one fully managed platform, paid for with credits as you use it, no subscriptions and no server admin. Get started with CodexFuse now, and put the admin hours back into the running.
