Stop Googling Your Marathon Fueling Plan

You've done the research. You've read the articles, scrolled through Reddit threads, bookmarked three different marathon nutrition guides. And every single one says some version of the same thing: aim for 30–60 grams of carbs per hour and drink 400–800ml of fluid.

That range is enormous. At the low end, you're taking three gels across an entire marathon. At the high end, you're taking eight. One of those plans gets you to the finish line. The other leaves you walking from mile 20.

So which is it?

The honest answer: no article can tell you. Because the right number depends on you — your body, your pace, your sweat rate, and the conditions on race day. And that's exactly why generic advice keeps failing runners who do everything "right" and still bonk.

The Problem With Averages

Most marathon fueling guides are built on population averages from sports science research. Those averages are real. They come from legitimate studies. But they describe the middle of a bell curve — and you might be standing at either end.

Here's what the research actually shows about individual variation:

Sweat rate varies 6x between athletes. During the same workout in the same conditions, one runner might lose 400ml of sweat per hour while another loses 2,400ml. That means the first runner needs a sip every 15 minutes and the second needs to drink aggressively just to stay functional.

Sodium loss varies 10x. Two runners with identical sweat rates can lose wildly different amounts of sodium. One might lose 200mg per litre of sweat, another 2,000mg. The runner with high sodium loss will cramp on a plan that works perfectly for their training partner.

Carb absorption capacity varies 2x. Some runners can comfortably absorb and use 90 grams of carbs per hour. Others hit GI distress at 40 grams. This isn't about toughness — it's about gut physiology, which can be trained but starts from a different baseline for everyone.

Pace changes everything. A 3-hour marathoner burns through glycogen at a fundamentally different rate than a 4:30 marathoner. But most fueling guides give the same advice to both. The slower runner actually needs more total fuel, not less — they're out there longer, burning through more glycogen, sweating for more hours.

When you stack these variables, the "right" fueling plan for one runner can be completely wrong for another. Copying your training partner's plan is like wearing their shoes — the size might be close, but the fit will be off in all the places that matter.

Why the Generic Range Exists (and Why It Doesn't Help)

The 30–60g/hr carbohydrate recommendation comes from the American College of Sports Medicine and similar bodies. It's not wrong — it's just not useful for an individual athlete building a race plan.

Think of it like a doctor saying "adults should eat 1,600–3,000 calories per day." Technically correct. Practically useless for meal planning.

The range exists because the research accounts for the variation described above. It's a safe window that covers most people in most conditions. But "most people in most conditions" isn't you, on your race day, at your pace, in that specific weather.

The same is true for hydration guidance. "Drink 400–800ml per hour" is the answer you get when you average across hundreds of athletes in controlled labs. Your actual sweat rate on a 15°C October morning in Chicago is a specific number — and it's a different specific number than on a 28°C afternoon in training.

What Actually Determines Your Numbers

Your personal fueling plan comes from four inputs that generic guides can't account for:

1. Your Sweat Rate in Race-Day Conditions

Your sweat rate changes with temperature, humidity, pace, fitness level, and acclimatisation. A plan built from summer training data will overestimate your fluid needs for a cool autumn race — and underestimating is just as dangerous as overestimating. A 2025 narrative review found that a hybrid approach, combining a pre-calculated plan with responsiveness to your body's cues, outperforms either pure scheduled drinking or pure drink-to-thirst.

The only way to know your race-day sweat rate is to measure it in conditions that approximate race day. Weigh yourself before and after a training run at race pace, in similar weather, and calculate the difference.

2. Your Body Weight and Pace

Heavier runners burn more calories per kilometre. Slower runners are out on the course longer and need more total fuel. A 60kg runner targeting a 3:15 marathon has fundamentally different carbohydrate needs than an 85kg runner targeting a 4:30. Yet most guides ignore body weight entirely.

Your pace also determines how hard your gut is working. At higher intensities, blood diverts from your digestive system to your muscles. This means faster runners may actually tolerate fewer carbs per hour despite burning more — a counterintuitive finding that trips up many athletes.

3. Your Gut Tolerance

Your gut can be trained to absorb more carbohydrates during exercise, but it takes time — typically four to eight weeks of progressive overload. If you haven't trained your gut to handle 60g/hr, a plan that prescribes it will send you to the porta-potties.

This is why "my training partner swears by Maurten and it destroyed my stomach" is one of the most common complaints in running forums. It's not the product — it's the mismatch between what the product delivers and what your gut can currently handle.

4. The Conditions on Race Day

Even a perfectly dialled plan needs adjustment when race-day conditions differ from training. Temperature and humidity are the obvious ones, but altitude, wind, and even the timing of the race (morning vs afternoon) change your needs.

A study of over 900 ultra-distance athletes found that athletes who adjusted their intake based on conditions outperformed those who stuck rigidly to a pre-set plan. The research suggests that flexibility, not rigidity, is the hallmark of effective race nutrition.

How to Find Your Actual Numbers

If you want to stop guessing, you need data — specifically, your own data from your own training.

Step 1: Measure your sweat rate. Do this on at least three long runs in varying conditions. Weigh yourself before and after, account for any fluid consumed, and calculate your per-hour sweat loss. You're looking for a range and a trend, not a single magic number.

Step 2: Test your carb ceiling. Start at 30g/hr on a long run and increase by 10g each week. When you hit GI distress, back off. That's your current ceiling. You can train it higher over time, but race day is not the time to push it.

Step 3: Map your plan to aid stations. Generic plans say "take a gel every 45 minutes." Practical plans say "take a gel at the mile 6 aid station, then at mile 11, then at mile 16." Know where the aid stations are and build your timing around them, because that's where the water is to wash down your gel.

Step 4: Run a full dress rehearsal. Your longest training run before taper should use your exact race-day products, in your exact race-day sequence, at your target race pace. This is the data point that matters most.

Step 5: Build in a Plan B. Every race goes sideways at some point. Know your fallback: if your stomach rebels, what do you switch to? If the weather is 10 degrees warmer than expected, how do you adjust fluid intake? If you're running 30 seconds per kilometre slower than planned, do you take more or fewer gels?

The Real Problem Is the Tooling

Here's the thing: all of the above is doable. Athletes have been doing sweat tests and gut training for years. But it requires a spreadsheet, a bathroom scale, weather data, and the discipline to log everything manually.

Most runners don't do it — not because they're lazy, but because the process is tedious and the calculations are error-prone. So they default to the generic advice, race on someone else's numbers, and wonder why their stomach revolted at mile 16.

This is the gap that wearable data was supposed to close. Your Apple Watch and Garmin already track your heart rate, pace, duration, and estimated calorie burn across every training run. The pattern that predicts your race-day needs is already sitting in your data. The problem is that no watch turns that data into a fueling plan.

Garmin's new nutrition tracking feature, launched in January 2026, is a step in the right direction — but it's a calorie tracker, not a race planner. It tells you what you ate today. It doesn't tell you what to eat at mile 14.

Sweatr bridges that gap. It pulls your training data from your Apple Watch, Garmin, or Strava, calculates your personal sweat rate and carbohydrate needs, and builds a race-day plan mapped to your actual pace and conditions — not the averages from a research paper. Your plan updates as your training progresses, so the plan you race on reflects the fitness you have, not the fitness you had eight weeks ago.

Stop Racing on Someone Else's Numbers

The next time you search "how many gels for a marathon," notice how wide the range is in every answer you find. That range exists because the answer is personal.

Your training partner's plan worked for their body, at their pace, on that day. Yours needs to work for you.

The data to build it is already on your wrist. The question is whether you want to do the maths yourself or let something do it for you.