Best-Running-Tips.com

Hunger After Running How Run Duration Changes Your Appetite

Let's face it — not every run leaves you raiding the fridge. Below about 40 minutes at easy effort, most runners won't notice much change in appetite. Push past 60 minutes, especially at moderate effort or harder, and expect a clear hunger rebound 60–90 minutes later. The table below breaks down exactly what to expect — and eat — at each length.

The Duration–Hunger Spectrum: What to Expect at Each Run Length

The tiers below aren't pulled from a single study — they're built from over 20 years of coaching recreational runners through calorie-deficit training blocks. Find your typical session length, and you'll know roughly what your appetite is about to do.


For the full hormonal mechanism behind that rebound — ghrelin, PYY and GLP-1, and how they interact — see how post-run hunger hormones work. This page sticks to the practical, duration-based picture; for deficit-specific strategy once the hunger arrives, see managing post-run hunger in a calorie deficit.

Intensity vs. Duration — Which One Drives Hunger More?

Here's a scenario I hear constantly: you do a brutal 30-minute interval session and you're starving an hour later, while your training partner jogs an easy 60 minutes and barely thinks about food. Neither of you is imagining it. Intensity accelerates glycogen drawdown, compressing what normally takes a long duration into a much shorter window.

As a rough planning rule, about 1 minute of interval-pace running burns through glycogen at roughly the same rate as 1.5–2 minutes of easy running. A session like 6 × 800m at 5K pace can leave you as hungry as a 45–60 minute moderate run — same appetite response, completely different clock time.

That doesn't make intervals worse for fat loss. It just means your post-session eating plan needs to account for the mismatch between effort and duration — see how different run types compare for calorie burn for the pace-and-calorie side of this.

Next-Day Hunger After Very Long Runs

Most runners expect to be hungry the afternoon after a long run. Fewer expect to wake up still hungry the next morning. But after 90 minutes or more, that's exactly what happens — and it's not in your head.

Two things are going on. Deep glycogen depletion takes 24–48 hours to fully replenish, even with good eating, so the hormones that regulate your appetite stay elevated until your stores catch up. At the same time, your muscles are busy repairing themselves overnight, and that repair process adds a hunger signal of its own on top.

If you're in a calorie deficit, plan for a slightly higher intake the day after a long run, or get ahead of it with a protein-forward breakfast. Don't treat the extra hunger as a willpower failure. Suppressing it properly will only slow your recovery and set you up for a bigger overcorrection later in the week. Some of this comes down to individual variation too — it's worth knowing whether you're a high or low calorie compensator, since that shapes how strongly you'll feel this next-day effect.

Morning vs. Evening Runs — Does Timing Change How Hungry You Get?

Run the same 25 minutes twice — once first thing in the morning, once after a full day of eating — and you'll get two different hunger responses. Here's why.

A fasted morning run starts from glycogen stores that are already partly depleted from the overnight fast. Even a short, easy 25 minutes can trigger a mild hunger response the general duration rule wouldn't predict on its own. The same 25 minutes run in the evening, after a normal day of eating, starts from full glycogen stores — and typically produces no meaningful hunger signal at all.

The practical takeaway: if you train fasted in the morning, treat yourself as one tier up on the duration-spectrum table above. A 25-minute fasted run behaves more like a 30–60 minute session for hunger purposes.

How Hunger Escalates as Your Long Runs Build During a Training Cycle

Six weeks into a marathon build, a distance that felt easy in week two can suddenly leave you ravenous. That's not a broken metabolism. It's the duration-tier effect meeting a new personal threshold.

In my experience, this hits most recreational runners somewhere around weeks 8–12 of a build, once long runs cross roughly 18–22 km. I start warning runners about it around week 6, so it doesn't blindside them.

Recalibrate your fuelling and post-run eating every 3–4 weeks through a long build, rather than assuming last month's plan still fits. Treat the rising hunger as a training signal, not proof the deficit isn't working — for the structure behind progressive long runs, see progressive long-run structure.

Planning Your Eating Week Around Predictable Hunger Patterns

Everything above is only useful if you actually use it. Here's how: before the week starts, flag which sessions fall into which duration tier using the table near the top of this page, then decide what you'll eat after each one — before you're standing in the kitchen hungry and making decisions on the fly.


On-the-day, emotional decisions about post-run eating almost always overshoot. Deciding in advance removes the willpower problem completely — for specific food ideas at each tier, see what to actually eat after each session.

Hunger after running isn't random. It tracks duration, intensity, timing and where you are in your training cycle, all in fairly predictable ways. Once you know your own pattern across the four tiers above, you can plan around it instead of being surprised by it, run after run.

Some Other Pages You May Like

Home > Running for Weight Loss & Nutrition > Managing Hunger When Running > How Run Duration Changes Your Hunger: A Runner's Guide

***weightlossfooter.shtml***

  ☕ Buy Dom a Coffee