Walking Time Calculator
Convert distance to walking duration using a configurable speed.
By Aryan Khan, Founder & Editor · Updated October 2026
For example, 6 miles at a textbook 3 mph is exactly 2 hours — the estimate every other walker on the path is silently using too.
How to use Walking Time Calculator
Time is distance at your speed. Choose the speed as honestly as the distance:
The Walking Time Calculator converts a walking distance into a duration at the speed you choose. Set places or enter the distance, pick the pace that matches the walker, and read the time — the simple division that turns 'a few miles' into a plan with a clock on it.
- 1Set places or distance.
- 2Choose walking speed.
- 3Read duration.
What people use Walking Time Calculator for
1. Everyday ETA on foot
“Twenty minutes away” should be a computation, not a courtesy. Distance from the Walking Route Planner, pace from the Walking Pace Calculator, answer here.
2. School-run and commute planning
Walking instead of driving is a decision made of minutes. Price it exactly and the decision gets fair.
3. Group walk scheduling
Set the group's pace — the slowest comfortable one — and the pub lunch books itself at the right hour.
4. Daylight checks
Distance and pace versus sunset: the winter walker's first calculation, done before the boots.
Worked examples
6 miles ÷ 3 mph = 2 h 00 min. Every guidebook's quiet assumption, made visible so you can replace it with your own.
10 km at 4.5 km/h = 2 h 13 min. A gentle pace over a real distance is a real chunk of day — the calculator's job is to say so early.
Walking times at common speeds
Duration = distance ÷ speed, at the speeds walkers actually sustain.
| Distance | At 2.5 mph | At 3 mph | At 3.5 mph | At 5 km/h |
|---|---|---|---|---|
| 2 mi | 0 h 48 m | 0 h 40 m | 0 h 34 m | 0 h 39 m |
| 5 mi | 2 h 00 m | 1 h 40 m | 1 h 26 m | 1 h 37 m |
| 6 mi | 2 h 24 m | 2 h 00 m | 1 h 43 m | 1 h 56 m |
| 10 mi | 4 h 00 m | 3 h 20 m | 2 h 51 m | 3 h 13 m |
| 15 mi | 6 h 00 m | 5 h 00 m | 4 h 17 m | 4 h 50 m |
Speeds are sustained averages, stops excluded. Hills move you down a column — Naismith's rule in the hiking tools prices climb explicitly.
How long is that walk?
A walk is distance divided by pace, and pace is more personal than people think: relaxed strolls run near 4 km/h, the average adult self-selects about 5, and a purposeful stride with somewhere to be pushes 6.5. Enter a distance in kilometres or miles, set your pace, and this tool returns the duration plus two bonus intuitions — an approximate step count from a standard stride, and a rough energy figure — turning any 'should we walk?' question into a number you can feel.
The page is honest about its simplicity: straight-line distance and flat ground, with hills, crowds and crossings left to your local knowledge, and it points one click onward to the Walking Route Planner when the question needs real footways, crossings and network truth instead of arithmetic. That pairing is the design philosophy in miniature: instant estimate first, network-true figure when it matters. Commuters, dog owners, event planners and anyone weighing the bus against their legs get a ten-second answer that respects both the math and its limits — free, private, and shareable like everything on the platform.
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 Walking Time Calculator:
- 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.
- Add a congestion buffer to any free-flow travel time: 20–40% in peak urban areas is a sane rule of thumb, and the interface labels its times as free-flow for exactly this reason. For appointments, plan with the buffer; for physics, trust the raw number.
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
Time is distance divided by entered speed. Step count assumes about 0.762 m per step and energy uses a 70 kg reference; neither considers route, slope or conditions.
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
- Time is distance divided by entered speed. Step count assumes about 0.762 m per step and energy uses a 70 kg reference; neither considers route, slope or conditions.
- 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.
Terrain?
Flat-pace estimate; hills and traffic lights add time.
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.
What about terrain?
The calculator takes the speed you set — set a hill speed for a hill walk. For climb priced into the estimate itself, the Hiking Time Calculator applies Naismith's rule.
Why is road distance longer than straight-line?
Enter the walking distance — from the pedestrian route, not the crow. Time belongs to the ground covered.
What speed should I choose?
Your measured one — the Walking Pace Calculator derives it from a real walk. Until then, 3 mph flatters most of us slightly.
Children or a dog in tow?
Choose the party's pace, not yours. A 2.5 mph column exists because toddlers and spaniels are real.
Stops included?
Add them on top. This is moving time at your speed; the day is moving time plus living time.
Does it work for running?
Enter a running speed and the same division serves. The running planners elsewhere handle routes; this page is the pure time arithmetic.
Why is my group always slower than the estimate?
Groups move at the slowest member plus conversation. Set the speed to the party's measured one — the calculator forgives; the sunset does not.
Related tools and resources
Your pace is measured by the Walking Pace Calculator; routes come from the Walking Route Planner; and hills belong to the Hiking Time Calculator.
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
Walking Time Calculator 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
Drive Time Map vs Radius Circle: Which One Should You Use? — A radius is equal distance in every direction. A drive-time map follows roads and speed. Here’s when each shape answers the real question.