Choosing the right video editor overlay telemetry format is crucial for the precision of your final render. Different devices export different files, and each has its strengths and weaknesses when it comes to time-alignment and data density.
GPX is the "industry standard" for GPS data. It is an XML-based format that is supported by almost every GPS device on the market. Its main advantage is its universal compatibility. However, GPX is often limited to 1Hz (one sample per second), which can result in "stuttery" gauges if not properly smoothed in your video editor.
Created by Garmin (ANT+), the FIT format is a binary format designed for fitness and sports data. Unlike GPX, it is much more compact and can store high-frequency data (up to 10Hz or more) along with specialized metrics like heart rate, power (watts), and cadence. For cycling and running overlays, FIT is the superior choice because of its data density.
Developed for Google Earth, KML is great for visualizing paths and shapes. While it works for telemetry overlays, it is often less precise than FIT or GPX for temporal data. We recommend KML only if you are exporting a path from a specialized GIS tool or Google Earth for a "map-only" overlay.
DJI drones like the Mavic, Air, and Mini series often store telemetry in an SRT subtitle file. This is a text-based format where every "subtitle line" contains a string of coordinates and altitude. ZTrack has a specialized parser for these SRT files, allowing you to burn drone telemetry onto your aerial footage without any conversion.
If you have the choice, **always go for FIT or the raw embedded metadata (GPMF)**. These formats provide the highest sampling rate, which translates to a much more responsive speedometer and altimeter on your final video. If you are stuck with GPX, make sure to enable "Cubic Interpolation" in ZTrack to fill the gaps between the 1-second samples.