1. Binary Header Verification
Every valid .FIT file begins with a 12- or 14-byte header containing the ASCII .FIT signature at byte offset 8, protocol/profile version numbers, and a payload byte length followed by a 16-bit CRC.
THE TOOLBOX / HEALTH & SPORTS TELEMETRY
Drop any Garmin, Wahoo, Zwift, or Coros .fit or .tcx workout file to inspect heart rate, watts, Normalized Power, cadence, speed, and elevation charts—and export clean CSV data locally.
| Elapsed (s) | HR (bpm) | Power (W) | Cadence (rpm) | Speed (km/h) | Elevation (m) |
|---|---|---|---|---|---|
| 5s | 142 | 210 W | 88 | 32 | 120 m |
| 10s | 148 | 225 W | 90 | 34 | 122 m |
| 15s | 155 | 245 W | 92 | 35 | 125 m |
| 20s | 162 | 260 W | 94 | 36 | 129 m |
| 25s | 168 | 280 W | 95 | 37 | 134 m |
| 30s | 174 | 310 W | 98 | 38 | 138 m |
ANT+ FIT BINARY STRUCTURE
| Format | Encoding | Typical 1-Hr Ride Size | Sensor Support |
|---|---|---|---|
| .FIT (ANT+) | Compact Binary + CRC-16 | 80 – 250 KB | GPS, HR, Power, L/R Balance, Cadence, Radar, Laps |
| .TCX | XML Text | 1.2 – 3.5 MB | GPS, HR, Cadence, Speed, Watts (via TPX extension) |
| .GPX | XML Text | 600 KB – 2 MB | GPS + Elevation (sensors require vendor extensions) |
Every valid .FIT file begins with a 12- or 14-byte header containing the ASCII .FIT signature at byte offset 8, protocol/profile version numbers, and a payload byte length followed by a 16-bit CRC.
Exporting your decoded records to CSV gives you clean numeric columns for elapsed seconds, HR, power, cadence, speed, and elevation ready for custom training dashboards.
Convert GPS routes in our GPX to KML Converter, model cycling aerodynamics in the Bike Speed Calculator, or check swim efficiency in our Swimming Pace Calculator.
Drop your .fit (or .tcx) workout file into the FIT file viewer above. It decodes the binary ANT+ FIT header, local definition messages, and Global Message 20 record streams locally in your browser.
It extracts elapsed time, heart rate (avg & max bpm), cycling/running power (average watts and Normalized Power), cadence (rpm), speed (km/h), and elevation (meters), then plots them interactively and exports clean CSV.
Yes. Drop your .fit file and click "Export CSV" to download a ready-to-analyze spreadsheet of every decoded record sample for Excel, Google Sheets, or Python.
GPX and TCX are human-readable XML text files, whereas FIT (Flexible and Interoperable Data Transfer) is a compact binary protocol built by Garmin/ANT+ that stores high-frequency sensor data in a fraction of the file size.
Yes. Any standard ANT+ FIT activity file using Global Message 20 (record) fields—including Garmin Edge/Forerunner, Wahoo ELEMNT, Zwift, Coros, and Suunto—is supported.
Never. Binary FIT decoding, telemetry charting, and CSV export run 100% locally inside your browser tab.