The 4-Hour Recovery Protocol After a Hot Long Run

You just finished 18 miles in August heat. Your legs are cooked. Your shirt weighs twice what it did at the start. Your watch is buzzing with stats you're too tired to read.

You know you should eat something. Drink something. But how much? What? When?

Most recovery advice stops at "drink water and eat carbs within 30 minutes." That's not wrong — it's just useless if you don't know how much fluid you lost, how depleted your glycogen is, or how far behind your electrolytes have fallen.

Your watch already tracked most of what you need. Here's how to turn that data into a recovery protocol that actually works.

Why Hot Long Runs Wreck You Differently

A 20-miler in 55°F is hard. A 20-miler in 85°F is a different event entirely.

In the heat, three things compound to make recovery harder:

Your sweat rate spikes. Most runners lose 1.0–1.5 litres per hour in moderate conditions. In summer heat, that can climb to 1.5–2.5 litres per hour — sometimes more. Even if you drank at every aid station, you almost certainly finished with a significant fluid deficit.

Your gut shuts down. When core temperature rises, blood diverts from your digestive system to your skin for cooling. That's why your stomach feels off after hot runs — and why you can't just slam food and fluid the moment you stop. Your gut needs 15–30 minutes of cooling before it can absorb efficiently again.

Your glycogen burn accelerates. Heat increases your carbohydrate oxidation rate. You burned through more glycogen per mile than you would have in cooler conditions, which means your stores are more depleted than your distance alone would suggest.

This is why the same recovery routine that works in April fails in August. The deficit is bigger, the absorption capacity is lower, and the timeline matters more.

Step 1: Read Your Watch Before You Do Anything Else

Before you reach for a drink, open your watch or phone app and note three numbers:

Total calories burned. Your Garmin or Apple Watch estimates this from heart rate, duration, body weight, and workout type. It's not perfect — wearable calorie estimates can be off by 15–25% — but it's a useful starting point for your carbohydrate target.

Estimated sweat loss (if available). Garmin devices with the Physio TrueUp feature now estimate sweat loss per workout. Apple Watch doesn't show this directly, but you can calculate it: weigh yourself before and after your run (in minimal clothing). Every kilogram lost equals roughly one litre of sweat. Add back whatever you drank during the run.

Average heart rate and duration. A long run where your average HR was 155 for 2.5 hours depleted you differently than one at 140 for 3 hours. Higher heart rate means higher carbohydrate oxidation — more glycogen burned, more fuel to replace.

These three data points set your personal recovery targets. Without them, you're guessing.

Step 2: The First 30 Minutes — Cool First, Then Sip

The instinct is to immediately drink a litre of water and eat a recovery bar. Resist it.

Minutes 0–15: Cool down. Walk for 5 minutes. Find shade. If you can, pour cold water over your wrists and neck. Your gut is still in "survival mode" — dumping fluid into it now means nausea, not absorption. This isn't wasted time. It's making the next 4 hours more effective.

Minutes 15–30: Start sipping. Begin with 300–500ml of fluid with electrolytes — not plain water. After a hot long run, you've lost significant sodium (typically 500–1,500mg per litre of sweat). Plain water dilutes your remaining sodium further, which can make you feel worse, not better.

A good starting target: 500ml of an electrolyte drink with at least 500mg sodium in this first window.

Eat something small. This isn't the main recovery meal — it's a bridge. A banana, a handful of pretzels, or a recovery drink with 20–30g of carbs. The goal is to restart digestion without overwhelming a gut that's still recovering from heat stress.

Step 3: Hours 1–2 — The Rehydration Window

This is where your watch data becomes your protocol.

Fluid target: 150% of what you lost.

The science is clear on this: you need to drink roughly 150% of your fluid deficit over the next several hours — not 100%. Why? Because your body continues to lose fluid through urine, breathing, and residual sweating even after you stop running.

Here's the maths. If your pre-to-post-run weight drop was 2kg (after accounting for fluid consumed during the run), you lost roughly 2 litres of sweat. Your rehydration target is 3 litres total — but spread across the full 4-hour window, not chugged at once.

In hours 1–2, aim for roughly 40% of that total. So for a 2-litre deficit: about 1.2 litres of fluid, sipped steadily — roughly 300ml every 30 minutes.

Electrolyte target: match what you lost.

The average runner loses 800–1,200mg of sodium per litre of sweat. If you lost 2 litres, that's 1,600–2,400mg of sodium to replace. Your first 500ml drink covered some of this. The rest should come from a combination of electrolyte drinks, salty foods, and your recovery meal.

