You ran 8:30 pace last Tuesday and it felt comfortable. Today it’s 85°F and humid, and the same route at the same effort produced 9:15 splits. You didn’t get slower overnight. The weather got harder.

This is one of the most common sources of frustration in running: chasing a pace that was set on a cool morning when today’s conditions make that pace physiologically impossible at the same effort level. And most training apps don’t help — they give you the same target regardless of whether it’s 55°F and dry or 90°F and swampy.

The performance cost of heat and humidity isn’t subtle. It isn’t psychological. It’s measurable, predictable, and — once you understand the numbers — easy to account for.

Why Heat Slows You Down

When you run, your muscles generate heat. A lot of it. Your body’s cooling system kicks in: blood gets redirected to your skin, you start sweating, and evaporation pulls heat away from your body. This works well in mild conditions.

In hot and humid conditions, the cooling system competes with the running itself. Your cardiovascular system has to do two jobs simultaneously: deliver oxygen to working muscles and pump blood to the skin for cooling. There’s only so much cardiac output to go around. When more goes to cooling, less goes to performance. The result is a slower pace at the same heart rate — or a higher heart rate at the same pace.

Ely and colleagues analyzed 36 years of marathon results and found a clear, linear relationship between weather conditions and finish times. Performance declined predictably as temperatures rose above roughly 50-55°F, with the slowest times occurring in the hottest conditions. This held true across ability levels — elites and recreational runners both slowed down.

The critical insight: this isn’t a failure of fitness or mental toughness. It’s thermodynamics. Your body can only dissipate so much heat, and when the environment makes dissipation harder, something has to give. That something is pace.

Dew Point: The Number That Actually Matters

Temperature alone doesn’t capture how hard the heat is hitting you. A dry 90°F day feels very different from a humid 80°F day — and the humid day is often worse for running, because humidity impairs your body’s primary cooling mechanism: sweat evaporation.

Dew point combines temperature and humidity into a single number that represents how much moisture is in the air. The higher the dew point, the harder it is for sweat to evaporate, and the harder your body has to work to cool itself.

Pacewright uses dew point as the primary metric for heat adjustment:

Dew PointPace AdjustmentWhat It Feels Like
Below 55°FNoneComfortable. Optimal running conditions.
55–60°F+1%Pleasant but starting to notice the air.
60–65°F+2.5%Warm. You’re sweating more than usual at the same effort.
65–70°F+4.5%Hot and sticky. Easy pace feels noticeably harder.
70–75°F+6.5%Oppressive. Running becomes a heat management exercise.
Above 75°F+9%Dangerous. Consider moving indoors or to early morning.

What Those Percentages Mean in Practice

A 1% adjustment doesn’t sound like much. Here’s what it looks like on real paces.

Say your easy pace is 9:30 per mile on a cool day:

  • Dew point 58°F (+1%): Target shifts to about 9:36. Barely noticeable.
  • Dew point 63°F (+2.5%): Target shifts to 9:44. You’d feel this if you tried to hold 9:30 — your heart rate would be higher than usual.
  • Dew point 68°F (+4.5%): Target shifts to 9:56. Now we’re talking nearly 30 seconds slower per mile. Trying to run your normal pace would feel like a tempo effort.
  • Dew point 73°F (+6.5%): Target shifts to 10:07. Holding 9:30 would spike your heart rate into zone 4 territory on what’s supposed to be an easy day.
  • Dew point 78°F (+9%): Target shifts to 10:21. Almost a minute slower per mile — and that’s the physiologically honest pace for the same effort level.

The runners who ignore these adjustments don’t get tougher. They accumulate more fatigue than their plan intended, push their ACWR higher without realizing it, and wonder why they feel burned out or end up injured mid-summer.

When Dew Point Isn’t Available

Dew point is the most accurate single metric for heat stress, but not every weather source reports it. When dew point data isn’t available, Pacewright falls back to a temperature-plus-humidity calculation:

  • Temperature component: 0.4% per degree Fahrenheit above 60°F
  • Humidity component: 0.2% per percentage point above 60% relative humidity

For example, a day at 80°F with 75% humidity:

  • Temperature: (80 - 60) × 0.4% = 8%
  • Humidity: (75 - 60) × 0.2% = 3%
  • Total adjustment: 11%

This fallback is less precise than dew point — it can overestimate or underestimate depending on the specific conditions — but it captures the right direction and magnitude. When dew point is available, it always takes priority.

Altitude: The Invisible Adjustment

Heat is obvious. You feel it immediately. Altitude is sneakier.

At sea level, the air contains roughly 21% oxygen — and that’s plenty for running. As elevation increases, the air pressure drops, and each breath delivers fewer oxygen molecules to your lungs. Your body has the same engine, but the fuel delivery system is working with less.

The effect is negligible below 3,000 feet. Above that, it becomes meaningful:

ElevationAdjustmentExample City
Below 3,000 ftNoneMost coastal and lowland cities
4,000 ft+1.5%Salt Lake City suburbs
5,280 ft+3.4%Denver
6,000 ft+4.5%Santa Fe
8,000 ft+7.5%Mountain resort towns
10,000 ft+10.5%High mountain passes

