How much sodium per hour for endurance?

Sodium matters mainly because it is part of fluid balance during exercise. When you sweat for a long time, especially in the heat, you lose both water and sodium. If fluid intake rises while sodium stays very low, some strategies become overly diluted and less coherent.

This page is not a complete lesson on electrolytes. The practical point is simpler: as sweat losses and drink volume rise, sodium becomes a more concrete planning variable. Its main role is to support a drink setup you can execute, not to promise performance or cramp prevention on its own.[1][6]

Think of sodium as one practical lever inside a wider plan, connected to hydration, duration and consistent intake.

Around 300 mg/h is often enough in cooler conditions, during a more moderate effort, with lower sweat losses or a contained fluid target. It is not automatically a low dose; in the right context, it is already a reasonable target.[2][4]

Around 500 mg/h is a common working range once duration increases or conditions become somewhat warmer. For many athletes, it is a solid practical baseline before considering more.

Around 800 mg/h is more often discussed when sweat losses are high, heat is more pronounced or fluid intake rises substantially. At this level, the relationship between mg/h and drink concentration needs particular attention.[2][4]

At 1000 mg/h and above, the context is usually more specific: high heat, very high sweat losses, long duration, or an athlete who already knows they both sweat and drink heavily. Feasibility now matters as much as the number itself.[2][4]

An hourly target only makes sense alongside drink volume. Delivering 1000 mg/h in 500 mL/h creates a much more concentrated drink than delivering 1000 mg/h in 1 L/h, so mg/h must always be checked against mg/L.[2]

Do not confuse salt with sodium when reading a label or preparing a DIY recipe. The European labelling conversion is salt = sodium × 2.5, so 1 g of salt provides about 400 mg of sodium. This is a chemical conversion, not an individual target.[1][6]

Temperature is often the first variable. As conditions get hotter, fluid intake tends to rise and sodium becomes more relevant. Next comes sweat rate: someone who sweats lightly in cool weather should not use the same target as someone whose clothes are saturated during a hot effort.

Duration matters too. A conservative target may be enough for a short or moderate effort. During a long ride, a hot marathon, a long trail race or several hours on the bike, underdosing or excessive dilution has more time to affect the plan.

The type of effort and a history of cramping can refine the decision, but they are not shortcuts. Cramps are multifactorial. Occasional cramps do not automatically justify a maximum sodium target; treat them as one contextual clue rather than decisive proof.

A simple profile-based approach is to use the lower range for lighter sweating, the middle range for moderate sweating, and a higher range for heavy sweating or severe heat—provided the drink remains palatable and logically formulated.

A lower target often makes sense in cool conditions, for a relatively short effort, with lighter sweating and a moderate drink volume. In that setting, adding a large sodium load may offer little practical value and can make the drink less pleasant.

It is also a sensible choice for athletes who first need to stabilize the rest of the plan. If hydration, carbohydrate intake and timing are not yet reliable, sodium does not need to be pushed immediately.

Restraint can improve execution. A moderate target you can hold consistently is better than an aggressive concentration that leads you to drink less or causes poor tolerance.

Increasing sodium becomes more logical when heat rises clearly, duration lengthens, sweat losses are obvious and fluid intake increases with them. These are the situations in which 500 to 800 mg/h, and sometimes more, become easier to justify.[1][6]

Long summer sessions, hot races, exposed long trail events and long-distance cycling are common examples. Even then, any increase should be gradual and tested in training.

The goal is not to add sodium by default. It is to prevent higher fluid intake or heavier sweating from making the plan too dilute or internally inconsistent. Sodium should follow the context, not replace it.

Pushing sodium too high does not automatically improve the strategy. If the drink becomes too salty, concentrated or unappealing, you may simply drink less or become inconsistent. The plan then loses in execution what it appeared to gain on paper.

Extra sodium also cannot repair a poorly designed hydration plan. If drink volume is unrealistic, heat is poorly managed or carbohydrate concentration is already excessive, adding sodium does not solve the underlying problem.

The right sodium dose is useful rather than maximal. It should support the drink, not make the plan harder to sustain.

Cool session with moderate sweating: a conservative range around 300 mg/h may be enough, especially when fluid intake remains moderate.[2][4]

Summer race with a clear rise in temperature: 500 mg/h often becomes a more logical working range, with drink concentration checked alongside it.

Hot trail race or long exposed effort: 800 mg/h may be defensible when sweat losses are high and the drink remains practical to consume.[2][4]

Long-distance cycling in the heat: some athletes may consider 800 to 1000 mg/h or more, but only when actual drink volume supports it and the plan has already been tested in comparable conditions.

These examples help frame a decision; they do not prescribe a universal protocol. Always test the final target against your real conditions.

The first mistake is ignoring sodium during long or hot efforts even as fluid intake becomes ambitious. The second is treating sodium only as a cramp solution, when its main relevance is often the coherence of the hydration plan.

A third mistake is increasing sodium without checking final drink concentration. An hourly target may sound reasonable but become impractical if it requires a drink that is too concentrated for the volume you actually consume.

The fourth mistake is isolating sodium from everything else. Sodium, hydration, carbohydrates, logistics and digestion must remain compatible, or the plan becomes more complicated without becoming better.[1][6]

The DYF pathway should stay clear. The endurance nutrition guide explains the scientific foundation. The ultimate endurance nutrition guide shows how to build a complete fueling strategy. The endurance carbohydrates page and carbohydrates-per-hour guide frame carbohydrate intake first. The sodium and electrolytes guide then explains when sodium becomes an important lever. This page helps you choose an hourly sodium target that fits the context.

The DYF calculator then turns that target into a practical plan: mg/h, drink concentration, bottles or capsules, and alignment with the rest of your intake. Sodium should become a clear plan variable, not a race-day patch.

If you are choosing between two targets, keep the simpler and more workable one, then test it properly before moving higher.