The Real Reason Heat Breaks Your Runs
What you're losing in the heat isn't just water
Two weeks ago, the heat shifted where I live, and last weekend it caught up with me on a long ride. I ran out of water about two-thirds of the way through, and the last stretch made that impact very clear. I cut the ride short by eleven miles because I hadn't managed the heat correctly, and my body made the decision for me.
This is the version of a bad hot weather workout that most runners never get a clear explanation for. They try to drink more water, they slow down, and they blame the heat or decide they're just not built for running in it, and they never isolate the variables that keep working against them.
Why Heat Makes Running Harder at the Same Effort
Heat does more than make running uncomfortable. It creates a specific physiological cascade that makes running measurably harder at the same effort level.
In normal conditions, your body generates heat as a byproduct of muscle activity and sweats to release it. The cooling demand is manageable and doesn't significantly compete with the cardiovascular work of running. In higher heat, the environment is already pushing your core temperature up before you've taken a step. The body responds by sweating more aggressively to compensate, and that's where the cascade starts.
Sweat comes from plasma, the fluid component of your blood. As sweat rate increases, plasma volume drops, making blood thicker. So your heart has to beat more frequently to move your blood and deliver the same amount of oxygen to working muscles.
This is cardiac drift - heart rate climbs over the course of a run even when pace and effort stay constant.
It happens to some degree in any long effort, but heat accelerates it, and it compounds on itself as your heart works harder. As your heart works harder, it generates more heat, which demands more cooling, which means more sweat, which reduces plasma volume further, which makes the heart work harder still. That's the real reason your usual run falls apart when the temperature spikes.
Drinking More Water Only Solves Half the Problem
Drinking more water when you're struggling in the heat addresses one part of the problem of adding back fluids. Sodium is the other part, and it's the one most runners don’t fully understand.
Electrolytes have had a marketing moment in running over the last few years, but the pitch has mostly been about preventing cramps. Cramps are one symptom of extreme dehydration, but they're not the reason sodium matters most in the heat. Sodium is the primary electrolyte in blood plasma, and it's what your body loses most through sweat. It's also what keeps water in your bloodstream. Without adequate sodium, the fluid you're drinking moves out of circulation rather than restoring plasma volume - and the cascade keeps running.
Sodium depletion and dehydration feel similar in the moment - fatigue, performance that falls apart faster than normal, and yes, eventually cramping. Runners confuse them because the symptom picture overlaps. They're different problems with different fixes, and drinking more water when sodium is the issue doesn't close the gap. In the most serious cases, it makes things worse by diluting what sodium you have left.
How to Know Which Problem You're Actually Having
The symptom overlap is real, but there are patterns worth paying attention to.
Dehydration tends to build gradually and respond to water. If you start a run adequately hydrated and drink consistently, dehydration is unlikely to be the issue on efforts under an hour. If you went in already behind - skipped fluids earlier in the day, running first thing without pre-hydrating - dehydration is worth considering first.
Sodium depletion looks different. The clearest signal is a runner who is drinking consistently, doesn't feel thirsty, and is still falling apart in the heat. Heart rate climbs faster than the effort explains, and performance continues deteriorating despite adequate water intake. The cascade is running at full speed because the sodium isn't there to keep those fluids in circulation.
If that's a recurring experience across multiple hot weather runs, the variable worth examining goes beyond how much you're drinking. It's about what you're drinking.
Standard Hydration Advice Is Built Around Averages, and You Might Not Be Average
The guidance around hydration in heat - how much to drink, how much sodium to replace - is built around average sweat rates and average sodium loss. For a lot of runners that's close enough. For some it falls significantly short.
Sweat rate varies considerably between individuals. Some runners produce high sweat volumes at moderate intensities. Some lose more sodium per unit of sweat than others. If you're on the higher end of either, the standard advice leaves you with a larger plasma volume deficit than it accounts for - which means the cascade runs harder and faster for you than it does for the runner next to you at the same pace and effort.
If you consistently struggle in the heat more than training partners at the same fitness level, this is worth examining. The gap isn't always conditioning. Sometimes it's that your physiology demands a more aggressive hydration and sodium strategy than the general guidance covers.
What to Replace and When
The right sodium strategy varies by individual, by conditions, and by effort duration - which is why I frame this as coaching guidance rather than a specific prescription.
For efforts under an hour in moderate heat, water is usually enough if you went in adequately hydrated. Past that point, and especially in high heat, sodium replacement starts to matter. Sports drinks, electrolyte tablets, or sodium-containing foods are the practical options. The amount varies based on your sweat rate, the conditions, and how long you're going - your needs may be higher than others'.
Timing also matters as much as volume. Waiting until you feel the cascade already underway puts you behind it. Starting sodium replacement earlier in the effort and maintaining it consistently is more effective than trying to catch up once performance is already deteriorating.
As a general starting point, most runners doing extended efforts in heat are looking at somewhere in the range of 16-24oz of fluid per hour and 500-1000mg of sodium per hour. Both numbers shift based on sweat rate, conditions, and effort intensity. If you're a heavier sweater or you know you run salty, you'll likely need to be toward the higher end of both. These are starting points to work from, not targets to hit exactly.
One flag worth raising: hyponatremia - critically low blood sodium - is the serious end of this spectrum. It happens when large volumes of plain water are consumed without electrolyte replacement, diluting whatever sodium remains. Symptoms look like dehydration, which is what makes it dangerous. If something feels seriously wrong in extended heat exposure, stop and get help.
The ride last weekend ended up eleven miles short. I ran out of water two-thirds of the way through, and my body shut the effort down before I did. The heat was the same heat it's going to be next weekend. What's changing is what I'm bringing with me.
How many bad summer runs have you written off as a fitness problem when sodium was the variable you were missing?