Heat Running Pace Calculator

How the heat running pace calculator adjusts pace

The heat running pace calculator converts air temperature and dew point to Fahrenheit, adds the two readings and uses that total to select a percentage band for your usual pace. The bands come from coach Mark Hadley’s temperature-and-dew-point guidance, with this tool applying its continuous-run version. You can then see the extra time added per mile or kilometer at both ends of the band. The source also discusses repeat workouts separately, while this interface keeps the calculation focused on continuous running.

Adjusted pace = baseline pace × (1 + adjustment percentage ÷ 100)

The combined number is an index for this coaching table. It isn’t the air temperature, a heat-index reading or a wet-bulb globe temperature measurement. Adding two Fahrenheit readings doesn’t create another forecast temperature.

For example, a sum of 145 selects a 3% to 4.5% increase in time per distance. An eight-minute mile therefore becomes slower, with more seconds added to each mile. The calculator shows both ends of the band so you can see the range instead of treating one second as a personalized prediction.

Enter temperature and humidity consistently

You’ll need air temperature and humidity information for the same forecast time and place, because pairing a morning temperature with an afternoon humidity reading can create conditions you won’t actually encounter together. You can enter relative humidity as a percentage or select dew point and enter a temperature instead. For instance, a 65°F dew point belongs in the dew-point field, even if 65 also looks like a plausible humidity percentage. Check the field label and its unit together before using the weather reading in your calculation.

When you enter relative humidity, the calculator estimates dew point with the Magnus approximation documented in WeatherFlow’s derived metric formulas. It works in Celsius for that step, then converts the temperatures into Fahrenheit before selecting the band.

Celsius inputs are therefore supported, but adding the two Celsius numbers yourself won’t reproduce the Fahrenheit index. Let the unit selector handle the conversion.

The tool requires humidity between 1% and 100% and a dew point no higher than air temperature. Its accepted air-temperature range is an input boundary, not a safe exercise range. If an input is rejected, check the units and forecast reading before changing it simply to obtain a result.

Worked heat and humidity example

If your baseline is 8:00 per mile and the forecast gives 80°F air with a 65°F dew point, adding the two readings gives an index of 145. That selects a 3% to 4.5% increase in the original 480 seconds per mile, with the two ends worked out below.

The five-mile total uses the unrounded pace. Multiplying the displayed 8:14 by five gives a different second count because that display has already dropped the decimal part.

Your optional distance multiplies the adjusted pace into an elapsed time, so you can see what the range represents over the run you’re considering. It uses the same selected band throughout that distance.

You can also start with kilometer pace and keep that unit for the calculation. If your baseline is written in another unit, the Pace Converter lets you change it first, making it easier to compare the weather adjustment with the pace shown on your watch.

Read the range and its limits

Your output shows a coaching band whose endpoints come from the table, rather than personal probabilities fitted to your own response. You can inspect both endpoints and the added seconds alongside the original baseline.

The comparison chart applies the same baseline to each band so you can see how the calculation changes as its index rises. Every row is a model comparison, with your actual forecast inputs identified in the current result.

The method stops providing a numerical band above an index of 180, and the calculator withholds the pace at that point. At the lower end, a zero adjustment simply leaves your baseline unchanged; conditions still need their own safety assessment.

Sun exposure, wind, health, acclimatization, clothing, hydration and the environment along your route all sit outside the tool’s input fields. Keep those factors in mind when deciding what to do with the result, particularly if your route differs from the place where the weather reading was taken.

Keeping the baseline and weather readings with the output gives you a more useful record than saving an adjusted pace alone. The printable summary includes those inputs, letting you check how the estimate was produced when you return to it later.

Use the result with heat-safety guidance

Your health takes priority over the pace calculation, and the CDC’s guidance for athletes in heat advises stopping activity and moving somewhere cool if you feel faint or weak. It also recommends scheduling activity for cooler parts of the day where possible. You can keep the calculator result as a record of the coaching adjustment while considering the actual conditions and whether the session remains appropriate. Record the forecast time as well, so a later change in the weather is visible when you review the plan.

For a general current-performance reference, the Training Pace Calculator uses a race result. The heat method starts after you’ve chosen a suitable baseline; it doesn’t decide that baseline for you.

And if your question is only how long a stated distance takes at a stated pace, use the Mile Pace Calculator. That calculation doesn’t need a weather adjustment. Keeping each tool’s job clear helps you use its output without reading a broader promise into a number on the screen.