It was 108 degrees at 10 AM on a Tuesday in July, and I was standing in my driveway in South Austin, holding a resistance band, wondering if I had finally lost my mind. Pixel was inside, sprawled on the tile floor, looking at me through the window with the expression dogs reserve for humans making poor life choices. I was not making a poor life choice. I was collecting data. Because heat changes everything. Not just your comfort. Not just your hydration. Your actual body composition metrics. Your BMI. Your body fat percentage. Your calorie burn. Your heart rate zones. All of it shifts when the ambient temperature climbs above 95 degrees, and if you are tracking your fitness data without accounting for heat, you are building a spreadsheet of lies.
I learned this the hard way. In March, when Austin was a pleasant 72 degrees, my morning weigh-in was 184.2 pounds. My body fat estimate from the caliper method was 16.8%. My resting heart rate was 58 bpm. I had a baseline. I trusted it. Then July hit. And in the span of six weeks, my weight dropped to 179.4 pounds, my caliper reading jumped to 18.2%, and my resting heart rate climbed to 64 bpm. I did not gain fat. I did not lose muscle. I was just hot. And my metrics were lying to me because I was not accounting for the heat.
Heat-induced dehydration drops your body weight by 2-4 pounds in a single workout. That is water. Not fat. Not muscle. Water. But if you weigh yourself after an outdoor summer workout and record that number as your "true" weight, you are lying to yourself. I did this for three weeks before I caught it. I thought I was making progress. I was just dehydrated. The scale said 179.4. My hydrated weight was 183.1. That is a 3.7-pound difference, entirely water, entirely meaningless for body composition tracking.
I pulled up the BMI Calculator with Chart and entered my March weight and my July weight, same height, same everything. The tool plotted both points and showed me a 1.2-point BMI swing — from 26.1 to 25.4 — that had nothing to do with body composition and everything to do with water loss. That is not progress. That is thermodynamics. That is your body shedding water to cool itself in 108-degree heat. And if you are celebrating that number, you are celebrating dehydration. Which is not a fitness goal. It is a medical emergency waiting to happen.
But here is where it gets interesting. Heat also changes your calorie burn. Not in the way you think. Yes, you burn more calories in the heat because your body is working harder to thermoregulate. But the increase is modest — roughly 5-10% above baseline for the same activity. The real change is in your heart rate. At 100 degrees, your heart rate for a given effort is 10-15 bpm higher than at 70 degrees. That means your "easy" run in March becomes a "moderate" run in July, even at the same pace. Your zones shift. Your training intensity shifts. And if you are using heart rate zones to guide your workouts, you are either overtraining or undertraining, depending on which direction you are wrong.
I ran the same 5-mile loop three times: once at 72 degrees, once at 92 degrees, once at 105 degrees. Same pace. Same route. Same time of day. My average heart rate was 142, 156, and 168 respectively. At 105 degrees, my "easy" run was happening at my lactate threshold. I was not building aerobic base. I was accumulating fatigue. And I was doing it because my watch told me I was in "Zone 2" based on my March max heart rate. My watch was wrong. The heat was right. And my body was paying the price.
The Calorie Needs Calculator has a heat adjustment feature I had been ignoring. I entered my weight, my activity level, and the average daily temperature. It bumped my maintenance calories up by 180 per day for July. Not because I was training harder. Because my body was working harder just to exist in Austin's outdoor sauna. That 180 calories is the difference between maintaining and slowly losing. Between fueling and underfueling. Between recovery and breakdown. I had been eating at my March maintenance level all summer and wondering why I was tired and cranky. Because I was underfed. Because my calculator had a heat adjustment and I was too stubborn to use it.
The body fat estimators are even worse in heat. Bioelectrical impedance — the method used by most smart scales — relies on water content to estimate body fat. In the heat, your extracellular water drops. Your scale reads higher body fat. Not because you gained fat. Because you lost water. My scale told me I went from 16.8% to 18.2% in six weeks. My DEXA scan — which I paid $85 for because I am a nerd with a spreadsheet problem — showed 17.1%. The scale was wrong by a full percentage point because of dehydration. A full percentage point is the difference between "lean" and "average" in most fitness apps. That is not a rounding error. That is a lie dressed as data. And I almost changed my entire training plan because of it.
The Body Fat Estimator helped me correct for this. I entered my scale reading, my hydration status, and the time of day. It applied a correction factor based on temperature and hydration and gave me an adjusted estimate: 17.0%. Close enough to the DEXA to make me trust it. Close enough to stop me from panic-cutting calories because my scale decided I was getting fat in July. I was not getting fat. I was getting dehydrated. There is a difference. And if you do not know the difference, your metrics will lead you astray.
So here is what I do now. I weigh myself first thing in the morning, before coffee, before Pixel's walk, before the heat has had a chance to pull water from my cells. I record the temperature alongside my weight in my spreadsheet. I adjust my heart rate zones by 5 bpm for every 10 degrees above 75 degrees. I add 150-200 calories to my daily target in July and August. And I do not trust any body fat reading from a scale between June and September unless I have been properly hydrated for 24 hours, which — let's be honest — rarely happens in Austin in summer. Proper hydration in 108-degree heat requires drinking water constantly, which means you are peeing constantly, which means you are not sleeping well. It is a trade-off. And the trade-off is that your metrics are garbage for four months of the year.
Your data is only as good as your context. And in a 110-degree summer, the context is: you are hot, you are dehydrated, and your metrics are lying to you. Adjust for it. Or spend September wondering why your "progress" disappeared the moment the temperature dropped back to 80 degrees and you rehydrated. Because that is what happens. The weight comes back. The body fat percentage drops. The heart rate zones normalize. And you realize that three months of tracking was mostly tracking water loss. Not fitness gain. Not fat loss. Water loss. And water comes back.
What is your real BMI in August? Not your dehydrated driveway number. The one that accounts for the fact that you are living in a convection oven. Find it. Track it. And stop letting the weather fake you out. Because Austin summer is not a fitness challenge. It is a thermoregulation challenge. And your metrics need to know the difference.
How much water do you lose on a summer run? Have you ever checked?
Heat-induced dehydration can drop body weight 2-4 pounds in a single workout. I saw a 3.7-pound swing between my dehydrated post-run weight (179.4) and hydrated morning weight (183.1). That is water, not fat.
Yes. Add 5 bpm to your zone thresholds for every 10 degrees above 75°F. At 105°F, my "easy" run heart rate was identical to my lactate threshold heart rate at 72°F. Training by feel or perceived exertion is more reliable than watch zones in heat.
Only modestly — about 5-10% above baseline for the same activity. The bigger issue is that your heart rate is elevated for thermoregulation, not exertion. My Calorie Needs Calculator adds 180 calories per day for July heat as a rough adjustment.
