Diet For Runners In Training

What actually keeps you from bonking at mile 18

The biggest mistake I see runners make is treating their diet like a supplement to their training instead of the foundation it actually is. You can log all the miles you want, but if you're running on empty glycogen stores, your pace is going to suffer and your recovery will take twice as long. I learned this the hard way during a half marathon prep cycle when I cut calories thinking I was being "efficient" — lasted three weeks before I was hitting the wall on every long run and my resting heart rate climbed eight beats per minute. This is probably the most important thing to understand going in. Running burns calories, so logically you'd think you should eat less. That logic is exactly what breaks most people. You need to eat more, and specifically more carbohydrates, around your hardest training blocks. The general guideline sits somewhere between 5 and 7 grams of carbs per kilogram of body weight on moderate training days, climbing to 8 or even 10 grams per kilogram when you're doing back-to-back long runs or double sessions. For a 70-kilogram runner, that's 350 to 700 grams of carbs daily depending on the week. Most recreational runners I talk to are eating maybe half that and wondering why they feel terrible. The practical problem isn't knowing the numbers though. It's actually getting that much food down when your stomach is already suspicious from three hours of running. I tried pushing 300 grams of carbs on a heavy training day once and immediately regretted it. A mid-morning bowl of oatmeal with banana and honey got me to about 80 grams easily. Lunch was pasta with a light tomato sauce — another 100 grams or so. The real trick came after that: I switched to liquid calories for a good chunk of the day. A carb powder mixed into water between meals is genuinely easier to consume than solid food when you're trying to hit aggressive numbers without feeling like you're going to vomit. Brands like Maurten and SiS make products specifically designed around this problem. They don't taste amazing but they deliver 100 grams of carbs in under 200 calories and cause zero gastric distress for most people.

Protein matters too, just not nearly as much as runners overcorrect toward it. Aim for roughly 1.4 to 1.7 grams per kilogram of body weight. That's it. More than that won't build more muscle or recover you faster — it'll just sit there as extra calories. I've seen serious amateur runners eating 200 grams of protein daily because they read something on Instagram, and their actual carb intake was pathetically low. The math doesn't work in their favor.

Timing matters more than people admit

Your body handles fuel differently depending on when you eat it relative to your run. The pre-run window, roughly 2 to 4 hours before you start, is where most of your main meal should land. Something digestible with moderate fiber and low fat. Eggs and toast works. Rice and chicken works. A bagel with peanut butter works if you're not sensitive to fat around run time. The goal is topping off glycogen without having food sloshing around in your stomach when you tie your laces. During the run is where the rubber meets the road for anything over 75 minutes. Your body's glycogen stores start running thin after about an hour of steady effort. Gels, chews, or sports drink are the standard tools here. The sweet spot for exogenous carb oxidation during exercise is roughly 60 grams per hour. You can push higher — some research supports up to 90 grams per hour using a combination of glucose and fructose — but most runners aren't trained to handle that and will pay for it with GI issues. Start with 30 to 60 grams per hour and work up only if your stomach allows it. I learned this by trial and error during a winter training block. Tried 90 grams per hour on a long run in cold weather, finished the run, and spent the next three days questioning every life choice that led to that decision. Dial it back to 60 and it's manageable. The post-run window is about refueling and repairing. Getting carbs in within the first hour after finishing is useful because your muscles are particularly receptive to replenishing glycogen at that point. Combine that with 20 to 30 grams of protein and you've started the recovery process properly. Chocolate milk is genuinely one of the most efficient recovery drinks available and I've recommended it to countless runners who found the taste unappealing until they actually tried it. It's not a joke recommendation — the carb-to-protein ratio is nearly perfect for this purpose.

Hydration is a separate problem you need to solve independently

Dehydration of even 2 percent body weight can reduce running economy by about 3 percent. That's significant. If you're running a 7-minute mile, you're now running closer to 7:14 without meaning to. Most people underestimate how much fluid they lose through sweat. A sensible starting point is drinking to thirst, which sounds obvious until you realize a lot of runners ignore thirst until they're already behind. Weigh yourself before and after runs longer than 60 minutes. Every kilogram lost is roughly a liter of fluid you need to replace. Add in a pinch of salt if it's a hot day or you're a heavy sweater, because replacing fluid with plain water alone can dilute your blood sodium and in extreme cases lead to hyponatremia, which is genuinely dangerous. I once ran a 20-mile loop in July wearing what I thought was appropriate summer gear. Lost about 2.5 kilograms of water weight during that run, drank only water the entire time, and spent the afternoon with a splitting headache and nauseous. Started adding electrolyte tablets to my bottle for runs over 90 minutes in warm weather after that. Cheap solution, made a noticeable difference immediately.

Weekly structure matters more than any single meal

Your diet should flex with your training load. Heavy weeks demand more calories, especially carbs. Easy weeks or recovery weeks can run slightly lower. This concept is called periodized nutrition and it's something serious training plans rarely address adequately. If you're doing two long runs on consecutive days, both of those days need above-average carb intake. The day after a very hard session might benefit from a slight reduction since your body is in repair mode rather than fuel storage mode. I stopped trying to eat the same amount every single day around six years ago and my performance improved noticeably, mostly because I stopped arriving at long runs already in a mild energy deficit from the day before. Iron deficiency is surprisingly common in endurance runners, particularly women and vegetarians. The mechanism involves a combination of foot-strike hemolysis — red blood cells getting mechanically destroyed with each impact — and increased iron loss through sweat and gastrointestinal bleeding. If you're training hard and feeling flat, exhausted, and your performance has stalled without an obvious reason, getting your ferritin checked is a reasonable step. I went through a phase where I couldn't figure out why my tempo runs felt impossibly heavy despite being well-rested. Bloodwork showed ferritin in the single digits. Supplementing fixed it in about eight weeks. It wasn't glamorous but it was probably the single most impactful change I made to my training diet. A solid training diet won't fix a bad training plan. You can eat perfectly and still be overtrained, under-recovered, or doing the wrong workouts. Nutrition is a multiplier, not a substitute for good coaching and sensible programming. It also won't help much if you're severely under-eating across the board — no amount of timing optimization changes the fact that 1,800 calories is 1,800 calories regardless of when you eat them. And for anyone with a history of disordered eating, the obsessive tracking this subject can encourage is genuinely harmful. If you find yourself weighing every gram of food or panicking about missed meals, that's not a nutrition problem, that's something else entirely and you should probably talk to a professional rather than reading another article about carb loading.

The bottom line is that running diet is simpler than it sounds but harder to execute consistently. Hit your carb targets on heavy days, drink during runs longer than 75 minutes, recover with carbs and protein within an hour of finishing, and let your intake follow your training load rather than staying rigid. Everything else is incremental detail.