Steady-State vs. Intervals vs. Tempo for Fat Loss A Head-to-Head Calorie Comparison
Intervals (repeated fast efforts with rests) and tempo running (a sustained, comfortably hard effort) burn within a few percent of each other, and both burn roughly 10 to 15% more calories per minute than steady-state running (easy, conversational pace), but tempo gives most runners the best balance of calorie burn and sustainability. Once you count afterburn, injury risk and extra recovery days, the differences between the three stay small and the recovery cost tips the balance. Below: how I define each run type, calories burned per session, the total including afterburn, the recovery and injury cost, which approach protects muscle best, why tempo earns its place, how to combine all three in a week, and the bottom line.Restructure your week around the wrong run and you can end up sore, tired and injured with very little extra fat loss to show for it. You've probably read plenty of articles claiming intervals torch more fat than easy running, so I'd rather you see the real numbers first, then decide what your legs and your schedule can actually support.
Defining Steady-State, Tempo, and Interval Running for This Comparison

Before the numbers mean anything, the definitions need to be locked down — running-specific ones, not generic cardio buckets. Much of the HIIT-vs-steady-state research is built on cycling or treadmill walk/sprint protocols, not running, which inflates the apparent per-session gap. Here's what each term means on the road or the treadmill:
| Run Type | Effort Descriptor | Conversation Test | Pace vs. 5K Pace | Heart Rate Zone |
|---|---|---|---|---|
| Steady-state (easy) | Conversational | Can hold a full conversation | 90-120 sec/mile slower | ~60-70% max heart rate (HR) |
| Tempo (threshold) | Comfortably hard | Short phrases only | 15-30 sec/mile slower | ~80-88% max HR |
| Intervals | Hard to very hard | Cannot hold a conversation | At or faster than 5K pace | ~90%+ max HR |
Keep these definitions in mind for everything that follows — the trick is comparing like with like, and most of the SERP doesn't. Every example on this page assumes a 5K pace of 8:00 per mile: steady-state at 10:00/mile, tempo at 8:20/mile, and interval reps at 7:30/mile.
Calories Burned During Each Run Type: Running-Specific Numbers
Here's the in-session picture, for a 30-minute run at two body weights, using running-specific MET values (Metabolic Equivalent of Task — a standard measure of exercise intensity relative to rest).| Run Type | MET | Cal/min (70 kg) | 30-min Total (70 kg) | Cal/min (85 kg) | 30-min Total (85 kg) |
|---|---|---|---|---|---|
| Steady-state (10:00/mile) | 9.8 | ~12.0 cal | ~343 cal | ~14.6 cal | ~417 cal |
| Tempo (8:20/mile) | 11.2 | ~13.7 cal | ~392 cal | ~16.7 cal | ~476 cal |
| Intervals (session average) | 10.9 | ~13.4 cal | ~382 cal | ~16.2 cal | ~463 cal |
MET values come from the Compendium of Physical Activities running entries (for example 9.8 at 6 mph), interpolated between listed speeds for the paces shown. Intervals: 1,000 m reps at 7:30/mile (MET 11.8) with 400 m recovery jogs at 11:00/mile (MET 9.3), a session average of MET 10.9. Calories/min = MET x 3.5 x bodyweight(kg) / 200. These are estimates: results vary with running economy and terrain, and scale with body weight.
Here's the finding worth taking away: the in-session gap between steady-state and tempo is about 14% — a real step for roughly 90 extra seconds of speed per mile. The interval session actually lands about 3% below tempo, because the recovery jogs pull the session average down, and only about 11% above steady-state. The "intervals crush everything" story mostly doesn't show up in the in-session calories.
Total Calorie Impact Including Afterburn: The Real Head-to-Head Table
Add excess post-exercise oxygen consumption (EPOC) — the afterburn effect covered in full on how much afterburn each run type actually produces — and you get the comparison that actually matters for fat loss: the true 24-hour calorie cost of each session, not just what the watch shows mid-run.| Run Type | Calories During (70 kg) | EPOC (afterburn) | Overall |
|---|---|---|---|
| Steady-state | ~343 cal | Small | ~343 cal plus a small extra |
| Tempo | ~392 cal | Small to modest | ~392 cal plus a little more |
| Intervals | ~382 cal | Modest | ~382 cal plus a modest extra |
EPOC varies with intensity, duration and training status, so I haven't put exact figures on it; it rises with intensity but stays small next to the run itself. Calorie figures are for a 70 kg runner. See the EPOC page for the full breakdown by session type.
This table is running-specific, so it's worth being precise about what it shows: EPOC is genuine, but easy to overstate. An interval session burning roughly 380 kilocalories (kcal, usually just called calories), as in the table above, adds a modest bonus on top — nothing like the claims some fitness marketing makes. Real. Modest. Not the multiplier it's sold as.
The Recovery and Injury Cost the Calorie Table Doesn't Show

