Running pace converter
Restate one running pace on every common scale: 5 minutes per kilometer is 12 km/h, 8.04672 minutes per mile and 7.45645430685 mph, so a metric race plan and an imperial watch finally agree. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Amount
- 5
- Input unit
- min_km
- Output unit
- mph
- Result
- 7.4564543069
- Min per km
- 5
- Min per mi
- 8.04672
- Km per h
- 12
Running pace conversion between minutes per kilometer, minutes per mile, kilometers per hour, and miles per hour is a daily task for road racers comparing metric and imperial race plans, coaches writing mixed-unit training tables, GPS-watch users switching between pace and speed displays, and journalists covering marathons for multi-region audiences. People search for a running pace converter when they need one pace or speed figure restated on every common scale, not a general multi-category unit toolbox that also converts mass or temperature. Zero pace and zero speed are rejected because both relations divide by the input amount or by the intermediate speed. Unrecognized unit names fail with a clear validation error instead of silently guessing a nearby symbol.
How the running pace converter maps min/km, min/mile, km/h and mph through a km/h bridge
Start from kilometers per hour as the coherent intermediate: higher values always mean faster motion, which keeps the arithmetic simple for both pace families and for imperial speed. Pace in minutes per kilometer is the reciprocal of speed in kilometers per hour scaled by sixty: kilometers per hour equals sixty divided by minutes per kilometer, and minutes per kilometer equals sixty divided by kilometers per hour.
One international mile is exactly one point six zero nine three four four kilometers, so minutes per mile equals minutes per kilometer times that mile factor, or equivalently sixty times the mile factor divided by kilometers per hour. Miles per hour equals kilometers per hour divided by the same mile constant, and kilometers per hour equals miles per hour times that constant.
When the input is already a pace, the path first inverts through sixty to obtain a speed, multiplies or divides by the mile factor if the pace used miles, then re-expresses the intermediate speed in every requested unit. When the input is already a speed, the path multiplies or divides by the mile factor once and then inverts only for the pace fields. This calculator never mixes those paths ad hoc.
Because every conversion shares the same intermediate, converting a five-minute-per-kilometer easy jog to miles per hour and back, or comparing a watch set to min per mile with a coach table in km/h, stays numerically consistent within ordinary floating-point precision. The tool does not parse colon-separated stopwatch strings as a primary input type, does not invent custom track distances, does not fetch live race results or elevation models, and does not estimate heart-rate zones.
It answers only the algebraic running-pace and running-speed unit conversion people mean when they type running pace converter into a search bar and expect min/km, min/mile, km/h, and mph.
What you enter and what you get back
Send three fields: amount, a finite positive number for the pace or speed magnitude; from, a string naming the input unit; and to, a string naming the output unit. For pace units amount is decimal minutes, so five point five means five minutes and thirty seconds per unit distance. When a unit string is unknown the error message includes Unrecognized unit and lists the four supported families so clients can fix the label rather than guessing.
When amount is not strictly positive the error explains that pace or speed cannot be zero or negative, which covers the classic zero-pace case. Classic checks include five minutes per kilometer becoming twelve kilometers per hour and about seven point four six miles per hour, eight minutes per mile becoming seven point five miles per hour, and ten kilometers per hour becoming six minutes per kilometer.
Where dedicated running pace conversion shows up in real work
Marathon and half-marathon training plans constantly restate target paces from min per kilometer tables used in continental Europe into min per mile for North American athletes, or the reverse when a US coach works with a metric club. Race directors and timing companies publish predicted finish times and pace bands on both scales so international fields can compare without a spreadsheet.
GPS watch and phone apps switch display modes between pace and speed; product teams and support docs need a trusted oracle that matches the international mile and the sixty-minute hour so help articles stay consistent with firmware. Journalism covering Olympic road races and major marathons often quotes winners in min/km for one market and min/mile for another, so a single conversion pass keeps headlines and tables aligned.
Secondary-school and college kinesiology or physics courses assign problems that give a speed on one scale and ask for the equivalent pace on another, often mixing imperial and metric in the same worksheet. If you later need fuel-economy conversion, general multi-category unit conversion, or pure time-unit conversion, treat those as separate search intents and landings rather than overloading this running pace converter page.
What you can do with it
Cross-region race plans
Restate min/km coach tables as min/mile or mph so athletes and race directors share one pace band across metric and imperial markets.
Watch and app display modes
Convert between pace and speed fields when GPS devices or training apps switch units without rewriting conversion factors in every client.
Homework and race coverage
Map student or journalist speed figures among min/km, min/mile, km/h, and mph without hand-written mile constants.
FAQ
How do pace and speed relate?
The same pattern holds for min per mile and mph, with the international mile linking metric and imperial.
What happens if amount is zero?
Pace and speed must be positive finite numbers; a zero pace would divide by zero when converting to speed.
Is amount in minutes or in mm:ss for pace?
Amount is a decimal number of minutes for pace units. Five point five means five minutes and thirty seconds per kilometer or mile.
What does it cost?
The browser tool is free and runs locally.
What is a 5 min/km pace in mph?
A pace of 5 minutes per kilometer is 7.45645430685 mph, which is 12 km/h or 8.04672 minutes per mile. All four figures appear together, so one entry covers a metric plan and an imperial watch.
Related tools
For developers — API access
Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.
API endpoint
Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.
Call it from your stack
curl -X POST https://api.kit.forhosting.com/conv/pace \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"amount":5,"from":"min_km","to":"mph"}'const res = await fetch("https://api.kit.forhosting.com/conv/pace", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"amount": 5,
"from": "min_km",
"to": "mph"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/pace",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"amount": 5,
"from": "min_km",
"to": "mph"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/pace", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"amount":5,"from":"min_km","to":"mph"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"amount":5,"from":"min_km","to":"mph"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/pace", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"amount": 5,
"from": "min_km",
"to": "mph"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.pace",
"status": "queued",
"_links": {
"result": "/tasks/tsk_…/result"
}
}The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.
Pricing
Published price — no tokens, no invented credits. A failed task is never charged.
Errors
| HTTP | Code | Meaning |
|---|---|---|
401 | unauthorized | Missing or invalid API key. |
402 | insufficient_balance | Your balance doesn't cover the task price. |
404 | unknown_type | That task type doesn't exist. |
429 | rate_limited | Too many requests. Use the webhook instead of polling. |
Technical notes
This capability accepts one finite positive amount plus from and to unit labels among min_km, min_mi, km_h, and mph, bridges every conversion through kilometers per hour so pace and speed scales stay consistent, and returns the target value together with the same figure expressed in all four units.
What you send and what you get back from the API and browser form
Both unit fields accept short keys and everyday words in any common casing, including min_km or min/km or minutes per kilometer or mpk, min_mi or min/mile or minutes per mile or mpm, km_h or km/h or kph or kilometers per hour, and mph or mi/h or miles per hour. Missing fields, non-numeric amount strings, NaN, Infinity, zero, negative amounts, and unrecognized unit labels fail with invalid_input and are not charged. On success the response echoes the cleaned amount, normalized from and to keys, the primary result in the target unit, the same figure as min_per_km, min_per_mi, km_per_h, and mi_per_h with twelve significant digits of stable precision, the exact mile_km constant used, the formula string, and method km_h_bridge. Pricing for successful API calls is the published base of $0.002 per item; validation failures do not consume prepaid balance.
Where dedicated running pace conversion shows up in real work
Data pipelines that ingest mixed watch exports with min_km, min_mi, and mph tags can call this capability once per sample instead of reimplementing the factors in every service. Because this capability is a pure parse engine, API pricing is the published base of $0.002 per successful item and failed validation does not consume balance.
Technical questions
Which units does this running pace converter support?
Minutes per kilometer (min_km), minutes per mile (min_mi), kilometers per hour (km_h), and miles per hour (mph). Common aliases such as min/km, min/mile, kph, and mi/h are accepted; the response normalizes to short keys.