GPS Watch Elevation Inaccurate? How to Fix It

If your GPS watch says your flat neighborhood loop climbed 900 feet, or your trail run shows half the elevation gain your friend recorded, the watch is not necessarily broken. Elevation is one of the messier metrics in running tech because watches estimate it from a mix of barometric pressure, GPS position, and elevation databases.

The fix is usually boring in the best possible way: calibrate the watch, start with a clean GPS lock, clean the barometer port if your model has one, and understand when your app is replacing the original elevation data from the watch.

If you are shopping instead of troubleshooting, start with our guide to whether you need a barometric altimeter in a running watch. It explains when the sensor is worth paying for and when GPS-only elevation is good enough. If you are still deciding what kind of device you want at all, our running watch vs smartwatch comparison is a better starting point than spec sheets.

Listing check: Amazon “GPS running watch” and “barometric altimeter watch” titles mix Forerunner 165-class units that have a barometer with cheaper GPS-only cousins that look identical in the photo. Confirm the spec sheet names a barometric altimeter if ascent is why you are shopping, and that the listing is not a kids toy tracker. Street prices move; treat any dollar figure on a BuyBox as a listing check, not a lock.

Who should buy a new watch — and who should skip

Skip a new watch first. Clean the port, calibrate, and compare the same loop three times. If distance is the number that looks wrong rather than ascent, read our breakdown of dual-band GPS accuracy and whether it is worth it — that is a horizontal GPS problem, not an altimeter problem, and no altimeter upgrade will fix it.

Upgrade only when you regularly care about trail or hill gain and the current watch has no barometer. Road and track runners can live with noisy GPS elevation. It is the same trade-off as chest strap vs wrist heart rate accuracy: the dedicated sensor is not magic, it is just measuring the thing directly instead of inferring it.

Skip the Ultra-class smartwatch when you wanted a training watch with a calibration menu, not cellular and maps. COROS/Garmin with a named altimeter setting is the narrower tool.

This desk compared manufacturer support pages (Garmin, Apple, COROS, Polar, Strava) and the owner complaints that repeat (blocked ports, app-rewritten gain). It is not a claim that we logged every model on the same ridge.

This guide walks through the practical fixes first, then explains when the problem is normal GPS noise, when it is a settings issue, and when it is time to upgrade to a watch with a real barometric altimeter.

Quick Fix Checklist

Try these in order before you delete workouts, factory reset the watch, or assume the altimeter is dead:

1. Start outside with a clear sky for a few minutes. Apple notes that GPS accuracy improves as more satellites become visible, and obstructions like buildings, vehicle roofs, mountains, and walls can block the signal.
2. Calibrate elevation before hilly or trail workouts. Garmin, COROS, and Polar all recommend calibration when accurate elevation matters.
3. Use a known elevation point if you have one. Trailhead signs, survey markers, sea level, or a reliable topographic map are better references than guessing.
4. Clean the barometer/altimeter sensor port. Mud, sunscreen, sweat salt, and pool residue can block the tiny pressure port on watches with barometric altimeters.
5. Check whether your app changed the data. Strava may use the barometric data from the original activity file or recalculate elevation from its own basemap depending on the device and activity.
6. Compare the same route over several runs. One weird day can be weather, GPS obstruction, or a bad lock. Repeatable drift on every activity points toward calibration, dirt, or hardware.
7. Update firmware and sync fully. Watch makers often improve sensor handling and post-workout corrections through software updates.

Why GPS Watch Elevation Goes Wrong

Distance and elevation are not measured the same way. A watch can track your route distance well and still report bad climbing data. If the number that looks wrong is distance rather than ascent, that is a horizontal receiver problem — our dual-band GPS accuracy guide covers what actually improves it.

Most running watches use one of three elevation methods:

