Strava's built-in manual activity
Strava's manual activity tool is the simplest way to add a missing session. You can enter the sport, date, start time, elapsed time, and distance, then save it directly into your account. For athletes who only care about keeping the calendar complete, that can be enough.
The limitation is that manual entry does not rebuild the route itself. There is no map, no real road trace, and no imported file structure carrying point-by-point context. It fills the gap in your log, but it does not recreate the full shape of the activity. If you want the session to include a visible route and richer data, the better path is the file import method described below. ForgePace also covers the broader upload flow in this guide on manually uploading an activity to Strava.
The file import method
Uploading a TCX or GPX file gives Strava more to work with than a typed-in manual entry. Instead of just storing totals, Strava can read the route path, timestamps, elevation changes, and in some cases structured workout metrics. The result is a fuller activity page with a map and a more normal upload workflow.
This is the practical answer for people searching for a strava activity creator or trying to create a Strava activity without GPS hardware. You generate the file first, then import it through Strava's standard upload screen. If your priority is route geometry, GPX is often enough. If you want the route and training data to stay tightly linked, TCX is usually the stronger option.
What data you can include
A generated activity file can be much more complete than a manual note in your training log. Depending on the format and the tool, you can include the actual route on real roads, timestamps across the workout, pace or speed targets, elevation, and sensor-style fields such as heart rate or watts. That extra structure is what makes the import feel closer to a normal recorded activity.
The key is consistency. A route that follows real roads, a pace that matches the duration, and metrics that fit the terrain will create a cleaner result than a generic file with disconnected numbers. ForgePace is built around that logic so you can shape the route first and then add the workout context around it.
Route on real roads
Build the activity around mapped roads so the imported route looks like a normal ride or run instead of a rough straight-line trace.
Pace, speed & timing
Control duration, target pace, and average speed so the timestamps, split feel, and total distance stay coherent from start to finish.
Heart rate & watts
Add structured training fields when you want the imported file to carry more context than distance and elapsed time alone.
Elevation profile
Include terrain and climbing context so the route, effort, and overall activity story line up more naturally.
Step-by-step: create a Strava activity from scratch
You do not need to edit XML manually or build track points by hand. ForgePace keeps the process practical: set the location, pick the workout type, choose the timing and metrics, download the file, then import it into Strava. The workflow is fast enough for a missed weekday workout and detailed enough for a route you want to preserve properly.
1. Set the start location
Choose the city, road, or landmark where the session happened. The closer the start point is to reality, the more natural the route import will feel on Strava.
2. Pick the activity type
Select running or cycling so the route logic, timing, and file structure match the workout you want to add to your training log.
3. Enter duration and target metrics
Set the length of the session, then add the pace, speed, heart rate, or watts you want the export to reflect. This keeps the activity data internally consistent before you generate the file.
4. Download the TCX or GPX file
Use TCX when you want richer workout context, or GPX when your priority is the map and route geometry. Either way, ForgePace gives you a file ready for Strava import.
5. Import it into Strava
Open Strava's upload flow, select the file, review the activity details, and save it with the original workout date so your training history stays complete.
Tips for making it look realistic
The best generated activity is not the one with the biggest numbers. It is the one where the route, duration, and metrics all make sense together. Start with the real location, then use figures that match the kind of ride or run you actually did. That keeps the training log useful and easier to review later.
It also helps to choose the right format. GPX is excellent when the route map is the main goal. TCX is usually better when you want pace, heart rate, or watts to travel with the activity in a cleaner structured form. If you need the upload process itself, the separate article on manual Strava uploads walks through the final import step.
Complete the missing workout properly
ForgePace lets you rebuild the route, set the metrics, and export a file that fits a normal Strava import workflow. Start from the homepage, or jump straight to the TCX generator or GPX generator.
FAQ
Can you create a Strava activity without a watch?
Yes. If no device recorded the workout, you can still add the session with a generated GPX or TCX file. That approach gives you a route-based activity with map data instead of relying only on Strava's basic manual entry form.
Is it possible to add a past activity to Strava?
Yes. You can upload an activity file or save a manual activity with the original workout date and time. That makes it possible to fill in a session after the fact when you forgot to record it live.
What file format does Strava accept?
Strava accepts common activity upload formats including GPX, TCX, and FIT. For this workflow, GPX is strong for route geometry while TCX is often the better fit when you want richer activity metrics attached to the upload.