Running GPX Generator

Running GPX Generator: Build Custom Run Routes with Realistic Data

Runners usually start searching for a running GPX generator after something ordinary goes wrong. Maybe the watch never locked GPS, maybe the phone stayed in low-power mode and never recorded the route, or maybe the whole session happened on a treadmill where there was no map data to save in the first place. In each case, the run itself is real, but the activity file is missing.

That is where a custom GPX file for running becomes useful. A good file can rebuild the route on real streets, carry sensible timestamps, and include training context like pace, elevation, and heart rate. Instead of logging a blank entry, you can create a complete running route GPX that fits the way the workout actually unfolded.

ForgePace is built for that practical workflow. You choose the start point, set the duration and target pace, add heart rate if needed, and export a file that is ready for the next step. If you also need help after a missed recording, the guides on forgotten Strava activities and manual uploads fit directly into the same process.

Missed recording

You completed the run, but your watch battery died or the app never started.

Treadmill session

You have duration and effort data, but no outdoor GPS track to upload later.

Fitness check

You want a clean route file that reflects a controlled test with sensible splits and heart rate.

What is a GPX running file?

A GPX running file is an XML-based track that stores the ordered points of a run. At minimum, those points contain latitude, longitude, and timestamps so the route can be drawn on a map and timed from start to finish. Most useful running files also carry elevation, because climbs and descents affect both pace and heart rate in ways that are easy to spot later.

When a running GPX file is built well, it does more than sketch a line. It gives each point a believable time sequence, includes altitude changes that match the terrain, and can store heart rate through extensions. That combination is what turns a simple map trace into something that behaves more like a normal activity file in Strava and related tools.

GPX is especially useful when route geometry matters most. If you want a file that follows roads cleanly and uploads without much friction, it is a strong default. If your priority is richer workout structure, you may eventually prefer TCX, but GPX remains the fastest route-first format for many running use cases.

Pace and heart rate: what makes a run look real

Real runs are not perfectly flat lines. Pace moves a little as corners, crossings, small hills, and fatigue change the effort. Heart rate usually lags behind pace rather than matching it point for point. If the runner speeds up, the heart rate tends to rise a bit later. If the route tilts uphill, pace may drift slower before heart rate settles higher.

That organic variation is why clean files feel more believable than rigid ones. A route with the same split every minute and a perfectly stable heart rate does not reflect how most runs unfold outdoors. Better files include subtle movement: slight pace drift on climbs, a short settling period at the start, and heart rate values that respond with realistic delay.

ForgePace is useful here because it starts from practical training inputs instead of raw XML. You can aim for a target pace, then let the generated route and surrounding data reflect the kind of variation runners expect to see in a normal effort.

Treadmill runs and GPS

The treadmill problem is simple: the workout exists, but there is no outdoor GPS track. Watches sometimes estimate distance from cadence, but many treadmill sessions still end with no map data that can be uploaded later. That becomes frustrating when you want your training history to stay complete.

A running GPX generator fills that gap by pairing a sensible route with the duration and pace you actually ran. Instead of a blank manual entry, you get a route file with timestamps, elevation, and optional heart rate context that can sit more naturally alongside your outdoor sessions.

How to generate a running GPX route on real streets

The easiest way to create a running route GPX is to start with the parts of the workout you actually know: where it began, how long it lasted, and roughly what pace you held. ForgePace uses those inputs to build a route on real roads rather than forcing you to manually edit dozens of track points.

1. Choose the starting point

Enter the neighborhood, road, or landmark where the run should begin. ForgePace uses that location to anchor the route on real streets instead of drawing a vague straight line.

2. Set duration and target pace

Pick how long the run lasted and the average pace you want the file to reflect. This sets the distance, timestamp spacing, and the overall rhythm of the activity.

3. Add heart rate context

Include average heart rate when you want the file to look more complete in training platforms. That extra context matters for athletes rebuilding a treadmill session or a missed outdoor run.

4. Export and upload

Download the GPX file and upload it through Strava's manual import flow. If you need a more structured workout container, you can switch to TCX from the same ForgePace workflow.

If you are deciding between formats, compare the route-first GPX generator with the more workout-structured TCX generator. The input flow is similar, but the resulting files serve slightly different goals.

TCX vs GPX for running on Strava

GPX is usually the simplest choice when you want to rebuild the route itself. It handles coordinates, timestamps, and elevation well, and it is widely accepted in manual upload flows. TCX can be the better format when you want richer workout structure and tighter handling of training metrics.

The right answer depends on the session. For a missed run or a treadmill file where map trace matters most, GPX is often enough. For a workout where the training fields matter just as much as the route, TCX may be worth using instead. The full comparison is in the ForgePace guide on TCX vs GPX.

Quick CTA

Build your run file fast

If you missed a recording or trained on a treadmill, you do not need to rebuild the file manually. Start from the homepage, enter the run details, and create your run file in under 2 minutes.

FAQ

Can I create a fake run on Strava?

What most runners actually need is a way to recreate a real session that did not record properly. If the run happened but the GPS file is missing, you can rebuild a route file and upload it manually. ForgePace is designed for that recovery workflow, especially for treadmill sessions and forgotten recordings.

How do I upload a GPX run to Strava?

Open Strava on desktop, go to the manual upload screen, choose your GPX file, review the route and activity details, then save it. If you need the full step-by-step process, the ForgePace guide on manual uploads covers the exact flow.

What pace should I set for a realistic run?

Start with the pace you could actually hold for that distance and terrain. A steady easy run should not carry interval-like speed changes, and a hilly route should not look perfectly flat in pace. The most convincing choice is normally your true average pace with small natural variation around it.