Add your TCX file
Drop one or more .tcx files onto the converter above, or browse for them. They load into browser memory only — nothing is uploaded, so there is no size-based pricing and no server queue.
Converting a .tcx font to .gpx repackages the same glyphs and metrics for a different delivery target. Free, private, and validated — the file never leaves your browser.
Batch files can each use a different output. Nothing uploads for local conversions.
Working inputs include camera RAW, browser-local audio/video, PDF, CBZ/CBR comics, office documents, ebooks, markup, 3D models, structured text, images, and archives.Converting a .tcx font to .gpx repackages the same glyphs and metrics for a different delivery target. A .tcx file is Garmin's Training Center XML: an activity file that records not only where you went but how the effort was structured — laps, heart rate, cadence, power and calories — alongside the positional track. It is a fitness format first and a geographic one second.
A .gpx file is the GPS Exchange Format: an XML schema for waypoints, routes and recorded tracks, where every point carries a latitude and longitude and may carry elevation and a timestamp. It is what a GPS watch or handheld exports. For this route the practical draw is universally supported across GPS devices and fitness platforms and distinguishes planned routes from recorded tracks, which matters in practice — balanced against verbose XML — large for the number of points it carries, which is worth knowing before you commit a large batch.
The practical trigger for this conversion is usually a mismatch: with .tcx, more verbose than GPX for the same track. Switching to .gpx buys you universally supported across GPS devices and fitness platforms, which is why it is the better fit for exporting a recorded run, ride or hike from a watch or phone. Because the conversion runs locally, trying it costs nothing but a few seconds of compute on your own machine.
| Aspect | Training Center XML (.tcx) | GPS Exchange Format (.gpx) |
|---|---|---|
| Format type | Text-based — characters and structure, so there is no visual quality loss | Text-based — characters and structure, so there is no visual quality loss |
| How it stores data | activities contain Laps, and Laps contain a Track of Trackpoints — a stricter hierarchy than GPX's | three distinct concepts: wpt waypoints, rte planned routes, and trk recorded tracks made of trkseg segments |
| Strongest at | exporting a structured workout from a Garmin device | exporting a recorded run, ride or hike from a watch or phone |
| Weak spot | more verbose than GPX for the same track | verbose XML — large for the number of points it carries |
| Metadata | positions, timestamps and altitude are preserved. Heart rate, cadence, lap aggregates and sport type have no equivalent in GPX, GeoJSON or KML and are not carried across | coordinates, elevation, timestamps and point names are preserved. Vendor extension data such as heart rate is not carried into targets with no equivalent field |
Drop one or more .tcx files onto the converter above, or browse for them. They load into browser memory only — nothing is uploaded, so there is no size-based pricing and no server queue.
Select .gpx in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if GPX is selectable, the route is real and validated.
Press Convert. The font tables are parsed and rewritten locally with fonteditor-core; glyph outlines, hinting, and kerning survive the trip.
Each result is signature-checked before the download unlocks, so a failed encode can never masquerade as a valid GPX file. Outputs keep the original filename with the .gpx extension.
There is no visual quality to lose — tcx is text-oriented and gpx is text-oriented, so the question is structural fidelity. Text, ordering, and basic structure are preserved; complex layout, embedded objects, and styling beyond the target's model are simplified.
Yes — the .tcx file is processed inside your browser tab and never uploaded. The font tables are parsed and rewritten locally with fonteditor-core; glyph outlines, hinting, and kerning survive the trip. Close the tab and the file is gone from memory.
Read by Garmin, Strava, Komoot, QGIS, Google Earth and the whole OpenStreetMap ecosystem. Novus Convert parses waypoints and track segments locally and converts to GeoJSON and KML.
It depends on the content: three distinct concepts: wpt waypoints, rte planned routes, and trk recorded tracks made of trkseg segments. Convert one representative file first and compare before batch-processing a large set.
In .tcx, positions, timestamps and altitude are preserved. Heart rate, cadence, lap aggregates and sport type have no equivalent in GPX, GeoJSON or KML and are not carried across. Re-encoding through the browser pipeline does not carry embedded metadata into the output, which doubles as a privacy scrub — check the exported file if you specifically need tags preserved.