Calibrate with treadmill
Calibrate with treadmill
Here’s a step-by-step method to calibrate your Forerunner 255 to a second treadmill even if it’s already calibrated to the first:
Start a treadmill run on the second treadmill
Go to your watch > Run > Treadmill.
Don’t worry about distance; just run normally.
Run at least 200 metres
This is the minimum for the watch to recognise the run for calibration.
Keep a steady pace and swing your arms naturally — the watch uses your arm motion to calculate steps.
End the treadmill run on the watch
Press Start/Stop, then Back to end.
Look for the “Calibrate and Save” option
After ending the run, the summary screen should show your distance, pace, calories, etc.
Scroll down — the option “Calibrate Treadmill” or “Calibrate & Save” should appear.
Select it. The watch will compare its step count with the treadmill distance and save a new calibration for this treadmill.
Optional: Reset old calibration
If the watch keeps defaulting to the first treadmill, go to the Garmin app:
Device Settings > Activity Profiles > Run > Treadmill > Reset Calibration.
Then run the second treadmill again and the “Calibrate & Save” option will appear.
Important: Garmin watches can only store one treadmill calibration at a time. So when you calibrate the second treadmill, it will replace the first treadmill’s calibration.
Here is a link to the Forerunner 255 owners manual that will walk you through the calibration steps, including the manual calibration option:
Yes, I am fully aware of the user manual guidance. I know it verbatim and I have applied it repeatedly.
I have calibrated and saved treadmill runs multiple times, including full factory resets, power cycling and repeating the process exactly as instructed. The calibration does not persist.
Using the same treadmill every time, a service engineer calibrated unit, my Forerunner 255 consistently records up to 30 percent less distance than the treadmill display. This is repeatable and not user error.
Historically, Garmin allowed users to manually set stride length. That functionality has been removed and the replacement logic does not work as intended. The steps required to complete a mile function is also inaccurate and does not resolve the issue.
Referring me back to the manual does not address the fault. This is a feature regression and a measurement accuracy problem, not a usage issue.
Hey, there! Did you see this before or after enrolling in our Beta program?
I have just upgraded from my much more accurate for treadmill work 245 to the dead potato on my wrist 255. I do not beta with any organisation - what I buy into I expect to be a fully functioning ready to roll out format and not one still being beta tested on its end users as the provider tries to get is programmers to sort their coding out. 1.6k = 1 mile Garmin right now records it at 1.2 to 1.3k at end of each mile completed. I should have the option end each workout to set the distance completed not 'be made' to just accept what the 255 says it is. Treadmill workouts I now revert back to wearing the 245 that I bought in 2019. 6 year old spec out performing your newest tech.