How to Prevent Cramps While Racing: A Plan

A calf that locks at mile 20, a hamstring that tightens on a climb, or a quad that threatens to seize in the final kilometres is rarely a random event. If you want to know how to prevent cramps while racing, start with the truth: cramps are usually a race-execution problem with several possible contributors, not simply a magnesium problem or a sign that you need to swallow more salt.

The best defence is a protocol you have tested under realistic fatigue. Pace within your capacity. Arrive fuelled. Replace enough fluid and sodium for your conditions. Train the muscles and movement patterns your race will demand. Then make sensible adjustments when the race gets hot, long or unexpectedly hard.

Why cramps happen in races

Exercise-associated muscle cramp is not fully explained by one mechanism. For endurance athletes, the most useful model is neuromuscular fatigue. When a muscle is working close to its limit for long enough, especially in an unfamiliar range or at an unfamiliar intensity, the nervous system can lose some of its normal control of contraction. The result can be a painful, involuntary tightening.

That is why cramps often arrive late in a hard race, on hills, after repeated surges, or during the run leg of a triathlon. The athlete may be underfuelled or dehydrated, but the immediate trigger is frequently that the muscle has been asked to produce more than it is prepared to sustain.

Fluid and sodium still matter. Large sweat losses, high sodium losses and heat strain can increase physiological stress and make a fatigued athlete more vulnerable. But drinking excessive plain water can also create problems. A cramp is not proof that you are low in sodium, and taking a large dose after it starts is not a reliable fix.

This matters because it changes the plan. Do not rely on one last-minute supplement. Build capacity, fuel the work and manage your personal losses.

How to prevent cramps while racing: use a four-part protocol

1. Race at an intensity you have earned

The most effective cramp strategy may be restraint in the first half of the event. A pace that feels comfortable when fresh can be unsustainable once glycogen falls, body temperature rises and eccentric loading accumulates.

Set your pacing plan from training and recent racing, not your best-case target. In a marathon, that means resisting the urge to bank time early. In a triathlon, it means keeping the bike effort controlled enough that your running muscles remain functional. In a cycling event, it means avoiding repeated surges that turn a steady endurance demand into a series of anaerobic efforts.

Hills deserve particular attention. Uphill running increases calf and hamstring demand, while descents can heavily load the quadriceps. If cramps tend to occur in one location, examine the course profile and your technique before blaming hydration. Specific hill sessions, downhill conditioning and strength work can make a meaningful difference.

"Every cramp I had in a race was written into the first half of it. Not the salt, not the bottle I missed. The pace I chose when I still felt good. Fuel and sodium give the muscle a chance. Pacing decides whether it needs one."
— Alistair Brownlee, Two-time Olympic Triathlon Champion and founder of truefuels

2. Start with carbohydrate availability, then keep it coming

Low carbohydrate availability does not directly cause every cramp, but it raises the cost of maintaining race pace. As fuel becomes limited, perceived effort rises, form deteriorates and the working muscles are more likely to be pushed beyond their conditioned limit.

For events lasting longer than around 90 minutes, build a carbohydrate plan around the duration and intensity of the race. Many athletes perform well with 60–90 g of carbohydrate per hour. Some can use more, including up to 120 g per hour, but only when they have trained their gut and are using a suitable mix of carbohydrate sources.

The key is consistency. Take in carbohydrate early and at regular intervals rather than waiting until you feel depleted. A practical approach is to set a timer or link intake to predictable course points.

The number of feeds matters more than most athletes expect, because every feed is a decision you have to make while tired. On a 25 g gel, a 75 g per hour target means three gels every hour and around twelve across a marathon. On a 40 g gel it is fewer than two an hour, or roughly seven. Missing one of seven costs you less than missing one of twelve, and by the point cramps usually arrive you are far more likely to miss one.

Your pre-race meal also matters. Arrive with glycogen stores supported by normal, carbohydrate-focused eating in the days before the event, then use a familiar pre-race meal that sits well. Race morning is not the time to experiment with fibre, fat or an oversized portion.

3. Match fluid and sodium to your sweat rate and conditions

There is no universal hourly fluid target. A cool, wet half marathon and a hot long-course triathlon require different decisions, even for the same athlete. Your sweat rate, body size, pace, clothing and acclimatisation all influence the amount you need.

