Skip to content
November 2026

Why Strava, your watch and AllTrails show different distances

Strava normally shows the distance your device wrote into the file. It can come out shorter when the data looked bad and Strava recalculated, when the file had no distance and Strava measured the GPS track, or when the recording lost signal.

Moving time differs because each one decides for itself when you stopped. AllTrails cleans up your track on its servers after you save, and a verified trail’s length is a separate measurement that counts climbs.

Want to change the number? Skip to what Strava can fix.

Why Strava and your device disagree

Usually not by much. Under normal conditions the difference should be minimal, and if Strava uses your device’s distance stream you should see a similar number. Small gaps come from number crunching on both ends: Strava works from the file on its own, while most devices tally the figures as they go.

A bigger gap can mean Strava stopped trusting the stream. Past a threshold of outlier or poor GPS data, it recalculates by blending GPS and device distance, and that can land away from what the device reported, especially if you had a speed sensor. So your watch can say 5 km and Strava a different number, and nobody edited anything.

Other ways Strava ends up shorter:

  • A lost signal. It can leave you with less distance than you traveled.
  • An Apple Watch started near your phone. Strava puts this down to a known Apple bug: start while the watch is still connected to a phone you’re leaving behind, and the route can begin late and come out shorter than the watch’s summary. Start away from the phone.
  • GPS math. Whether the device or Strava does it, the calculation assumes a flat surface and joins points with straight lines, so climbing isn’t counted and some distance can be lost on curves. A device’s result can drift further with battery-saving features on, and device calculations can produce stuck points, where no distance is added after the previous point.

A wheel sensor does count the climbing, but it’s only accurate if the wheel size is right and the magnet catches every turn. Moving it to a bike with a different wheel size without updating it can skew things.

Bad GPS can push the total either way. Bounce near tall buildings can add distance, and drift under trees can take it away. That’s also why a friend beside you can finish with a different number.

Where each number comes from

SourceDistanceMoving time
StravaThe file’s distance stream, with smoothing to remove outlier GPS points. No stream: adds up GPS point to point. Too much bad data: blends GPS and device distanceRuns: the timer, if the file has pauses; otherwise worked out from GPS. Rides: a speed threshold on the GPS data
GarminPer Strava’s help, an Edge bike computer uses a PowerTap hub first, then a speed sensor, then GPSOn a Forerunner 570, Moving Time is its own data field
Apple WatchSeries 8 and later, Ultra and SE (2nd generation) use their own GPS. Older models use the iPhone’s when it’s available. Calibration helps when GPS is limitedAuto-Pause is a setting for outdoor runs and rides
AllTrails recordingYour phone’s GPS, filtered moderately while you record and smoothed on its servers when you saveAllTrails shows total moving time
AllTrails verified trail pageAveraged from many members’ recordings, then measured along that route with climbs and descents includedDoesn’t apply

Why AllTrails is different again

Your own AllTrails recording changes after you save it. Phone GPS is noisy; the app filters it moderately while you record, and much of the cleanup happens during sync, when AllTrails’ servers recompute your stats. The saved number is the one to compare.

The length on a verified trail’s page comes from somewhere else. AllTrails averages anonymized members’ tracks to define the route, then measures along it, counting ups and downs. Strava’s GPS calculation assumes flat ground, so on a steep trail the two are measuring different things before anyone’s GPS goes wrong.

Moving time, elapsed time and pauses

Elapsed time runs from start to finish, stops included. Moving time is meant to be how long you were active, and Strava generally shows that one, with pace based on it.

  • Runs. Strava uses the timer time and respects pauses in the file, automatic or manual. If there’s even one pause event, its server removes no further rest, so pausing at one light and not the next inflates moving time. With no pauses at all, it calculates moving time from GPS.
  • Rides. Strava applies a speed threshold to the GPS data during upload, for its own app and third-party devices alike. Poor GPS can make you look like you were moving when you weren’t, and your device may define a rest differently. Strava’s view is that neither is necessarily wrong.
  • Races, segments and Best Efforts. Tag a run as a race and Strava uses elapsed time; that’s Strava’s way to make a run show it. Segments and Best Efforts always use it, which is why a Best Effort can be slower than you expected after a stop. Distance plays no part in segment times.

Auto-pause can trip on slow speeds. In the Strava app it uses GPS for rides and the phone’s accelerometer for runs. Turn it off for walks and hikes, where it can pause too often and struggle to resume. With it off, Strava works out moving and stopped time during upload. Watches have their own version; on a Garmin Forerunner 570, Auto Pause stops recording when you stop or drop below a speed you set, and the Elapsed Time field keeps counting through a stopped timer.

Suunto files have a known quirk. Points with time but no GPS update look like standing still, which can make moving time too short and pace too fast. Strava’s workarounds are Correct Distance, or tagging the run as a race.

When the distance jumped, or the phone restarted

