Supported GPS formats

Keep different track files in one archive.

MTL Explorer reads nine common GPS and activity formats, from GPX and FIT to KML and IGC. All your tracks end up on the same map, whatever device recorded them.

MTL Explorer map showing imported GPS tracks from one archive
Imported activities share the same map, filters, and statistics views.

File format reference.

On a small screen, scroll the table sideways to see all columns.

Recognized file formats and their import paths
FormatExtensionProcessingCommon source
GPX.gpxRead directlyGPS devices, route planners, and activity exports
FIT.fitConverted automaticallyGarmin and other fitness devices
TCX.tcxConverted automaticallyTraining Center activity exports
KML.kmlConverted automaticallyGoogle Earth and mapping tools
KMZ.kmzUnzipped and converted automaticallyCompressed Google Earth files
IGC.igcConverted automaticallyGliding and flight loggers
NMEA.nmeaConverted automaticallyRecorded NMEA 0183 GPS sentences
GeoJSON.geojsonConverted automaticallyGIS and web mapping tools
GDB.gdbConverted automaticallyGarmin MapSource databases
The extension is only the first check. A file must contain usable track geometry and valid data for its format. Invalid, empty, or unsupported variants can be reported as failed imports.

What gets imported?

MTL Explorer reads positions, timestamps, elevation, and the track name and description. What you get depends on what your file contains.

Data used by the GPS track import
DataNative GPXFIT, TCX, KML/KMZ, IGC, NMEA, GeoJSON, GDBWhat to expect
Track positionsGPX track points and route pointsTrack or route geometry emitted by conversionNeeded for every track. Files with only single waypoints don't create a track. Planned routes without times show on the map, but without speed or duration.
TimestampsPoint times when presentPoint times retained by conversionNeeded for speed, duration, and segment times. Routes exported from a planner often have no times.
ElevationPoint heights when presentHeights retained by conversionUsed for elevation profiles and climb. Converting a file can't add heights that aren't in it.
Name and metadataTrack name, description, type, creator, and supported metadataSupported fields emitted in GPXSome device-specific labels may look different.
Sensor extensionsHeart rate, cadence, and power in the file are not importedNot importedKeep the original file for these values. MTL Explorer estimates power and energy, and can add heart rate from Google Health.
Original fileRetainedRetainedYou can download the original file or a GPX version from Track Details.
Try one file before importing your whole archive.Check the map, date, elevation, and graphs. Keep your original files. Try the synthetic GPX example.

If a file has problems, Review shows what's wrong. There you can download it to fix it in another tool, or hide it from the map or statistics. See Review.

Choose how to add files.

All files are processed the same way, whichever method you use.

Watch folder

Copy files into the ./data/gpx/ folder. MTL Explorer picks up new files automatically.

Settings upload

Open Settings → Import & sync and upload your files from the browser. Unzip ZIP archives first.

Garmin sync

Optionally, download your new Garmin Connect activities automatically.

Manual rescan

If new files don't show up, for example on a network drive, use Settings → Maintenance → Rescan GPS. Check the result in Settings → Processing.

After import

One archive for all your tracks.

Your original file stays where it is. After import, MTL Explorer:

  • finds duplicates and failed imports,
  • detects the activity type, keeping any type you set yourself,
  • prepares the track for fast display on the map,
  • offers the original file and a GPX version for download.
MTL Explorer track details and graphs for an imported activity
Track Details after a file has been processed.

Continue with related guides.