Your GPS watch is less useful at altitude than it was at sea level. Not because it’s broken, but because the number it shows you is built on a lie the air tells every runner who moves here.
At altitude, the same effort buys a slower pace. Chase your old sea-level number and you’ll work too hard, recover too slowly, and wonder why you feel so beaten up.
The answer is to run by effort instead. Here’s how.
Why the watch misleads you here
At 5,280 feet, the air is thinner. Every breath carries less oxygen to your muscles. Your body works just as hard, but gets less out of each lungful.
On short, punchy efforts, this barely shows. On anything lasting more than a few minutes, it adds up fast. The longer the run, the bigger the gap between the effort you feel and the pace your watch records.
A runner who moves here and immediately tries to hit their old easy pace isn’t running easy. They’re working in a zone that used to mean something harder, and the body knows it, even when the watch doesn’t.
For a closer look at what’s physically happening in the thin air, running at altitude in Denver covers the underlying physiology.
The simple fix: talk test and RPE
You don’t need a sports-science lab to pace by effort. Two tools are enough.
The talk test is the simplest: easy running means you can hold a conversation without gasping. If someone asked you a question mid-run and you couldn’t answer in full sentences, you’re working too hard for an easy day.
Perceived effort (RPE) is the broader version. A 1-to-10 scale works fine: 1 is sitting still, 10 is a full sprint you can’t hold for more than a few seconds. Easy days sit around 4-5. Hard efforts push into 7-8. At altitude, those effort numbers stay meaningful even when the pace numbers don’t.
Denver’s altitude changes how every race feels; pace by effort, not your sea-level numbers.
Use these two tools together. If you can’t talk and your effort feels like a 7, you’re not on an easy run, no matter what the watch says.
Most days should be easy
This is true everywhere, but it matters more at altitude because the cost of overdoing it is higher here.
On easy days, run at a pace where you could comfortably narrate the run out loud. That’s the benchmark. If you push past it to hit a number, you’re paying a cost that shows up later in the week as fatigue and flat legs.
A full guide to staying fueled and recovered through longer efforts is in staying hydrated running at altitude, which pairs well with any shift to effort-based training.
The rough breakdown that works for most recreational runners:
- 4-5 days per week: easy effort (conversational pace, RPE around 4-5)
- 1 day per week: one harder session, done deliberately (see below)
- 1-2 days: rest or very easy movement
This isn’t a rigid plan. It’s a description of what effort-based training looks like in practice for most people who aren’t chasing a specific race time.
What hard days look like
Not every run should be easy. The harder sessions are worth doing, but they earn their place.
A hard run at altitude feels more demanding than the same session at sea level, and recovery takes longer. That’s not a reason to skip them, but it is a reason to run them sparingly.
Signs you’re working hard enough on a hard day:
- Conversation is impossible
- Effort feels like 7-8 on the RPE scale
- You couldn’t hold this pace for more than 20-30 minutes comfortably
Signs you may have overdone it:
- Still tired two days later
- Easy runs feel harder than usual
- Your appetite and sleep are off
If those signs show up regularly, back the hard sessions off. The altitude is already a training stressor on its own. As you prepare for a first race here, training for your first 10K in Denver covers how to structure harder sessions around a goal event.
Heart rate at altitude: a useful input, not the full answer
Heart rate monitors can help, but altitude distorts them in ways worth knowing.
When you first arrive, your heart rate tends to run higher than normal for a given effort. Your heart is working harder to compensate for the thinner air. Chasing a heart-rate zone you held at sea level will often push you too hard in the first weeks here.
Sports-science literature on altitude adaptation generally finds that resting and exercise heart rates drift back toward normal over several weeks as the body adjusts. Until then, treat your heart rate as one piece of information among several, not the single governor of your pace.
The talk test tends to stay reliable even when heart rate is elevated. If you can talk, you’re easy. That’s a harder number to game than a bpm target.
How long before the gap closes?
The gap between effort and pace is largest in the first week or two. Most runners see meaningful improvement within a month as the body adapts, and your watch numbers start to catch up to how you actually feel.
Expect your easy pace to sit a little below your old sea-level number even after full adjustment. That gap shrinks but doesn’t fully disappear for most people. The good news: once you’ve trained here long enough, racing at lower elevation tends to feel noticeably easier.
The full picture of that adjustment arc is in your first month running in Denver, which covers week-by-week what to expect.
The bottom line
Run by effort. Use the talk test. Let the watch tell you what happened after the fact rather than letting it pull you into a pace that doesn’t fit the air.
Give it a few weeks, and the gap between effort and pace will narrow on its own. Push through it instead, and you’ll just be tired and slow at the same time.
Train for the course you’ll run: hills, trail, and thin air are three different problems.