Calorie efficiency means nothing if a workout forces a rest day that displaces another session — and this is where the binary HIIT-vs-steady argument falls apart for anyone training regularly. Here are the recovery windows I actually plan around: intervals need 48 or more hours before your legs are ready for another hard effort; tempo runs need 24 to 36 hours; steady-state runs need only 12 to 24.
Think of it as a weekly calorie budget question, not a per-session one. Three steady-state sessions can produce comparable — sometimes better — total weekly calorie expenditure than one interval session plus two easy days, once you account for the extra rest the interval session forces. In over 15 years of building fat-loss plans, I've seen more runners stall by replacing all their runs with intervals than by keeping a structured mix. The per-session efficiency gain evaporates the moment extra rest days are required to recover from it.
Here's a pattern I see constantly: a runner does 5 x 1,000m repeats on Tuesday, feeling fantastic about the session. By Friday, they're still not running well — tired legs, flat pace, low motivation — and that missed or half-hearted Friday run costs more calories than the Tuesday interval session ever gained. Interval-heavy programmes produce an expected calorie spike in week one; by week three, total weekly output often drops as recovery debt piles up.
Which Approach Best Preserves Muscle While Losing Fat?
Briefly, because this deserves a straight answer without turning into its own article: the evidence doesn't clearly favour intervals for preserving lean mass. Direct comparisons of high-intensity intervals against moderate continuous exercise, including a 2017 meta-analysis by Keating and colleagues in Obesity Reviews, found no significant difference in fat-mass loss, and lean-mass data are thin. Worth knowing the context, too — most of this research was done on sedentary or overweight non-runners, not on runners already training regularly.The coaching caveat matters more than the headline: at a moderate deficit (250 to 400 kcal/day) with adequate protein intake, any muscle-retention advantage of intervals is likely to be small. If tempo suits your recovery capacity better than intervals, you're not sacrificing much muscle by choosing it.
Tempo Running: A Strong Fat-Loss Option

