Running pace calculator

A running pace calculator converts between distance, finish time, pace, and speed. Runners usually think in pace because “5:00 per kilometer” or “8:00 per mile” is easier to execute during a workout than a speed value.

Use it to set even-split targets, compare min/km with min/mile, find treadmill-style speed, or build a split table before a race. For physiological race prediction, pair this with the race predictor or VDOT calculator.

Example: 25:00 over 5K is 1,500 seconds divided by 5 km, which gives 300 seconds per kilometer, or 5:00/km. Because 5K is about 3.10686 miles, the same run is about 8:03/mile.

The calculator uses the exact relationship 1 mile = 1.609344 km, matching NIST length standards. To convert min/km to min/mile, multiply seconds per kilometer by 1.609344. To convert min/mile to min/km, divide seconds per mile by 1.609344.

The tool uses official race distances such as 21.0975 km for the half marathon and 42.195 km for the marathon. Longer-distance projection rows should be read as arithmetic projections only because endurance, fueling, fatigue resistance, and race conditions matter.

Speed is useful for treadmill settings and cycling-style comparisons. Pace remains the cleaner race-planning metric for most runners because split targets are easier to follow on the road or track.

Start with an even-split pace, then decide whether the course and your experience support a slight negative split or a conservative start. Pacing research supports the idea that strategy affects performance, but no one split pattern is universally best for every athlete and course.

For more detailed pacing plans, use the race strategy calculator and the split calculator.

Easy pace should feel controlled and conversational. Tempo or threshold pace is harder and usually held for shorter blocks. Race pace depends on the event: 5K pace is not marathon pace, even if both can be calculated with the same arithmetic.

Training targets should come from recent races, time trials, or a coach-supported plan. Use the training zones calculator when you need intensity guidance beyond simple pace conversion.

• Treating a long-distance arithmetic projection as a guaranteed race prediction.
• Ignoring heat, wind, hills, surface, and crowding when choosing a goal pace.
• Starting faster than goal pace to “bank time,” then losing more time late.
• Using treadmill or GPS pace without considering device calibration or signal error.
• Changing training paces aggressively after one unusually good workout.

All core outputs use exact arithmetic: pace = time / distance, time = pace × distance, distance = time / pace, and speed = distance / time. Race distances are stored in kilometers using official standard values where applicable.

The optional condition context is deliberately conservative and labeled as an estimated adjustment. Weather and altitude can affect performance, but individual heat acclimation, terrain, hydration, fitness, and race execution make exact correction unrealistic. For terrain-specific planning, use the grade adjusted pace calculator.

Sources are used for distance conversion standards and conservative context around pacing strategy, endurance determinants, heat, and altitude. Core pace calculations are direct arithmetic.

Key sources include NIST length standards, Abbiss and Laursen, and Joyner and Coyle.