Your Fueling Plan Was Built at Sea Level — Here's What Altitude Does to It

You spent months dialling in your fueling plan. You tested gels on long runs, practised your hydration timing, nailed your carb targets. Then you travel to a race at 1,800 metres and everything you tested stops working.

Your heart rate is higher at the same pace. You're breathing harder. Your stomach feels off. You're not hungry. And somewhere around mile 16, the wheels come off — even though you followed the plan perfectly.

The plan was fine. It was built for the wrong atmosphere.

Altitude changes the physics of fueling in ways that most nutrition guides ignore completely. The air is thinner, drier, and your body compensates by burning more carbs, losing more water through every breath, and suppressing the appetite signals that normally remind you to eat.

This is what changes above 1,500 metres and how to adjust before race day.

You burn through carbs faster

At sea level, your body uses a comfortable mix of fat and carbohydrate to fuel endurance exercise. As elevation increases, that ratio shifts hard toward carbohydrate.

The reason is oxygen efficiency. Carbohydrate produces more ATP per litre of oxygen consumed than fat does. When oxygen is scarce — which it is at altitude — your metabolism leans on the fuel source that squeezes the most energy from each breath. Research shows carbohydrate oxidation increases by 10–20% at moderate altitude (1,500–3,000 metres) compared to the same intensity at sea level.

What that means in practice: the 70 grams of carbs per hour that sustained you through your long runs at home may only cover 80–90% of what you need at altitude. Your glycogen stores deplete faster, and the bonk arrives sooner.

What to adjust:

• Increase your hourly carb target by 10–15%. If you normally aim for 60g/hr, plan for 65–70g. If you aim for 80g/hr, push to 88–92g.
• Start fueling earlier in the race. Take your first gel 5–10 minutes sooner than you would at sea level. The carb debt accumulates faster at altitude, and playing catch-up above 1,500m is harder than at sea level.
• If you haven't trained your gut to handle the higher load, use liquid carbs (drink mix) to supplement gels rather than adding more solid fuel.

You lose water through breathing — not just sweating

Most hydration plans focus on sweat. At altitude, you have a second significant source of fluid loss that your sweat rate test never captured: respiratory water loss.

At elevation, the air is drier and you breathe faster. Every exhale carries water vapour out of your body. At moderate altitude, respiratory water loss can double compared to sea level — adding 500ml or more of fluid loss over a three-hour race that isn't showing up as sweat on your skin.

On top of that, your body triggers altitude diuresis in the first 24–48 hours at elevation. This is a natural response: your kidneys increase urine output to reduce blood plasma volume, concentrating oxygen-carrying red blood cells. Useful for acclimatisation. Bad for your fluid balance if you don't compensate.

The combination means you can arrive at the start line already dehydrated — even if you followed the same pre-race hydration routine that worked at sea level.

What to adjust:

• Increase daily fluid intake by 500–1,000ml starting 48 hours before the race, beyond your normal pre-race hydration.
• During the race, add 100–200ml per hour on top of your sea-level plan. If you normally drink 500ml/hr, aim for 600–700ml.
• Don't wait for thirst. At altitude, the dry air and increased breathing mask thirst cues. Your body may be losing fluid faster than your brain registers.
• Bring electrolytes for your non-training hours too. The altitude diuresis flushes sodium along with the extra urine. Sipping plain water without electrolytes during the 48 hours before the race can make things worse.

Your appetite drops — at the worst possible time

Altitude suppresses appetite. Above 2,000 metres, leptin levels increase and sympathetic nervous system activity ramps up, reducing hunger signals. Many athletes arrive at altitude training camps or destination races and simply eat less because nothing sounds good.

The problem: your energy expenditure at altitude is higher, not lower. Basal metabolic rate increases 10–20% in the first few days at elevation as your body works harder to maintain oxygen delivery. Add training on top of that and you can easily fall into a 500–1,000 calorie daily deficit without realising it.

A deficit in the days before a race means you arrive with partially depleted glycogen stores. No amount of race-day fueling can fix what you failed to eat on Tuesday and Wednesday.

What to adjust:

• Eat by the clock, not by hunger. Set reminders for meals and snacks every 3–4 hours whether you feel hungry or not.
• Prioritise carbohydrate-dense foods that are easy to eat without appetite: rice, bread, pasta, fruit juice, smoothies, cereal. Skip high-fibre and high-fat meals that fill you up faster.
• If solid food feels impossible, liquid calories work. Recovery shakes, fruit smoothies, and carbohydrate drinks count toward your daily intake. Getting 200g of carbs from liquids is better than skipping meals.
• Begin carb loading 48 hours before the race at the same 8–12g per kg of body weight target you would use at sea level — but pay closer attention to actually hitting the number, because your appetite will fight you.

Your heart rate lies (a little)

If you use heart rate to pace your effort or monitor intensity, altitude will throw your data off. Resting heart rate typically increases by 10–20% at moderate altitude. At the same running pace, your exercising heart rate will be 5–15 beats per minute higher than at sea level.

This matters for fueling because many athletes and apps use heart rate zones to estimate calorie burn and set fueling targets. At altitude, the elevated heart rate inflates those estimates. Your watch may tell you that you burned 3,200 calories when the real number is closer to 2,800.