Elevation method	What it uses	Strength	Weakness
GPS elevation	Satellite position	Works without a barometer	Noisy vertically, especially near buildings, trees, cliffs, and switchbacks
Barometric altimeter	Air pressure sensor	Better for changes in ascent/descent during a workout	Weather, blocked ports, and poor calibration can shift the baseline
Database correction	Map/elevation model from an app	Can clean up activities from devices without barometers	Depends on route matching and local map quality

Garmin describes barometric altimeter accuracy as dependent on proper calibration. COROS says its watches combine GPS and an internal barometer, with the barometer converting air pressure into elevation and periodic GPS checks helping recalibrate the result. Polar says its supported devices measure altitude with an atmospheric pressure sensor and recommends manual calibration when you know your current altitude.

Translation for runners: your watch is estimating the vertical profile, not reading a perfect ruler from the sky.

First, Diagnose the Pattern

Before changing settings, look at the shape of the error.

The Start Elevation Is Wrong, But the Climbing Looks Reasonable

This usually means the watch needs calibration. If the route profile has the right hills in the right places but starts 200 feet too high or low, the barometer baseline is off.

Fix: manually calibrate elevation at the start of the run, or enable automatic calibration if your watch offers it. For races, trail runs, and workouts where elevation matters, do this before pressing Start.

Total Ascent Is Way Too High on a Flat Run

This often means pressure noise is being counted as climbing, GPS is jumping around, or the barometer port is contaminated. It can also happen when a windy jacket sleeve or tight wrist position interferes with the pressure port.

Fix: clean the sensor port, wear the watch normally exposed to air, and test on a known flat route. If the watch keeps inventing hundreds of feet on flat routes, contact the manufacturer.

Elevation Drifts Up or Down Through the Whole Activity

A slow climb or drop on an out-and-back route that starts and ends at the same place is classic barometric drift. Weather pressure can change during a run, and a blocked or wet port makes this worse.

Fix: calibrate before the run, let the watch dry after swimming or washing, and compare the recorded start and finish elevation on a loop.

Drift Shows Up Right After Swimming or a Downpour

A wet pressure port is a specific and common failure mode. Water sitting in the port changes the pressure the sensor reads, so the first run after a pool session or a soaked sleeve can drift even when every dry-weather run is fine.

Fix: rinse the watch in fresh water after swims, dry it fully before the next workout, and check whether the drift disappears on dry days. If it does, the sensor is fine — the port just needs better aftercare.

Only the Canyon, Downtown, or Tree-Covered Sections Look Wrong

If the profile spikes exactly where buildings, cliffs, or dense canopy block the sky, that is degraded GPS geometry, not a broken sensor. Vertical position degrades faster than horizontal position when satellites cluster low on the horizon.

Fix: start in the open, wait for a full lock, and judge the watch on its unobstructed miles. If elevation is only noisy where the sky is blocked, a new altimeter will not change much — but a barometric watch will smooth those sections better than GPS-only elevation.

Strava, Garmin Connect, Apple Fitness, and COROS Do Not Match

This is normal. Strava explains that elevation is calculated from different sources depending on the device and activity: if the device has a barometric altimeter, Strava can use elevation data from the original file with smoothing; if not, it can look up elevation from its basemap.

Fix: decide which number you trust for your training log and stay consistent. Do not compare weekly climbing totals across apps unless you know they are using the same elevation source.

How to Fix Elevation on Garmin Watches

Garmin models with barometric altimeters, including many Forerunner, fenix, epix, Enduro, Instinct, Venu, and vivoactive models, can drift if the altimeter is not calibrated or if the pressure port is dirty.

Garmin Checklist

1. Calibrate at the start of the run. On many Garmin watches, look for Settings > Sensors & Accessories > Altimeter > Calibrate. Exact menu names vary by model.
2. Use DEM or GPS calibration when available. Some Garmin watches can calibrate from GPS or digital elevation model data.
3. Clean the barometer sensor port. Garmin’s altimeter troubleshooting pages recommend cleaning when readings are significantly off. Use fresh water and avoid poking objects into sensor holes.
4. Turn on elevation corrections after upload if needed. Garmin Connect can use map-based elevation corrections on some activities, especially when the device does not have a barometric altimeter or the barometric data looks wrong.
5. Test a known loop. Start and finish in the same place. If the start and end elevation are still far apart after calibration and cleaning, the sensor may need service.

