Strava and Garmin Elevation Data Conflict Explained

Strava and Garmin have long disagreed on elevation figures, and that gap matters more than most athletes realize. Your Garmin Fenix 7 might log 1,200 meters of climbing on a trail run while Strava corrects it down to 950 meters using its own elevation database. Two platforms, two methodologies, one frustrated runner staring at mismatched stats.

Garmin uses barometric altimeters on most of its GPS watches, from the Fenix series down to the Forerunner 265. That sensor reads air pressure changes to estimate altitude in real time. It's responsive, but it drifts, especially on long efforts where weather pressure shifts mid-run. Coros handles this similarly on the Vertix 2, while Apple Watch Ultra leans more heavily on GPS-fused altitude, which brings its own inaccuracies on steep switchbacks.

Strava applies a correction layer called "elevation correction" that cross-references your GPS track against a digital elevation model. The idea is solid in theory. In practice, it smooths out real climbs, misreads rooftop routes, and sometimes strips 200 to 300 meters off a legitimate mountain effort. Polar Flow takes a different approach and largely trusts the onboard sensor data, which runners often prefer for consistency.

For competitive athletes chasing FKTs, segment records, or training load accuracy, the discrepancy is not cosmetic. A 20% elevation error changes your TSS calculation, your vertical oscillation context, and how your week stacks up in tools like TrainingPeaks. Whoop doesn't track elevation at all, which sidesteps the problem entirely but leaves trail runners without altitude-based strain context.

The verdict: trust your Garmin barometric altimeter for real-time pacing and effort on the day. Use Strava data carefully, especially if you race on segments where elevation drives your ranking. Know which number you're comparing before you argue with your training partner about who climbed more.