
Image generated by our model.
cycling file formats
FIT vs TCX vs GPX: Choose the Right Cycling File Format
FIT vs TCX vs GPX is not a file nerd debate. It decides what data survives when you move rides, routes, workouts, and history between platforms.
Why cycling file formats matter
FIT vs TCX vs GPX sounds like a back-office problem until something important disappears.
You export a ride and the power data is gone. You send a route to a head unit and the cues are missing. You move years of training history to a new platform and suddenly laps, sensor streams, or workout targets do not line up. The ride still exists, but the useful part of the file has been flattened.
That is the real issue with cycling file formats. They are not just containers. They decide which parts of your ride are treated as essential, which parts are treated as optional, and which parts may be impossible for the next platform to rebuild.
For a quick decision, start here:
| Format | Best use | Likely preserved data | Common losses | When not to use |
|---|---|---|---|---|
| FIT | Completed rides, training history, structured workouts, device-native activity files | GPS, timestamps, power, heart rate, cadence, laps, pauses, sensor and device context, workout detail when recorded and imported | Data can still be dropped if the source never recorded it or the destination chooses not to import it | Simple route sharing where broad compatibility matters more than training detail |
| TCX | Compatibility fallback, some course and cue workflows, older training tools | GPS track, timestamps, heart rate, cadence, laps or course points depending on source and destination | Device-specific fields, richer sensor data, advanced workout or activity detail | Archiving high-value rides when FIT is available |
| GPX | Route lines, GPS tracks, broad sharing between mapping tools | Coordinates, route geometry, sometimes timestamps and elevation depending on export | Power, cadence, heart rate, laps, pauses, workout steps, sensor context, interval structure | Serious training analysis or long-term ride history |
The mistake is assuming one file type is always best. FIT, TCX, and GPX overlap, but they were not built around the same priorities. If you understand what each one protects best, you can avoid most export problems before they happen.
What a FIT file stores best
For completed cycling activities, FIT is usually the best starting point.
The reason is simple: a modern ride is not just a line on a map. It is a time-based record of what your body and bike were doing. A useful ride file may include GPS position, speed, heart rate, power, cadence, temperature, laps, pauses, device information, sensor data, and sometimes workout-step information.
FIT handles that type of ride well because it is built for structured activity data. It is compact, device-friendly, and better suited to preserving the full training record from a head unit or watch. When a cycling computer records your ride, there is a good chance FIT is the native or preferred format behind the scenes.
That matters because post-ride analysis depends on relationships between data streams, not just the presence of one field. Power without the correct timestamps is hard to align with intervals. Heart rate without pauses can distort effort review. Laps without the underlying sensor streams become labels rather than useful segments. Once those relationships are stripped during export, the receiving platform usually cannot reconstruct them. It can display what survived, estimate some derived metrics, or ignore missing fields, but it cannot recreate sensor data that was never written into the new file.
This affects everything from FTP tracking to training load, interval review, power curve analysis, pacing evaluation, and fatigue monitoring. If the export format drops the wrong fields, the platform receiving the file has to work from a simplified version of the ride.
This is where FIT usually wins for cycling workflows. If you are exporting a completed ride from a device, training app, or analysis platform and want to preserve as much detail as possible, choose FIT first.
That does not mean FIT preserves everything in every situation. Preservation still depends on what the source device or platform recorded, how the export was written, and what the destination platform chooses to import. FIT gives the data the best chance of surviving, but it cannot protect fields that were never recorded or fields the next system decides to discard.
The downside is accessibility. FIT is not human-readable in the way a text-based file is. If you open it directly, it will not look like a tidy list of coordinates and timestamps. That is usually irrelevant for normal cyclists, but it can matter if you are manually inspecting files or trying to troubleshoot a corrupt export.
Use FIT when the ride data itself matters. If the file represents a completed activity that will feed your training history, performance analysis, or long-term records, it is the safest default.
When TCX is still useful
TCX sits in the middle. It is more training-aware than GPX, but usually less complete than FIT for modern device data.
The main advantage of TCX is that it can carry more workout and activity context than a plain GPX file. It can include a track, timestamps, heart rate, cadence, lap-like structure, and course-related information depending on how it was created and how the receiving platform interprets it.
That makes TCX useful as a fallback when FIT import is not available or when a platform handles TCX more predictably than FIT. Some older tools and some route workflows still treat TCX as a practical bridge format.
It can also be useful for routes when you want more than a basic line on the map. Depending on the source and destination, TCX may preserve course points or cues better than GPX. This is not universal. The frustrating part of GPX vs TCX is that support is not only about the file type. It also depends on how the exporting platform writes the file and how the importing platform reads it.
The tradeoff is that TCX can simplify the ride. If device-specific messages, sensor context, workout-step logic, or richer activity fields are not represented cleanly in the TCX export, the receiving platform cannot infer them later. It may still have enough for a useful ride record, but the file is more likely to behave like a translated version of the activity rather than the original record.
I would not choose TCX first for archiving a high-value completed ride if FIT is available. It may preserve enough to be useful, but it is more likely to lose device-specific fields or advanced ride detail. For routine training analysis, that tradeoff is rarely worth it unless compatibility forces the choice.
Use TCX when you need compatibility, course cues, or a middle-ground export that keeps more training context than GPX but FIT is not an option.
What GPX is good for, and what it drops
GPX is best understood as a GPS exchange format. Its strength is location.
If the job is to share a route line, move a basic track between mapping tools, or give someone a file they can load almost anywhere, GPX is often the easiest choice. It is widely supported, readable by many mapping platforms, and simple enough that it usually travels well.
But that simplicity is also the limitation.
A GPX file is not designed to protect the full richness of a cycling activity. It may carry coordinates, elevation data, and timestamps depending on the export. Some platforms add extra information through extensions, but those extras are not always preserved when the file moves to another system.
That is where data gets lost. A platform may export the GPS track cleanly while leaving out the power stream, lap structure, pauses, workout instructions, sensor identity, or proprietary fields. Once those fields are absent from the GPX, the next platform cannot know whether you rode steady tempo, repeated short efforts, coasted through descents, or paused for traffic unless that information still exists somewhere else. The map survives, but the analytical context is gone.
GPX can easily drop or fail to preserve the data cyclists often care about after a ride:
- Power
- Cadence
- Heart rate
- Laps
- Pauses
- Workout steps
- Device and sensor detail
- Rich interval structure
- Platform-specific metrics
This does not make GPX bad. It makes it specific. It is a good route and track format, not a complete training-history format.
The biggest mistake is using GPX because it feels universal, then expecting it to behave like a full activity file. If the ride was just a scenic route you want to share, GPX is fine. If it was your key workout of the week and you want the data to survive, GPX is the wrong export unless no better option exists.
Use GPX for route geometry and broad compatibility. Do not use it as your primary archive for completed training rides.
Which format to use for routes, workouts and ride history
The cleanest way to choose is to start with the use case, not the file extension.
Completed ride history
Choose FIT when available.
This is the file that should feed your training log, performance charts, and long-term analysis. If you are moving activities between platforms, backing up ride history, or importing rides for deeper review, FIT gives you the best chance of preserving the important streams.
Use TCX only if FIT is not accepted or the platform specifically recommends TCX. Use GPX only when you care mainly about the map track and do not need the ride to behave like a full training file.
Routes for navigation
Choose based on what your head unit and planning platform handle best.
For a simple route line, GPX is often enough. It tells the device where the route goes. If you only need to follow the map, that may be all you need.
If you want turn cues or course points, TCX or FIT may work better depending on the device ecosystem. This is where testing matters. A file that looks perfect in a route planner can behave differently once it lands on a head unit.
Before an important ride, load the route and check it on the device itself. Verify that turn prompts appear where expected, off-course behavior makes sense, the elevation profile loads properly, and the device treats the file as a navigable course rather than only a passive track. That distinction matters because a line on the map may be enough for exploration, but it is not the same as turn-by-turn guidance when the route gets complicated.
Structured workouts
Use FIT or the native workout format supported by your platform and device.
A structured workout is not just a GPS file. It needs targets, steps, durations, intensity ranges, and sometimes repeats or ramps. If you are working from FTP estimator outputs or building sessions around FTP, the file needs to carry workout instructions accurately enough that the device can guide the effort.
GPX is not the right tool for that. TCX can sometimes carry workout-like structure depending on the system, but FIT or a platform-native sync is usually safer.
Sharing a ride casually
If the goal is simply to show someone where you rode, GPX is usually fine.
If the goal is to let a coach, teammate, or analyst inspect the actual effort, send FIT if possible. The distinction matters. A map answers where. A training file answers how the ride was done.
Common export and import mistakes
Most file-format problems come from assuming that export means preserve. It does not. Export means a platform wrote a new file in a selected format. During that process, it may simplify, convert, or drop data.
Mistake: exporting GPX for serious ride analysis
This is the classic error. The route appears, so the file looks successful. But the data that makes the ride analytically useful may be gone.
If you need power, heart rate, cadence, laps, or interval structure, do not choose GPX unless there is no alternative.
Mistake: assuming TCX and FIT are interchangeable
They are not. TCX can be useful, but FIT generally does a better job carrying modern activity detail. If both are available for a completed ride, start with FIT.
Mistake: trusting every import without checking the result
After importing, open the ride and inspect the key fields. Check that the map, timestamps, power, heart rate, cadence, laps, and elapsed time behavior look reasonable. Do this before deleting the original file or closing the old account.
This check matters because the import screen can make a partial file look complete. A ride can have a map, a duration, and a title while still missing the sensor streams that determine whether it is useful for training analysis.
Mistake: using one export to rebuild an entire archive
If you are migrating years of ride history, test a small sample first. Include different ride types: outdoor rides, indoor rides, workouts, races, rides with pauses, rides with sensors, and any files you know were messy. If the sample survives cleanly, then scale up.
Mistake: confusing route files with activity files
A route is a plan. An activity is a record. They may both contain GPS points, but they are not the same object. Sending a GPX route to a head unit is not the same as preserving a completed ride for analysis.
A practical file-format checklist for cyclists
Use this decision tree before you export cycling data.
If you are saving a completed ride
Choose FIT.
Check that the imported file preserves:
- Power if recorded
- Heart rate if recorded
- Cadence if recorded
- GPS track if it was an outdoor ride
- Lap or interval structure if relevant
- Moving and elapsed time behavior
- Sensor-dependent fields you rely on
If FIT fails, try TCX. Use GPX only if the map track is the main thing you need.
If you are sending a route to a head unit
Choose the format your device handles best.
Use GPX for a simple route line. Try TCX or FIT if you need cues, course points, or tighter device integration. Always load the file and inspect it on the device before an important ride. Check turn prompts, off-course behavior, the elevation profile, and whether the device treats it as a course or only a track.
If you are exporting a structured workout
Use FIT or native platform sync when available.
Check that workout steps, targets, durations, and repeats appear correctly on the device. Do not use GPX for structured workouts.
If you are moving training history to a new platform
Start with FIT.
Import a test batch before moving everything. Compare the imported rides against the originals. If key data fields are missing, change format before continuing.
If you are sharing a simple track
Use GPX.
It is the cleanest choice when the receiving person or platform mainly needs the line on the map.
The bottom line on FIT vs TCX vs GPX
FIT vs TCX vs GPX is not about choosing the most advanced file every time. It is about matching the format to the job.
For completed ride history and serious training analysis, FIT is the default. It gives your data the best chance of surviving the move from device to platform to archive, as long as the source recorded the data and the destination imports it properly.
For compatibility and some route or course workflows, TCX still has a role. It is especially useful when FIT is not accepted or when it carries cues better in a specific device setup.
For routes, tracks, and broad sharing, GPX remains valuable. Just do not mistake a GPS track for a complete ride record.
The hierarchy is straightforward: FIT for the ride, TCX for compatibility, GPX for the line. Use that, check the import before trusting it, and you will avoid most of the data-loss problems that make cycling file formats feel more complicated than they need to be.


