Why Water Alone Isn't Enough on Long, Hot Efforts
Sweat isn't pure water -- it carries dissolved sodium out with it, and the hotter and more humid the conditions, the more a runner sweats to manage the same core temperature, which means more sodium lost alongside the fluid. In Southeast Asia's heat and humidity, sweat rates during a long run or race can run well above what most runners would produce for the same effort in a temperate climate, and replacing only the fluid half of that loss with plain water leaves the sodium side of the ledger increasingly out of balance as the run goes on.
That imbalance doesn't announce itself the way dehydration does. A runner who feels thirsty and simply drinks more water to match is addressing fluid volume, not sodium concentration -- and on a long enough effort, that combination is exactly the setup for the more serious problem covered below, rather than a fix for it.
The Overhydration Risk: Hyponatremia
Exercise-associated hyponatremia is a drop in blood sodium concentration that can occur during or after prolonged exercise, and updated guidelines from the Wilderness Medical Society identify its main driver as overdrinking -- specifically, taking in more hypotonic fluid (plain water or standard sports drink) than the body is losing through sweat, urine, and other routes, which dilutes existing sodium levels rather than the more intuitive-sounding cause of simply losing too much sodium[1]. It's a genuinely serious condition in its more severe form, and the risk rises specifically with exercise duration beyond roughly two hours, hot conditions, and a tendency to drink more than thirst calls for.
This is worth stating plainly because it cuts against the instinct many runners have in the heat: more water is not automatically the safer choice on a long, hot effort. The Wilderness Medical Society guidance is explicit that inadequate sodium intake before or during an event isn't itself well-supported as a cause of hyponatremia -- the core issue is fluid volume outpacing what the body needs, not a sodium deficit on its own[1]. Drinking to thirst, rather than to a fixed volume target or out of heat-driven anxiety, is the more defensible default for most runners on most long runs.
When Electrolyte Replacement Actually Matters
For runs under roughly 60-90 minutes, plain water is generally sufficient regardless of conditions -- sweat sodium losses over that timeframe are rarely large enough to matter, and there's little practical benefit to electrolyte replacement on a short easy run. Past that duration, a carbohydrate-electrolyte beverage becomes more useful, and sodium specifically becomes a relevant variable once an effort passes about two hours, or any time sweat rate is unusually high due to heat, intensity, or simply being a naturally salty sweater (visible white residue on dried kit is a reasonably reliable sign of the latter)[2].
In practice, that means a 45-minute recovery jog and a four-hour long run in Southeast Asian heat call for genuinely different fueling plans, not the same bottle scaled up. The four-hour effort is squarely in the window where sodium replacement -- via electrolyte tablets, capsules, or a sports drink taken alongside plain water rather than instead of it -- has a real physiological rationale behind it; the 45-minute jog mostly doesn't.
How This Connects to (and Differs From) Race-Day Fueling Timing
This site's race-day nutrition and fueling timing guide covers when and how much carbohydrate to take in during a long run or race -- a separate question from the one this article covers, even though the two plans often execute through the same bottles and gels on race day. Carbohydrate timing is about sustaining energy availability and blood glucose; electrolyte and sodium planning is about fluid and mineral balance. They interact (some electrolyte products also carry carbohydrate, and dehydration can worsen how a stomach tolerates carb intake) but solving one doesn't automatically solve the other.
The practical takeaway is to build both plans, not just one and assume it covers the other -- know your carbohydrate-per-hour target from the fueling article, and separately know your approximate sweat rate and sodium needs from this one, then test the combined plan in training rather than improvising it for the first time on race morning. Long, hot Southeast Asian courses are exactly the conditions where getting either half wrong shows up fastest.