Edit, simplify and merge GPX tracks with local privacy zones
Clean up route files while keeping the difference between recorded data and assumptions visible. Inspect gaps, protect selected endpoints, and download real edited files without an account or external map service.
GPX Route Workbench
The example contains two fictional tracks, an exact duplicate, a missing elevation sample, a waypoint and sensor extensions. Try an edit, undo it, then compare actual exports.
Supported scope: GPX 1.0/1.1 UTF-8 XML only: 20 files / 12 MiB combined, 50,000 total points, 500 tracks/routes, 5,000 segments, 20,000 extension elements and 32 XML levels. Elevation magnitude up to 1,000,000 m. No DTD, external entities, KML/TCX/KMZ input, road routing or elevation lookup. Worker timeout 60 seconds; export budget 32 MiB. Simplification and privacy filtering each have a 2 million comparison budget; up to 1,000 endpoint zones per session. Complex jobs can be refused.
Recorded route sources
Required fields are marked with an asterisk.
Geometry, measurements and editing
Review your output, then save it to your device.
Make the next step clear.
Your findings, assumptions and next steps will appear here after you run the check.
GPX Route Workbench · https://gpx.kitforma.com/ · KitForma
Keep segment gaps intact
Trim revisited endpoint zones
Local geometry and real exports
Understand the evidence.
Focused guides explain the rules, the edge cases and the checks worth doing before you act.
Edit GPX tracks without inventing routes across gaps
Distinguish routes, tracks and segments before cleaning, splitting or combining a recording.
Read the guide ↗Field guide / 02Remove endpoint privacy zones before sharing a GPX file
Check later revisits, connecting edges and hidden metadata rather than trimming only the first few points.
Read the guide ↗Field guide / 03Check GPX distance, elevation and time before converting
Understand measurement assumptions, sensor preservation and the differences between GPX, KML and CSV.
Read the guide ↗Before you start
Are my private coordinates sent to a map or elevation service?
No. The preview is a local SVG geometry drawing. There are no external map tiles, reverse geocoding, route calculation or elevation requests. Files are processed in a local worker, and coordinates are not placed in the report metadata used by the shared application shell.
Does merging two tracks draw a route across the gap?
No. Merge combines the selected track objects while retaining each existing segment. Distance, elapsed intervals and exported geometry do not connect separate segments. You can split an existing segment at a recorded fix or at configured distance/time gaps.
How are endpoint privacy zones different from ordinary trimming?
Distance trim removes fixes at the beginning and end of selected tracks by cumulative traveled distance. Privacy zones remove fixes and connecting edges near the selected current endpoints across every track, including later revisits. Default privacy mode also strips names, timestamps, waypoints and extensions. Other identifiable locations can remain; the tool does not guarantee anonymity.
Will missing altitude, GPS points or time be repaired?
No. The tool only retains, removes or reorganizes existing fixes. It does not invent coordinates, fill elevation or synthesize time. Missing elevation and unzoned timestamps are excluded from the relevant calculations and reported explicitly. Simplification can remove sensor or time samples attached to removed fixes.
Do sensor extensions survive editing and export?
Supported foreign-namespace extension trees stay attached to retained points and segments in GPX. Removed points take their fields with them. Merge replaces track-level metadata/extensions, and default privacy mode strips all extensions. KML omits sensor extensions; CSV includes retained point extension JSON. The change report explains these differences.
Why can the distance or ascent differ from my watch?
Surface distance uses a mean-radius sphere and original point-to-point edges. Your device may filter GPS noise, use an ellipsoid, map-match roads or change pause handling. Ascent/descent here are unsmoothed adjacent elevation differences, and gaps or missing values are not filled. Treat them as transparent file measurements, not a promise of terrain-accurate totals.
Sources & assumptions
Formats, algorithms and supported features are documented below. Check the stated scope and inspect your output before using it.
- Topografix: GPX 1.1 schema ↗
Track segments, WGS84 coordinates, metric fields, point records and extension placement.
- Topografix: GPX 1.0 developer manual ↗
Legacy 1.0 input structure and the distinction between routes, tracks and waypoints.
- OGC: KML standard ↗
The KML output uses the standard 2.2 namespace and separate geometry placemarks.
- Google: KML reference ↗
Longitude-latitude coordinate ordering, line geometry and altitude interpretation.
- GeographicLib: geodesic reference ↗
Independent ellipsoidal reference used in validation; the browser’s distance model is explicitly a mean-radius sphere, not survey-grade ellipsoidal geodesy.
Reviewed 2026-10-18. Read our methodology or report an issue.