Don't worry about precision here. The point is magnitude: you need grams of sodium, not milligrams. A single electrolyte tablet with 300mg isn't going to cut it after a hot 20-miler.

Carbohydrate target: 1.0–1.2g per kg of body weight.

Research consistently shows that consuming 1.0–1.2g of carbs per kg of body weight within 2 hours of finishing maximises glycogen resynthesis. For a 70kg runner, that's 70–84g of carbs — roughly equivalent to a large bowl of rice with a banana, or two slices of toast with jam and a recovery drink.

If your watch showed a higher-than-usual calorie burn (because of the heat), push toward the upper end of this range. Your glycogen deficit is deeper than a cooler run of the same distance.

Step 4: Hours 2–4 — The Normalisation Phase

By hour 2, your gut should be functioning closer to normal. This is when your main recovery meal does its work.

A real meal, not supplements. Recovery shakes are fine for the first hour when your appetite is suppressed. By hour 2–3, eat actual food. A plate with a palm-sized portion of protein (chicken, eggs, tofu), a generous serving of carbs (rice, pasta, potatoes), and some vegetables covers your remaining macronutrient needs.

Keep sipping fluid. Continue drinking the remaining 60% of your rehydration target. If you started with a 3-litre target, you should be working through the final 1.8 litres during hours 2–4. Don't force it — steady sipping is more effective than large volumes at once.

Check your urine. By hour 3–4, you should be urinating. If your urine is still dark amber, you're behind on rehydration. If it's pale yellow, you're on track. If it's completely clear, you may be overdoing fluid and diluting electrolytes — add more sodium.

The Numbers Most People Get Wrong

"I drank during my run so I don't need to worry about recovery hydration." You almost certainly didn't keep up with your losses. Studies show most runners replace only 30–50% of fluid lost during exercise, even when drinks are readily available. The deficit carries forward.

"I'll just drink to thirst." Thirst is a lagging indicator. By the time you feel thirsty, you're already 1–2% dehydrated. After a hot long run, thirst can take 30–60 minutes to fully register — and by then, you've lost the most effective absorption window.

"My watch says I burned 2,800 calories so I need to eat 2,800 calories." No. Wearable calorie estimates include your basal metabolic rate and are often inflated by 15–25%. Focus on the carbohydrate and protein targets above, not on matching a calorie number. Eat to replace glycogen and repair muscle — not to zero out a calorie count.

Why This Gets Easier With Data

Every long run is a data point. If you track your pre/post weight, fluid intake, and conditions, you start building a picture of your personal sweat rate across different temperatures and intensities.

After 3–4 long runs with data, you'll know: "In 80°F heat at marathon pace, I lose about 1.6 litres per hour and need roughly 900mg of sodium per litre." That's your formula. It makes recovery predictable instead of reactive.

Your Garmin or Apple Watch already captures the intensity, duration, and environmental data. What's missing is the translation layer — the part that converts those numbers into "drink this much, eat this much, in this order."

That's exactly what Sweatr does. It takes your wearable data — sweat estimates, calorie burn, heart rate, training load — and builds a personalised recovery protocol after every session. No spreadsheets, no guesswork, no generic advice.

Your Protocol at a Glance

| Window | Fluid | Food | Electrolytes | |--------|-------|------|-------------| | 0–15 min | Nothing — cool down first | Nothing | Nothing | | 15–30 min | 300–500ml with electrolytes | Small snack (20–30g carbs) | 500mg sodium in drink | | 30 min–2 hr | 300ml every 30 min | Recovery drink or light food | Continue electrolyte drink | | 2–4 hr | Sip to remaining target | Full recovery meal | Salty food, electrolyte top-up |

Adjust the fluid column based on your actual sweat loss. Adjust the carb column based on your watch's calorie estimate and your body weight. Adjust sodium based on how salty your skin tastes after the run (yes, that's a real signal).

Make Your Next Long Run's Recovery Automatic

You ran the hard miles. Your watch tracked the data. The only piece missing is the plan that connects the two.

Sweatr reads your Apple Watch or Garmin data after every workout and builds your personalised recovery targets — fluid, carbs, sodium, timing. No manual calculations. No guessing how much you lost. Just open the app, and your protocol is waiting.

Your summer long runs are building the dataset for your fall race-day plan. Every recovery done right is a rehearsal for October.