Pace Converter

Pace is time per unit of distance - minutes per kilometre or minutes per mile. It is the single number that links your effort to your result, and almost every decision a runner makes about training and racing revolves around it.

When you know your pace, you can project finish times, calibrate effort across different distances, and judge whether a session is hard, easy, or tempo. A 5:30/km easy run today and a 4:00/km race effort next weekend might feel completely different, but both communicate exactly where you are on the effort spectrum.

The problem is that running uses two parallel systems. Athletics, road racing, and most training tools outside the United States quote pace in minutes per kilometre. American races, many GPS watches sold in the US, and a substantial portion of English-language training plans use minutes per mile. When you cross between those systems - or when a training plan uses one format while your watch displays another - the numbers stop making intuitive sense instantly.

Speed in kilometres per hour adds a third format. It appears on treadmills, in fitness apps, and in physiological testing contexts. A speed of 10 km/h is exactly a 6:00/km pace, but holding that equivalence in your head under fatigue is surprisingly difficult.

Pace also underpins every race prediction. Finish time is simply pace multiplied by distance. If you know your target finish time and the distance, your required pace follows directly. If you know your current pace but want to know the finish time, the arithmetic is equally straightforward - but nobody wants to do it in their head at kilometre 35 of a marathon.

There is no single answer, because pace means nothing without context. A 6:00/km effort is a comfortable jog for an experienced club runner and a strong tempo for someone six months into their first training programme. Distance, terrain, and current fitness all change what a given pace represents.

A useful starting framework: beginner runners typically complete 5K races between 6:30/km and 8:00/km; intermediate runners between 5:00/km and 6:30/km; and experienced or competitive runners between 3:30/km and 5:00/km. These are broad bands, and there is no shame in being outside them in either direction - fitness is a continuum, not a ladder with fixed rungs.

For training paces, most plans distinguish easy runs (conversational, roughly 60-75% of maximum heart rate), tempo runs (comfortably hard, around 80-85%), and intervals (near race effort or above). The exact pace attached to each zone varies by individual. That is why training plans use relative effort as the anchor, and why a pace converter only tells part of the story - the effort behind the number matters as much as the number itself.

The table below gives a concrete reference point: the finish times produced by a selection of paces across the four most common race distances. Use it to translate your current training pace into projected finish times, or to work backwards from a goal time to the pace you need to hold.

Minutes per kilometre is the global default for road running. If you are training in Europe, Australia, South Africa, or anywhere metric is the standard, your GPS watch almost certainly defaults to min/km, and most races will display kilometre splits on course signs. The metric system makes mental arithmetic easy: a 5:00/km pace over a 10K gives you 50 minutes - straightforward multiplication.

Minutes per mile is the default in the United States, and it persists in the UK alongside metric - partly because of the Boston Marathon and other historically mile-marked major races, and partly because many runners learned the sport via American training plans. If you follow a plan written in min/mile and race in a metric country, you will need to convert constantly to make sense of your split markers.

The two systems also create different intuitions about what a good pace looks like. A 7:00/mile sounds faster than a 4:21/km, even though they are exactly the same effort. Runners who switch countries or switch training systems often spend weeks recalibrating their sense of what numbers feel right.

Some GPS platforms let you display both simultaneously, but not all do. Apple Watch defaults to min/km or min/mile based on your device region. Garmin watches let you toggle between metric and imperial units from the settings menu. Strava follows your account preferences. If you travel to races internationally, it is worth checking your watch settings the night before - arriving at a race with your watch displaying the wrong unit is a minor but fixable headache that is easier to avoid.

A quick conversion reference: 1 mile is 1.609 km. To convert min/km to min/mile, multiply by 1.609. To convert min/mile to min/km, divide by 1.609. A 5:00/km pace is 8:03/mile. A 6:00/mile pace is 3:44/km. The converter above handles all of this instantly, so you never need to do the arithmetic by hand.

Enter any single value - a pace in min/km, a pace in min/mile, or a speed in km/h - and the tool recalculates all three formats simultaneously. There is no submit button to press; results update as you type.

The most common use case is race planning. If a training plan sets an interval session at 4:15/km but your watch is set to miles, type 4:15 into the min/km field and read your target pace in min/mile directly. Or work the other way: if you finished a parkrun in 26:30 and want to know your pace per kilometre, your pace per mile, and your average speed, enter 5:18/km (26:30 divided by 5) and all formats appear at once.

For marathon and half-marathon planning, use the finish-time table in the section above to identify the pace you need, then convert it to whichever format your watch displays. That way your target pace is in the same units as your live readout during the race, which removes one source of mental load at exactly the point in a race when mental load is highest.

The tool also helps when comparing performances across different formats. If a friend ran a 7:30/mile tempo session and you ran at 4:30/km, you can convert both to the same unit and see at a glance who was moving faster. (It was you, by about ten seconds per kilometre.)

One common misuse to avoid: do not use pace conversion to compare efforts at different distances without accounting for the fact that race pace scales with distance. A 4:00/km 5K pace is not the same physiological effort as a 4:00/km marathon pace - the marathon version would represent one of the fastest times in history. Pace is always contextual; this tool converts the number, not the effort behind it.