Synchronizing Insta360 Camera with GPS Track [Solved]

[GotoesUser]

Hi, I discovered your tool through a YouTube video showing how to sync Garmin data with Insta360 footage. I tested it with a .gpx file first to make sure it worked well, and it did; the data and video sync'd after adding in the offset. I then donated $10 to get access to exporting files as .fit, but there seems to be no change between the original file and the modified file when I add it to the video. The Activity Start Time does show the new, changed start time from using the TimeShift feature, but the data is still sync'd to the video the same way as the original, unaltered file.

[fulmar2]

Hmm, that doesn’t seem right; the time shift should work just right. Also, why do you need FIT vs GPX for this goal? Did it work correctly for GPX and not for FIT? Please help me understand and maybe send me a test file please. I’m not aware of any issue with the time shift feature so I’d like to investigate.

[GotoesUser]

To be more clear:

I'm uploading a *.fit file from my Garmin Edge Explore 2. At first, I didn't have the option to export as a *.fit file, so I was choosing *.gpx (Insta360 Studio only supports .fit and .gpx).

The *.fit file contains power and cadence data that the *.gpx does not. At least, it won't display cadence and power in Insta 360 unless I use a *.fit file.

Anyway, I uploaded the *.fit to test. Changed the Activity Start time from 8/22/2026 9:06:40AM to 8/22/2026 9:06:29AM (11 second offset), exported as *.gpx and my data was correctly synced. However, when I export it as *.fit, it shows that the Activity Start Time has changed (from 9:06:40 to 9:06:29) but it displays data at the same time stamps in the video editor as the original, unedited file.

[fulmar2]

First, thanks for bringing this to my attention. I did some work yesterday, last night and finally finished this morning… but I don’t know for sure if I fixed it.. You’ll have to test for me.

1) I noticed that GOTOES does properly shift the RECORDS when you do a time shift. The records also match the GPX timestamps.. so from that point of view, GOTOES was consistent between FIT and GPX… BUT there are other “clocks” in the FIT file that GOTOES was not shifting. My only guess is that Insta360 somehow looks at these other clocks when it has a FIT available… but defaults to the basic records in the case of GPX (because that is all that is available)… This is just a guess that I hopefully resolved this morning.

2) GOTOES does insert Heart Rate and Power into GPX. However it uses a less common schema called “Cluetrust”. This is supported by Strava… and theoretically could be used by insta360 if they wanted… then insta360 could read that data and you would not have to donate to GOTOES just to get the FIT export. You’d have to write them to support that schema, though. For them, this should be an easy upgrade.

3) GOTOES does have a “randomize ID Tag” feature - this is a way to bypass Strava’s “duplicate activity” “feature”. Strava just looks at the very start of a file to see if it matches anything that has already been uploaded. GOTOEES tweaks with that slightly - just a few seconds - so that user can upload “duplicate” activities. I put this as default because I get so many people trying to leave their old (pre GOTOES) files on Strava until they run it through GOTOES.. or they just don’t know/read the instructions. It’s definitely a pain, because it does very slightly change the timing of the activity - but overall it results in me having fewer support calls. This could POSSIBLY be messing with your insta360 adjustment - because you’re only changing by 10 seconds… so my advice for you would be to uncheck that “Randomize ID Tag” box.

Please let me know if that all fixes this for you and if you see anything else. Thanks again!!

[GotoesUser]

Thanks for the detailed and quick response.

I just tested it, and so far, so good! The insta360 *.fit file IS syncing up with my video now after changing the timestamp.

You're awesome, thank you!