Travel distance unit converter
100 statute miles are exactly 160.9344 km, because a mile is fixed at 1.609344 km and a nautical mile at 1.852 km. Every conversion uses those definitions and shows the distance in all three units. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Distance magnitude to convert
- 100
- Input distance unit
- km
- Output distance unit
- mi
- Result
- 62.1371192237
- Kilometers
- 100
- Miles
- 62.1371192237
- Nautical miles
- 53.9956803456
Travelers, pilots, sailors, and logistics planners constantly need a trustworthy travel distance unit converter when road itineraries in kilometers meet US highway miles or when aviation and marine charts quote nautical miles instead. One international statute mile is exactly one point six zero nine three four four kilometers, while one international nautical mile is exactly one thousand eight hundred fifty-two meters, so ad-hoc mental multiplies drift as soon as a ferry leg, a great-circle estimate, and a rental-car odometer share the same trip plan.
How kilometers, statute miles and nautical miles relate
Travel distance on land, in the air, and at sea is still reported in three everyday length units that look similar but are not interchangeable. The kilometer is the SI-derived unit used on most road signs outside the United States and the United Kingdom-influenced markets. The statute mile, also called the international mile, is the road and rail unit familiar from US highway exits and many aviation still-air rule-of-thumb tables that talk about statute rather than nautical miles.
The nautical mile is defined so that one minute of arc along a great circle of the Earth is one nautical mile under the international agreement of one thousand eight hundred fifty-two meters exactly, which is why pilots, mariners, and ocean routing tools prefer it for course and range. Converting among them is pure linear scaling with no inversion: you always multiply by a constant factor. This converter first maps every input into kilometers using fixed constants.
One international statute mile is exactly one point six zero nine three four four kilometers. One international nautical mile is exactly one point eight five two kilometers. A value already in kilometers is the bridge itself.
Once the bridge value is known, converting outward is division by the same factors. Amounts must be finite numbers; missing fields, non-numeric garbage, NaN, Infinity, and unrecognized unit strings fail early with invalid input rather than inventing a silent default.
What you send and what you get back
Send three fields. The field amount is a finite number, or a string that parses to such a number. The field from is the unit of that amount, and the field to is the unit you want as the primary result.
Matching is case-insensitive and tolerant of spaces, hyphens, and slashes. Classic checks include one hundred kilometers into statute miles near sixty-two point one four, one hundred statute miles into one hundred sixty point nine three four four kilometers exactly, and sixty nautical miles into about one hundred eleven point one two kilometers. Wire the free browser form for quick itinerary checks, then call the identical contract from scripts when you need bulk route normalization.
Where a travel distance unit converter shows up in real work
Cross-border road-trip planners constantly mix European motorway distances in kilometers with US or UK guidebook legs in statute miles; apps that normalize every leg into one column avoid misleading day-by-day totals. Flight and yacht crews comparing a charted nautical-mile range with a land transfer in kilometers need a single oracle that never confuses nm with mi, a classic source of fuel and timing errors. Logistics and freight desks importing mixed carrier CSVs want every leg length in one reporting unit before ranking lanes or estimating drive time.
Travel content sites and itinerary APIs cite both statute and nautical figures when a cruise port transfer meets a coastal sailing segment, and they need reproducible numbers rather than spreadsheet drift between editors. Geography and navigation classrooms teaching unit conversion use this path as a concrete bridge problem with exact legal definitions of the statute mile and the international nautical mile.
If you later need average speed from distance and elapsed time, great-circle destination points from bearing, or fuel economy in MPG versus L/100km, treat those as separate search intents and landings rather than overloading this travel distance unit converter page.
What you can do with it
Cross-border road itinerary normalization
Map European kilometer legs and US or UK statute-mile guidebook segments into one column so day totals and hotel hops stay comparable.
Aviation and marine range checks
Convert charted nautical-mile ranges into kilometers or statute miles when briefing land transfers, rental cars, or multi-modal ETAs.
Freight and carrier CSV cleanup
Bulk-convert mixed distance unit columns from carriers into a single reporting unit before lane scoring and drive-time models.
FAQ
Is a nautical mile the same as a statute mile?
No. One international nautical mile is exactly 1.852 km (1852 m). One international statute mile is exactly 1.609344 km. Always set from and to explicitly.
Does the converter handle zero or negative distances?
Yes, any finite number is accepted, including zero and negative offsets. Non-finite values such as NaN or Infinity are rejected.
What does it cost?
The browser tool is free and runs locally.
Do I get the distance in all three units at once?
Yes. Besides the unit you asked for, the result always shows the same distance in kilometres, statute miles and nautical miles, so one conversion can feed a road plan, a flight plan and a sea passage.
Why do pilots and sailors use nautical miles?
Because one nautical mile matches one minute of arc along a great circle of the Earth, fixed by international agreement at exactly 1,852 metres. That makes it the natural unit for courses and ranges on charts.
Related tools
For developers — API access
Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.
API endpoint
Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.
Call it from your stack
curl -X POST https://api.kit.forhosting.com/travel/distance-unit-convert \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"amount":100,"from":"km","to":"mi"}'const res = await fetch("https://api.kit.forhosting.com/travel/distance-unit-convert", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"amount": 100,
"from": "km",
"to": "mi"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/travel/distance-unit-convert",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"amount": 100,
"from": "km",
"to": "mi"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/travel/distance-unit-convert", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"amount":100,"from":"km","to":"mi"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"amount":100,"from":"km","to":"mi"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/travel/distance-unit-convert", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"amount": 100,
"from": "km",
"to": "mi"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "travel.distance_unit_convert",
"status": "queued",
"_links": {
"result": "/tasks/tsk_…/result"
}
}The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.
Pricing
Published price — no tokens, no invented credits. A failed task is never charged.
Errors
| HTTP | Code | Meaning |
|---|---|---|
401 | unauthorized | Missing or invalid API key. |
402 | insufficient_balance | Your balance doesn't cover the task price. |
404 | unknown_type | That task type doesn't exist. |
429 | rate_limited | Too many requests. Use the webhook instead of polling. |
Technical notes
This capability accepts a finite distance amount with explicit from and to units among kilometers, statute miles, and nautical miles, bridges through kilometers with those fixed legal definitions, returns the target result plus every supported unit in one JSON object, and rejects unrecognized unit strings so a bad CSV label never looks like a valid range.
How kilometers, statute miles and nautical miles relate
Because every step is deterministic floating-point arithmetic with no network call, no random seed, and no wall-clock timestamp, the same amount and units always produce the same JSON.
What you send and what you get back
Accepted labels include km for kilometers, mi for statute miles, and nmi for nautical miles, plus common aliases such as kilometers, kilometres, mile, miles, statute_mile, nm, nautical_mile, sea_mile, and marine_miles. Missing fields, non-numeric garbage, NaN, Infinity, and unrecognized unit strings fail with invalid_input and are not charged. On success the response echoes the cleaned amount, the canonical from and to keys, the primary result in the to unit, and the same physical distance expressed as kilometers, miles, and nautical_miles so a single call can feed road apps, aviation fuel plans, and marine ETAs. Bridge factors factor_from_km and factor_to_km document the exact kilometers-per-unit constants used on each side. The formula string records the mile and nautical-mile definitions, and method is always kilometer_bridge. Pricing for successful API calls is the published base of $0.002 per item; validation failures do not consume prepaid balance.
Where a travel distance unit converter shows up in real work
Because this capability is a pure parse engine, API pricing is the published base of $0.002 per successful item and failed validation does not consume balance.
Technical questions
What units does this travel distance converter support?
Kilometers (km), statute miles (mi), and nautical miles (nmi), including common aliases such as kilometers, miles, nm, and nautical_mile.
What happens if the unit is unrecognized?
The request fails with invalid_input. Only km, mi, nmi and their documented aliases are accepted; other strings are rejected rather than guessed.