A Runner's Nutrition Guide: What to Eat Before, During, and After

Good runner nutrition is simpler than the supplement aisle makes it look: eat mostly carbohydrate-rich whole foods day to day, top up with easy-to-digest carbs before longer runs, take in 30-60 grams of carbs per hour only when a run passes roughly 75-90 minutes, and pair carbs with protein soon after hard or long sessions to refuel and repair. Drink to thirst, and drink more around heat and long efforts. Everything below is just the detail on that frame.

Fueling is the half of training most runners under-think. You can have a perfect plan built on how running training actually works, but if you show up to a workout empty or limp through a long run on water alone, you cannot hit the paces that drive adaptation. Food is not a side note to training. It is the raw material your body turns training stress into fitness with.

What does daily runner nutrition actually look like?#

Most of your nutrition wins happen on ordinary, non-workout days, not in some magic pre-race meal. The foundation of runners nutrition is a daily pattern that keeps your muscle glycogen (stored carbohydrate) topped up so you can train hard and recover between sessions.

A simple, balanced template for most days:

• Carbohydrates make up the largest share — rice, potatoes, oats, bread, pasta, fruit, beans. They are your primary running fuel.
• Protein at every meal — eggs, dairy, fish, poultry, tofu, legumes — to repair the muscle that training breaks down.
• Fats for hormones, satiety, and long-term energy — olive oil, nuts, avocado, fatty fish.
• Color and fiber from vegetables and fruit for the micronutrients and antioxidants that support recovery.

You do not need to weigh every gram. The practical test: are you fueled enough to hit your workout paces, recover by the next hard day, and feel decent through the day? If yes, your baseline is working.

How many carbs do runners need per day?#

It scales with how much you run. Sports-nutrition consensus puts daily carbohydrate roughly in these ranges, and you periodize toward the high end as training volume climbs:

The point is not to hit a number to the gram. It is to eat more carbohydrate on bigger training days and less on easy or rest days — a principle called carbohydrate periodization. This mirrors the training logic in polarized 80/20 training: easy days are genuinely easy and don't demand heavy fueling; quality and long days do.

What should I eat before a run?#

Before a run, your goal is topped-up energy without a heavy or sloshing stomach. The right answer depends almost entirely on how long the run is and how much time you have.

Short, easy runs (under ~45-60 min). You generally need nothing special. Your existing glycogen covers it. Many runners do easy morning miles fasted or on a banana or a couple of dates. Water, then go.

Longer or harder runs. Eat 150-300 calories of mostly carbohydrate, 30-90 minutes before, low in fiber and fat so it clears your stomach. Think toast with honey, a banana, oatmeal, a bagel, or a small bowl of cereal. The more time you have before the run, the larger and more normal the meal can be.

Big efforts with hours of lead time. A real meal 2-3 hours out — oatmeal and fruit, rice and eggs, a bagel with a little nut butter — gives you a fuller tank and time to digest.

The single most important rule: nothing new on race day. Practice your exact pre-run meal in training so you know your gut tolerates it. Caffeine, around 1-3 mg per kg of body weight, is one of the few legal aids with solid evidence behind it for endurance — but test your tolerance in training, not in a race.

Do I need to eat during a run?#

Only when the run is long enough that you would otherwise run low on fuel. The dividing line most coaches and sports dietitians use is roughly 75-90 minutes.

• Under ~75-90 minutes: Stored glycogen plus a normal pre-run meal carries you. Water is enough. You do not need gels for a 5K.
• Over ~75-90 minutes (long runs, half and full marathons, hard sustained efforts): Take in 30-60 grams of carbohydrate per hour to keep blood sugar and energy steady and to delay the "bonk."

Thirty to sixty grams an hour is the workable range for most runners. Very long ultra-distance efforts can push toward 90 g/hr using multiple carb types (glucose plus fructose), but that requires a trained gut and is beyond what most road runners need.

Forms that all work — pick what your stomach likes:

• Gels: ~20-30 g carbs each, compact, take with water.
• Chews / sports beans: easy to dose in small bites.
• Sports drink: fuel and fluid together, useful in heat.
• Real food: dates, banana, dried fruit, even gummy candy — cheaper and gentler for some runners.

Start fueling early — within the first 30-45 minutes of a long run, not when you already feel empty. By the time you feel the bonk, you are an hour behind. As with pre-run food, rehearse mid-run fueling in training so your gut adapts and race day holds no surprises.

How much should runners drink, and when?#

Hydration is about staying within a sensible range, not drinking as much as possible. Both under- and over-drinking cause problems, and the science has shifted firmly toward drinking to thirst for most runners.

Day to day: Drink normally with meals and when thirsty. A quick gut check is urine color — pale straw is the target; consistently dark suggests you are behind, and clear-and-frequent all day may mean you are overdoing it.

Before a run: Sip water in the hours beforehand. No need to chug right before — that just leaves it sloshing.

During a run:

• Under an hour: Usually no fluid needed in moderate conditions. Carry water in heat if you want it.
• Over an hour or in heat: Drink to thirst, roughly small, regular sips. In long, hot efforts a sports drink adds sodium, which helps you hold onto fluid and replaces what you sweat out.

