Open a running .fit file — cadence, pace and running dynamics
A running .fit file is denser than it looks: under the pace and distance sits a set of fields most tools never surface, and one of them is routinely halved.
Open your file
Drop your file here
a .fit file from a watch or bike computer
No account. No upload. The file is read on this device and never leaves it.
Nothing has been sent anywhere. 0 requests to this site, for the page's own code.
Why your cadence looks like 90, not 180
FIT stores running cadence as revolutions per minute — full stride cycles, meaning one leg — so the raw field is half your steps per minute. A runner turning over at 180 steps a minute writes a cadence of 90 to the file, and a reader that prints the raw number reports it as if you were shuffling. The doubling to steps per minute is a convention the file does not state; a parser has to know to apply it, and many do not.
Running dynamics, if your watch wrote them
Newer Garmin and some third-party sensors add running-dynamics fields — ground contact time in milliseconds, vertical oscillation in centimetres, stride length, and left/right ground-contact balance. They live in the same record messages as pace and heart rate but are absent on older devices, so whether they are in your file is a question only the file answers. This page lists which of them yours actually contains rather than assuming a model.
What you get from this page
Drop the file and it reads on your device: the sport and sub-sport it declares, the record and lap structure, and every field present with its count — cadence shown both raw and as steps per minute so the halving is never a surprise. Nothing is uploaded.
In the corpus this tool is tested against, 1,074 activities resolved to this sport. See the full activity-type list for every sport a .fit file can declare, and open any .fit file whatever its sport.