You send a run to your coach. The correct route appears on the map, but laps and some sensor curves disappear. Another file preserves heart rate, yet the receiving app shows different time and distance figures. This does not necessarily mean the export went wrong. You may have transferred a different data layer, or the receiving programme may have interpreted only part of the file.

FIT, GPX and TCX have three different structures, but none of their extensions is a complete contents list. The useful question is what you want to preserve: the route, the detailed recorded workout or a task to follow? We start with the formats’ official descriptions and current Strava exports, then use original checking examples to explore how to avoid unnoticed data loss.

Three separate data layers can belong to the same run

The first layer is the spatial story: where you went, where you turned and which points you passed. The second is measurement over time: what happened when and which heart-rate, pace or other sensor data the device recorded. The third is workout structure: which laps, intervals or planned instructions are associated with the activity. These may be connected, but they do not represent the same information.

In an original imaginary example, you run the same five-kilometre loop easily on one occasion and with short fast sections and stops on another. The line on the map could be identical. Workout time, laps and sensor history nevertheless differ. If you transfer only the route, the structure of the second session cannot be deduced from the map. The line does not inherently contain why or how you ran it.

First identify the purpose of the transfer. If a friend needs the weekend route, they may not need the entire sensor history. If your coach is analysing exertion intervals, the map alone may be insufficient. If you want instructions for your next session on your watch, the track of a previous run is not automatically an executable workout plan.

FIT Activity can preserve a detailed activity structure

The official Garmin FIT Activity description defines distinct message types. Record can store data at individual time points, such as position or a sensor value; Lap and Session describe summary sections. Events and device information can also be included, some optionally. A detailed format does not guarantee every device filled every possible field.

You also need to check the file type: FIT does not mean only a completed activity; separate course and workout file types exist too. Activity data can contain a plan associated with the task, but that does not automatically make a completed run the same as a separate workout to execute. Beyond the extension, the file’s own type and actual messages matter.

In an original transfer example, a run has five manual laps and an overall distance, plus individual heart-rate samples. An original file that actually stores all three may preserve more than a copy made only from points. The receiving programme still has to recognise those parts, however. A rich file structure and a complete import are two separate conditions.

GPX centres on spatial description, but can be extended

The Topografix GPX 1.1 schema defines points, routes and tracks. Track points have latitude and longitude, and can also have time and elevation. The document allows extensions from other namespaces. Saying “GPX never contains heart rate” is therefore too strong: sensor information can be included through an extension, but both exporter and receiver must support it.

A route and a track are not exactly the same either. The former can describe successive points leading to a destination, while the latter can describe a line already travelled. The schema allows a track to be divided into separate segments, which can also mark interruptions. A stream of map points is not, on its own, the same as a running watch’s manual or automatic workout laps. An apparently identical line can retain a different organisation behind it.

In our original example, two GPX files contain the same hundred location points. One has a time for every point; the other does not. The first allows analysis of progress over time, while the second primarily transfers the line. The extension is the same, but usefulness differs. Merely opening the file is therefore an insufficient check if pace or stopping history matters too.

A woman runner reviews a notebook beside a café window, looking for patterns in her running log.Enlarge image
An editorial illustration created using AI showing a running-log review; not a documentary photograph.

TCX can contain activity laps and point data

The official Garmin TCX v2 schema describes activities, laps and their track points. Points may include time, position, elevation, distance, heart rate and cadence under the specified conditions; extensions can provide further data. The structure also includes separate workouts. Again, a field being possible and actually being present in a particular file are different questions.

In an original imaginary import, a programme shows the five laps and heart-rate curve but does not interpret a manufacturer-specific extra metric. This does not necessarily mean the entire TCX is faulty. The receiver may read only the elements it knows. Identify the omission specifically: which value or detail is missing, and is it present in the export at all?

The XML-based text structure has the advantage that field names can be recognised in a suitable viewer. This does not mean you need to edit the file by hand. Changing dates, units and namespaces can easily introduce new interpretation errors. Inspecting the contents is a useful check; editing should be a separate process on a traceable working copy.

Current Strava exports illustrate the app’s role

The official Strava guide dated 14 September 2026 generally recommends exporting the original: it can be downloaded in the original format uploaded. The documentation also describes separate TCX and GPX exports. The original is therefore not necessarily FIT; it comes in whichever format that activity was uploaded in.

