What is GOTOES?
GOTOES is a set of ten browser utilities for the moment your data ends up in more than one place. Your bike computer recorded the route but the heart rate strap was paired to your watch. The power meter dropped out for ten minutes. The FIT file is corrupt and Strava rejects it. A race went through a tunnel and the GPS came out the other side in a different postcode. Each tool does one of those repairs, in the browser, and hands you a file to upload.
The flagship is the merger, and its description is the clearest statement of the whole site's purpose: it combines heart rate, power, position, cadence, elevation, distance and temperature from separate files into one, and repairs corrupted FIT files while it is at it. Feed it up to twenty files and it works out how to lay their streams on a single timeline. If you have a GOTOES account you can pull the source activities straight from Strava rather than exporting them by hand.
It is not an analytics site and it does not keep a copy of your training. There is no dashboard of your season, no charts, no social feed. It is closer to a workshop bench: you bring a broken file, you leave with a fixed one. The site has been running since 2015, it is maintained by one person, and the changelog is the best evidence of that. The merger is on version 43.4, dated September 2, 2026, and recent entries cover things like Insta360 camera timestamps and an iOS file-picker bug.
Key Features
Merge and repair FIT, GPX or TCX
The core tool. It combines heart rate, power, position, cadence, elevation, distance and temperature across files, so a route from your head unit and a heart rate trace from your watch become one activity. It also repairs corrupt FIT files that upload as errors, includes a point editor that flags spurious GPS spikes on a map and deletes them in bulk, and can export to XLSX as well as the usual formats. Free accounts get 20 files per job at 14MB each and 19MB total; donors get 28MB and 38MB.
Race Repair, for when the GPS gave up
Give it exactly two files, your original activity with its heart rate and cadence, plus a course file for the event, and it builds a synthetic position track that fits your real start and finish times. Then it hands you off to the merger to combine the streams. This is the fix for a marathon where the watch lost signal among tall buildings but you still have the official route.
Timestamps and time shifting
Creates timestamps on files that have none, shifts an activity to the correct time, and rebuilds missing sections. Useful for indoor and virtual rides, where Strava cannot infer a timezone from GPS coordinates at all.
Shrink a FIT file under Strava's limit
Keeps every second, fifth, tenth or twentieth record, for reductions of 50 to 95 percent. The use case is a very long or very high-frequency recording that Strava or Garmin refuses to accept.
Garmin Connect to Strava, activity by activity
The standing Garmin-to-Strava auto-sync is all or nothing. This tool lets you pick which activities to send, which is how you keep a treadmill test or a lawn-mowing "ride" out of your Strava feed. It needs a GOTOES account with Garmin connected.
Upload to Strava by email
Email a FIT, GPX or TCX file as an attachment from your registered address and it lands in your Strava account, with the subject line becoming the activity title. You can connect up to two Strava accounts and send to both at once. Strava retired its own email uploader years ago.
Bulk upload from a spreadsheet
Fill in a Google Sheets or Excel template and it creates the manual activities in Strava in batch. This is the tool for backfilling years of logbook entries, and the sport names have dropdown validation because they have to match Strava's exactly.
Inspect and convert
A FIT file viewer for reading the actual fields and diagnosing why something is wrong, a FIT-to-CSV converter for pulling record streams into a spreadsheet, and a waypoint filter that strips a POI file down to the points near your course.
Who It's For
- Anyone running two devices, where the route lives on one and the sensor data on the other
- Racers whose GPS died mid-event but who have the official course file
- Garmin users who want to choose what reaches Strava instead of syncing everything
- People backfilling history, whether from a spreadsheet of old logbook entries or a pile of files
- Anyone Strava has rejected, with a corrupt FIT or a file over the size limit
