Pace Calculator
Estimate pace for running, walking, or cycling, solve for total time or distance, check split-by-split pace changes, convert pace units, and project a finish time from a current race split.
Use hh:mm:ss, mm:ss, or seconds.
Current preset: 5K
Placeholder zeros are optional. `5:03` is treated as 5 minutes and 3 seconds.
Multipoint Pace Calculator
Enter cumulative checkpoints from the same session to see how your pace changed between splits. Use cumulative distance and cumulative elapsed time for each row.
| # | Distance | Unit | Time (hh:mm:ss) |
|---|---|---|---|
| 1 | |||
| 2 | |||
| 3 | |||
| 4 | |||
| 5 | |||
| 6 | |||
| 7 | |||
| 8 |
Pace Converter
Convert a pace between per-mile and per-kilometer formats without re-entering the workout.
Use hh:mm:ss, mm:ss, or seconds.
Finish Time Calculator
Project a finish time from your current split and elapsed time if you keep the same average pace for the rest of the effort.
Typical Race Distances and Pace Benchmarks
Use these common distances and sample benchmark paces as quick context when you sanity-check a result. They are not prescriptions.
| Event | Distance | Solid pace example | Aggressive pace example |
|---|---|---|---|
| 1 mile | 1 mi / 1.609 km | 6:00 / mile | 4:30 / mile |
| 5K | 5 km | 5:00 / km | 3:30 / km |
| 10K | 10 km | 5:05 / km | 3:35 / km |
| Half marathon | 21.1 km | 5:25 / km | 3:55 / km |
| Marathon | 42.2 km | 5:40 / km | 4:15 / km |
How to Use a Pace Calculator
Pace is simply time divided by distance. If you know any two of those three pieces, you can calculate the third. That makes pace useful for race planning, workout design, and quick reality checks after a session.
Use the Pace tab when you already know total time and distance. Use the Time tab when you want to know how long a goal pace will take over a set distance. Use the Distance tab when you want to know how far a given pace and time window would carry you.
What a Pace Number Actually Tells You
A pace number is a planning tool, not a promise. A 5:30 per kilometer pace means each kilometer needs to average 5 minutes and 30 seconds over the full effort. It does not mean every split must be identical on hills, in traffic, or late in a race.
Use pace to answer practical questions: Can I hold this effort for the whole distance? Does my current split line up with my goal? If I slow down in the opening segment, what finish time does that point toward? Those are the decisions that make a pace calculator useful.
Pace vs Speed
Pace is usually expressed as time per kilometer or time per mile. Speed is expressed as distance per hour. Endurance athletes often prefer pace because it maps more directly to training cues and race splits.
Both are valid. The best one is the format you can apply consistently when planning sessions and reviewing results. If your watch, treadmill, or coach uses miles while your race plan uses kilometers, convert the pace instead of guessing.
How to Pick the Right Mode
Use Pace mode
When you already know the total distance and total time and want the average pace per mile or per kilometer.
Use Time mode
When you have a target pace and want to know the finish time for a 5K, 10K, half marathon, marathon, or any custom distance.
Use Distance mode
When you know how long you will train and what pace you want to hold, and need to estimate how far that session will cover.
How to Read Split Changes
- Flat splits usually mean steady effort and better pace control.
- Early fast splits can make later segments fade more than expected.
- Late faster splits often suggest you started conservatively or finished strong.
- Use cumulative checkpoints from the same route or race to compare segments cleanly.
How to Use Pace for Training
Easy runs should usually feel repeatable and conversational. Tempo or threshold efforts should feel controlled but demanding. Interval work is different again because pace can be faster while recovery breaks change the average over the full workout.
That is why pace works best when you use it together with context. Weather, terrain, fatigue, and race conditions can all shift what a “good” pace looks like on a given day. The number matters, but the situation matters too.
| Session type | What the pace should feel like | Best use of this page |
|---|---|---|
| Easy run | Controlled, steady, sustainable | Check realistic finish times and compare mile vs kilometer pacing |
| Tempo run | Comfortably hard, repeatable for a block of time | Convert target paces and monitor split drift across segments |
| Long run | Even effort matters more than forced split perfection | Project total time and compare checkpoints during the run |
| Race effort | Specific to distance, terrain, and current fitness | Use presets, finish-time projection, and split analysis together |
When a Finish-Time Projection Is Reliable
- It is more reliable after you have covered a meaningful early segment instead of only a few hundred meters.
- It is more reliable when the course profile stays similar rather than shifting from flat to steep hills.
- It is less reliable when you started too fast, stopped at crossings, or had long downhill openings.
- Use it as a pacing checkpoint, not as proof that the same effort will always hold to the finish.
Practical Notes
- Placeholder zeros are optional. `5:03` already means 5 minutes and 3 seconds.
- Projected finish time assumes your average pace stays constant for the remaining distance.
- Pace from a short segment can be misleading if the route is hilly, crowded, or interrupted.
- For training decisions, compare several sessions rather than reacting to one reading.
Common Pace Mistakes
- Mixing up per-mile and per-kilometer pace when comparing workouts.
- Judging a full race target from a very short fast opening split.
- Ignoring terrain, weather, and crowding when comparing efforts.
- Treating one projected finish time as a guarantee instead of a check-in.
- Reacting to one bad split instead of looking at the full pattern across the effort.