After a run: Rehydrate gradually with fluids and salty food alongside your recovery meal. A rough guide is to replace fluid over the hours that follow rather than all at once.

One safety note: drinking far beyond thirst over a long event can dangerously dilute blood sodium (a condition called hyponatremia). More water is not always safer. Thirst is a good guide, and during long, sweaty efforts, sodium matters as much as the water itself. If you ever feel confused, nauseated, or unusually swollen during a long run, stop and seek help — that is a medical issue, not a coaching one.

What should I eat after a run to recover?#

After a run, your job is to refill the fuel you burned and give muscles what they need to rebuild. The two levers are carbohydrate (to replace glycogen) and protein (to repair and adapt).

A practical recovery target after a hard or long session:

• Carbs: roughly 1-1.2 g per kg of body weight in the first hour or two.
• Protein: about 20-40 grams to support muscle repair.

The classic ratio people remember is roughly 3-to-1 carbs to protein, and it is a fine starting point. Familiar examples that hit it: chocolate milk, Greek yogurt with fruit and granola, a turkey-and-rice bowl, eggs on toast with fruit, or a smoothie with milk, banana, and a scoop of protein.

Does the "recovery window" really matter?#

Less than people think, but it is not nothing. The old idea of a rigid 30-minute "anabolic window" that slams shut has been overstated. What actually matters most is your total daily carbohydrate and protein, spread across the day.

The window matters more in two specific cases:

1. You trained fasted or under-fueled before the session.
2. You have another run coming soon — a second session that day, or a hard day tomorrow — where fast glycogen refill is genuinely useful.

For a single daily run with normal eating, just have a balanced meal within a couple of hours and you are fine. Don't let "I missed the window" become a reason to skip refueling — the day's total is what counts. This is the food side of the stress + rest = growth equation that underpins all training: recovery, including what you eat, is when fitness is actually built. Under-fuel recovery and you blunt the adaptation you just earned, and you can leave yourself more vulnerable to the kind of overuse problems covered in how to avoid running injuries.

How does nutrition change for race day and racing distances?#

Fueling scales with distance, and the longer the event, the more your stomach — not your legs — can decide your day.

• 5K / 10K: A normal pre-race meal 2-3 hours out and water is plenty. No mid-race fuel needed.
• Half marathon: Solid pre-race carbs, then carbohydrate during if you are out longer than about 90 minutes — a gel or two for many runners.
• Marathon: This is where fueling makes or breaks the race. Aim for 30-60 g carbs per hour start to finish, begin early, and drink to thirst with some sodium. Most "marathon walls" are under-fueling, not under-training.

In the days before a long race, many runners do a light carb-loading approach — nudging carbohydrate intake up for 1-3 days while easing training during the taper — to maximize stored glycogen. It is most useful for the marathon and longer; it does little for a 5K. Match the strategy to the distance, as covered in how to train for any race distance.

This is exactly where pre-loaded coaching shines. RunScend, our AI running coach, builds your fueling and pacing into the session before you head out and talks you through it in real time — including reminders to take a gel or sip at the right moments — so the plan reaches you even when you are deep on a trail with no signal.

Common runner nutrition mistakes to avoid#

A short list of the errors that trip up the most runners:

1. Under-fueling overall. Chronically eating too little to support training stalls progress, wrecks recovery, and risks low energy availability — a real and serious problem, especially around bone health and hormones. If you are constantly exhausted, frequently injured, or losing weight unintentionally, see a sports dietitian or physician.
2. Trying new foods on race day. The cardinal sin. Your gut is a muscle you train; rehearse everything.
3. Fueling by the clock, not the run. Gels on a 30-minute jog are unnecessary; nothing on a 3-hour run is a recipe for the bonk.
4. Over-drinking. More water is not always better. Drink to thirst.
5. Ignoring protein and iron. Runners, especially women and vegetarians, are prone to iron deficiency, which can quietly drag down performance. If you feel inexplicably flat, ask your doctor for a blood test rather than guessing.

A genuine note on individual needs: this is general guidance, not a personal prescription. Body weight, sweat rate, gut tolerance, medical conditions, and goals all shift the numbers. For diagnosed conditions, disordered eating, suspected deficiencies, or a high-stakes goal race, work with a registered dietitian or physician who can tailor a plan to you.

Putting it together: a simple fueling rhythm#

You can run most of your nutrition on a handful of habits:

• Daily: Carb-forward, protein at every meal, color on the plate. More fuel on big days, less on easy ones.
• Before: Easy carbs 30-90 minutes out for longer runs; little or nothing for short easy ones. Never anything new on race day.
• During: Water under ~75-90 minutes; 30-60 g carbs per hour beyond that.
• After: Carbs plus 20-40 g protein within a couple of hours of hard or long sessions.
• Hydration: Drink to thirst; add sodium for long, hot efforts.

Dial those in and your fueling will quietly support every other part of your training — the easy base, the hard workouts, and the long runs where fitness is forged. If you want the plan and the fueling cues delivered in your ear at the right moment, run by run, that is exactly what an AI running coach like RunScend is built to do. Run Further. Run Smarter. Run Within.