For buying decisions, the important part is simple: if elevation gain matters for trail running, hill workouts, hiking, or ultra training, buy a model with a barometric altimeter. Entry watches that rely more heavily on GPS elevation can be fine for pace and distance but less reliable for ascent.

For a fuller buying framework, read do you need a barometric altimeter in a running watch?, and see our Garmin Forerunner 165 review plus the Forerunner 165 vs 265 comparison for where the barometer-bearing value picks sit in the lineup.

How to Fix Elevation on Apple Watch

Apple Watch handles elevation differently than a dedicated trail watch, and the exact behavior depends on your model, workout type, phone pairing, and location settings. Apple says calibration can improve distance, pace, and calorie accuracy and helps the watch learn your stride when GPS is limited or unavailable.

Apple Watch Checklist

1. Check Location Services. On iPhone, go to Settings > Privacy & Security > Location Services and make sure Location Services is on.
2. Enable Motion Calibration & Distance. Apple specifically lists this under Location Services > System Services.
3. Do a calibration run or walk. Apple recommends going to a flat, open outdoor area with clear GPS reception and doing an Outdoor Walk or Outdoor Run for about 20 minutes.
4. Give GPS time to settle. If you start under a parking garage, downtown building, or dense tree cover, your first minutes can be messy.
5. Reset calibration data only after settings are correct. In the Watch app, use My Watch > Privacy > Reset Fitness Calibration Data, then repeat the outdoor calibration session.

If you use an older Apple Watch that borrows iPhone GPS when the phone is nearby, the phone position matters. A phone in a pack, pocket, or stroller can produce different GPS behavior than a watch worn on the wrist.

If you are torn between the two ecosystems rather than troubleshooting one, our Garmin vs Apple Watch comparison for runners covers where each platform’s strengths actually sit.

How to Fix Elevation on COROS Watches

COROS watches take a hybrid approach: COROS support describes an internal barometer converting air pressure into elevation, with periodic GPS checks helping recalibrate the reading during an activity. That fusion is why a COROS usually self-corrects a drifting baseline mid-run, but also why a blocked port or a bad initial GPS fix can still poison the first few miles.

COROS Checklist

1. Let the GPS settle before you press Start. Because GPS participates in the calibration, starting under cover can hand the barometer a bad baseline that takes time to unwind.
2. Calibrate manually when you know your elevation. Depending on firmware, calibration lives in the watch’s system/navigation settings or in the COROS app’s device settings — menu names shift between versions, so search the app for “calibration” if the path has moved.
3. Rinse and dry the pressure port after swims and muddy runs. COROS watches are pool-friendly, and pool residue plus sweat salt is the classic recipe for a port that stops breathing.
4. Update firmware through the app. COROS ships sensor-handling changes regularly, and altimeter behavior has improved across firmware generations.
5. Compare a known loop before concluding hardware failure. Repeatable drift after cleaning and calibrating is the case for a warranty contact.

For budget shoppers who want a barometer without the Garmin price, our COROS Pace 3 vs Garmin Forerunner 165 comparison covers which trade-offs actually matter for elevation-sensitive training.

Polar and Other Barometric Watches

Polar’s supported devices measure altitude with an atmospheric pressure sensor, and Polar recommends manual calibration when you know your current altitude — same principle, different menu. The three rules that fix most Polar, Suunto, and Amazfit elevation problems are identical to the Garmin list: calibrate from a known elevation, keep the port clean and dry, and judge the watch on repeated known loops rather than one strange activity file.

If your current Polar is aging and ascent numbers are the reason, the best GPS running watches under $200 roundup notes which budget models finally include a barometer.

Why Your App Disagrees With Your Watch

