How to Fuel a Marathon: Race-Day Nutrition From Start Line to Finish

Most marathons fall apart at 32 kilometers because of decisions made two days earlier. Knowing the guidelines is not the problem. In a study of endurance athletes, 36% could correctly name the carbohydrate loading target, only 10% hit it, and knowledge of the guideline had no relationship to what they ate (carbohydrate knowledge and practice study, PMC11451575). Race-day nutrition is a short list of numbers you rehearse until they are boring. Here they are, in the order you use them.

The fuel math behind your last 10K

Your body stores a limited amount of carbohydrate as muscle and liver glycogen. At easy paces, fat covers the rest of your energy needs, but at marathon effort your working muscles and your brain both want carbohydrate, and the tank is the binding constraint. A computational model of marathon metabolism found that more than two-fifths of runners hit severe, performance-limiting depletion of their carbohydrate stores during a race (Rapoport, PLOS Computational Biology). That is the wall. Three levers move it.

• Raise the tank before the gun. Carbohydrate loading in the last days before the race tops up muscle and liver glycogen so you start with more in the bank.
• Add fuel during the race. The same model notes that eating carbohydrate mid-race lets runners hold paces closer to their aerobic ceiling without emptying glycogen, and every gram you absorb is a gram you do not withdraw from storage.
• Pace so the tank lasts. Running the first 10K faster than goal pace shifts the fuel mix toward carbohydrate and raises the cost of every kilometer after it, which is why the best fueling plan in the world loses to a reckless first 5K. A pace band for locking in even splits is a fueling tool as much as a pacing one.

Fix all three or the other two stop mattering.

Carb loading: two days, not two weeks

The guideline is 10-12 g of carbohydrate per kg of bodyweight per day (carbohydrate knowledge and practice study, PMC11451575), and general sports nutrition consensus applies it across the last day or two before the race, which for a 70 kg runner works out at 700-840 g of carbohydrate a day. More food than most people picture. A large bowl of pasta is around 100 g.

The athletes in that study who knew the number consumed 6.1 g/kg on average. Roughly half short. If your loading has never felt uncomfortable, you have probably never loaded.

• Two days is enough. The classic depletion week has fallen out of favor: taper the running, raise the carbohydrate, and the tank fills. Use a carb loading calculator to convert bodyweight into grams per day so you are working from a number instead of a feeling.
• Go low fiber and low fat. White rice, white bread, pasta, bananas, honey, jam, sports drink, potatoes. Fiber and fat are the two things that make race morning uncomfortable, and this is the one window where the beige food wins.
• Drink your carbs when you run out of appetite. Juice, sports drink, and maltodextrin powder cover the last 150-200 g without another plate of food.
• Expect the scale to rise. A kilo or two of gain is water bound to stored glycogen, which is the sign the load worked, and it is not fat.
• Load into a real taper. Cutting volume while raising carbohydrate is the whole point, and if you are unsure how much to cut, the taper guide has the framework.

Race morning and the final hour

The pre-race meal target is 1-4 g of carbohydrate per kg (carbohydrate knowledge and practice study, PMC11451575), eaten far enough out that it has cleared your stomach by the gun, and it is the one guideline most athletes already meet. Common practice puts the meal somewhere between one and four hours before the start, and the further out you eat, the more you can eat.

Three hours out, a 70 kg runner can handle 150-250 g: oatmeal with honey and a banana, white toast with jam, a bottle of sports drink. Ninety minutes out, drop to the bottom of the range. Liquid, or close to it.

• Nothing new, nothing high fiber, nothing greasy. Same breakfast you ate before your two longest runs. Same coffee. Same timing.
• Stop eating well before the gun. Among 805 recreational long-distance runners, eating within 30 minutes of the start was associated with more bloating, more flatulence, and more urge to defecate during the race (survey of 805 recreational runners, PMC12325075). The corral is not a dining room.
• Sip fluid to comfort, then stop. Small amounts across the last two hours, finishing early enough for one last toilet stop, because chugging half a liter in the corral buys you a line at the first toilet.
• A gel 10-15 minutes before the start is optional and personal. Some runners like it. It is a rehearsal question, so test it on a long run rather than at 08:55 on race morning.