The formula is straightforward: 1.5% per 1,000 feet above 3,000 feet. A runner visiting Denver from sea level should expect their 9:00 easy pace to feel more like 9:19 — and that’s the right pace for the same effort.

Chapman and colleagues documented the individual variability in altitude response: some runners adapt faster than others, and the initial performance hit can be substantial. The first 3-5 days at altitude are the worst, with the body losing plasma volume before compensatory red blood cell production kicks in.

The Altitude Arrival Paradox

If you’re traveling to altitude for a race or a training trip, timing matters. The worst window to arrive is 2-5 days before the event. You’ve been at altitude long enough for the initial plasma volume drop but not long enough for acclimatization to help.

The two safe options:

  • Arrive 2+ weeks early and give your body time to acclimatize (10-14 days minimum for meaningful adaptation)
  • Arrive the day before and race on residual sea-level fitness before the decline kicks in

Acclimatization: Your Body Adapts (But It Takes Time)

The adjustments above apply to runners in their current state. But your body isn’t static — given time, it adapts to environmental stress.

Heat acclimatization takes 10-14 days of consistent heat exposure (at least 60 minutes per session in actual outdoor heat — treadmill in air conditioning doesn’t count). During that period, your body makes real physiological changes:

  • Plasma volume increases. More blood available for both cooling and muscle delivery.
  • Sweat response improves. You start sweating earlier and at a higher rate, which means more efficient cooling.
  • Resting heart rate drops. Your cardiovascular system becomes more efficient at the dual task.
  • Core temperature decreases. Your baseline body temperature runs slightly lower, giving you more thermal headroom.

Périard and colleagues documented these adaptations extensively. After full heat acclimatization, you can recover roughly half of the performance you lost to the heat. Not all of it — a 75°F dew point is never going to feel like 50°F — but the body genuinely gets better at handling the stress.

Altitude acclimatization takes 1-3 weeks, driven primarily by increased red blood cell production. More red blood cells means more oxygen-carrying capacity per unit of blood. This is the mechanism behind altitude training camps — train high, race low, keep the extra red blood cells.

During the first 1-2 weeks of a seasonal weather change, expect your runs to feel harder than the numbers suggest. That’s normal. It’s your body in the process of adapting, and it will adapt — you just have to give it time instead of forcing your old paces.

How the Adjustments Stack

Heat and altitude adjustments are additive. If you’re running in Denver on a humid summer day, you get hit with both.

Take a runner with a 9:00 easy pace at sea level in cool conditions:

  • Cool day in Denver: Altitude adds 3.4%. Target becomes 9:18.
  • Hot day at sea level (dew point 70°F): Heat adds 4.5%. Target becomes 9:24.
  • Hot day in Denver (dew point 70°F): Both apply. Total adjustment: 7.9%. Target becomes 9:43.

The combined effect explains why summer running at altitude can feel so brutal. You’re fighting two physiological constraints at once, and the math adds up fast. A pace that felt easy in March at sea level requires substantially more effort in July at 5,000 feet.

What You See in the App

When weather conditions affect your target paces, Pacewright tells you exactly what’s happening:

Minor adjustments (under 3%): “Slightly warm conditions today. Your target paces are adjusted by 2.5% — about 14 seconds per mile on your easy runs.”

Moderate adjustments (3-6%): “Hot and humid today (dew point 68°F). Your paces are adjusted by 4.5%. An easy run that would target 9:30/mi in cool conditions targets 9:56/mi today.”

Significant adjustments (6% or more): “Dangerous heat today (dew point 76°F). Your paces are adjusted by 9%. Consider running early morning, late evening, or indoors. If running outside, prioritize hydration and be prepared to cut the workout short.”

The explanation includes the specific dew point or temperature reading, the percentage adjustment, and the adjusted pace in minutes and seconds. No vague “it’s hot, slow down.” Actual numbers.

If you ran faster than the adjusted target, that’s fine — your RPE and heart rate data tell the real story. But if you forced a pace that was too fast for the conditions and your heart rate spiked, the app captures that too and factors it into your training load. Running 9:00 pace on a 9:43 day doesn’t mean you had a great run. It means you ran at a harder effort than intended, and tomorrow’s plan will reflect that.

The Honest Truth About Weather

You can’t outrun the weather. You can’t “push through” a dew point of 75°F and come out ahead. The physics of heat dissipation don’t care about your mental toughness. And a training plan that ignores this — that gives you the same 8:30 target in January and July — isn’t being ambitious. It’s being wrong.

The pace adjustment isn’t making you slower. It’s telling you the truth about what the same effort costs in different conditions. An adjusted 10:00 pace at a 70°F dew point and a “normal” 9:20 pace at a 50°F dew point are the same workout. Same effort, same heart rate, same training stimulus, same adaptation. The only difference is the number on your watch.

Pacewright adjusts your targets because the goal of training isn’t to hit a specific pace. It’s to apply the right stimulus to your body. And the right stimulus depends on conditions that change every day.