How Much Sodium Do You Need Per Hour During an Endurance Race?

If somebody handed you a blanket sodium rule like "take 1,000 mg an hour," they were guessing. That number might be perfect for a big, salty sweater dragging themselves through a hot Ironman. It might be ridiculous for a smaller runner on a cool marathon morning.

And that's the whole problem with sodium advice online. In a large dataset of 1,303 athletes, endurance athletes averaged 1.28 L/h of sweat loss and 51.7 mmol/h of sodium loss, about 1,190 mg per hour, but the spread was wide enough that the average is almost useless by itself (Barnes et al.). Two athletes can race the same course at the same pace and lose very different amounts of sodium.

Average is a trap.

So what number should you actually use? I think the cleanest answer is this: start with your sweat rate, make an educated guess about how salty your sweat is, adjust for heat and race length, then test the plan in training. Sodium matters. The one-size-fits-all number doesn't.

The internet loves one number. Your body doesn't.

Participation in an endurance event lasting about two hours can cost roughly 1.6 g of sodium, and hard sessions in the heat can push total losses much higher (GSSI). But that does not mean you need to replace every milligram while you're moving. Not even close.

You're not trying to finish with zero sodium deficit, same as you're not trying to finish with zero glycogen deficit. You're trying to stay inside a range where thirst, fluid balance, and late-race function do not go sideways. For some athletes that might mean a couple hundred milligrams an hour. For others it can mean four figures.

Copying your friend's sodium plan is a bit of a catch 23. His 1,200 mg/h might be solving a real problem. Or it might just be expensive pee for you.

What sodium actually does, and what it doesn't

Sodium helps you hold on to fluid, maintain plasma volume, and keep thirst working the way it's supposed to. That's useful, especially in long races and hot weather. The GSSI review on sodium and drinking is pretty direct about this: sodium intake helps stimulate thirst and supports fluid retention, which is part of why sports drink usually works better than plain water when you've been sweating for hours (GSSI).

But sodium is not race-day magic either.

In a randomized cycling trial in cool conditions, athletes taking 700 mg/h of sodium rode no faster than when they took a placebo (Cosgrove and Black). And in a 2023 hot-condition ultra study, replacing 100% of measured sweat sodium losses raised plasma sodium more than placebo, but it still did not meaningfully change fluid balance, heart rate, core temperature, or perceived strain (McCubbin and da Costa).

So the practical takeaway is simple. Sodium can help support a good hydration plan. It does not rescue a bad one. It will not fix overdrinking, bad pacing, or a stomach that hates the concentration you're pouring into it.

Your number starts with two variables

I think the cleanest formula is:

hourly sodium loss = sweat rate x sweat sodium concentration

That sounds annoyingly technical, but the first half is easy. You can estimate sweat rate at home with a pre- and post-workout weigh-in, which I walked through in the sweat rate post.

The second half is harder. Unless you have access to lab or field testing, sweat sodium concentration is mostly an educated estimate. So most people need to start with clues:

• heavy salt crust on clothes or hat
• sweat that stings your eyes
• workouts in heat where water alone stops feeling useful
• a history of fading late that improves when sodium intake goes up

Those clues are blunt tools, but they're better than pretending everyone loses the same amount.

Here are three simple examples:

Athlete profile	Sweat rate	Sweat sodium	Hourly sodium loss
Smaller runner, cool day	0.8 L/h	500 mg/L	400 mg/h
Middle-of-the-road endurance athlete	1.2 L/h	800 mg/L	960 mg/h
Big, salty sweater in the heat	1.5 L/h	1,000 mg/L	1,500 mg/h

Pretty different.

And heat changes the picture fast. Heat acclimation can lower sweat sodium concentration within just a few days of repeated exposure, so the number that made sense in your first ugly June long run may be too high by late summer (Buono et al.). That's one reason rigid sodium rules age badly.

Need a starting number built from your pace, body size, weather, and race length? Build your personalized carb, fluid, and sodium plan in about 60 seconds: Use the free EnduranceOS calculator.

A practical starting range for most endurance athletes

If you do not know your sweat sodium concentration, you still need a plan. So here's the honest version: the best starting number is a range, not a single target.