A straight line across the map, or a sudden leap, can be a gap in the recording, though a leap can also be one bad GPS point far off your path. Strava joins the points on either side with a straight line, however much time passed between them. A jump can happen when a device stops recording GPS for a while and then starts again, which is what a phone restart looks like if the recording picks up afterward.

For next time: on Android, allow background location and turn off battery savers (Strava’s Android article has steps per phone maker). On iPhone, watch for apps that kill background apps to save battery.

What Strava can fix

Strava can’t correct or fill in GPS data after recording, so its tools cut, recalculate or work around bad data. If Strava came out short, none of these adds back distance that wasn’t recorded; a manual activity is a number you type in yourself.

ToolWhat it doesLimits
Correct DistanceReplaces the device’s distance with one calculated from GPS after upload, removing outlier pointsWebsite. In the three-dot menu or under the distance figure (Strava’s help gives both). Click again to revert
CropTrims the start or endWebsite and app, GPS activities only. Not the middle. No undo
SplitDivides one activity into 2 or 3Website, GPS rides and runs. Kudos and comments stay on the first piece. No undo
Race tagShows elapsed time on a runStrava documents it for runs
Manual activityLogs a distance as its own activityNo segments, no Challenges. To edit its distance later, use the app; the website can’t

For bad data in the middle, Strava’s advice is to split, then crop the piece that resulted. That leaves you with separate activities. Neither has an undo. Getting the full activity back means deleting it and uploading the original file, which costs its kudos, comments and photos, so export the original first.

A treadmill run is a different case. Correct Distance works from GPS points, so it has nothing to go on indoors.

Where file tools fit

Anything else, apart from a Combine.Run merge, means changing the file and uploading it again. Export the original, edit it, delete the activity on Strava, then upload, because Strava won’t hold two versions of the same activity. That costs the same kudos, comments and photos, so for a small error we’d leave it alone.

Strava generally uses a distance stream when the file has one, so if a tool edits GPS points, check what it does with that stream. No tool here adds back distance that wasn’t recorded: a typed total is a number you chose, and a rebuilt or interpolated section is an estimate, not a recording.

Listed alphabetically:

ToolWhat it offers for thisWhat happens to the distance
Combine.RunJoins a run or ride that ended up as two activities, with waypoints you can click to shape it. Uploads the result to Strava and can take the originals off your feed without deleting themThe joined activity carries interpolated GPS across the gap
FIT File EditorCuts any section, including the middle. Drags, smooths or deletes GPS pointsTotals are recalculated after a cut. A typed total scales distance, speed and pace across the whole activity, not one stretch
FIT File ViewerShows a file’s records as tables, charts and a map, so you can see what the device wrote. Recovers partly corrupted filesViewing and repair, not editing
GOTOES ToolsEdit Points flags likely bad points, such as a jump or an impossible speed, for you to review and delete. Trims ends. Split GPS Files cuts a file at points you choose and keeps the parts you tick, which can go on to Merge / Repair together. Race Repair rebuilds missing race GPS from a course fileOn export, the distance stream can be left out, recalculated or kept (TCX and FIT only). The existing stream carries over only if you pick Use Embedded. Upload an outdoor activity without distance and Strava recalculates it

Our guide to editing and merging activities walks through these jobs one by one, and repairing a corrupt FIT file covers a file Strava rejects. The Garmin Connect, Apple Watch and Suunto pages cover how each one reaches Strava.

Sources

All pages read November 14, 2026.

Apps in this post

The social network for athletes. Track your runs, rides, and workouts with GPS, compete on segments, join challenges, and connect with millions of athletes…

Strava
Working · checked Nov 2026
DetailsOpen site

Garmin's app and site for its devices. Activities uploaded to Garmin Connect post to Strava automatically; starred Strava courses and segments sync the other…

Strava
Working · checked Nov 2026
DetailsOpen site

Companion app for Suunto GPS sports watches that automatically uploads recorded activities to Strava and syncs starred Strava routes and Live Segments back to…

Strava
Working · checked Nov 2026
DetailsOpen site

Merges a run or ride that Strava saved as two activities. Connect Strava, pick a suggested pair, click waypoints to fill the gap, and it uploads the merged…

Strava
Working · checked Nov 2026
DetailsOpen site

Free FIT file editor in the browser: cut a range, cap or smooth bad heart rate or power, move GPS points, change the sport or device, merge files, or repair a…

Strava
File tool, no login
DetailsOpen site

Free FIT file viewer for files from your watch or a Strava export: every message type as a table, a zoomable chart, the route on a map, and a fixed copy of a…

Strava
File tool, no login
DetailsOpen site

More from the blog

Spotted something out of date, like a price or a feature that changed? Tell us and we'll check it against the maker's site and fix it.

Fixes and apps for Strava, mid-month

The new guides (fixing a bad file, merging, getting your data out), the best new apps, and any that stopped working. One short email. Reply "unsubscribe" any time.