How to Fuel Easy Runs, Speed Work, and Long Runs — Why One Plan Doesn't Fit Every Workout

Most runners have a race-day nutrition plan. Fewer have a plan for Tuesday's tempo run. Almost nobody has a plan for Thursday's easy shakeout.

That's a problem. Not because an easy run demands careful fueling — it doesn't — but because the gap between "I only think about nutrition on race day" and "I fuel every session according to what it demands" is where performance stalls, gut issues emerge, and training fatigue accumulates.

If you're training for a half marathon, marathon, or triathlon and you eat the same thing before every run regardless of what that run asks of your body, this post is for you.

Why your body needs different fuel for different workouts

The short version: different workout intensities burn fuel differently.

Easy runs (Zone 1–2 heart rate) rely heavily on fat oxidation. Your body has essentially unlimited fat stores, so the glycogen demand is low. You don't need much — if any — supplemental fuel.

Speed work and tempo runs (Zone 3–4) flip the fuel mix. At higher intensities, your body shifts toward glycogen as its primary energy source. Glycogen is limited. A hard 60-minute threshold session can drain a significant portion of your muscle glycogen stores, which is why bonking mid-interval feels different from bonking at mile 20 — it's the same energy crisis, just compressed.

Long runs (90+ minutes, any intensity) combine the challenge of duration with cumulative glycogen depletion. Even at an easy pace, a 2.5-hour long run will eventually exhaust your glycogen stores if you don't take in carbohydrates.

Your wearable data already captures this. When your Garmin or Apple Watch shows you spent 45 minutes in Zone 4 during intervals, that's telling you something about fuel demand — even if no watch currently translates that into "eat this many carbs." That's the gap Sweatr fills.

Easy runs: the session most people over-fuel

Duration: 30–60 minutes Intensity: Zone 1–2 (conversational pace) Glycogen cost: Low

Before

For a morning easy run under 60 minutes, you can run fasted or have a light snack. If you ate dinner the night before and slept normally, your glycogen stores are sufficient. A banana and a glass of water 30 minutes before is more than enough. Many runners prefer fasted easy runs and perform just fine.

If you run in the evening after a normal day of eating, you almost certainly don't need anything extra beforehand.

During

Nothing. Water if it's hot and you'll be out longer than 45 minutes. No gels, no sports drink. Your body is running primarily on fat at this intensity, and you have hours of fat fuel available.

After

A normal meal within 1–2 hours is sufficient. You don't need a recovery shake after every easy 5-miler. Save your recovery protocol for the sessions that actually deplete you.

The exception

If your easy run follows a hard session from the previous day — say, you did intervals on Tuesday and you're running easy on Wednesday morning — your glycogen may be partially depleted from the day before. In that case, a carb-rich breakfast 2 hours before the run helps. Your Garmin's Training Load or Body Battery reading can signal this: a lower-than-usual Body Battery on waking suggests your body is still recovering and may need fuel support.

Speed work and tempo runs: the session most people under-fuel

Duration: 40–75 minutes (including warm-up and cool-down) Intensity: Zone 3–5 (threshold to VO2max effort) Glycogen cost: High

This is where training-day fueling matters most — and where most runners get it wrong.

Before

Eat 2–3 hours before the session. Aim for 1–1.5g of carbohydrate per kilogram of body weight. For a 70kg runner, that's 70–105g of carbs — roughly a bowl of oatmeal with a banana and honey, or two slices of toast with jam and a glass of orange juice.

Why so specific? Because glycogen is your primary fuel at high intensities, and a speed session with depleted glycogen stores means you'll hit a ceiling before you hit your target paces. You'll feel sluggish in your third interval and blame it on fitness when it's fuel.

If you train in the morning and can't eat 2–3 hours early, aim for a smaller carb-rich snack (40–50g carbs) 60 minutes before. A white bagel with honey or a couple of rice cakes with jam works well. Avoid fibre and fat close to a hard session — they slow digestion and increase GI risk at high intensities.

During

For sessions under 60 minutes of hard effort, water is usually sufficient. If your total session (warm-up + intervals + cool-down) exceeds 75 minutes, or if it's hot, consider sipping a carb-electrolyte drink (30–40g carbs per 500ml) throughout.

For threshold runs lasting 50+ minutes at pace, a small amount of in-session carbs (a few swigs of sports drink) can help maintain intensity in the final third.

After

This is where recovery nutrition matters. After a hard glycogen-depleting session, your muscles are primed to absorb carbohydrates and begin replenishing stores. Within 30–60 minutes, aim for:

• 1–1.2g carbs per kg body weight (70–85g for a 70kg runner)
• 20–30g protein

A recovery smoothie with banana, oats, milk, and protein powder hits this easily. Or a bowl of rice with chicken and vegetables. The key is speed — the longer you wait, the slower glycogen replenishment happens, and that affects your next session.

If your watch shows a high Training Load or Acute Load after the session, take the recovery nutrition seriously. That metric is telling you the session cost was real.

Long runs: the session where race-day nutrition gets rehearsed

Duration: 90 minutes – 3+ hours Intensity: Zone 1–3 (mostly easy, with some marathon pace or progression) Glycogen cost: Very high (cumulative)

Your long run isn't just a fitness session — it's a fueling rehearsal. Everything you plan to do on race day should be tested here first.

Before

