Why You'd Need to Convert Pace Into Speed
Runners think in pace — minutes per kilometer or mile — because that's how splits, race markers, and most running watches display effort. Treadmills, cycling computers, and many fitness apps, though, work in speed — kilometers or miles per hour — since that's the more natural unit for a machine setting a constant belt speed. For example, imagine you're used to running outdoors at a 5:30/km pace, and you step onto a treadmill that only lets you set a speed in km/h. Without converting, you're stuck guessing at a number, when the actual equivalent speed is a precise 10.91 km/h.
Pace to Speed Conversion Formula
Speed = 60 ÷ Pace (in minutes per unit distance)
This works because pace and speed are mathematical inverses of each other. If your pace is 6 minutes per kilometer, you're covering 1 kilometer every 6 minutes, which means in 60 minutes you'd cover 60 ÷ 6 = 10 kilometers — so your speed is 10 km/h. Let's say your pace is 5 minutes and 30 seconds per kilometer. Convert the seconds into a decimal first: 30 seconds is 0.5 of a minute, so your total pace is 5.5 minutes per km. Divide 60 by 5.5, and you get a speed of roughly 10.91 km/h.
Converting Between Kilometer-Based and Mile-Based Units
Once you have a speed figure, converting between km/h and mph is a separate step from the pace-to-speed conversion itself, and it's worth understanding both directions clearly.
mph = km/h × 0.621371
km/h = mph × 1.60934
Let's say you calculated a speed of 10.91 km/h from a 5:30/km pace. Multiply by 0.621371 to get the mph equivalent: roughly 6.78 mph. Going the other direction, imagine you're running at an 8:00/mile pace instead. Since 60 ÷ 8 = 7.5, your speed is 7.5 mph. Multiply that by 1.60934 to get the km/h equivalent: roughly 12.07 km/h.
Setting a Treadmill Speed to Match Your Outdoor Pace
This is one of the most common practical reasons people need this specific conversion. A typical mistake we often see is a runner guessing at a treadmill speed setting based on a vague sense of "medium effort," rather than calculating the exact number that matches a known outdoor pace. One common scenario: someone who comfortably runs 6:00/km outdoors steps onto a treadmill and sets it to a rounded "10 km/h," not realizing that 6:00/km actually converts to exactly 10 km/h — a happy coincidence in this specific case, since 60 ÷ 6 works out to a clean number, though most paces don't convert to such a tidy figure.
For a pace like 5:45/km, the math is less obviously round: 5.75 minutes per km converts to roughly 10.43 km/h — a number worth calculating precisely rather than rounding to "10.5" or "10," since even a small rounding error compounds meaningfully over a longer treadmill session.
Speed-Based Training Zones vs Pace-Based Zones
Many structured training plans define effort zones by heart rate or by percentage of a runner's maximum speed, rather than by pace directly — particularly common in cycling-adjacent or cross-training programs, and increasingly in some running apps that pull data from a treadmill or indoor trainer. Converting a known outdoor pace into speed makes it possible to translate a pace-based training plan onto equipment that only accepts a speed input, or vice versa, without losing the intended effort level in the process.
Imagine you're following a training plan that specifies a "Zone 2" effort at roughly 65-75% of your maximum running speed, but your plan otherwise describes everything in pace terms. Converting your known paces into speed first makes it possible to check whether a given workout actually falls within that percentage range, since the zone itself is defined in speed terms, not pace.
A Common Scenario: Comparing Data From Different Devices
Many runners experience a frustrating mismatch when comparing data between a running watch that reports pace and a treadmill or cycling app that reports speed, especially when trying to track consistent effort across both outdoor and indoor sessions. Converting both into the same unit — either both as pace or both as speed — before comparing is the only reliable way to check whether an indoor session and an outdoor session were actually run at a comparable effort, rather than eyeballing two differently-formatted numbers side by side and guessing.
A Worked Example: Building a Treadmill Interval Workout From Outdoor Paces
Imagine you're planning an interval workout that normally uses outdoor paces — say, 4 repeats of 800 meters at a 4:30/km race pace, with recovery jogs at 6:30/km in between — but you need to run the session on a treadmill due to bad weather. Converting each pace into speed lets you set precise treadmill numbers instead of guessing: 4:30/km converts to 60 ÷ 4.5 = roughly 13.33 km/h for the fast repeats, and 6:30/km converts to 60 ÷ 6.5 = roughly 9.23 km/h for the recovery jogs.
Having both numbers calculated precisely beforehand means less time fumbling with the treadmill console mid-workout, and a more accurate replication of the intended outdoor effort than rounding both paces to a "fast" and "slow" guess would produce.
A Typical Mistake: Confusing Similar-Looking Numbers Across Units
A typical mistake we often see is someone glancing at a speed figure without checking whether it's in km/h or mph, and misjudging the actual effort involved. A treadmill showing "8" could mean 8 km/h — a brisk walk or easy jog for most people — or 8 mph, which is a genuinely fast running pace equivalent to roughly 7:30/mile. These two numbers look nearly identical on a display but represent a dramatically different physical effort.
Checking the unit label on any speed display before setting a target, especially on unfamiliar gym equipment or when reading fitness data from an app built for a different regional unit system, avoids an easily-made mix-up that could mean attempting a workout at nearly double the intended effort.
Why Speed Matters for VO2 Max and Fitness Testing
Many fitness assessments and VO2 max estimation methods, including several popular running watch algorithms, calculate results based on speed rather than pace, since speed integrates more naturally into the underlying physiological formulas used to estimate aerobic capacity. If you're trying to manually cross-check a watch-reported VO2 max estimate, or compare your numbers against a published fitness test table, you'll often need your pace converted into speed first, since that's the unit most reference tables and formulas are built around.
One common scenario: someone doing a timed test like a 12-minute run (measuring total distance covered in exactly 12 minutes) needs to convert their result into a speed figure to compare it against standard fitness benchmarks, most of which are published in km/h or mph rather than in a pace format.
Using This Calculator Effectively
Enter your pace in minutes and seconds, and select whether it's per kilometer or per mile, to instantly see the equivalent speed in both km/h and mph. This is especially useful right before a treadmill session, when you need a precise speed setting that matches a specific outdoor pace you're targeting.