Running Route Planner
Create a pedestrian-network route as a practical baseline for runs, jogs and city training routes, with distance, map line and GPX export.
By Aryan Khan, Founder & Editor · Updated October 2026
For example, a planned riverside 8.2 km with the distance known before the laces are tied — the session prescribed, measured and exportable.
How to use Running Route Planner
A run planned is a run measured. Build it on the network runners are allowed:
The Running Route Planner creates a route between start and finish on the pedestrian network — streets and paths a runner can use — and reports its distance, drawn on the map. Plan the run, check the distance needed, and export GPX for your watch or phone.
- 1Set the start and finish.
- 2Calculate the pedestrian route.
- 3Use the distance for your running plan.
- 4Export GPX if you want the route in a GPS app.
What people use Running Route Planner for
1. Session planning
The plan prescribes distance, not geography: build the route that delivers exactly the kilometres — loops are the Running Route Loop Generator's craft when home is both ends.
2. New-city running
Travel runs on unknown streets deserve a pedestrian-legal route and a known distance. This is the traveller's local knowledge, generated.
3. Route sharing
GPX is the runner's lingua franca: plan here, send the file, and the whole club runs the same line on Saturday.
4. Race reconnaissance
An unfamiliar race town's training runs, planned before arrival — distances known, surfaces checkable in the Route Surface and Road Type Finder.
Worked examples
Training says 12 km easy. The planner iterates a route until its reported distance is the session's distance — the map bends to the plan, not the reverse.
Exported, the planned line becomes the watch's breadcrumb. The run you designed at the desk is the run your feet execute.
Planner versus loop generator
Two running-route tools, two shapes of question — this page is the start-to-finish column.
| Question | This planner | Loop generator |
|---|---|---|
| Shape | Start → finish | Start → start |
| Distance | Whatever the route measures | Aims at your target |
| Network | Pedestrian | Pedestrian or cycling |
| Export | GPX built in | Via this planner |
| Best for | Planned sessions, travel runs | Breaking the routine |
Pedestrian routing follows the open network data; a path the data does not know cannot be planned on — local signs remain the law.
Plan distance first, then apply your own running pace
For runners, mapped distance is usually more useful than a generic travel-time estimate. This route planner uses the pedestrian network as a baseline so roads and mapped paths are followed instead of drawing a straight line through buildings or rivers.
The routing engine does not know your fitness, target pace, temporary closures or every informal trail. Review the line on the map, use the distance for your training plan and export GPX when you want to carry the route into a watch or navigation app.
How to interpret the result
The most common errors come from using a correct result to answer the wrong geographic question. Keep these points in mind for Running Route Planner:
- Place route endpoints on roads, not rooftops. Routing engines snap points to the nearest drivable way, and a point in a river or a courtyard can snap somewhere surprising — nudging the pin to the nearest street makes results stable and explainable.
- When optimising many stops, keep the true origin first and let the engine order the rest; then sanity-check the result visually. Optimizers minimise distance, not your time windows — hard appointments still belong in manual order.
Limits & appropriate use
Routing's limits live in three places: data vintage, access reality and time modelling. The network is OpenStreetMap's current picture — new interchanges lag, private gates may be missing, seasonal ferries keep their own calendars. Access rules reflect mapped law, not today's roadworks. And durations are free-flow physics: speed limits and road classes without your city's sociology, so peak hours, weather and parking belong in your buffer, not in the engine's promise. The tools label all three limits on every result, because an unlabelled estimate is a trap.
What the stack does brilliantly is the reproducible core: the same stops, mode and engine give the same route to everyone, everywhere, which makes it a superb baseline for comparison, screening and planning. Escalation is domain-specific and well understood — professional dispatch adds live traffic and driver hours; logistics tenders add contracted networks; navigation products add certified maps. A free browser tool that hands you a clean, exportable baseline with its assumptions printed is not competing with those; it is feeding them.
- Live congestion and ETAs → traffic-aware commercial routing.
- Driver-hours and windows → transport-management systems.
- Certified navigation → licensed map products with update guarantees.
Data & methodology
Routes follow the available pedestrian network through the site's open routing providers; displayed duration is not a personalized running pace prediction.
For source details, licences and model limitations, see Data Sources and Methodology.
Key terms worth knowing
- Free-flow time
- Travel time from speed limits and road classes, without congestion.
- Travelling-salesman ordering
- Reordering stops to minimise total route distance.
Editorial guidance: MapBench explains the method and limitations so the tool can be used as a transparent reference, not as a black-box answer. For legal boundaries, safety-critical routing, surveying, engineering, regulated decisions or official statistics, verify the result with the responsible authority or a qualified professional.
Category: Routing & Travel Time. Results are intended for everyday analysis and planning unless a page explicitly states otherwise.
Method, assumptions & limits
- This tool’s method
- Routes follow the available pedestrian network through the site's open routing providers; displayed duration is not a personalized running pace prediction.
- Before relying on the answer
- Check the stop order, travel mode and whether the result is a network route or a simplified estimate. Repeat the calculation after changing any of these inputs.
- What the result cannot establish
- Road access, congestion and closures can change. An estimated duration is not a live arrival-time commitment.
Coverage: Worldwide. Search, basemap and external data requests may use third-party services; browser-based does not mean every operation is offline. Read the source and licence notes, calculation methodology and privacy policy. If a result looks inconsistent, report a correction with the inputs and mode used.
Frequently asked questions
Clear answers about the calculation, accuracy and appropriate use.
Does it know every trail?
Routing depends on the underlying OpenStreetMap network. Missing or restricted paths may not be routable.
Is running speed included?
The routing engine provides a walking-style duration; runners should use the road/path distance with their own pace.
Does the route include live traffic?
Unless the tool explicitly says otherwise, travel times are planning estimates and should not be treated as live-traffic predictions.
Why is road distance longer than straight-line distance?
Roads must follow the available network, terrain, bridges and restrictions, while straight-line distance measures the geometric minimum between two points.
Can route results change over time?
Yes. Road-network data, access restrictions and routing datasets can change, so recheck important journeys close to travel time.
Why is road distance longer than straight-line?
The pedestrian network winds like every network. The reported distance is the run's real length.
Can I export to my watch?
GPX export is built in, and GPX is the format watches and run apps import. Plan here, run there.
Point to point leaves me far from home.
Then the run is a journey — or generate a loop instead. Many runners plan one-way runs toward a train station on purpose.
Does it avoid main roads?
Pedestrian routing prefers paths and pavements where the data offers them; a road section appears when the network has no gentler link.
Can I plan interval sessions?
Plan the route for distance, then run the session on it — the planner measures the stage, your watch conducts the play.
My watch wants a different format.
GPX is the common tongue; if a device insists otherwise, its own app converts GPX happily.
Related tools and resources
Loops are the Running Route Loop Generator; paces convert in the Pace to Speed Calculator; and rides get the Cycling Route Planner.
More free tools
Sources, methodology & editorial trust
- ✓ Browser-first processing where supported
- ✓ External sources are documented
- ✓ No account required for public tools
- ✓ Review data sources
Calculations are documented with their assumptions, limitations and source context rather than presented as unexplained answers.
Reviewed and maintained by Aryan Khan, Founder & Editor of MapBench.
Part of our routes & travel time hub
Running Route Planner sits in the routes & travel time cluster, alongside 62 other tools that answer neighbouring questions with different methods or datasets.
You may also need
When this answer is only part of the job, these clusters cover the next step.
Read the guide behind this tool
Radius vs. Drive Time vs. Straight-Line Distance: Which Map Should You Use? — A practical guide to choosing between a radius circle, road travel-time map and straight-line distance so your result matches the real question you are trying to answer.