Free Pace Calculator Online

Pace Calculator: Solve Pace, Time, or Distance From the Other Two

A pace calculator solves one simple relationship — pace equals time divided by distance — for whichever piece of a run, walk, or ride you don't already know. Know your distance and finish time and want your per-kilometer or per-mile pace? Know your target pace and distance and want a projected finish time? Or know your pace and how long you moved and want to back into the distance covered? Three tabs at the top of this tool switch which value gets solved for, and the fields below adjust to ask only for the two inputs that particular calculation actually needs.

This is a straightforward, informational math tool, not a training plan, and the numbers it returns are only as good as the pace, time, and distance you feed into it. It carries no medical claims of its own and nothing here is medical advice, but pace targets still interact with training load — runners returning from injury, managing a chronic condition, or increasing mileage quickly should still run any new pace goal past a coach or physician before chasing it on the road, rather than treating a calculated number as a target to hit regardless of how the body responds on a given day.

How to Use the Pace Calculator

1. Choose which value you want solved for using the three buttons at the top: Calc pace, Calc time, or Calc distance. The two input sections shown below change depending on which one you pick, since the tool only asks for the two values needed to solve the third.
2. When distance is a required input, enter the number and choose a unit, kilometers or miles, from the dropdown next to it.
3. When time is a required input, enter hours, minutes, and seconds in three separate boxes rather than typing one combined string.
4. When pace is a required input, enter minutes and seconds per your chosen distance unit in two separate boxes.
5. As soon as both required fields have valid values, a result card appears below showing the solved value, pace, time, or distance, formatted for easy reading.
6. When solving for pace specifically, the result card also shows your equivalent speed in distance-per-hour, a handy cross-check if you're more used to thinking in km/h or mph than minutes-per-distance.

Why Runners and Cyclists Reach for a Pace Calculator

• Planning a race-day pace strategy. Knowing a goal finish time for a 10K or marathon isn't the same as knowing what that pace feels like per kilometer or mile — converting the target time into a per-distance pace turns an abstract goal into a number you can check against a watch at each split.
• Predicting a finish time from training paces. If you've been running comfortably at a known pace during training, plugging that pace and your race distance into the calculator gives a reasonable projected finish time, useful for setting a starting-corral expectation or a personal goal.
• Working out splits for interval training. Structured workouts often specify a target pace for repeated distances, and converting that pace into a concrete time for the specific distance you're running removes the mental math mid-workout.
• Comparing performances across different distances. Pace per kilometer or mile is a common unit for comparing effort across a 5K, a half marathon, and a full marathon, even though the absolute times involved are very different from one another.
• Converting between metric and imperial units. Race organizers, training plans, and GPS watches don't always agree on kilometers versus miles, and switching the distance unit here recalculates pace and speed without you doing the conversion by hand.
• Checking a treadmill or rowing machine display against a real-world unit. Cardio machines often report their own speed or pace figures in whatever unit the manufacturer chose, and running the same numbers through this tool translates them into the pace-per-kilometer or pace-per-mile figure a training plan actually calls for.

The Math Behind Every Result

Every value this tool produces comes from one relationship, rearranged three ways depending on what you're solving for:

Solving for	Formula	Worked example
Pace	pace = time / distance	50:00 over 10 km = 5:00/km
Time	time = pace x distance	5:00/km over 10 km = 50:00
Distance	distance = time / pace	50:00 at 5:00/km = 10 km

The 10-kilometer, 50-minute example is a useful one to check by hand: fifty minutes is 3,000 seconds, and dividing that by 10 kilometers gives exactly 300 seconds, or 5 minutes flat, per kilometer. The same arithmetic works regardless of whether your time is entered as raw seconds, a "MM:SS" clock format, or a longer "HH:MM:SS" format for anything over an hour — the calculator converts whatever format you type into total seconds internally before doing the division, then formats the result back into a readable clock string for display.

Speed, shown alongside pace when that's the value you're solving for, is really the same relationship inverted and rescaled to a per-hour figure — distance divided by time expressed in hours, rather than time divided by distance. A 5:00/km pace corresponds to 12 km/h, since covering one kilometer every 5 minutes means covering twelve of them in a 60-minute stretch. Both numbers describe an identical effort; pace is simply the more common way distance runners think about it, while speed is more familiar to cyclists browsing a bike computer.

How the Same Pace Plays Out Across Race Distances

Because time is just pace multiplied by distance, a single training pace produces very different finish times once you scale it up from a short interval to a full marathon. The table below applies the time = pace x distance relationship from the earlier section to four standard race distances, using a half marathon at 21.0975 km and a full marathon at 42.195 km:

