Calculator
What the Mile to KM does
Mile to KM: 1 mi = 1.609344 km, so multiply a mile value by 1.609344 to get kilometre, or divide to go back. Example: 1 mi = 1.609344 km.
Point it at Value, From and To and it returns Result, How it was calculated and Reverse conversion. Edit a field and the answer updates in place.
Typical users are people following a recipe or spec written elsewhere. Two industries often use the same word for slightly different quantities.
There is no back end here. The calculation runs where you are sitting, not on a server somewhere.
The sections that follow cover the fields, the method, and one full example computed from the defaults.
What do the Mile to KM fields mean?
The Mile to KM uses 3 inputs. Each input has a default that makes sense on its own, so a partial edit still gives a valid result.
| Field | What to enter | Default |
|---|---|---|
| Value | required | 1 |
| From | choose from Nanometre (nm), Micrometre (µm), Angstrom (Å), Millimetre (mm), Centimetre (cm) or Metre (m) | Mile (mi) |
| To | choose from Nanometre (nm), Micrometre (µm), Angstrom (Å), Millimetre (mm), Centimetre (cm) or Metre (m) | Kilometre (km) |
How does the Mile to KM work?
Both units are converted through length's base unit (m), so any of the 19 units in the dropdowns can be paired in either direction without loss of accuracy.
Definitions are taken from the SI system where one exists, and from CODATA or the IAU where a unit is established by measurement. No factor is rounded before the calculation.
Worked example
These are the values the Mile to KM loads by default, and the result it produces from them. Here is the calculation as it stands the moment the page loads.
| Value | 1 |
|---|---|
| From | Mile (mi) |
| To | Kilometre (km) |
| Result | 1.609344 km |
|---|---|
| How it was calculated | 1 mi = 1.609344 km, so 1 × 1.609344 = 1.609344 km |
| Reverse conversion | 0.62137119 mi (if you meant 1 km) |
Miles and kilometres
1 mile equals exactly 1,609.344 metres by international definition (since 1959), not a rounded figure, so multiplying by 1.609344 always gives the exact conversion.
Worth knowing
- For quick mental math, multiplying miles by 1.6 gets within about 0.6% of the exact answer, which is generally close enough for trip-planning or fitness-tracking purposes.
- This is the one conversion most people encounter without meaning to: US road-trip distances, marathon and 5K/10K race branding (a "5K" is 5 kilometres, a "half marathon" is 13.1 miles/21.1 km), and vehicle fuel-economy comparisons all straddle the mile/km boundary.
- The nautical mile (1,852 m) is a completely different, unrelated unit despite the similar name. It is based on a minute of latitude, not on this statute-mile definition, so it must not be substituted here.
Definitions: BIPM SI Brochure · NIST reference on units
How to use it
- Enter Value.
- Pick a value for From: the options are Nanometre (nm), Micrometre (µm), Angstrom (Å), Millimetre (mm), Centimetre (cm) or Metre (m).
- Pick a value for To: the options are Nanometre (nm), Micrometre (µm), Angstrom (Å), Millimetre (mm), Centimetre (cm) or Metre (m).
- Each keystroke triggers a fresh calculation, which is cheap because it happens locally.
- You get Result, How it was calculated and Reverse conversion back.
- Copy Link is the quickest way to send the exact scenario to someone else.
What this tool does not do
- Repeated conversions compound rounding, so convert once from the original value where you can.
- Conversion factors use SI definitions; some industries use their own rounded factors.
- The method is fixed. There is no option to substitute your own formula.
- Results are only as good as the inputs. Check your units before reading anything into the output.
Frequently asked questions
Value, From and To. That is the whole form. Nothing starts empty, which means a single edit is enough to get a meaningful answer.
With the values loaded when the page opens, result comes out as 1.609344 km. Any edit re-runs the calculation, so there is no stale number on screen.
Nothing is stored. The page has no back end to send data to, and holds your input only in memory.
Nothing at all. There is no registration, no paywall and no per-use quota.
Reliable for the case described. Where more than one convention exists, the method section says which one is used.