Stop Overthinking What You Eat For a Run
Three windows, three jobs, and none of it requires a supplement
I was on a run with one of my clubs last week when one of the regulars asked me what she should eat before a run.
She's a retired nurse with decades of experience in healthcare. She understands how the body works at a level most people don't. And she was genuinely uncertain about whether fruit was okay before a workout, whether she needed protein beforehand, and whether her muscles would break down if she got it wrong.
That question stuck with me, because it wasn't all that surprising compared to many other conversations I’ve had around nutrition for fitness. If someone with a medical background is confused about what to eat around a run, the problem isn't the person. The problem is how much noise surrounds a question that used to have an easy answer.
Fitness Culture Turned a Simple Framework Into an Anxiety Spiral
The information about workout nutrition isn't exactly wrong. It's just that a lot of the advice comes from research on one narrow context, and gets applied like it covers everything. That mismatch is where the confusion and contradictions come from.
Protein timing windows. Pre-workout supplements. Post-workout shakes. The carb debate. The fat debate. Influencer content that treats every meal around exercise like a high-stakes optimization problem with serious consequences if you get it wrong. All of it benefits from you believing the framework is harder than it is because complexity sells products and simple answers don't.
Another runner I know recently found out that protein has calories. He'd been tracking macros for months thinking protein was essentially free. That's more than just a gap in education. That's what happens when you learn nutrition in pieces instead of looking at it holistically for your needs.
And the actual cost of getting it wrong goes beyond failing some optimization protocol. It ends up with going into a workout underfueled and wondering why the run felt harder than it should have. It's training consistently for months, only to not see the adaptation you worked for because the recovery window keeps getting skipped. It's blaming your fitness and effort when the real problem has always been the fuel.
Your Body Wants Carbohydrates Before it Works Hard
The job of pre-workout food is to fuel the effort. That’s it.
Your body runs on two fuel sources during exercise - carbohydrates and fat. Fat is always available and burns well at the lowest intensities. But when the effort picks up - when you're pushing pace, running intervals, or doing anything that elevates your heart rate - your body reaches for carbohydrates first. Fat can't keep up with the energy demand at higher outputs.
Going in with low carbohydrate availability means the tank runs dry faster and the effort costs can’t be sustained.
Fruit is fine. Natural sugars are carbohydrates. Your body doesn't check the source before using them. A banana, some berries, a piece of toast - all of it does the job of giving your body readily available fuel for energy.
Protein before a workout isn't necessary. The fear that muscles will break down during a run without pre-workout protein is mostly a product of supplement marketing. Muscle protein breakdown during a normal training session is minimal. Your body is not cannibalizing muscle on a 45-minute run. Protein has a different job, and that job comes after the workout, not before it.
Light, carbohydrate-focused food 30-60 minutes before a workout is enough. A fuller meal 2-3 hours before if you have the time. Heavy meals, high-fat content, or large amounts of protein close to a workout can slow digestion and cause GI discomfort during the effort.
Not All Runs Need Mid-Workout Fuel
For workouts under 60-75 minutes, if you properly pre-fueled, then you probably don't need to eat anything mid-effort. Your muscles store a limited amount of carbohydrates as glycogen, and that stored glycogen, plus the sugar from your pre-fuel, should be enough to get you through it.
Past that point, re-fuelling carbohydrates start to matter. The longer the effort, the more you're drawing down glycogen stores, and the more performance depends on what comes in during the workout rather than what was stored beforehand. Simple carbs that digest quickly are what you want mid-effort. Protein and fat both digest too slowly to be useful while you're moving, and the intensity of work rises as a byproduct of the duration.
What you ate before the workout covers most shorter efforts. For longer workouts, simple carbs during the effort are what keep you going.
The Post-Workout Window Isn't Racing a Clock
The workout creates the stimulus for adaptation, but recovery is when the adaptation happens - muscles repair and rebuild during rest, not during the run. Post-workout food is what supplies that rebuild.
Two things need to be replaced after a hard effort: glycogen and muscle protein.
The workout burns through your glycogen stores to fuel the effort, and the harder or longer the workout, the deeper that hole gets. At the same time, the effort creates small amounts of muscle damage that the body needs raw material to repair. Carbohydrates refill the glycogen. Protein rebuilds the muscle. Both jobs matter, and neither one covers for the other.
Skip the carbs, and you can eat all the protein you want, but you're walking around depleted, and your next workout starts from a hole instead of a full tank. Skip the protein and the glycogen gets replaced fine, but the repair work has less to build with. They're doing different jobs at the same time, which is why the meal needs both, regardless of which one gets the marketing attention
That marketing attention has mostly gone to protein, specifically to a 30-60-minute "anabolic window" that supposedly closes quickly and costs you the workout if you miss it. That part is mostly myth. There's a mild advantage to eating protein soon after training, but it's small, and the body stays primed to use it for repair for hours afterward. What helps drive recovery is whether you're meeting your total protein needs throughout the day, not whether you had a shake in hand the second you finished.
None of that changes the urgency around carbohydrates. Glycogen replenishment starts working best in the hours right after a workout, and if you're training again the next day, or even later the same day, getting carbs in matters for how that next effort feels. Waiting too long to refuel doesn't ruin anything, but it does mean showing up to the next session running on less than you could have.
A meal or snack with both carbohydrates and protein within an hour or two after a workout covers both jobs. The specific minute you eat it matters far less than whether you eat it, and whether the rest of your day gets you to full on both fronts, not just one.
The Framework Doesn't Change, the Workout Needs Do
Pre-workout food fuels the effort. During-workout food maintains it when the effort runs long. Post-workout food rebuilds from it. That's the whole framework, and it holds regardless of what kind of run you're doing.
An easy morning run under an hour barely tests it. Something light with carbs beforehand, nothing mid-run, and your next meal covers recovery. A long run or a hard interval session is where the framework earns its keep. You fuel more intentionally going in, you bring simple carbs if you're out past 75 minutes, and you don't skip the recovery meal just because you're tired and don't feel like eating.
The decisions inside the framework - what specifically to eat, how much, what timing works for your digestion - vary by person and by workout. But the job each window is doing doesn't change. Once you know what each window is for, most of the choices about what goes on your plate stop being a guessing game.
When I finished explaining this to the retired nurse on that run last week, she went quiet for a second. Then she said, "That's it?"
She'd been carrying around years of conflicting advice and "hack" tips that had only confused her. The answer to what she'd been asking fit in three sentences.
What will you do differently in your next workout knowing that the framework has always been this simple?