What is TDEE, and why does yours keep changing?

TDEE is short for total daily energy expenditure: every calorie your body spends across a full 24 hours. That includes the energy that keeps your heart beating and your organs running whether or not you leave the couch, plus everything layered on top of that baseline. Most people hear TDEE and picture a gym session, but formal exercise is usually the smallest slice of the total, not the biggest.

The number matters because it is the line your weight balances on. Eat consistently below it and you tend to lose weight. Eat consistently above it and you tend to gain. Eat close to it and your weight holds roughly steady. That is also why TDEE is called your maintenance calories, a term covered in more depth on the maintenance calories page.

Where TDEE gets confusing is that it is not a fixed number stamped on your body. It is an estimate of a moving target, built from several components that each shift on their own timeline, which is the whole reason a single formula struggles to keep up with a real person.

Four things add up to your daily total. Resting energy, the calories your body burns simply staying alive, is typically the largest single share for most people, since organs, circulation, and cell repair run around the clock regardless of what you do that day. Next is daily movement and non-exercise activity: walking, standing, fidgeting, chores, commuting, all the motion that happens outside a workout.

Structured exercise, the deliberate training sessions, adds its own slice on top, and it is usually a smaller share of the day than people assume, even for people who train seriously. Rounding out the total is the energy cost of digesting and processing the food you eat, a real but modest expenditure. Exactly how these four shares split varies widely from person to person, so it is more useful to think about the rank order than to memorize a percentage.

Because non-exercise movement can swing so much between a sedentary desk day and a day full of errands, two people with near-identical workouts can still land on meaningfully different TDEEs. This is part of why a device burn figure or a formula estimate is a starting point, not a verdict.

BMR, basal metabolic rate, is only the resting-energy piece from above: the calories your body needs to keep functioning if you stayed in bed all day. It is the floor. TDEE is the whole-day total, BMR plus daily movement, exercise, and food processing stacked on top of it.

TDEE is always higher than BMR, and the size of that gap is set almost entirely by how much you move. Someone with a sedentary job and little exercise has a TDEE fairly close to their BMR. Someone on their feet all day with regular training can push TDEE well above BMR. Knowing your BMR alone tells you almost nothing about your maintenance calories without also accounting for activity, which is covered in more detail on the maintenance calories page.

TDEE is not a number you calculate once and file away. Body weight itself moves it, since a larger body generally costs more energy to run than a smaller one. Body composition matters too: muscle and fat carry different metabolic costs, so two people at the same weight are not necessarily burning the same amount.

Day-to-day movement is one of the biggest swing factors. A week where you are walking more, standing more, or simply living a busier life raises TDEE even with no change to your training plan. Training volume itself matters directly too: a heavier block of workouts adds real energy cost on top of everything else.

Across a long fat-loss phase, TDEE tends to drift downward as body weight falls, since a smaller body generally costs less energy to maintain. Some further downward adjustment beyond what weight loss alone explains is a real and researched phenomenon, but its size varies a great deal between people and it is easy to overstate. It is one contributor among several, not the dominant explanation for a stalled plateau.

There are two fundamentally different ways to arrive at a TDEE number, and understanding the difference is the most useful thing on this page. The formula path starts from an equation: estimate resting energy needs from things like weight, height, age, and sex, then apply an activity multiplier that reflects how much you typically move. The result is a useful starting range, built entirely from population averages rather than your own body.

The adaptive path works the opposite direction. Instead of predicting your energy balance from formulas, it observes what actually happened: what you logged eating on days you actually logged, and how your body weight actually moved. Because day-to-day scale weight is noisy, that weight gets smoothed into a trend first. The system then compares your logged intake against the direction and rate of that trend to infer what your maintenance was likely to have been. When logging or weigh-in history is too thin to trust, it falls back to the formula estimate rather than presenting a shaky number as fact.

That 3,500 kcal per pound figure is a practical conversion applied to a smoothed, multi-week weight trend, not a claim that any single pound of scale movement equals exactly 3,500 calories of body fat. Water, glycogen, and digestive contents move the scale for reasons that have nothing to do with fat, which is exactly why the trend gets smoothed before the conversion is applied. The mechanics of why calories in and calories out do not map one-to-one onto the scale are covered on the calories in, calories out page.

Wellness Project runs both paths rather than picking one and hoping it is right. Every account gets a formula-based estimate from day one: a resting-needs calculation combined with an activity read from your last two weeks of steps, workouts, and runs, shown as a range rather than a single hard number. As you log meals and weigh in, an adaptive estimate builds alongside it, reading your actual intake against your actual weight trend.

The adaptive estimate only takes over once it has earned enough trust: it needs a real stretch of logged intake days, a real spread of weigh-ins across enough calendar time, and consistent enough logging overall. A day with no food log entry is treated as unknown, never assumed to be zero. A day you deliberately logged as zero calories, a genuine fast, counts as a real data point. Short of that bar, you see the formula estimate instead of a number built on thin data.

Whichever path produced your number, treat it as a hypothesis to test rather than a fact to defend. Hold a steady intake for a couple of weeks and watch what your actual weight trend does. If it moves the way you expected, the estimate is doing its job. If it stalls or moves the wrong way, the honest response is to adjust the target, not to assume you found the one true number and stop checking.

This is especially true right after a change in training, travel, or life circumstances, since any of those can shift the real number faster than a formula updates. For the practical side of turning your TDEE into a target for losing, gaining, or holding weight, see the maintenance calories page.

A calorie figure from a fitness watch or ring is a related signal, not a substitute for TDEE and not ground truth. Device-reported burn estimates come from their own models of your heart rate and movement, and they carry their own error, just like a formula does. Wellness Project reads device burn from Fitbit, Apple Health, Health Connect, Oura, and Withings when connected, and treats it as one input alongside logged intake and weight trend rather than the final word.

For more on how device numbers compare to logged intake and what the gap between them usually means, see the calories burned page.

If you just want a fast, formula-based estimate before you start logging anything, the free Mifflin-St Jeor calculator gives you a starting range in under a minute. It is the right tool for a quick number, and it lives on its own page rather than being repeated here.

Open the TDEE calculator to get a formula-based estimate now, or keep reading here for how that estimate gets sharper once you start logging.