Do you still burn calories on a rest day?

I get asked some version of this a lot, usually from someone staring at their tracker on a day they skipped the gym: "did I actually burn anything today?" The honest answer is that a rest day is not a zero-calorie day — it's a day where one specific slice of your burn (structured exercise) goes to roughly zero, while the other three keep running on autopilot.

What's actually still burning while you rest

Total daily energy expenditure (TDEE) is made up of four pieces, and only one of them depends on you working out:

• Basal metabolic rate (BMR) — the calories spent on breathing, circulation, cell repair, and keeping your organs running. This is the largest piece for almost everyone, and it runs 24/7 whether you train or not. Mayo Clinic's metabolism guide notes that your basal rate is largely fixed by things like age, sex, and muscle mass — it isn't something a rest day pauses.
• Thermic effect of food (TEF) — digesting and absorbing what you eat costs calories too, roughly 10% of what you take in. Eat the same lunch on a rest day as a training day, and TEF is the same.
• Non-exercise activity thermogenesis (NEAT) — walking to the kitchen, fidgeting, standing at your desk, carrying groceries. I wrote about this in more detail in NEAT vs. exercise calories; the short version is that NEAT often outweighs a single workout, and it doesn't disappear on a rest day — if anything, some people's NEAT barely changes, because walking around the house or office was never "the workout" in the first place.
• Exercise activity thermogenesis (EAT) — the one slice that genuinely drops to near zero on a true rest day. If a hard run usually costs you 400–500 calories, that's the piece you're not spending today.

So when someone skips leg day and logs "0 calories burned," that number is wrong — it's just the EAT column at zero, not the whole day.

A rough number, so this isn't just theory

Cleveland Clinic's guide on calories burned in a day puts a typical resting metabolism somewhere around 1,300–2,000+ calories daily on its own, before any deliberate activity, and that figure climbs with body size and muscle mass. Add ordinary movement — showering, cooking, a walk to get coffee — and most people land well above that baseline even on a day with no structured workout at all. The exact number depends heavily on your height, weight, age, and sex, which is why a generic "how many calories does resting burn" answer is only ever a starting point, not your actual number.

Worth saying plainly, though: wearables and apps that show a live "calories burned" figure on a rest day are estimating, not measuring. They're reasonably good at BMR (it's predictable) and rougher at guessing your incidental movement. If your watch says you burned exactly 1,842 calories lying on the couch, treat that as a decent ballpark, not a lab result.

Should you eat less on a rest day?

This is where people usually overcorrect. Because BMR barely changes day to day, your maintenance number — the calories that keep your weight stable over time — doesn't swing much just because you skipped a workout. The piece that actually drops on a rest day is EAT, which for most non-athletes is a smaller slice of the total than people assume (see the NEAT piece above for why).

If you're actively trying to lose weight, the practical move isn't "eat way less on rest days" — it's keeping your average intake below your average TDEE across the week. One rest day eating close to your usual total won't undo progress; it's the accumulated weekly gap that matters, which I've gone into more in calorie deficit to lose weight. Athletes training at a high volume are a different case — they sometimes do deliberately eat less on true recovery days — but that's a periodization decision for people already tracking closely, not a rule for someone who lifts three times a week.

Why this trips people up in the first place

A lot of this confusion comes from conflating "exercise calories" with "all calories," which is an easy mistake when your tracker's main number of the day is the workout. I think it's also partly a framing problem: calling it a "rest day" makes it sound like the body is resting too, when really it's your training schedule that's resting, not your metabolism. Your heart is still beating the same number of times either way. It's a different confusion than the one covered in why fitness trackers overestimate calories burned, which is about the workout number itself being inflated, not about what the rest of the day is doing.

This is exactly the kind of day where a photo-based log earns its keep — logging what you actually ate on a rest day, without assuming it "doesn't count" because you didn't train, keeps your weekly numbers honest. Bocco logs a meal from a photo in seconds and syncs your Apple Health activity, so a rest day still shows a real, specific total instead of a guess.