Duration, not distance
Duration sets the fueling clock, not distance.
Carbohydrate needs scale with how long you are running, not how far. Two runners who are both out on course for four hours have a similar fueling clock, whether one is running a marathon and the other is covering a shorter distance more slowly. The limiting factor is how long your muscles and liver are drawing on stored glycogen. That is why the planner asks for a goal finish time. Distance sets the shape of the day. Duration sets how much fuel has to move through you.
The practical consequence is that two runners at the same race can need very different plans. A 3:10 marathoner and a 5:30 marathoner cover identical ground, but one is fueling for a little over three hours and the other for more than five. The slower runner spends longer drawing on stored fuel, so the total grams of carbohydrate and the number of feeding opportunities both rise. The planner works out the hourly rate and the total, and shows both.
- Goal finish time drives the hourly targets, not race distance
- Efforts under about an hour rarely need carbohydrate during the race
- Longer finishing times mean more total grams and more feeding stops
- Hourly rate and total load are shown as separate numbers
Carbs per hour
The ranges the evidence actually supports.
Sports nutrition consensus gives a workable set of starting ranges by duration. Around 30 g of carbohydrate per hour suits efforts of roughly one to two hours. Around 60 g per hour suits two to three hours. Beyond three hours, up to about 90 g per hour becomes possible, but only with multiple transportable carbohydrates, meaning a glucose and fructose blend, and only if the gut has been trained to absorb that much. Those ranges are the backbone of this planner.
The reason for the glucose and fructose blend is absorption. Glucose uses an intestinal transport route that saturates near 60 g per hour. Fructose uses a different route, so combining the two raises the ceiling. Above roughly 60 g per hour from a single carbohydrate source, the surplus is unlikely to be absorbed and can contribute to gut symptoms instead. The planner shows the reasoning next to the target, including why the blend matters once the number climbs past that level.
- Roughly 30 g per hour for efforts of about 1 to 2 hours
- Roughly 60 g per hour for efforts of about 2 to 3 hours
- Up to about 90 g per hour beyond 3 hours, using glucose plus fructose
- Above 60 g per hour, a single carbohydrate source limits absorption
- The untested, practiced and gut-trained settings move you within these ranges
Gut training
An untrained gut is the most common reason fueling fails.
High carbohydrate intakes are a trained skill, not a purchase. Fueling plans commonly fall apart because the runner practiced the pace but not the feeding. Nausea, bloating, and an urgent search for a toilet at 30 km are often a gut meeting a load it has not handled before. If your race plan calls for 75 g per hour, your long runs need to call for 75 g per hour first.
The general approach is to build gradually. Start at a rate you tolerate comfortably, add a modest increment every couple of weeks, and rehearse in the sessions that most resemble race day: long runs at goal effort, in similar heat, with the same products and the same timing. Give it weeks of repeated practice rather than one rehearsal shortly before race day. If a rate causes symptoms more than once, it is worth stepping back rather than pushing through.
- Rehearse the exact products, doses, and timing you plan to race with
- Practice in the heat you expect, not only on cool mornings
- Long runs at goal effort are the honest test, not easy runs
- Back off a rate that causes symptoms twice rather than forcing it
Fluid and sodium
Sweat rate is personal. Measure it rather than guess it.
Fluid needs vary enormously between individuals, and heat widens the spread further. Two runners of the same weight at the same pace can lose very different amounts of sweat, and the same runner loses more on a warm day than a cool one. Any calculator, including this one, is producing an estimate from population averages. A sweat rate test in training beats it: weigh yourself before and after an hour of running, account for what you drank, and use your own number.
Sodium is the same story with a wider range still. Sweat sodium concentration differs several-fold between runners, and it is not something you can read off how salty your shirt looks. The planner gives a starting band and tells you what it assumed. The safety point matters more than the precision: drink to thirst and to a plan you have tested, not far beyond it. Taking on much more fluid than you are losing over several hours carries a real risk of hyponatremia.
- Weigh in before and after an hour of running to find your own sweat rate
- Repeat the test in warm weather, since conditions change the answer
- Sweat sodium concentration differs several-fold between runners
- Drinking far beyond thirst for hours is a genuine safety risk
Scope and limits
This is education, not a prescription.
The race fueling planner is general sports nutrition education. It is not personalized dietary advice, and it is not medical advice. It cannot see your medical history, your medication, your gut, or your race. If you have a medical condition, take medication, are pregnant, or have a history of disordered eating, talk to a qualified professional before changing how you eat or drink around training and racing. That conversation is worth more than any calculator.
The output is deliberately product-agnostic. It says a 25 g carbohydrate gel, or 500 ml of drink mix at 40 g carbohydrate, so you can map it onto whatever you already use and tolerate. Nothing here is a recommendation to buy a particular brand. Every number is shown with the assumption behind it, because a plan you understand is a plan you can adjust when the day turns out hotter, slower, or harder than you expected.
- Grams per hour and grams total, with the assumption behind each number
- A pre-race section and a minute-by-minute timeline with a running total
- Product-agnostic amounts you can map onto what you already use
- General sports nutrition education, not medical or dietary advice
FAQ
Fueling questions, answered.
Carbohydrate, fluid, sodium and caffeine on race day, with the ranges the evidence supports and the limits around them.
01How many carbs per hour should I eat when running?
Carbohydrate intake during running is usually set by duration: roughly 30 g per hour for efforts of about one to two hours, roughly 60 g per hour for two to three hours, and up to about 90 g per hour beyond three hours. Rates above 60 g per hour require a glucose and fructose blend, because glucose absorption saturates near that level, and they require a gut trained for the load in advance.
02How do I build a marathon fueling plan?
A marathon fueling plan starts from your goal finish time rather than the distance, because carbohydrate needs scale with hours on your feet. Set an hourly carbohydrate rate appropriate to that duration, multiply it out to a total, then divide the total into feedings you can actually take at fixed points on the course. Add fluid and sodium based on your own tested sweat rate. Then rehearse the whole plan in long runs before race day.
03Do you need to fuel during a half marathon?
A half marathon nutrition plan depends mostly on how long you will be out there. A 1:25 finisher sits in the one to two hour window, where roughly 30 g of carbohydrate per hour is a reasonable starting point. A 2:30 finisher is closer to the two to three hour window and often does better nearer 60 g per hour. Fluid needs depend far more on heat and individual sweat rate than on the distance.
04What is gut training and how do I do it?
Gut training is deliberately practicing race-day carbohydrate intake in training so your digestive system can absorb it without symptoms. Begin at a rate you tolerate comfortably, add a modest increment every couple of weeks, and rehearse in long runs at goal effort using the exact products, doses, and timing you plan to race with. An untrained gut is a common reason a fueling plan fails on race day, not the plan itself.
05Can you drink too much water during a marathon?
Drinking far more fluid than you are losing over several hours can cause exercise-associated hyponatremia, a dilution of blood sodium that is dangerous and occasionally fatal. It is more common in slower finishers who drink at every aid station rather than to thirst. Drink to thirst and to a sweat rate you have tested, rather than to a fixed schedule. Confusion, headache, nausea, or swelling during a long race needs immediate medical attention.
06How much sodium do I need during a race?
Sodium needs during a race vary several-fold between runners, so any single number is a starting band rather than a prescription. Sweat sodium concentration differs widely between individuals, and total losses rise with heat and duration. Published race-day guidance for longer efforts generally falls in the hundreds of milligrams per hour, adjusted upward in the heat. The reliable way to narrow that range is to test your own sweat rate and tolerance in training.
07Should I take caffeine on race day?
Caffeine is among the better-supported performance aids in endurance sport, and the planner includes it only if you ask for it. Typical protocols use a moderate dose before the start, sometimes with a smaller top-up later in longer races. It does not suit everyone. It can worsen gut symptoms, disturb sleep before an evening race, and interact with medication. If you have not used it in training, race day is a poor place to start.
08How accurate is a race day nutrition calculator?
A race day nutrition calculator produces a defensible starting point from population averages, not a personalized prescription. Carbohydrate targets are the most transferable, because the absorption ceilings behind them are reasonably consistent between runners. Fluid and sodium are the least transferable, because sweat rate and sweat sodium vary enormously between individuals and with conditions. Treat the output as a hypothesis to test in long runs, and replace the fluid estimate with your own measured sweat rate as soon as you have one.
09What should I eat before a race?
A familiar, carbohydrate-rich meal two to four hours before the start is the standard approach, sized so it is comfortably digested by gun time. Consensus guidance for endurance events suggests roughly one to four grams of carbohydrate per kilogram of body weight in that window, with the lower end for shorter lead times. Keep fat and fiber modest. The strongest rule is familiarity: race morning is not the time to try a new breakfast.
10Do you need to fuel during a 5K or 10K?
Races under about an hour rarely need carbohydrate taken during the event, because muscle glycogen is generally sufficient for that duration when you start well fueled. For most runners a 5K and a 10K are settled by the days beforehand: normal carbohydrate intake, a familiar pre-race meal, and enough fluid to start hydrated. A carbohydrate mouth rinse is sometimes used in short, hard efforts, but swallowing gels mid-5K offers little.
Sources and verification
- Nutrition and Athletic Performance: Joint Position Statement of the Academy of Nutrition and Dietetics, Dietitians of Canada, and the American College of Sports Medicine (2016)Source for carbohydrate intake by exercise duration and pre-event carbohydrate guidance.
- Jeukendrup, A Step Towards Personalized Sports Nutrition: Carbohydrate Intake During Exercise, Sports Medicine (2014)Source for duration-based carbohydrate targets and multiple transportable carbohydrates.
- Jeukendrup, Training the Gut for Athletes, Sports Medicine (2017)Source for the adaptability of the gut to higher carbohydrate loads.
- Statement of the Third International Exercise-Associated Hyponatremia Consensus Development Conference (2015)Source for drinking to thirst and the risks of overdrinking during endurance events.