Here's the coaching call I'll happily own: for many intermediate fat-loss runners, tempo is the best workout type on the table, and it's easy to think of tempo purely as race preparation rather than as a fat-loss tool in its own right.
The case for it is straightforward. Calorie burn sits materially higher than easy running — roughly 14% per the table above, and level with an interval session. Injury risk sits materially lower than intervals — no lactate spike, no all-out mechanical loading. Recovery cost is compatible with running four or more days a week. And the pace is sustainable for 20 to 40 minutes at a stretch, which intervals simply aren't for most runners.
Put those four things together — decent calorie return, low injury cost, fast recovery, high weekly frequency — and tempo running does more for a sustained fat-loss plan than its reputation as "just race training" suggests.
How to Combine All Three in a Week for Fat Loss
Here's the structure I recommend for a runner training four to five days a week, built around the calorie-budget and recovery-capacity logic from the sections above, not lifted from a generic template:| Day | Session | Duration | Approx. Calories (70 kg) | Recovery Status |
|---|---|---|---|---|
| Monday | Steady-state | 30-35 min | ~343-400 cal | Fully recovered by Tuesday |
| Tuesday | Rest or cross-train | - | - | Recovery day |
| Wednesday | Tempo | 30 min | ~392 cal | 24-36 hrs before next hard effort |
| Thursday | Steady-state | 30 min | ~343 cal | Fully recovered by Friday |
| Friday | Rest | - | - | Recovery day before intervals |
| Saturday | Intervals | 30 min (session average) | ~382 cal | 48+ hrs before next hard effort |
| Sunday | Steady-state (or rest) | 30-40 min | ~343-457 cal | Flexible |
One interval session, one tempo session, and two to three steady-state sessions — that's the fat-loss structure I'd recommend as a starting point. Steady-state days aren't filler here; they accumulate volume without driving up your recovery cost, which is exactly why they earn three slots in this week and intervals earn one. Treat this as a coaching starting point, not a fixed prescription — your own recovery capacity and current fitness will shift the balance.
The Bottom Line
On calories alone, intervals do not beat tempo — the in-session claim made for high-intensity interval training (HIIT) doesn't survive once the recovery jogs are counted, and the two land within a few percent of each other. The afterburn bonus is real but modest, and the recovery cost of an interval-heavy week can quietly erase any advantage by week three. For most runners training three or more days a week, a mix anchored by tempo and steady-state, with one interval session on top, beats an all-intervals approach on total weekly calorie expenditure — and it's the one you'll actually stick to. See choosing the right running pace for fat loss for the full pace guidance, and the fat-burning zone and why intensity matters for the physiology behind why harder running wins on calories at all. For the deficit fundamentals underneath this whole comparison, see building your weekly calorie deficit through running.Frequently Asked Questions
Does tempo running burn more fat than easy steady-state running?
Yes, both per minute and per session - roughly 14% more calories at matched duration (about 392 vs. 343 kcal at 70 kg), plus modestly higher EPOC. Its real advantage over intervals is that it's sustainable at a higher weekly frequency.
Is HIIT really better than steady-state running for fat loss, or is it a myth?
Intervals burn about 11% more than easy running per session (382 vs. 343 kcal at 70 kg) and slightly less than tempo, and the advantage is modest once you factor in recovery cost and total weekly training volume. For runners already training four or more days a week, the binary claim oversimplifies things.
Does interval training put you at higher injury risk when the goal is fat loss?
Yes, relative to steady-state and tempo running. Higher mechanical load per session and longer recovery windows make intervals a real trade-off if you stack them too frequently.
Is steady-state running a waste of time compared to intervals for fat loss?
No. Steady-state days build calorie volume without a heavy recovery cost, which makes them a structural necessity in any multi-day fat-loss plan, not filler.
How do I choose between these three approaches if I'm short on time?
Calories are about the same for tempo and intervals (roughly 392 vs. 382 kcal at 70 kg), so choose by recovery cost. Training once or twice a week, either works. Training three or more days a week, tempo is the better efficiency-to-recovery-cost trade-off.
Some Other Pages You May Like
About the author
Dominique de Rooij (Dom)
Advanced Running Coach certified by Athletics Australia with 20 years of writing about running and over a decade coaching runners — from first-timers to marathoners. Dom's beginner programs have guided thousands of runners and been praised above plans from Jeff Galloway, Hal Higdon, and Runner's World. Now over 50, Dom still loves trail running, parkrun, and the coffee after.

Free beginner guide • From Coach Dom
Start Running This Week, Even If Your Week Is Already Full
Most beginners don't quit for lack of motivation. They quit because their plan doesn't fit their life. The 3-Run Busy Week Starter plans your first week around the week you actually have.
- Find 3 run slots you can actually keep
- The talk test: the simple way to stop running too fast
- Your complete week 1 plan: 3 run/walk sessions, about 20 minutes each
I'll email you a link to confirm your address, then send the guide plus a short email every few days to help you through week 1. Unsubscribe any time. Privacy policy.
What's New?
-
Cut 90 Seconds Off Your 1.5 Mile Run for the Army Test
Cutting 90 seconds off a 1.5 mile run in 3-4 weeks for the Army test: Dom breaks down realistic pacing to reduce 10:32 toward sub-9:00 for Paras selection. -
Training for a 1.5 Mile Run - How to Qualify For Your Test
Coach Dom's 3-step plan for 1.5 mile run training: build aerobic base, add strides, then tempo and pace work to hit your test time. -
Improve Your 1.5 Mile Running Time to 10:30: Shin Splints
From 12:59 to 10:30 for 1.5 miles: Coach Dom's shin-splint fix and training plan to improve your running time in 2-3 months.