Take the route with you.
A route that stays on a website is a nice drawing. The point of drawing it is the file at the end — and the file is a plain GPX, which every device that navigates anything already reads.
One button, one file.
When the route is done, export it. What comes out is a standard GPX track: the line, its points, and the elevation along it. No account is needed on the other end, nothing has to be paired, and the file is yours — put it wherever you keep files.
What is in the file
- The full route as recorded on the map, at the resolution the router returned.
- Elevation along the line, so a device that draws a profile draws yours.
-
The name you gave the route, so it is not
track_2026-08-12.gpxon the head unit.
Anything that reads a GPX.
Which is, in practice, all of them. These are the ones people ask about:
There is no sync and no integration to set up: you copy a file across, the same way you always have. That also means nothing here breaks when a manufacturer changes an API.
Already have a track?
Upload it and it opens on the map with its own numbers — distance, ascent, profile, gradient. From there you can leave it exactly as it is, or hand it to the router for a different sport and get a version that suits how you are actually going out.
Imported lines are kept as they are — An imported track is a record of something, so the planner does not quietly redraw it. It stays the line in the file until you ask for a recalculation. And for a sport no router can draw — swimming — it simply stays a track, which is the honest answer rather than a button that could only fail.