Ask Tempo

Why does heart rate drift upward on runs?

Tempo · 4 min read

Short answer: heart rate climbing on a run that feels just as hard as it did at the start is being pulled up by your blood, not your effort. Sweat loss shrinks the volume of blood returning to the heart, so each beat carries less of it, and heart rate rises to make up the difference. Rising body temperature adds a second pull, sending blood to the skin to cool you down instead of to working muscle. Neither of those needs a drop in fitness to happen. Both are the system doing its job under heat and duration.

The mechanism behind the climb

Stroke volume is the amount of blood the heart pushes out with every beat. Early in a run it's near its peak, and heart rate can sit low for the pace you're holding. As sweat loss accumulates, the fluid available to fill the heart between beats drops, so stroke volume falls. The heart has only one lever left to keep the same amount of blood moving to working muscle: beat more often. That's the core of cardiac drift. It isn't the muscles tiring in the way a hard finishing kick would; it's the delivery system adjusting to a shrinking supply.

Heat management runs on the same blood supply and competes for it directly. As core temperature rises, a growing share of blood gets routed to the skin to shed heat, leaving less for the legs at the same pace. The heart answers by beating faster still, even though the pace on the watch hasn't moved. Combine those effects and you get the familiar shape: heart rate drifting upward across a steady run while pace stays flat.

Why it shows up even when effort feels unchanged

Heat and humidity speed up both halves of the mechanism: sweat loss accelerates, and skin blood flow demand goes up, so the same pace on a warm afternoon drifts harder than it would on a cool morning. Duration matters on its own too. Drift tends to build gradually across a sustained effort rather than showing up in the opening stretch, which is why a short run rarely reveals much of it.

Runners holding an identical pace side by side can show different amounts of drift, and that difference usually traces back to things that have nothing to do with how hard either of them is trying. Hydration going into the run, a trained heart's stroke volume ceiling, and how recently someone's legs absorbed hard training all shape how steep the climb looks on any given day.

When drift is ordinary and when it's a flag

A gradual rise of a handful of beats across a long or warm run is the expected response, not evidence that fitness is slipping. What's worth a second look is drift that runs far steeper than the conditions call for, or shows up on a cool day at an effort that used to sit flat for the whole distance. That combination is a reasonable prompt to check sleep, fueling, and fluid intake going into the next similar session.

Pace is the sharper cross-check than heart rate alone. Steady pace with climbing heart rate is the classic drift pattern described above. Pace fading alongside the climb points at something heavier than drift: accumulated fatigue, under-fueling, or an effort that was simply too hot for the plan.

What to do with the number

Treating every uphill tick in heart rate as a reason to ease off misreads what drift measures. A more useful habit is holding a given run up against your own history in similar conditions: a warm long run drifting the way your warm long runs always have is not a red flag. One drifting far outside that pattern is worth a closer look at the days before it, before deciding anything about the next one. The call on what that means for training sits with the runner holding the history, not with a fixed heart rate ceiling.