Conversely, if you use heart rate to determine intensity and pace by feel, you may slow down to keep your heart rate in its usual zone — which means you're actually running at a lower intensity than you think, burning fewer total calories but still in a higher carb-oxidation state.

What to adjust:

• Don't recalibrate your heart rate zones for a one-off altitude race. Accept that the numbers will read high and focus on perceived effort instead.
• If your fueling plan is pegged to heart rate zones, shift to a time-based fueling schedule at altitude: specific grams of carbs every 20–30 minutes regardless of what your watch says.
• For training camps at altitude lasting more than two weeks, let your watch establish a new baseline before trusting zone-based metrics.

The acclimatisation timeline for nutrition

How early you arrive at altitude changes what you need to adjust.

Arriving race morning or the night before (no acclimatisation): You'll race on acute altitude exposure. Heart rate will be highest, respiratory rate will be highest, and your body hasn't adapted at all. This is actually the worst scenario for fueling: maximum carb burn increase, maximum respiratory water loss, maximum appetite suppression from travel plus altitude.

• Use your sea-level fueling plan but increase carbs by 15% and fluids by 200ml/hr.
• Pre-load sodium: 1,000–1,500mg with 500ml of water 2–3 hours before the start.
• Accept that the race will feel harder than your fitness suggests. Don't chase pace.

Arriving 2–3 days early: You've passed through the initial diuresis phase. Your body has started to stabilise fluid balance. Appetite may still be reduced but the worst of the suppression has passed.

• Hydrate aggressively on days 1 and 2, then return to race-prep hydration levels on day 3.
• Eat to your carb targets even if appetite is low.
• Increase race-day carbs by 10% and fluids by 100–150ml/hr above sea-level targets.

Training at altitude for 2+ weeks: Full acclimatisation takes 3–4 weeks, but after 10–14 days your body has made significant adaptations. Red blood cell production is increasing (which demands more iron), resting heart rate is normalising, and your fluid balance has stabilised.

• Iron intake matters now. Eat iron-rich foods (red meat, spinach, lentils) or consider a supplement if you're training at altitude for more than two weeks. Your body is making more haemoglobin and needs the raw materials.
• Carb needs will still be slightly elevated but less dramatically than during acute exposure.
• Your sea-level fueling plan is closer to correct, with a 5–10% carb increase.

What your watch data tells you at altitude

Your wearable data at altitude isn't wrong — it's measuring a different physiological state. Use it as a signal, not a prescription.

Elevated resting heart rate: Normal at altitude. Don't interpret this as under-recovery and reduce training volume unless it persists beyond the first week. Do use it as a reminder that your body is working harder and needs more fuel.

Suppressed HRV: Expected in the first 3–5 days at altitude. Your autonomic nervous system is adapting. Add 10–15% to your daily carb intake on suppressed-HRV days, same as you would at sea level.

Higher estimated calorie burn: Partly real (your metabolism is higher) and partly artifact (elevated heart rate inflates the estimate). Split the difference: increase fueling by about half the percentage your watch suggests.

Training Load climbing without more training: Your watch is correctly detecting that the same sessions produce more physiological stress at altitude. This is your signal to increase recovery nutrition proportionally. More training load demands more glycogen replacement.

Putting it together: the altitude fueling checklist

48 hours before the race:

• Increase daily fluid intake by 500–1,000ml with electrolytes
• Hit your carb loading target (8–12g/kg/day) by the clock, not by appetite
• Add 300–500mg extra sodium per day to offset altitude diuresis

Race morning:

• Eat your pre-race meal 3–4 hours before start as normal
• Pre-load 1,000–1,500mg sodium with 500ml fluid 2–3 hours out
• Have an extra 20–30g carbs in your pre-race meal if above 2,000m

During the race:

• Increase hourly carb target by 10–15% above your tested sea-level plan
• Increase fluid by 100–200ml/hr above your tested plan
• Start fueling 5–10 minutes earlier than you would at sea level
• Use time-based fueling (every 20–30 min) rather than heart rate zones
• Carry extra fuel — altitude is not the place to run out

After the race:

• Recovery nutrition matters more at altitude because glycogen depletion is deeper
• Replenish within 30 minutes: 1.0–1.2g/kg carbs plus 20–25g protein
• Continue aggressive hydration for 4–6 hours post-race

Why this is hard to do manually

The adjustments above are specific and stacked: more carbs, more fluid, more sodium, different timing, different pacing, adjusted heart rate expectations. Tracking all of it while also racing is a lot of cognitive load on top of the physical effort.

This is where wearable data becomes genuinely useful. Your watch is already tracking heart rate, pace, elevation, and (if you have a Garmin) estimated sweat loss. Sweatr takes those inputs along with the race-day conditions — temperature, humidity, altitude — and builds a fueling plan that accounts for all the adjustments automatically.

You don't need to remember that altitude increases carb oxidation by 15%. You need a plan that already reflects it. Sweatr does the altitude maths so you can focus on running.

The bottom line

Altitude is not just "harder air." It changes your metabolism, your fluid balance, your appetite, and how your wearable data reads. A fueling plan that worked perfectly at sea level will underperform at 1,500 metres and may fail you at 2,500 metres.

The athletes who race well at altitude aren't tougher. They adjusted their nutrition to match the environment. The ones who bonked thought their sea-level plan would travel.

It doesn't. Adjust before you arrive, fuel more than you think you need, and trust the data over your appetite.