Kilometer converter
Enter one distance in kilometers and get meters, miles and feet together: 1 km is 1000 m, 0.621371192237 mi and 3280.839895013 ft. Only exact definitions, never rounded shortcuts. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Kilometers
- 1
- Meters
- 1,000
- Miles
- 0.6213711922
- Feet
- 3,280.8398950131
- Factor meters
- 1,000
A kilometer is the everyday metric length used on road signs, race courses, hiking maps, and most scientific distance reports, yet many drivers, runners, construction crews, and US-facing product sheets still need the same figure in meters, statute miles, or international feet. This kilometer converter accepts one finite distance in kilometers and returns the same length in meters, miles, and feet using only exact definitions: one kilometer is one thousand meters, one international mile is one thousand six hundred nine point three four four meters, and one international foot is zero point three zero four eight meters.
What a kilometer is and which exact factors this converter uses
Statute miles and international feet are different units, fixed by the 1959 international yard and pound agreement rather than by SI itself. One international foot is exactly zero point three zero four eight meters. One international mile is exactly five thousand two hundred eighty of those feet, which is exactly one thousand six hundred nine point three four four meters, or one point six zero nine three four four kilometers.
Bridging every output through the meter therefore gives a unique, reproducible triple: meters equal kilometers times one thousand; miles equal kilometers times one thousand divided by one thousand six hundred nine point three four four; feet equal kilometers times one thousand divided by zero point three zero four eight. One kilometer is therefore one thousand meters, about zero point six two one three seven statute miles, and about three thousand two hundred eighty point eight four international feet. Ten kilometers scale those identities by ten without changing the factors.
Approximate rules such as point six two miles per kilometer or three thousand two hundred eighty feet per kilometer are rejected so homework checks, exam keys, and route exports match engineering tables instead of drifting on long corridors. This landing is a dedicated kilometer converter: the input is always kilometers, and meters, miles, and feet are always returned together. It is not a general from-to length hub, not a kilometers-to-miles-only form, and not a nautical-mile or astronomical tool.
Where a kilometer converter earns its keep, and what it costs
Road signs outside the United States, athletic race markings, hiking maps, and most scientific reports still quote length in kilometers, while the people who have to act on those numbers often think in meters, statute miles, or international feet.
A logistics script comparing a forty-two point two kilometer marathon with a US mile split sheet, a student converting textbook problems that mix metric roads and imperial construction drawings, and an app importing a kilometer column into a feet-based CAD pipeline all need the same three numbers without opening a general multi-unit hub and picking from and to by hand. Classroom oracles and exam generators need a deterministic contract that rejects non-finite input instead of silently returning NaN that a buggy grader might treat as success.
Failed validation does not consume balance. Keep requests small, pin the rounded meters, miles, and feet in tests, and you get reproducible conversions for briefing cards, LMS plugins, and edge workers without standing up a full unit-conversion library of your own.
What you can do with it
Travel and logistics planning
Turn a metric route or race distance in kilometers into meters, statute miles, and international feet so a briefing card matches US maps, CAD drawings, and split sheets.
Classroom and exam checks
Let students submit a finite kilometer distance and verify the exact meter, mile, and foot answers against the SI and 1959 international definitions.
FAQ
How many meters are in one kilometer?
Exactly 1000 meters. One kilometer is defined as one thousand metres in SI, so meters equal kilometers times 1000.
How many miles are in one kilometer?
About 0.621371192237 statute miles. Miles equal kilometers times 1000 / 1609.344, using the exact international mile of 1609.344 metres, not a 0.62 shortcut.
How many feet are in one kilometer?
About 3280.839895013 feet. Feet equal kilometers times 1000 / 0.3048, using the exact international foot of 0.3048 metres.
What happens if I enter a non-numeric distance?
Missing, non-numeric, NaN, or infinite values are rejected and are not billed.
Can I enter a negative distance?
Yes. A negative value is read as a displacement in the opposite direction, and the meters, miles and feet come back with the same negative sign.
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/kilometer \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"kilometers":1}'const res = await fetch("https://api.kit.forhosting.com/conv/kilometer", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"kilometers": 1
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/kilometer",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"kilometers": 1
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/kilometer", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"kilometers":1}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"kilometers":1}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/kilometer", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"kilometers": 1
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.kilometer",
"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
Missing, non-numeric, NaN, or infinite input fails with invalid_input and is not billed.
What a kilometer is and which exact factors this converter uses
The kilometer is an SI-derived unit of length: one kilometer is defined as exactly one thousand meters, and the meter is the SI base unit of length. That identity is not an approximation and does not depend on latitude, a survey foot, or a classroom rounding rule.
Input contract, response fields, and how invalid distances fail
Zero converts to zero in every output unit. Send a JSON body with one required field named kilometers. The value must be a finite number, either a JSON number or a plain numeric string, including optional scientific notation when you need a very large corridor. Aliases km, kilometres, value, distance, length, and amount are accepted so spreadsheets, typed forms, and SDK clients can reuse the name that already exists in the source system. Signed values are allowed as displacements; missing fields, empty strings, bare plus or minus signs, spelled-out words without a number, NaN, and Infinity fail with invalid_input naming kilometers so the web control can be marked invalid. Those failures are never billed. Magnitudes above one trillion kilometers are rejected so the Worker isolate stays inside a published limit and IEEE double results stay finite. Pair the numbers with your own map or plot if you need a picture; this endpoint converts length only and does not emit tracks, bearings, or pace.
Where a kilometer converter earns its keep, and what it costs
This page does not convert nautical miles, does not turn miles or feet back into kilometers as a primary form, and does not accept mixed unit strings such as ten km plus two miles; send a single finite kilometer figure and read the three companion units from the JSON.
Integration use cases
App and spreadsheet imports
Convert a column of kilometer values into SI and imperial fields for a warehouse, fitness export, or CI fixture without a general multi-unit converter.
Technical questions
What does the kilometer converter cost?
The browser tool is free. API requests use prepaid KIT balance at $0.002 per successful call; invalid input is not billed.