Fix your workout's elevation gain on Strava

Strava checks if your file was created by a device with a barometric altimeter. The iFit export doesn't include a recognized device tag, and it also lacks GPS data—so Strava has nothing to validate the elevation against and defaults to zero. This tool adds the device metadata Strava needs.

No. Your heart rate, distance, time, and elevation values are untouched. We only change two things: the activity type label (so it imports as a Hike/Run/Walk) and the device creator tag (so Strava trusts the altitude data). Everything runs in your browser—nothing is uploaded anywhere.

Any iFit-connected treadmill or incline trainer that exports TCX with altitude data. This includes the x22i, x32i, Commercial 2950, Commercial 2450, EXP series, and ProForm/Freemotion machines. If your iFit export has AltitudeMeters values in the file, this tool will work.

When you edit the activity type in Strava's UI, even after using this converter, it triggers a full reprocessing of the file. Without GPS coordinates, Strava can't cross-reference the elevation and resets it to zero. That's why this tool lets you set the type before uploading—so you never need to edit it inside Strava.

Yes. Once Strava accepts the barometric elevation data, it counts toward your weekly stats, elevation challenges, and segment leaderboards just like any outdoor activity.

Strava's developer docs describe a universal override: any device name with "with barometer" appended tells Strava to trust the elevation data in the file, regardless of whether it recognizes the specific device. This is the safest option if you don't want to spoof a particular brand.

TrainingPeaks already reads iFit elevation correctly from the original file, so you don't need this tool for TP. The fixed file will still import fine to TrainingPeaks if you want to use one file for both platforms.