Start by measuring sweat rate in training. Weigh yourself before and after a known-duration session, account for fluid consumed, and note weather and intensity. Repeat the process in different conditions. The aim is not necessarily to replace every drop of sweat. It is to avoid substantial dehydration without overdrinking.

Many athletes will land somewhere around 400–800 ml per hour, with higher needs possible in hot conditions and lower needs in cooler weather. Use that only as a starting range, not a prescription. Your stomach comfort, thirst, body-mass changes and urine output after training help refine the plan.

Sodium requirements are also individual. Athletes with salty sweat residue on kit or skin, a history of high sweat losses, or races in sustained heat may need a more deliberate sodium strategy. A broad working range is often 300–600 mg of sodium per hour, while heavy, salty sweaters racing in heat may require more. Test this in training rather than guessing on the start line.

This is where a lot of athletes go wrong in the opposite direction. The response to a cramp is often to reach for the highest-sodium product available, and several popular options carry three to four times what most athletes actually lose in an hour. More is not safer. Excess sodium without matching fluid can cause its own gastrointestinal problems.

The truefuels formulation is built to replace roughly 80% of average sodium loss per 500 ml, which sits in the range where replenishment is useful and gastrointestinal risk stays low. Use sodium alongside an appropriate fluid plan, not as an excuse to neglect drinking or to consume plain water beyond thirst. If you have a medical condition involving blood pressure, kidneys or fluid balance, get individual advice before following a high-sodium protocol.

4. Prepare the exact muscles that cramp

Cramps are often specific. A runner may repeatedly cramp in the calves; a cyclist in the adductors; a triathlete in the hamstrings during the first kilometres off the bike. That pattern is valuable data.

Build race-specific durability. Include progressive long sessions, course-specific elevation where relevant, and controlled blocks at planned race intensity while fatigued. Strength training can help, particularly calf raises, hamstring work, single-leg control and quadriceps strength for runners. The goal is not to chase soreness. It is to increase the tissue and neuromuscular capacity needed late in the race.

Technique can be part of the issue. Overstriding, forcing an unfamiliar cadence, riding too low or using a new shoe can shift load into a vulnerable muscle group. Change one variable at a time in training, then retain what improves comfort and performance.

Build a cramp-resistant race plan in training

Treat every long session as a rehearsal. Test the carbohydrate dose, gel frequency, drink volume, sodium amount and timing you intend to use in competition. Record what happened: temperature, pace, total intake, gastrointestinal comfort, perceived thirst and any muscle warning signs.

Heat preparation deserves its own block. When conditions are warm, your fluid and sodium needs may rise, but so does the importance of lowering intensity expectations. Acclimatisation can improve your response to heat, yet it does not make aggressive pacing sensible. Adjust the plan to the day rather than defending a target set in cooler conditions.

Do not overlook recovery between hard sessions. Inadequate carbohydrate intake, poor sleep and accumulated fatigue can reduce the quality of key training and leave you carrying fatigue into the race. A disciplined system of fuel, hydration and recovery gives your muscles a better chance of doing their job when it counts.

What to do when a cramp starts

First, reduce the load on the affected muscle. Ease the pace, lower the gear or walk briefly if continuing at full effort will force a complete stop. Gentle lengthening may help: for a calf cramp, bring the toes towards the shin; for a hamstring cramp, carefully straighten the knee and hinge at the hip. Avoid aggressive stretching that adds more strain to a tired muscle.

Then assess the likely cause. Did you surge on a hill? Have you missed several feeds? Is the day hotter than expected? Are you drinking far less, or far more, than planned? Make a measured correction rather than consuming large amounts of fluid or electrolytes at once.

If cramps are accompanied by confusion, fainting, severe weakness, chest pain, marked swelling or symptoms that do not settle after stopping, seek medical support. Those signs need more than a race-day workaround.

The strongest race plan is not the one with the most products or the most complicated spreadsheet. It is the one you can execute under pressure: controlled pacing, trained carbohydrate intake, personal hydration and sodium targets, and muscles conditioned for the demands ahead. Rehearse it until it is automatic, then let the race reveal your fitness rather than your preparation gaps.