You’ve probably learned this the hard way: eating a burrito 30 minutes before a run is a mistake you only make once. But the opposite — running on a completely empty stomach — leaves some runners feeling flat, lightheaded, or unable to sustain effort.

The right answer is somewhere in between, and it depends mostly on timing, not food selection.

The Timing Guidelines

2-3 hours before: A normal meal is fine. Carbohydrate-focused (pasta, rice, bread, oatmeal) with moderate protein and low fat. Your stomach has time to digest before running. This is the ideal scenario for morning races or afternoon runs.

1-2 hours before: A small snack — 100-300 calories, mostly carbohydrates, very low fat and fiber. Examples: a banana, toast with jam, a sports bar, a small bowl of cereal. Enough to top off glycogen without sitting in your stomach.

30-60 minutes before: Only simple sugars if anything. A few bites of banana, a handful of pretzels, a small energy gel. Anything with fat, fiber, or significant protein is risky this close to running.

Under 30 minutes: Water only. Your body can’t digest anything fast enough to be useful, and undigested food in your stomach causes nausea, cramping, and side stitches.

What to Avoid Before Running

Fat. Slows gastric emptying dramatically. A peanut butter sandwich takes longer to leave your stomach than plain bread. The fat is still sitting there when you start running.

Fiber. Draws water into the intestines and adds bulk. High-fiber foods (beans, cruciferous vegetables, bran cereal) before running are the leading cause of urgent mid-run bathroom stops.

Dairy. Many runners experience GI distress from dairy before running, even if they’re not normally lactose intolerant. The jostling of running plus partially digested dairy is an unpleasant combination.

Large portions. The volume of food matters as much as the composition. Even “safe” foods cause problems in large quantities because the stomach is being jostled during running.

Fasted Running

Running first thing in the morning without eating is common and generally safe for easy runs under 60-90 minutes. Your body has enough stored glycogen from the previous day’s meals to fuel moderate aerobic exercise.

When fasted running works: Easy runs, recovery runs, and moderate long runs (up to 90 minutes for trained runners). These efforts primarily burn fat, and your fat stores are essentially unlimited.

When fasted running fails: Hard sessions (tempo, intervals) and long runs over 90 minutes. These require more glycogen, and starting with depleted stores means you’ll hit the wall earlier. Eat something for quality sessions.

The performance trade-off: Research is mixed on whether fasted easy running enhances fat oxidation adaptations. It might provide a small metabolic benefit for easy aerobic running. It definitely impairs high-intensity performance. The pragmatic approach: eat before hard sessions, and for easy runs, do whatever makes you feel better.

Individual Variation

GI tolerance during running varies enormously between individuals. Some runners can eat a full meal 90 minutes before a hard run with no issues. Others need 3+ hours of fasting to run comfortably.

The only way to learn your personal tolerance is experimentation — during training, not on race day. Try different foods, different timing windows, and different portions on easy runs. Once you find what works, repeat it consistently.

The most important pre-run nutrition rule is also the simplest: nothing new on race day.