Pace	5K	10K	Half marathon	Marathon
5:00/km	25:00	50:00	1:45:29	3:30:59
5:30/km	27:30	55:00	1:56:02	3:52:04
6:00/km	30:00	1:00:00	2:06:35	4:13:10

Notice how a modest 30-second-per-kilometer difference in pace compounds into a roughly 21-minute gap by marathon distance, even though it barely registers over a 5K. That scaling effect is exactly why small, sustainable pace improvements in training matter more the longer the target race is, and why pacing guidance for a marathon is usually far more conservative than pacing guidance for a 5K.

Common Pace Calculation Mistakes

Unit mismatches cause more wrong answers here than any arithmetic error. Racing a 10K but entering your goal pace in minutes-per-mile instead of minutes-per-kilometer will produce a finish-time projection that's off by a wide margin, since a mile is roughly 1.6 times a kilometer — always double-check which unit the distance dropdown is set to before trusting a solved time. A second common slip is confusing total time with pace when typing numbers into the wrong field: entering "45" into a pace box meant for minutes-per-kilometer when you actually meant a 45-minute total time produces a nonsensical result, since a 45-minute-per-kilometer pace is closer to a slow stroll than a run. Finally, watch for rounding compounding across long distances: a pace rounded to the nearest second per kilometer can shift a marathon-distance projected finish time by close to a minute purely from rounding, which is normal and expected rather than a sign of a broken calculation.

Manual Pace Math vs. Using This Tool

• Mental math mid-run. Experienced runners sometimes estimate splits in their head during a race, but doing that reliably under fatigue, especially converting between minutes-and-seconds and decimal minutes, is a skill that takes real practice and still leaves plenty of room for error.
• GPS watches and running apps. Most modern running watches calculate live pace automatically from GPS data, which is excellent for real-time feedback but doesn't help with pre-run planning, deciding on a goal pace before you've laced up your shoes.
• Spreadsheet formulas. A time-per-distance formula in a spreadsheet works fine for a training log you're already maintaining, though converting between "MM:SS" text and a usable number for arithmetic takes an extra formatting step most spreadsheet software doesn't handle natively.
• Race-pace wristbands and printed charts. Some races sell or hand out laminated pace-band charts pre-printed with splits for common goal times; useful on race morning, but inflexible if your goal time falls between the printed options or you want to test a pace the chart doesn't cover.
• This calculator's API. Training-log apps, race-registration sites, or coaching dashboards that need pace math built into their own interface can call the same solve-for-pace-time-or-distance logic as a metered API endpoint that accepts flexible time formats and returns a structured result — see the API documentation for request details and credit cost.

Can I enter time as just a number of seconds instead of MM:SS?

Yes. The time and pace fields both accept a plain number of seconds in addition to "MM:SS" or, for longer durations, "HH:MM:SS" — whichever format is more convenient for the number you happen to be working with.

Does this calculator account for elevation, terrain, or weather?

No. Pace here is pure time-over-distance arithmetic with no adjustment for hills, heat, wind, or surface — a flat 5:00/km and a hilly 5:00/km are treated identically by the math, even though they represent very different physical efforts. Factor terrain and conditions into your goal pace yourself before entering it here.

Why did switching from kilometers to miles change my pace number?

Pace is always expressed per unit of distance, so a fixed finish time divided by a longer unit, a mile, produces a different-looking number even for the exact same run — switching units recalculates the same underlying speed into the new distance's terms rather than changing anything about your actual performance that day.

What's a reasonable starting pace goal for a first 10K?

That depends entirely on individual fitness, so there's no single universal number — a sensible approach is to use a recent comfortable training pace as your time and distance input and let the calculator project a realistic finish time, rather than picking an aspirational pace with no training data behind it.

What's the difference between pace and speed, and does it matter which one I use?

They describe the identical rate of movement expressed two different ways — pace is time per unit of distance, while speed is distance per unit of time — so converting between them never changes the underlying effort, only how it's displayed. Distance-sport communities tend to have a strong default: runners generally talk in pace, cyclists generally talk in speed, and picking whichever one matches how your training plan or race organizer communicates times is usually the more practical choice.

Related Fitness Tools

Pace is one piece of a broader running or endurance plan. Check the heart rate zones calculator to see what effort level a given pace roughly corresponds to, and the calories burned calculator to estimate the energy cost of a run at that pace and duration. For strength work on rest days, the one-rep max calculator covers the equivalent planning problem for lifting.