How Weather Affects Your Marathon Pace (And What to Do About It)

You've spent months training. You have a goal pace dialed in. Then race morning arrives and it's 72 degrees instead of the 50 you trained in all fall. How much should you slow down?

Most runners guess. And most runners guess wrong.

They either ignore the conditions entirely and blow up at mile 18, or they panic and leave 10 minutes on the table by going out too conservatively. The truth is that weather affects your marathon pace in predictable, well-studied ways. Once you understand the science, you can make race-day adjustments that are smart, not scared.

The Big Three: Heat, Wind, and Humidity

Three weather factors determine how much your marathon pace needs to change on race day. In order of impact:

1. Heat is the biggest pace killer. Every degree above the ideal range forces your body to divert blood flow to cooling instead of running. This is well-documented and unavoidable.

2. Wind is the hidden tax. Headwinds cost you far more energy than tailwinds give back, and most courses don't run in a straight line.

3. Humidity is the multiplier. High humidity prevents your sweat from evaporating, which is your body's primary cooling mechanism. Moderate temperatures can feel brutal when the air is already saturated with moisture.

Let's break each one down.

Heat: The Biggest Pace Killer

The science here is clear. A landmark 2007 study by Ely et al. in Medicine & Science in Sports & Exercise analyzed decades of marathon data across seven major races and found that performance degrades progressively as temperature rises above about 50 degrees. The slower the runner, the bigger the hit.

For recreational marathoners, the penalty is roughly 0.3% per degree above 50 degrees when you account for heat, humidity, and sun exposure together. That doesn't sound like much until you do the math over 26.2 miles.

Here's what that looks like in practice:

A follow-up study by El Helou et al. (2012) confirmed these findings across nearly 1.8 million marathon finishes. The optimal temperature sits around 48 degrees, and the penalty curve is asymmetric: being a little too cold barely matters, but being a little too warm matters a lot.

Sports scientists use something called WBGT (Wet Bulb Globe Temperature) to capture the full picture. Unlike a simple thermometer reading, WBGT combines air temperature, humidity, wind, and solar radiation into a single number. It's what race medical teams use to decide whether conditions are safe, and it's what racecast.io uses under the hood to calculate your pace adjustments.

Why does this matter? Because 70 degrees and sunny at 9 AM with no wind is a very different race than 70 degrees and overcast with a breeze. WBGT captures that difference. A plain temperature reading doesn't.

Wind: The Hidden Tax

Wind is the adjustment most runners overlook. And it hides a nasty trick: headwinds cost you far more than tailwinds give back.

This is because air resistance scales with the square of your speed relative to the air. Even a modest 5 mph headwind adds roughly 10-15 seconds per mile. A 5 mph tailwind? Only saves about 3-5 seconds. At higher wind speeds, the penalty grows exponentially — a 15 mph headwind can cost 30-60 seconds per mile depending on your pace. You never break even.

This asymmetry means that on an out-and-back course, you lose time even if you have a tailwind for exactly half the race. The headwind half hurts more than the tailwind half helps. Research by Beaumont and Polidori (2025) quantified this in detail: an ~18 mph headwind increases energy expenditure by 37%, while the same tailwind only reduces it by 9%.

On a point-to-point course, wind direction becomes even more critical. Boston runs west to east, so a prevailing west wind is a tailwind and an east wind is a headwind. In 2018, runners had a strong tailwind and course records fell. Many runners have also experienced the opposite. Same course, completely different race.

One more thing: if you're running with a tailwind at roughly your pace, you lose the cooling benefit of moving through the air. A 7 mph tailwind for a 7 mph runner means zero airflow across your skin. In warm weather, that makes heat buildup worse even though the wind is technically "helping" your pace.

Dew Point and Humidity: The Sweat Problem

Your body's primary cooling system is sweat evaporation. When humidity is high, sweat can't evaporate efficiently. It drips off you instead of cooling you. Your core temperature rises, and your body responds by slowing you down whether you like it or not.

The key metric here isn't relative humidity. It's dew point.

Relative humidity is misleading because it changes with temperature. A 60-degree morning with 80% humidity and a 75-degree afternoon with 40% humidity can feel equally oppressive because they have similar dew points. The dew point tells you how much moisture is actually in the air, regardless of temperature.

This is where WBGT earns its keep. It rolls humidity into the same number as temperature and sun exposure, giving you one metric that captures the full thermal stress on your body. A 65-degree day with low humidity is a different animal than a 65-degree day with a dew point of 62. WBGT tells you which one will actually slow you down.

The practical impact: when dew point climbs above 60 degrees, expect to add pace adjustment on top of what the temperature alone would suggest. Your body is working harder to cool itself, and that energy isn't going to your legs.

How to Adjust Your Race Plan

Knowing the science is one thing. Applying it on race morning is another. Here's the playbook:

Check the hourly forecast 48 hours out. Not just the high temperature for the day. Your race starts at 7 AM, not 3 PM. The conditions at mile 1 will be different from the conditions at mile 20. An hourly breakdown is far more useful than a daily average.

Run by effort in the first half, not pace. If conditions are warm, your target pace should feel easier than expected through mile 13. If it feels "right" at mile 5 in the heat, you're going too fast. The goal is to bank energy, not miles.

Use the temperature table above as a starting point. If race morning is 68 degrees with moderate humidity, plan for 10-20 seconds per mile slower than your trained goal. Round up, not down. Nobody regrets being conservative at mile 8. Plenty of runners regret being aggressive.

Don't try to "make up" time lost to weather. If you go through the half at 3 minutes behind your original goal, that's not a deficit. That's smart pacing for the conditions. Trying to accelerate into the back half of a warm marathon is how blow-ups happen.

Adjust fueling, not just pace. Heat increases fluid loss and can slow gastric absorption. Take water at every aid station in warm conditions, even if you don't feel thirsty yet. Your sweat rate in 72-degree racing is much higher than in your 50-degree training runs.

Let a tool do the math. Racecast.io's race pages calculate weather-adjusted pace automatically using the same WBGT model described above, with hourly weather data specific to your race. It accounts for temperature, humidity, wind, solar radiation, and precipitation so you don't have to do mental math at 5 AM.

The Bottom Line

Weather doesn't ruin your race. Ignoring weather ruins your race.

A 3:30 runner who adjusts to 3:40 in warm conditions and nails even splits ran a smarter, better race than a 3:30 runner who went out on goal pace and crawled home in 3:55. The adjusted runner ran to their fitness. The other one ran into a wall.

The research is consistent: heat above 50 degrees, headwinds, and high humidity all cost real time. But they cost predictable time. Once you accept that and plan for it, weather becomes just another variable you manage, like fueling or pacing hills.

Check the forecast. Do the math. Run your race.

More Guides

• How to Run a Marathon in the Heat — a complete race day guide for hot conditions
• Boston Marathon Course Strategy — mile-by-mile breakdown including wind analysis
• Find your race — weather forecasts and pace adjustments for thousands of races