Mile conversion
1 mile is exactly 1.609344 km, 1609.344 m, 1760 yards and 5280 feet. Enter a route, a training run or a trail length in miles and get all four distances at once for metric itineraries, track splits and imperial signage. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Miles
- 1
- Kilometers
- 1.609344
- Meters
- 1,609.344
- Yards
- 1,760
- Feet
- 5,280
Converting a distance in miles into the units people actually use on maps, race plans, shipping labels, and school worksheets is a daily chore whenever imperial road signs meet metric itineraries. This mile conversion calculator takes one non-negative statute-mile value and returns four exact companion distances in a single response: kilometers, meters, yards, and feet. The arithmetic follows the international definition fixed in 1959: one mile equals 1.609344 kilometers, 1609.344 meters, 1760 yards, and 5280 feet.
The four exact mile factors and why they never drift
The international statute mile is a fixed length, not a rounded classroom estimate. After the 1959 yard and pound agreement, one yard is defined as exactly 0.9144 meters and one foot as exactly 0.3048 meters. A statute mile contains five thousand two hundred eighty of those feet, so one mile is exactly 1609.344 meters.
Dividing by one thousand meters in a kilometer yields the kilometer factor 1.609344, which is exact rather than a three-decimal approximation. A yard is three feet, so the same mile is exactly 1760 yards. One mile therefore becomes 1.609344 kilometers, 1609.344 meters, 1760 yards, and 5280 feet; ten miles become 16.09344 kilometers, 16093.44 meters, 17600 yards, and 52800 feet.
There is no table lookup, no nautical-mile option, and no US survey-mile variant on this landing. If you need a signed map offset, convert the absolute length here and apply the sign in your own geometry layer. Zero miles converts to zero in every listed unit, which is a convenient default for empty forms.
Where the four distances come in handy
Pair the four output fields with your own reverse conversion if a pipeline must round-trip labels, but keep this page focused on converting miles outward into kilometers, meters, yards, and feet. Source inputs follow the same retention rules as other parse items: they are processed and discarded. Authors shipping SDKs can map miles into a number field and show kilometers, meters, yards, and feet as result badges.
Keep requests small, treat negative miles as a client bug, and you get reproducible distances for homework, LMS plugins, and edge workers without standing up a general unit-conversion library of your own.
What you can do with it
Travel itineraries and road signs
Travelers and mapping tools convert a US or UK route in miles into kilometers and meters for metric itineraries, plus yards and feet when a walking last-mile or trail description needs imperial subunits.
Running, cycling, and race plans
Athletes and coaches convert training miles into kilometers for metric calendars, meters for track splits, and yards or feet when a course is marked in imperial subunits.
FAQ
What happens if I enter a negative distance?
A physical distance cannot be negative; signed map offsets should be applied after converting the absolute length.
Which mile definition does this calculator use?
The international statute mile from the 1959 yard and pound agreement. It does not convert nautical miles or the US survey mile; those are different factors and different search intents.
Can I send the distance as a numeric string?
Empty strings, spelled-out words without a number, NaN, and Infinity are rejected.
How far is 10 miles in kilometers and meters?
10 miles are 16.09344 km, or 16093.44 m, and also 17600 yards and 52800 feet. Every result comes from the exact international mile, so nothing is rounded to three decimals.
Does it handle nautical miles?
No. It only converts the statute mile of 1609.344 meters. Nautical miles and the old US survey mile are different lengths and are not offered here.
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/conv/mile-conversion \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"miles":1}'const res = await fetch("https://api.kit.forhosting.com/conv/mile-conversion", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"miles": 1
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/mile-conversion",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"miles": 1
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/mile-conversion", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"miles":1}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"miles":1}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/mile-conversion", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"miles": 1
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.mile_conversion",
"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.
Limits
max_abs | 1000000000000 |
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
Negative values and non-finite numbers such as NaN or Infinity are rejected with invalid_input instead of being treated as a reverse heading. Successful API calls bill at $0.002 per item; validation failures are not charged.
The four exact mile factors and why they never drift
Those four identities are what this mile conversion endpoint applies on every request: kilometers equal miles times 1.609344, meters equal miles times 1609.344, yards equal miles times 1760, and feet equal miles times 5280. Results are quantized to twelve decimal places so JSON goldens stay identical across JavaScript runtimes while remaining far more precise than any odometer.
Input contract, aliases, and why negatives fail
Numeric strings, including scientific notation, are parsed; empty strings, missing fields, objects, and arrays are not. The same error is raised for NaN, Infinity, and non-numeric text such as a spelled-out phrase without a number. Failed validation is not billed. Use this landing when the search intent is mile conversion as a bundle of units; a dedicated miles-to-kilometers-only tool is a different query and a different page. POST a JSON body with the required field miles, a finite non-negative number representing statute miles. If the value is negative the task fails with invalid_input and a message that names miles, because a physical distance cannot be negative. Magnitudes above one trillion miles are rejected so Worker isolates stay inside a published limit. On success the JSON echoes the parsed miles value and returns kilometers, meters, yards, and feet as four parallel numbers. Companion fields document the exact factors: km_per_mile 1.609344, meters_per_mile 1609.344, yards_per_mile 1760, and feet_per_mile 5280. A formula string restates the identity in one line for tutoring interfaces, and method is always exact_international_mile so downstream code can pin the definition.
API usage, pricing, and where the four outputs land
Successful conversions bill as one item at $0.002; invalid_input never consumes balance, so you can validate forms without burning prepaid credit.
Integration use cases
Homework checks and logistics manifests
Students, teachers, shippers, and fleet tools verify one mile-to-four-units answer with exact factors, a readable formula line, and a clear invalid_input error on negative or non-numeric input.
Technical questions
How do I convert miles to kilometers, meters, yards, and feet?
Send a finite non-negative number in the miles field (aliases value, mi, mile, distance). The API returns kilometers, meters, yards, and feet using the exact factors 1.609344 km, 1609.344 m, 1760 yd, and 5280 ft per mile.
What does the mile conversion calculator cost?
The browser tool is free. API requests use prepaid KIT balance at $0.002 per successful call; invalid input is not billed.