How to Merge Two Strava Activities Into One
You rode once. Strava shows it twice. Your watch died at mile 30, or you hit stop at lunch and the device saved two rides in place of one. Now your feed has two half rides, your friends have liked the wrong one, and your longest-ride stat is gone.
The first thing to know: Strava has no merge button. Its help pages say so, and they point users to outside file tools to join the files first. That is not a flaw in your account. It is how the platform works. Activities are stored as fixed files, and the platform will not stitch two of them into one.
So the real job is done at the file level, before Strava ever sees the ride. You take the two files your devices saved, merge them into one file, and upload that one file. Then you delete the two split ones. This guide walks through each step, plus the traps: uploads that clash, time that counts twice, and comments on the wrong half.
If your two files are still on your computer as GPX, the join itself is covered in depth in how to merge two GPX files into one activity. This guide starts where that one ends: with one merged file in hand and a Strava account to fix.
Why Strava will not merge them for you
A training platform is a store of files. Each activity you see is one file, read once, with its totals worked out at upload. The platform has no tool that opens two stored files, joins their points, and writes a third. That is true of Strava, and it is true of Garmin Connect too. Both point you to file tools when you ask.
There is a fair reason for this. A merge is a judgment call. Which file wins where they overlap? What if one has heart rate and the other has power? A platform that made those calls for you could wreck data you care about. So the merge is left to you, with a tool built for it, where you can see the health check and the totals before anything is final.
The good news: platforms accept a fresh upload of a merged file with no fuss. A FIT or GPX file that is well formed uploads like any ride your watch made. The whole fix takes minutes, and most of it is care, not work.
This is not a rare edge case. Any rider who trains for years will hit it: a battery that fades at hour four, a unit that locks on a climb, a café stop that ends the file. Event riders hit it most — a 200 km day is long enough for two files on many units. The split is a fact of how devices save data. The only real choice is what you do with the pair once you hold it.
It also helps to know that the two halves are not worth less as data. Each half is a true record of its span: its points, its times, its streams. Nothing inside them is second-rate. The flaw is pure shape — one ride wearing two coats. Shape is the cheap kind of flaw. It can be fixed whole, with no loss, which is more than can be said for most data problems.
Your options, side by side
There are three ways people try to fix a split ride. Only one of them ends with a true single activity.
| Option | How it works | The catch |
|---|---|---|
| Leave both halves | Do nothing; the log keeps two short rides | Stats, maps, and longest-ride marks stay wrong |
| Delete one half | Keep the long half, drop the short one | You lose real miles and real time |
| Merge the files, upload once | Join the raw files, upload the merged file, delete the pair | Takes a few minutes of care — the only full fix |
You will also see advice to use a platform's crop tool or to edit the start time of one half. Those tricks change how a single activity looks. They cannot join two activities, and a wrong start time can make a later upload clash. The file merge is the sound path.
A word on the export choice in step one, since it shapes the result. “Export original” gives you the file as the device wrote it — FIT, most times, with every stream the device held. “Export GPX” gives you a track made from that file: fine for a map, thin for data. If the ride held heart rate or power and you want them in the merged file, take the original. You can always make a GPX from a FIT. You cannot make the lost streams come back the other way.
If the two halves are already split across two platforms — one half on Strava, its mate on Garmin — pull both files to one place first. The merge does not care where a file spent last night. It cares that the pair is the true pair, whole and raw. Ten minutes of tidy file work here is the whole cost of the fix.
Step by step: merge first, upload once
Step one: get the raw files. If the rides came from a Garmin or Wahoo, pull the FIT files from the device or from the app's export. If they are on Strava now and you kept no local copy, open each activity and use the export GPX or export original choice. The original file is best — it holds the most data.
Step two: merge the files. In FitMerge, upload both files, read the health check, and pick stitch in time order for parts of one ride. If the two files ran at the same time on two devices, that is a different job — see how to combine FIT files from two devices. Download the merged file with its totals block.
Step three: check the merged file. Points out should match points in, the map should be one line, and the start and end times should be the true ones. Step four: upload the merged file to Strava as a new activity, with the title and notes you want. Step five: once the new activity looks right, delete the two halves. Do it in that order — new one first, old ones last — so you are never left with no copy at all.
Photos ride along with activities, and they do not move on their own. If you shot photos mid-ride and they sit on the half you plan to delete, save them first, then add them to the merged activity once it posts. The same goes for a title you liked and notes you wrote at the end of the day — copy the text before the delete, paste it onto the whole ride. A minute of care, and the record keeps its color as well as its miles.
There is one case where you should not merge at all: when the “two rides” were in fact two rides. A morning spin and an evening spin on the same day are two entries by right. Merging them would forge a ride you never did. The test is the clock and the place: parts of one ride meet at a seam — one ends where the next begins, in time and on the map. Two true rides have a real gap, a change of clothes, a meal at home. If the seam is not there, leave the pair alone.
What happens to the two old activities
When you delete the two halves, their likes and comments go with them. There is no way to move them to the merged activity. If a half holds a comment thread you care about, note it before you delete. Most riders find the clean record worth the loss, but it is your call, and it can only be made once.
Your totals for the week will dip for a moment and then come back right. While both the halves and the merged file are live, the miles count twice — that state should last minutes, not days. Segment times are worked out fresh for the merged file, and they will be your true times for the whole ride, often better than the half times were.
One more warning: do not re-upload the merged file twice. Platforms spot a file whose points they have seen and may block it as a copy, or worse, post it twice. One merged file, one upload. If an upload fails, read the error first — our guide on file faults that block uploads can save you a loop of blind retries.
When the two files overlap in time
A split ride is back to back: file one ends, file two starts. But some pairs overlap. You started the watch and the bike computer, stopped one late, or a restarted device re-saved the last minutes. If you stitch an overlap as if it were back to back, the overlapped minutes count twice — twice the miles, twice the points, a kink in the map.
The health check shows overlap plainly: file two starts before file one ends. For true overlaps, merge stream by stream in place of a stitch. Each time point is kept once, and each stream is taken from the file you trust for it. Our guide on how to fix a corrupt FIT file covers the worse case, where an overlap came from a device fault that also broke the file itself.
Overlap has a second, quieter form: the short seam. A device that restarts may hold the last two minutes of the ride in both files. Stitched blind, those two minutes count twice — a small lie, but a lie with a shape: the map doubles back on itself for a short stretch. If your merged file shows a spike of doubled road near the seam, this is why. A stream merge, or a trim of the repeated tail off one file, sets it right.
How much overlap is too much? Even a few seconds matter less for miles than for trust. The point of the merged file is that it can stand as the record. A seam you know is doubled is a seam you will doubt on every read. Take the extra pass. It is the last pass — once the pair is joined clean, the ride is done being a problem.
One platform habit is worth a note here: segments and leaderboards read the merged file fresh. Your times on the day's known segments will post from the whole ride, which is as it should be — the halves each held half a segment picture. If a segment time looks off, check the seam span first. A clean seam gives clean segment math.
If the merged upload is rejected
A clean merged file uploads like any other ride. If yours is turned away, the fault is in the file, not in your account. The usual causes are a missing ending, a bad checksum, or points with no time stamps. Each has a plain fix, and we walk through them in why a Garmin activity won't upload — and how to fix the file. The same faults block a Strava upload in the same way.
Keep the raw files until the merged activity has sat in your log for a day and you have seen it on the map. After that, the pair is just clutter. One ride, one file, one upload — that is the end state you want for every ride, split or not.
The short version
Strava will not join two activities, but you do not need it to. Merge the raw files into one, check the totals, upload the one file, then delete the halves. Start with your two files — the health check flags overlaps before they can count your miles twice.
Sources and further reading
- Exercise and Physical Fitness — MedlinePlus — The National Library of Medicine's plain guide to exercise types and their gains.
- Physical Activity Guidelines: Current Guidelines — health.gov — The current U.S. guidelines for weekly activity — the base your training log is built on.
- GPS Accuracy — GPS.gov — The U.S. government's own page on how exact GPS fixes are, and what makes them drift.