Carbs per hour, and why almost everyone undershoots

A single carbohydrate source oxidizes at up to roughly 60 g/h, which is the recommendation for exercise lasting 2-3 hours. In ultra-endurance events the target rises to around 90 g/h, and hitting it requires multiple transportable carbohydrates, meaning a glucose and fructose blend that uses two absorption pathways instead of one (Jeukendrup, PMC4008807). Most current guidance carries that upper band down to any race running much past three hours, marathons included, and almost every modern gel and drink mix is formulated this way. Check the label for fructose.

Now the reality. Across 160 runners at the Seville Marathon, average carbohydrate intake during the race was 35 g/h, with fluid at 466 mL/h, sodium at 192 mg/h, and caffeine at 57 mg/h, and the runners who landed inside the 30-60 g/h band that study measured against were more likely to finish under three hours (Seville Marathon field study, PMC11911277). Roughly half of what the guideline asks for. That is where the average marathoner is fueling.

A practical way to translate the range, once your gut has been trained up to the number:

• Sub-3:00 finishers: 75-90 g/h. High intensity, high carbohydrate cost, short time on feet.
• 3:00 to 4:00: 60-80 g/h. The middle of the guideline, and where most PR attempts live.
• 4:00 and beyond: 50-70 g/h. Lower intensity means more fat oxidation, but the clock runs longer, so total intake still matters.
• Count in products, not grams. A typical gel holds 20-25 g. Eighty grams an hour is 3-4 gels, or two gels plus a bottle of carbohydrate drink, so work it out before race week with a race nutrition calculator that converts your target into gels and bottles.
• Start at 30-40 minutes and run a clock. Take the next one every 20-25 minutes whether you want it or not, because waiting until you feel low means you are already an hour behind on absorption.

The ceiling has moved for athletes who train for it. In a small trial, elite trail runners taking 120 g/h through a mountain marathon showed better neuromuscular function and high-intensity running capacity 24 hours later than groups at 60 or 90 g/h (mountain marathon trial, PMC7400827), and those were gut-trained elites on a course where they were moving slower than road pace. Treat 120 g/h as a destination, not a starting point.

Fluid and sodium: thirst first, your own numbers second

There is no universal milliliters-per-hour figure. Sweat is the most variable thing in this guide: whole-body sweating rate typically runs 0.5 to 2.0 L/h, around 2% of athletes exceed 3.0 L/h, and sweat sodium concentration, estimated across the whole body rather than from a single skin patch, spans roughly 10 to 70 mmol/L between individuals (Baker, PMC5371639). Two runners side by side can lose several times what the other does.

The bigger risk for a mid-pack marathoner in temperate weather is drinking too much, not too little. Reported prevalence of exercise-associated hyponatremia in marathon runners ranges from under 1% to 22%, driven by sustained fluid intake that exceeds losses, and the standing recommendation is to drink to thirst rather than to a schedule (review of exercise-associated hyponatremia, PMC9699060).

• Measure yourself instead of guessing. Weigh in nude before a long run and again after, adding back what you drank, and that gives you your liters per hour in your conditions. A sweat rate calculator to turn those two weights into a number does the arithmetic.
• Use thirst as the governor on race day. Drink when you want it, at the volume you want, and if you finish a cool-weather marathon heavier than you started, you drank too much.
• Know the warning signs. Hyponatremia is a medical emergency, not a bad patch. A headache that builds, nausea, confusion, or puffy hands and fingers late in a race means stop drinking and find the medical tent.
• Add sodium when the loss is real. Hot race, long day, visible salt crust on your face, a history of cramping. The Seville field averaged 192 mg/h, which is low against most guidance. Carry your own if the on-course drink is weak.
• Know the course before you know your plan. Aid station spacing and the brand of drink on the tables decide whether you carry bottles, so check both in the race manual. Hydration tracking for athletes covers the day-to-day side of this.

