You just ran a 5K in 27 minutes. Was that good? Could you hold that pace for a 10K? What about a half marathon? These are the questions every runner asks — and the answers all start with understanding your pace.
What is running pace, exactly?
Pace is how long it takes you to cover one mile or one kilometer. That's it. If you ran 3 miles in 24 minutes, your pace was 8:00 per mile. It's the single most useful number in running because it tells you exactly how fast you're going in terms your body can feel.
Speed (miles per hour) is how we measure cars. Pace (minutes per mile) is how we measure runners.
Why does the distinction matter? Because when you're out on a run, you don't think "I'm going 7.5 mph." You think "I'm running 8-minute miles." Pace connects directly to effort in a way that speed doesn't.
How to calculate your running pace
The math is straightforward: divide your total time by the distance you ran. A 30-minute 5K means 30 ÷ 3.1 = roughly 9:41 per mile. But who wants to do division mid-run?
That's where a pace calculator earns its keep. Plug in any two of the three variables — distance, time, or pace — and it spits out the third. You can switch between miles and kilometers, pick preset race distances like 5K, 10K, half marathon, or marathon, and instantly see your pace, speed, and projected finish times.
When you open the tool, you'll see three modes:
- Pace mode — Enter distance and total time, get your pace per mile and per kilometer
- Time mode — Enter distance and your target pace, get your projected finish time
- Distance mode — Enter time and pace, find out how far you went
Each mode also shows your speed in both km/h and mph, so you've got the full picture.
Pace charts for popular race distances
Here's a quick reference for common race finish times and what pace they require:
5K (3.1 miles)
- 20:00 finish → 6:26/mile
- 25:00 finish → 8:03/mile
- 30:00 finish → 9:41/mile
- 35:00 finish → 11:17/mile
10K (6.2 miles)
- 45:00 finish → 7:15/mile
- 50:00 finish → 8:03/mile
- 60:00 finish → 9:41/mile
Half marathon (13.1 miles)
- 1:45:00 finish → 8:01/mile
- 2:00:00 finish → 9:09/mile
- 2:15:00 finish → 10:18/mile
Marathon (26.2 miles)
- 3:30:00 finish → 8:01/mile
- 4:00:00 finish → 9:09/mile
- 4:30:00 finish → 10:18/mile
- 5:00:00 finish → 11:27/mile
Don't see your exact time? Punch your numbers into the pace calculator and get a precise answer in seconds.
Using pace to set realistic race goals
Here's a mistake runners make constantly: they pick a goal finish time based on what sounds impressive rather than what their training supports. "I want to run a sub-4-hour marathon" is great. But if your current easy run pace is 11:00/mile, a 9:09/mile marathon pace isn't realistic yet.
A better approach? Work backwards from your recent race results.
If you ran a 25-minute 5K, that's about an 8:03/mile pace. For longer distances, you'll naturally slow down — most runners add 15-30 seconds per mile when doubling the race distance. So a reasonable 10K goal might be 8:20-8:30/mile pace, putting you around 52-53 minutes.
Use the time mode in the pace calculator to test different scenarios. Enter half marathon distance, try a few pace targets, and see which finish times feel achievable based on where you are right now.
Training paces: not every run should be a race
One of the biggest breakthroughs new runners experience? Slowing down. Seriously.
Most of your training should happen at conversational pace — that's about 1-2 minutes per mile slower than your race pace. If you're targeting 9:00/mile for a 10K, your easy runs should be somewhere around 10:00-11:00/mile.
Here's a rough breakdown of training zones based on your race pace:
- Easy/recovery runs — Race pace + 1:30 to 2:00/mile (60-70% of your weekly mileage should be here)
- Tempo runs — Race pace + 0:15 to 0:30/mile (comfortably hard, you can say a few words but not chat)
- Intervals/speed work — Race pace minus 0:30 to 1:00/mile (short bursts with rest periods)
- Long runs — Race pace + 1:00 to 1:30/mile (building endurance, not speed)
Running too fast on easy days is the number one reason runners get injured or plateau. Your pace calculator isn't just for race day — it's for every run in between.
Pace per mile vs. pace per kilometer
If you're following a training plan from Europe or using a metric-based running app, you'll see paces in minutes per kilometer. The conversion factor is 1.609 — so a 5:00/km pace equals roughly 8:03/mile.
You don't need to memorize that. The pace calculator shows both units automatically every time you calculate. It displays pace per km, pace per mile, speed in km/h, and speed in mph all at once.
How pace changes with distance
Ever wonder why your 5K pace feels so much faster than your marathon pace? It's physiology. At shorter distances, your body can rely more on anaerobic energy systems. As distance increases, you shift toward aerobic energy, which is more sustainable but slower.
Here's a general rule of thumb for how pace slows as distance grows:
- 5K to 10K: Add 15-20 seconds per mile
- 10K to half marathon: Add 15-25 seconds per mile
- Half marathon to marathon: Add 10-20 seconds per mile
These aren't exact — fitness level, terrain, weather, and training all play a role. But they're a solid starting point for setting expectations.
Common pace calculation mistakes
Not accounting for elevation. A flat 5K and a hilly 5K are two very different races. If your goal race has significant hills, your target pace should be adjusted. Expect to add 10-15 seconds per mile for a moderately hilly course.
Comparing treadmill pace to outdoor pace. Treadmills don't account for wind resistance, and many models aren't perfectly calibrated. Your 8:00/mile on the treadmill might feel more like 8:20-8:30 outside.
Ignoring weather. Heat kills pace. For every 10 degrees above 55°F (12°C), expect to add about 1-2% to your pace. A 9:00/mile runner on a 75°F day might genuinely be running at 9:10-9:20 effort even though it feels the same.
Starting a race too fast. You feel great at the start line, adrenaline is pumping, and you blast through mile one 45 seconds faster than your target pace. By mile 4, you're dying. Negative splits — starting slightly slower and finishing faster — almost always produce better overall times.
Putting it all together
Knowing your pace turns guesswork into a plan. Whether you're training for your first 5K or chasing a marathon PR, the process is the same: figure out where you are now, set a realistic target, and train at the right effort levels to get there.
Grab the pace calculator, enter your most recent race result, and start mapping out your next goal. The numbers don't lie — and once you know yours, every training run has a purpose.