Eat a proper pre-run meal 2–3 hours before. This is your race-morning dress rehearsal. Aim for 2g of carbs per kilogram of body weight — for a 70kg runner, that's around 140g. A bowl of porridge, a banana, toast with honey, and a glass of juice gets you there.

Start practising your exact race-morning breakfast 8–10 weeks before the event. By race day, your body should know exactly what's coming.

During

This is where in-run fueling practice happens. The current sport science consensus targets:

• 60g carbs per hour for efforts up to 2.5 hours
• 80–90g carbs per hour for efforts over 2.5 hours (using a glucose-fructose blend for dual-transport absorption)
• Water intake matched to your sweat rate — typically 400–800ml per hour, higher in heat

Start fueling early. Take your first gel or carb source at 30–40 minutes, not when you start feeling tired. By the time you feel the dip, you're already behind.

Use every long run from week 8 onward to test:

• Which gels or fuel sources your stomach tolerates
• What frequency works (every 20 minutes? Every 30?)
• How much water you need alongside each gel
• Whether your stomach handles higher carb rates (80g+/hr) or needs to stay at 60g

After

Post-long-run recovery is critical, especially in the heat. Aim for a recovery meal within 30 minutes:

• 1.5g carbs per kg body weight
• 25–30g protein
• 500–750ml fluid with electrolytes

Your long run is the biggest glycogen expenditure of the week. If you skimp on recovery here, your Tuesday run will feel heavy, your Thursday speed session will suffer, and the fatigue compounds.

How your wearable data tells you what to fuel

You already own the data that answers "how much should I eat for this session?" — you're just not using it for nutrition yet.

Here's what to look at:

Heart rate zone distribution shows you the fuel mix. A run that's 90% Zone 1–2 burned mostly fat. A run with 40 minutes in Zone 4 burned through serious glycogen. Your post-run fueling should match the cost.

Training Load / TRIMP quantifies the total stress of the session. A Training Load of 50 is a different beast from a Training Load of 200. Your recovery nutrition should scale accordingly.

Body Battery (Garmin) or Recovery metrics tell you what you're bringing to the session. A Body Battery of 85 in the morning means full glycogen stores and fresh legs. A Body Battery of 35 means you're already depleted — eat before you run.

Estimated calorie burn from your watch is directionally useful even if the exact number isn't perfect. Don't ignore it entirely — use it as a rough guide for how much to eat back, then adjust based on how you feel in subsequent sessions.

The problem is that no watch currently connects these dots for you. Your Garmin shows you the data, but it doesn't say "based on this session's Zone 4 time and your body weight, eat 90g of carbs within the next hour." That translation layer — from raw wearable data to specific fueling actions — is exactly what Sweatr builds for you automatically.

A weekly fueling framework

Here's how this looks across a typical marathon training week:

| Day | Session | Pre-run | During | Post-run | |-----|---------|---------|--------|----------| | Mon | Rest | Normal meals | — | — | | Tue | Speed / intervals (60 min) | 70–100g carbs 2–3hrs before | Water, maybe sports drink | 70–85g carbs + 25g protein within 60 min | | Wed | Easy run (45 min) | Light snack or fasted | Nothing or water | Normal meal | | Thu | Tempo / threshold (50 min) | 70–100g carbs 2–3hrs before | Water | 70–85g carbs + 25g protein within 60 min | | Fri | Rest or cross-train | Normal meals | — | — | | Sat | Easy run (40 min) | Light snack or fasted | Nothing or water | Normal meal | | Sun | Long run (2–3 hrs) | 140g carbs 2–3hrs before | 60–90g carbs/hr + water to sweat rate | 100g+ carbs + 30g protein within 30 min |

This isn't a rigid prescription — your body weight, training volume, sweat rate, and the temperature outside all change the numbers. That's the point. A 55kg runner doing 60-minute long runs needs fundamentally different fuel than a 90kg runner doing 3-hour long runs in July heat.

The training-day fueling mistakes that wreck race day

Mistake 1: Only practising nutrition on long runs. Your gut needs practice at race pace, not just easy pace. If you only take gels at Zone 2 on your Sunday long run, your stomach may rebel when you take them at Zone 3–4 on race day. Include fueling practice in at least one mid-week session per month at tempo effort.

Mistake 2: Skipping recovery nutrition after hard sessions. The damage from a skipped recovery meal doesn't show up that day — it shows up 48 hours later when your next hard session feels impossible. Chronic glycogen under-recovery is a leading cause of mid-block training fatigue.

Mistake 3: Eating the same thing before every run. A 200-calorie granola bar is fine before an easy 5-miler. Before a 75-minute threshold session, it's not enough. Match the fuel to the demand.

Mistake 4: Ignoring your wearable data. Your watch already knows how hard the session was. If your Garmin shows a TRIMP of 180 and you eat a banana and call it recovery, you're setting yourself up for accumulated fatigue.

Let your data do the thinking

Every session in your training plan has a different fuel cost, and your wearable data already captures the inputs needed to calculate it — heart rate, duration, intensity zones, estimated calorie burn, training load, and recovery status.

The missing piece isn't the data. It's the translation layer that turns your post-run Garmin summary into "eat this, drink this, within this window."

Sweatr connects to your Apple Watch, Garmin, and Strava data and builds a personalised fueling plan for every session — not just race day. It calculates your carbohydrate needs based on the actual intensity and duration of each workout, adjusts for heat and sweat rate, and tells you exactly what to eat and when. No spreadsheets, no guesswork.

Your training plan is personalised. Your fueling should be too.