Running nutrition has a way of expanding into a second hobby — macros, timing windows, supplements, competing philosophies. For most runners, that complexity is not just unnecessary; it's counterproductive, because the runners who burn out on nutrition tracking usually stop doing the two or three simple things that actually matter.
Here's the practical core: what to eat before runs, what to eat after, and — the part most advice skips — how it should change as your training changes.
The one principle everything hangs on
Eat in proportion to your training load. Hard or long days need more fuel, especially carbohydrate; easy and rest days need normal, decent eating. That's the entire skeleton. Most fueling mistakes are violations of it in one direction or the other: under-eating on big days (leading to dead-legged sessions, poor sleep, and stalled recovery) or eating every day like it's marathon day (leading nowhere good either).
The corollary: your nutrition should follow your training week, not a fixed template. A plan that changes daily — as adaptive training does — implies fueling that flexes with it. This is exactly why TempoRun ties its nutrition guidance to your actual training load rather than issuing one static diet: the food follows the work.
Before a run
Easy runs under about an hour
Honestly? Not much is required. If it's morning, you can run fasted or grab something small — half a banana, a slice of toast. If it's later in the day, normal meals eaten sensibly (nothing huge in the final hour) cover it. Beginners are often relieved to hear this: the pre-run snack industry vastly exceeds the pre-run snack requirement.
Hard workouts and long runs
Here fuel matters. A carbohydrate-focused meal 2–3 hours before, or a smaller carb snack 30–60 minutes before, makes the difference between a workout you perform and one you survive. Practical options: oatmeal, rice, toast with jam, a banana, a bagel. Keep fat and fiber modest in the final couple of hours — they're healthy but slow to digest, and digestion and hard running are bad roommates.
The universal pre-run rules
Nothing new before a hard session; experiment on easy days.
If a food repeatedly wrecks your runs, believe your experience over the general list.
Hydrate through the day rather than chugging at the door.
After a run
Easy days
Your next normal meal handles recovery. The famous "anabolic window" that demanded a shake within 20 minutes has been considerably softened by later evidence — for a moderate session followed by lunch, timing barely matters. Don't build a ritual you don't need.
Hard workouts and long runs
Two things earn their place after big sessions:
Carbohydrate to restock. Glycogen — your stored carb fuel — is what long and hard running drains, and it's what tomorrow's legs run on. Prioritize a carb-rich meal within a couple of hours.
Protein to rebuild. A solid protein serving with that meal supports muscle repair. Real food covers this fine: eggs, yogurt, meat, fish, beans, milk. Shakes are convenience, not magic.
If a hard session kills your appetite — common — liquid options (milk, smoothies) bridge the gap until eating sounds appealing again.
The double-day trap
The costliest recovery mistake isn't the wrong food; it's the quiet under-eating after big days. A long Sunday run followed by a light, distracted Sunday and a rushed Monday leaves you training Tuesday on empty. String a few of those together and you get the signature pattern of under-fueling: heavy legs, worsening sleep, flat mood, plateaued fitness. If your training load went up and your appetite didn't, eat by plan rather than hunger for a day or two.
Scaling with your training week
A simple mental model, day by day:
Rest day: normal balanced eating. No compensation, no restriction theater.
Easy run day: normal eating, perhaps one extra snack if the run was longer.
Workout day: deliberate carbs before, deliberate carbs and protein after, and don't skimp at dinner.
Long run day: the biggest eating day of your week, on purpose. It should look different from a rest day, and if it doesn't, that's the first thing to fix.
Notice this requires knowing what kind of training day you're having — which an adaptive plan makes explicit. When TempoRun assigns your day based on your readiness check-in, the nutrition guidance moves with it, and its weekly summary shows training and nutrition side by side, which is where the under-fueling patterns become visible.
Tracking without the obsession
Detailed calorie tracking helps some runners and quietly harms others. A sustainable middle path:
Log loosely — what you ate, not gram-perfect weights. (In TempoRun, you log a meal by describing it in plain words and the AI works out what it was, which keeps the habit cheap enough to keep.)
Review weekly, not per-meal. You're looking for patterns — hard days paired with small eating days — not daily verdicts.
Track weight as a slow trend if it's relevant to you, never as a daily judgment; it fluctuates for a dozen reasons that aren't fat or fitness.
If tracking of any kind pushes you toward anxiety or restriction, drop it and keep only the load principle: big days, bigger fueling. And if you have any history of disordered eating, running nutrition is a topic to handle with a professional, not an app or an article.
The short version
Eat mostly normal food, mostly normally. Put carbs before and after the hard stuff. Make long-run days big eating days. Watch for the under-fueling pattern when training climbs, and let your fueling follow your actual training week — not the week a template imagined. Runners who nail that simple loop out-recover the ones with perfect macros and empty glycogen every time.