The single most common “my elevation is wrong” report is not a sensor problem at all — it is two platforms reporting different numbers from the same run.

The mechanics: if your device has a barometric altimeter, most platforms will honor the elevation curve already in your activity file, lightly smoothed. If it does not, the platform rebuilds elevation by matching your GPS trace against a basemap and reading the terrain under it. Route matching is where the second method fails — a trace that wobbles across a valley wall in a switchback zone can pick up phantom climbing.

That is why the same run can show different gain in Strava, Garmin Connect, Apple Fitness, and COROS, and why Strava’s own elevation documentation describes both paths.

How to stop the mismatch from mattering:

• Pick one platform as your log of record and read weekly climbing totals only there.
• Do not compare your totals against a friend’s unless you both know which elevation source each app used.
• If you run a GPS-only watch, the basemap-corrected number in your app is usually more believable than the raw watch total.
• If you run a barometric watch, the device file is usually more believable — after calibration and a clean port.

A Simple Maintenance Routine

Most repeat elevation complaints trace back to aftercare, not hardware. A routine that takes a couple of minutes a week:

• After every swim or muddy run: rinse the watch in fresh water and dry it before the next workout.
• Weekly: glance at the sensor port for sunscreen film, salt crust, or lint; rinse gently if you see any.
• Monthly: run a known loop and check that start and finish elevation agree. One bad loop is noise; a month of drifting loops is a calibration or port problem.
• At every firmware prompt: update and sync fully before judging the sensor, since sensor handling changes ship in software.
• Before races and trail days: manual calibration at a known elevation, even if auto-calibration is on.

When It Is Time to Upgrade

If the checklist, cleaning, and calibration do not stabilize ascent numbers — and distance is still accurate — the sensor may genuinely be failing, and warranty service is the right next step.

If the watch simply has no barometer and your running has moved to trails, hills, or ultra prep, that is an upgrade with a clear reason attached. Independent long-term reviewers such as DC Rainmaker cover barometer behavior in their watch reviews, and our own pages can shortcut the decision:

• Do you need a barometric altimeter in a running watch? — the sensor-vs-GPS trade-off in full.
• Best GPS watches for hiking — when elevation and battery both matter.
• Best GPS running watches under $200 — which budget picks include the sensor.
• Garmin Forerunner 165 vs 265 and COROS Pace 3 vs Forerunner 165 — the two most common upgrade paths with barometers.

Elevation Questions Runners Actually Ask

Can I trust elevation from a watch with no barometer?

As a rough trend, yes. As a total you log against friends, no. GPS-only vertical position is noisy near buildings, cliffs, and canopy, and app-side basemap correction only partially cleans it up.

Why did my friend’s watch show different gain on the same run?

Different sensors, different apps, different elevation sources. A barometric watch and a GPS-only watch on the same route can disagree by hundreds of feet on a hilly loop without either being broken.

How often should I calibrate a barometric watch?

Manufacturer guidance converges on “whenever accurate elevation matters” — before races, trail runs, and workouts you will log against climbing goals — plus anytime the start elevation is obviously wrong at your door. Automatic calibration options help between those moments but do not replace the manual check on elevation-critical days.

Will a factory reset fix bad elevation data?

Rarely. Elevation problems are overwhelmingly calibration, port contamination, GPS lock, or app re-processing issues, and those are all fixed with the checklist above. Save the factory reset for after support asks for it, because it wipes your calibration history along with everything else.

Can I fix the elevation on a run I already recorded?

Sometimes. Garmin Connect and Strava both offer elevation corrections that re-process an uploaded activity from map data, which can rescue GPS-only files. What no app can do is un-block a sensor port retroactively — which is why the maintenance routine comes first.

Sources

• Garmin Support Center — altimeter calibration and troubleshooting guidance
• Apple Support: Get the most accurate measurements using your Apple Watch
• COROS Support — barometer and GPS elevation behavior
• Strava Support — how elevation is calculated from device files vs basemaps
• DC Rainmaker — independent long-term GPS watch reviews