Trim Warmup & Cooldown from GPX Before Strava Upload
By TrailBlender
Why Trim Your Ride?
You finished an epic ride, but the first 15 minutes were spent doing laps around a parking lot waiting for your group. Or the last 20 minutes were a slow cooldown spin back to the car. Now your Strava stats are diluted — average speed is down, elapsed time is inflated, and the route map shows an ugly tangle at the start.
Strava's "Crop" tool lets you trim the beginning or end of an activity after upload, but it's limited. You can only trim from the edges, not remove a segment from the middle. And if you want to trim before uploading — to keep your Strava profile clean — Strava doesn't offer that at all.
How to Trim a GPX File Before You Upload to Strava
The cleanest way to trim a GPX file before you upload is to cut it before Strava ever sees it. Cut the GPX or FIT first and your distance, time, average speed and map are right from the first upload, with nothing to fix afterwards.
Already uploaded? Then the ride is on Strava and the options are different: see how to trim a Strava activity that is already uploaded. If the ride is spread over several files, merge them into one GPX before you trim.
Common Scenarios for Trimming
- Parking lot warmup — Riding circles while waiting for friends, inflating distance and creating map clutter.
- Forgot to stop recording — You finished the ride but kept recording during the post-ride coffee stop or the drive home.
- Indoor warmup on a trainer — Your file starts with 20 minutes of indoor trainer data before you headed outside.
- Cooldown spin — Easy spinning at the end dragging down your average speed and power.
- GPS wander at start — The first few minutes of GPS data are wildly inaccurate as the device acquires satellites.
The Hard Way: Editing GPX XML
GPX files are XML, so you can technically open one in a text editor, find the timestamp where your warmup ends, and delete all <trkpt> elements before that point. Then do the same at the end for the cooldown.
The problems with this approach:
- A 2-hour ride can have 7,200+ trackpoints (one per second). Finding the right timestamp in that wall of XML is tedious.
- Deleting the wrong element or leaving an unclosed tag breaks the entire file.
- You lose the visual context — there's no map to show you exactly where the warmup ends and the ride begins.
The Easy Way: Trim with TrailBlender
TrailBlender's trim tool gives you a visual editor with map and timeline, so you can see exactly what you're cutting.
- Open your GPX or FIT file in TrailBlender.
- Select the Trim tool from the toolbar.
- Drag the start handle on the timeline to skip past the warmup. The map updates in real time to show the new starting point.
- Drag the end handle to cut the cooldown. Watch the map update as you adjust.
- Review the trimmed activity — Check distance, time, and average stats to make sure it looks right.
- Export the trimmed file as GPX or FIT. Upload to Strava with clean stats and a tidy map.
Tips for Clean Trims
- Trim to a recognizable landmark — Use the map to cut at a specific intersection or trailhead, not an arbitrary time.
- Check your stats after trimming — Make sure distance, elevation, and time look correct before exporting.
- Keep the original file — TrailBlender exports a new file, leaving the original untouched. You can always re-trim if you cut too much.
- Consider splitting instead of trimming — If you did a structured workout (intervals, tempo blocks), splitting into separate files may be more useful than trimming. For a trip over several days, see how to split a multi-day ride for Strava.
- Trim after merging — If your ride was recorded in pieces, merge the GPX files first, then trim the combined file once.
Checked 19 October 2026: Strava’s manual upload limit is 25 MB per GPX, TCX or FIT file. Check the exported file size before uploading.
Sources
Frequently Asked Questions
Can I remove a segment from the middle of a ride?
Yes. TrailBlender's split tool lets you cut a ride into segments and discard any you don't want. Split the activity at the start and end of the unwanted segment, delete that segment, and merge the remaining pieces back together.
Will trimming affect my Strava segments?
Strava matches segments based on GPS coordinates, not activity start/end times. As long as the segment portion of your ride is included in the trimmed file, Strava will still match and score it correctly.
Can I trim FIT files too, not just GPX?
Yes. TrailBlender handles both GPX and FIT files natively. The trim workflow is identical regardless of format. All sensor data (power, HR, cadence) is preserved in the trimmed output.
Does Strava's built-in crop do the same thing?
Not quite. Strava's crop only works on an activity that is already uploaded. It can only trim the start or the end of the ride, so it cannot remove a section from the middle. TrailBlender trims the GPX or FIT file before you upload, can drop middle segments with split and merge, and shows a map preview of exactly what you are cutting. It works offline.
Can I crop Strava ride files before uploading?
Yes. Strava has no pre-upload editor, so crop the GPX or FIT file first: open it in TrailBlender, drag the start and end handles past the warmup and cooldown, and export. Upload the trimmed file and Strava shows the cleaned ride from the start.
Related Guides
How to Trim a Strava Activity (Crop & Fix)
Trim or correct a Strava activity: use Strava's crop tool, learn what it can't fix, then trim the original file in TrailBlender and re-upload it.
tutorialMerge Strava Activities: Combine GPX Files
Strava can't merge two activities. Export both, merge GPX or FIT files in TrailBlender, upload one ride, delete the duplicates. Free, offline.
scenarioSplit a Strava Activity: Multi-Day Ride into Daily Rides
Split a Strava activity into daily rides. Strava's web split is manual; TrailBlender finds overnight pauses and writes one file per day.
tutorialFix GPS Drift in GPX and FIT Files: Remove Spikes
Fix GPS drift and position spikes in GPX and FIT files: detect the jumps, remove them, check your distance. Tunnel gaps are not filled.