According to the guide, Strava’s GPX export can include location, time and additional data such as heart rate, cadence and temperature. It distinguishes preservation of recorded power-meter data from estimated power. TCX export also contains power data and, on this service, is an option linked to GPS data. The old generalisation “GPX is only a map, TCX contains everything” therefore does not accurately describe current operation.

The general working rule from this example is that you need the specific service’s export description alongside the format specification. Another platform may export different fields into the same extension. App updates can change the options too. Check the data exchange using the file actually downloaded, rather than merely a ranking of formats read years ago.

What does conversion lose if it retains only the track?

In our original illustrative export, the activity consists of thirty minutes of running and five minutes stopped. Total elapsed time is thirty-five minutes and active time thirty. If the converted file retains only a line with start and end times, the receiving programme may recalculate moving time according to its own rules. The two summary values have not necessarily been preserved directly.

The same can happen with manual laps. In our imaginary example, the runner pressed the lap button when the coach signalled, not at exact kilometre boundaries. If the destination app creates kilometre splits from the new line, its table may resemble a lap list while showing a different structure. Splits generated afterwards by the programme and laps marked on the original device are separate data layers.

Missing data does not automatically reappear through conversion back. If a file contains only position and time, giving a version made from it a FIT extension does not restore heart rate or original lap markers that were not preserved. The packaging may be richer while the information inside is not necessarily greater. Conversion is not the same as recovering a lost measurement.

Compare five things before the transfer

First check total distance and the type of time stated. In an original example, the original watch shows 10.00 kilometres and sixty minutes of active time, while the import shows 9.86 kilometres and sixty-two minutes of elapsed time. Both the distance calculation and the concept of time may differ here. It is wrong to dismiss both differences under one label of an “inaccurate export”. Investigate each field’s origin and meaning separately.

Second, check the number and boundaries of laps; third, the important sensor curves; fourth, a clearly recognisable stop or fast section. Fifth, check start time and time zone too. Together, these make it easier to identify a display difference, partial import or genuinely missing data. One matching summary number does not establish that the whole activity was preserved.

Try the process with a short, familiar activity before converting an entire archive the same way. A useful sample might be one of your own runs with a lap marker, a short stop and recorded heart rate, if you normally use those features. You do not need a separate workout for an export. Existing data you know well is often enough to understand the process.

While reviewing training-log data, a runner adds a separate note to an uncertain measurement.Enlarge image
An editorial illustration created using AI showing traceable marking of suspect sensor data; not a documentary photograph.

Keep provenance and version alongside the filename

Keep the original download unchanged, and give the converted file a separate name or folder. In an original naming example, “original”, “sharing track” and “coach import trial” distinguish three different roles. You can add the download date and source service. This is much more useful later than several identically named files whose origins you no longer know.

The data included should match the purpose of sharing. A complete running file may contain a precise route, time and sensor data. If the group needs only the loop after the meeting point, sharing your departure from home and entire personal measurement may be unnecessary. Check the sharing copy separately for that reason. The public app view and the downloaded file’s actual contents are not necessarily identical.

The extension alone does not settle the privacy decision. GPX can contain precise time and location too, while a detailed FIT may include more personal device or sensor information. The question is who needs what and what the particular file transfers. Keeping the original privately and sharing a targeted copy can be compatible tasks.

Which should you choose for the situation?

For a detailed personal archive, keeping the original activity file is a good starting point, with a readable summary alongside it if needed. To share a route, a track format handled well by the destination app may suit, with the actual extensions checked. For coaching analysis, choose an export you have tested on a sample to confirm that the receiver correctly reads the important time, lap and sensor data too. Let the task drive the decision rather than a generic contest between files.

If the system accepts only another format, conversion may be a necessary intermediate step. Document what was retained and what the importer recalculated. Keep the original version for later checks. Successful upload is technical confirmation; matching content is a separate quality check. Both are needed if you want to rely on the data later.

FIT, GPX and TCX therefore define possibilities, not automatic completeness. The recording device, exporter and receiving programme together determine what your run’s digital copy contains. Keeping route, measurement history and workout structure distinct makes it easier to choose a suitable format. A checked sample file proves more than the extension alone.

Sources

Helpful? Pass it on.