uturn.bike
Small, private tools for cyclists - compare routes, meet in the middle,
find the nearest stop.
No accounts, no uploads, no tracking. Three things, each one tap from
the home screen:
Open uturn.bike →
🔒 Private by design. Everything runs in your browser. Your GPX
files are read locally and
never uploaded - no server, no
account, no cookies, no tracking.
Three optional, clearly-labelled features reach the network: map
tiles (like any web map), looking up nearby coffee/water/fuel from
OpenStreetMap (only when you turn it on), and the Meet feature, which
sends the two shared points to the BRouter routing service to draw
the route. Meet links carry the locations in the link itself - never
on our server. Nothing ever receives your route file.
🆘 SOS - nearest stops
-
Out on a ride and need water, coffee or fuel? One tap shows
the nearest of each, with distance and a compass arrow.
- Bike directions to any stop, straight from the list.
🤝 Meet in the middle
-
Share a link with a friend (no accounts) and get a fair
meeting point - halfway along an actual bike route, not as the crow
flies.
- Gravel or road-only routing, your pick.
-
Per-rider distance and climb, plus a handoff to Google Maps or OSM
for turn-by-turn.
🗺️ Compare GPX routes
- Up to 3 routes in blue / red / green, drawn together.
-
Stats - per-route distance, the difference between routes, how
much they overlap, and an elevation profile.
- Basemaps - street, satellite or terrain.
-
Extras along route - find ☕ coffee, ⛽ fuel/air and 🚰 water
near your route (opt-in).
-
Save the route with its extras - writes your GPX back out with
each found stop added as a named waypoint, one file per route. Stops
are pinned to the nearest point on the route, with how far off the
route they really are in the label - Garmin drops any waypoint more
than ~40 m from the line. Komoot lists them along the tour; Garmin
Connect turns them into course points.
How it works
Plain static pages using
Leaflet and
OpenStreetMap. GPX files are
parsed with the browser's built-in XML reader; distances use the
haversine formula. Nearby-stop search uses the
Overpass API; meeting-point
routing uses BRouter. Saved files are
rebuilt in the page from the GPX you loaded - nothing is uploaded. There
is no backend at all.
Good to know
-
Distances are 2-D estimates - accurate to roughly 1%, not
survey-grade.
-
Overlap is an approximate grid heuristic, not exact path matching.
-
The meeting point is halfway by riding distance, not effort -
one rider may climb more.
-
Nearby search and routing use free shared services that can be slow
at peak.
- Very large GPX files (100k+ points) can feel sluggish on hover.
uturn.bike is free, ad-free and runs on shared community services. If
it saved your ride, you can
☕ Buy me a coffee