This next table is an inference from the published sweat-rate and sweat-sodium-loss data, not an official ACSM rule. I think that's the better way to use the evidence anyway. The Academy of Nutrition and Dietetics, Dietitians of Canada, and ACSM position stand leans the same direction by pushing individualized fluid and electrolyte strategies instead of one universal number.

Scenario	Starting sodium target
Cool weather, smaller athlete, race under 3 hours	300-500 mg/h
Most marathon, 70.3, and century-ride setups	500-800 mg/h
Hot race, heavy sweater, visibly salty sweater, or very long day	800-1,200+ mg/h

That middle band is where a lot of people land. But you still need to count what's already in your plan. Sports drink, gels, chews, broth, aid-station food, salt caps, all of it counts. I've seen plenty of athletes add salt tabs on top of a high-sodium drink mix and accidentally build a plan their gut hates.

And you usually do not need to replace 100% of losses during the race. A marathon, 70.3, or hot century ride often goes better when you're reasonably close, drinking sensibly, and keeping the concentration in your stomach manageable. Chasing exact replacement can turn into a chemistry project when what you really need is a plan you can follow with tired hands and a foggy head.

Salt pills won't save you from overdrinking

This is the part people get backwards. Exercise-associated hyponatremia is usually driven by drinking too much fluid relative to what you're losing, not by forgetting a salt tab.

A 2022 review called out excess hypotonic fluid intake as the main cause, with longer event duration and smaller body mass increasing the risk (Seal and Kavouras). Another study applying thirst-based hydration guidance to marathon trail runners and Ironman athletes saw hyponatremia become rare, even without some elaborate sodium-loading protocol (Del Coso et al.).

So if you're pounding water at every aid station because you're scared of dehydration, sodium tabs do not give you a free pass. You can absolutely overdrink and still finish low on blood sodium. That's how people end up confused, nauseous, puffy, and in the med tent.

Bad trade.

But the opposite mistake is common too. Athletes hear "drink to thirst" and treat it like "ignore fluids until everything feels terrible." That's not the message. The point is to let thirst and tested numbers keep you from doing something dumb in either direction. The hot weather nutrition post gets into this in more detail, because heat is where the math gets nasty.

Body size, sex, and race type change the answer

In one field study of recreational runners, men averaged 1.3 L/h sweat rates and women averaged 0.9 L/h, with lower hourly sodium losses in women on average too (Rai et al.). But I would be careful with the takeaway there. The individual spread is still huge, which means "men need X and women need Y" is lazy advice.

Body size usually tells you more. A lighter athlete often needs less fluid per hour and, in absolute terms, less sodium per hour too. A larger athlete putting out more heat usually moves the other direction. Race type matters for the same reason.

A cool marathon might go just fine around the middle of the range. A hot Ironman, an ultra, or a century ride where you're sweating for six hours straight can push you much higher, especially if you're already a salty sweater. And if you're building a marathon fueling plan or an Ironman carb plan, sodium needs to live inside that bigger system. It can't be its own little side quest.

How to test it without turning training into lab class

You do not need a sweat lab and a spreadsheet with seventeen tabs. Keep it simple.

1. Measure your sweat rate in conditions that look like race day.
2. Start with a sodium range that matches your body size, race length, and whether you're obviously a salty sweater.
3. Count the sodium already in your fuel instead of adding salt caps blindly.
4. Test the plan on long sessions, then write down how much you drank, how your stomach felt, and whether you finished thirsty, sloshy, crampy, or covered in salt.
5. Nudge the plan up or down next time.

That's it.

And practice the logistics too. Write the plan on your arm, tape it to your top tube, set watch alerts, whatever keeps you from doing math in hour five when your head is half-cooked. If your sodium plan only works when you're calm, cool, and standing in your kitchen, it doesn't work.

A better sodium plan is usually a simpler one

Most athletes do not need a heroic sodium protocol. They need a reasonable starting number, a realistic drink plan, and enough training reps to see what happens before race day.

So start with sweat rate. Respect the weather. Count the sodium already in your bottles and fuel. Then adjust based on what your body actually does, not what some random forum guy said worked for his cousin at Leadville.

The EnduranceOS planner builds a personalized carb, fluid, and sodium plan from your race, your body size, and your conditions. It takes about 60 seconds, and it's free.