Strava Import Guide

How to Upload a TCX File to Strava

TCX stands for Training Center XML. It is a structured activity format widely used by Garmin, Wahoo, and other GPS training workflows, and it is fully supported by Strava for manual uploads. If you have exported a workout from a watch, bike computer, or third-party tool, a `.tcx` file is often the cleanest format to import because it can carry both the route and the training context.

Uploading a TCX file to Strava is usually straightforward, but it helps to know what the platform expects before you start. The steps below cover the manual upload flow, what happens during processing, and what to do when the source file has missing GPS data or needs to be rebuilt from scratch. If you are comparing formats first, the ForgePace guide on GPX vs TCX explains when each one makes more sense on Strava.

For many athletes, the manual upload option is useful when device sync did not work, when an older activity needs to be imported later, or when a custom workflow produced the file outside the native Garmin or Wahoo ecosystem. As long as the TCX file is structured correctly, Strava treats it as a standard activity import rather than a special-case format.

Generate your custom TCX file with ForgePace Read the Strava Editor Guide

Garmin Files

Manual imports work well for workouts exported from Garmin watches, Edge devices, and related training software.

Wahoo Files

Wahoo-generated TCX exports follow the same broad workflow when you want to upload outside the native sync path.

Custom Files

ForgePace can generate a clean TCX file when you need more control than a device export gives you.

Step-by-step: Upload a TCX file to Strava

1. Go to Strava and open Upload Activity

Log in on strava.com, then open the Upload Activity flow from the top-right menu. The manual import entry point is the large orange upload button on desktop.

2. Select your .tcx file

Choose the TCX file exported from your Garmin or Wahoo device, or any custom file you created with ForgePace. Strava accepts TCX as a standard activity import format.

3. Wait for processing

After selection, Strava validates the file and builds the activity preview. Processing can take one to two minutes depending on file size and server load.

4. Edit the activity details

Before saving, review the title, description, date, and activity type. This is the moment to correct anything that looks generic or does not match the workout.

5. Save the activity

Confirm the import to publish it in your account. Once saved, the session appears in your Strava feed and training history like any other uploaded activity.

In most cases, that is all you need. The important part is that the file contains a valid timeline and route track so Strava can parse the activity correctly. A clean TCX file typically produces a smoother import than a heavily edited export with broken XML or missing points.

If you want to adjust an existing activity file before uploading it, the ForgePace article on the Strava activity editor workflow covers that file-first approach in more detail.

It is also worth checking for duplicate uploads before saving. Strava may reject a file when the timestamps and distance closely match an activity already present in your account. If that happens, review the original export, confirm the workout date, and make sure you are importing the intended version of the session.

What if my TCX file has no GPS data?

Strava can only map the activity if the TCX file contains valid track points. If the upload succeeds but the route is empty, or if the import fails entirely, the file may be missing GPS data, timestamps, or a coherent point sequence.

In that case, it is often faster to rebuild the activity than to keep patching a broken export. ForgePace is useful when you need to generate a cleaner file with route structure and training fields aligned for upload. Start with the TCX generator if the original source no longer contains usable GPS data.

This is especially relevant for indoor files, partial exports, or workouts recovered from older software backups. If there is no reliable track to recover, generating a fresh file is usually more predictable than trying to repair every missing point by hand.

Create a custom TCX file from scratch

When you need a custom activity rather than a device export, ForgePace Generate gives you a way to build a TCX file from scratch. That is useful for testing workflows, recreating a route, or preparing a structured activity with a cleaner import path into Strava.

The generator is designed for route-based activity files that need to look consistent across platforms. If you are deciding whether a simpler route file would be enough, compare the formats in the GPX vs TCX guide.

FAQ

Does Strava accept TCX files?

Yes. Strava accepts TCX files for manual imports, alongside other common activity formats. TCX is a standard Training Center XML format used by Garmin, Wahoo, and many training tools.

What's the difference between GPX and TCX on Strava?

GPX is mainly route geometry and track points. TCX can also include timestamps and structured workout fields such as heart rate, cadence, or power. If you want a deeper comparison, read the ForgePace guide on GPX vs TCX.

Why is my TCX upload failing?

The most common causes are malformed XML, missing timestamps, duplicated points, unsupported sensor fields, or no valid GPS track. If the source file is incomplete, rebuilding it with a clean route and consistent metrics usually solves the issue.

Can I upload a TCX file without using Garmin Connect?

Yes. Manual upload on Strava does not require Garmin Connect. Any valid TCX file can work, whether it comes from a device export, a third-party app, or a custom generator.

Generate your custom TCX file with ForgePace

Build a TCX file with route data that is ready for manual Strava import, then refine your workflow with ForgePace guides and tools.

Open the TCX Generator Explore More Strava Guides