Caffeine and the rest of the kit

Caffeine has the strongest evidence of anything else you might carry. The ISSN position stand reports consistent performance improvement at 3-6 mg/kg, most commonly taken 60 minutes before exercise, with aerobic endurance showing the most reliable moderate-to-large benefits (ISSN caffeine position stand, PMC7777221).

For a 70 kg runner that is 210-420 mg. The top of that band is a large dose, the response varies between people, so start at the bottom in training and see how you sleep the night before and how your stomach handles it at speed.

• Split it if you like. Half 60 minutes before the start, half through caffeinated gels in the second half, and the Seville average of 57 mg/h suggests most runners take far less than they could.
• Test it in a rehearsal, not a race. Caffeine on an empty, nervous stomach is a different experience from caffeine on a Tuesday afternoon.
• Keep the rest of the shelf out of it. Carbohydrate, fluid, and caffeine carry the evidence. Anything new goes in the training block, never in the start pen. See caffeine for endurance for dosing detail and the sleep trade-off.

Train your gut, then rehearse the whole thing

Your gut is trainable. Untrained guts are why good plans end in a hedge at 28K, and gastrointestinal symptoms during races were reported by 26.1% of 805 recreational long-distance runners (survey of 805 recreational runners, PMC12325075). A systematic review of gut-training and feeding-challenge protocols found gut discomfort dropped by an average of 47% with a two-week repeated-carbohydrate protocol and by 26% with a repeated fluid-ingestion protocol, with interventions running 4 to 28 days and most clustering around two weeks (systematic review of gut training, PMC10185635).

Two weeks is the floor. Give it two months and build in steps.

• Progress the hourly rate. Start long runs at 40 g/h, then add 10 g/h every couple of weeks until you reach your race number, which puts the climb from 40 to 80 inside six to eight weeks.
• Use the exact products. The gel brand, the drink mix, the flavour, the bottle. Different formulations sit differently. Gut training for carb tolerance has the progression in detail.
• Fuel the long run even when you do not need to. A 90-minute run does not require 80 g/h. Practicing it does.
• Run two full dress rehearsals. Your two longest runs, at race-morning wake time, with the race breakfast, the race gels, the race drink, and the race kit. If something is going to go wrong, it goes wrong there, where the cost is a bad Sunday.
• Write down what happened. Rate of intake, timing, how the stomach felt at each hour, what you skipped. A race day checklist to lock the plan down turns those notes into something you can follow when you are nervous and half awake.

The rest of the fueling picture across a training block sits in fueling around long sessions. Race day is the smallest part of it.

How Movement Rebels fits

Writing a fueling plan takes an afternoon. Holding it across a 16-week block is the hard part, and that is where the coaching sits. The Movement Rebels coach reads your Garmin or Apple Health data and sees your last 14 activities with per-kilometer splits, pace, cadence and average heart rate, so a long run where the last hour came apart shows up in the splits, and after each sync it posts an analysis of that run. It also sees your logged lifts and PRs, your morning readiness check-ins, and your HRV, resting heart rate and sleep, so the strength work you drop in the final three weeks is accounted for in the plan rather than ignored.

Write "practicing 80 g/h on long runs" in the "Notes for your coach" field and the coach reads your next long run against that note. It does not read your meal log, so put what you took in as the note on the activity itself, and the analysis has the number in front of it. When your resting heart rate climbs and your HRV drops across a heavy block, that feeds into Sunday's plan generation and the week gets pulled back. The Sunday plan puts your two dress rehearsals on the calendar with the right duration, and planned sessions push to your Garmin watch, so the rehearsal is on your wrist before you leave the house.

Put your first gel at 30 minutes and set a repeating alarm on your watch for every 25 after it. The runners who come apart at 32K are almost always the ones who were waiting to feel hungry.