Skip to content

Length Converter

Quick picks

Result

1 Kilometres (km) = 0.621371 Miles (mi)

Estimates for educational purposes — not financial, medical, or legal advice. See terms.

Convert any length value between ten different units: millimetres, centimetres, metres, kilometres, inches, feet, yards, miles, nautical miles, and light-years. Both sides are editable — type into the source or the target and the other updates. Swap button flips the direction. Five quick-pick buttons jump to common pairs (km ↔ mi, ft ↔ m, in ↔ cm).

How it works

All values route through metres as the canonical base. Converting from source to target is a single two-multiplication operation: multiply by metres-per-source, then divide by metres-per-target. The factor table holds exact conversion constants derived from the 1959 international yard-and-pound agreement (inch = 0.0254 m exactly) and international standards for nautical miles (1852 m exactly) and light-years (Julian year × c).

Example: highway speed limits

A 60 mph speed limit in km/h: enter 60 in the source (mi), target shows 96.56 (km). Or set up the converter in mi → km permanent-style with the swap button. Useful for anyone driving across the US-Canadian or US-Mexican border, where the speed-limit signs change units. (Speed is a different quantity — for mph ↔ km/h directly, use the speed converter.)

Example: metric-to-imperial translation

Height 1.75 metres in feet and inches: 1.75 m → 5.7415 ft → 5 ft + 0.7415 × 12 = 5 ft 8.9 in. Or directly: 1.75 m = 68.898 in ≈ 5 ft 8.9 in. The tool gives you the single target unit cleanly; mixed units (feet and inches) need a bit of manual arithmetic on the feet-decimal.

Example: interstellar distances

The nearest star other than the Sun is Proxima Centauri at about 4.246 light-years. In kilometres: 4.246 × 9.46 × 10¹² ≈ 4.01 × 10¹³ km — 40 trillion km. The scientific-notation display handles values of this scale without overflowing; the precision stays at about 15 significant digits regardless of magnitude.

Exact vs. approximate factors

ConversionValueExact?
1 in → m0.0254yes (1959 agreement)
1 ft → m0.3048yes (= 12 × 0.0254)
1 yd → m0.9144yes (= 3 × 0.3048)
1 mi → m1609.344yes (= 1760 × 0.9144)
1 nmi → m1852yes (international convention)
1 ly → m9.4607304725808 × 10¹⁵yes (Julian year × c)
1 km → m1000yes (metric)

The light-year uses the Julian year (365.25 days × 86400 seconds = 31,557,600 seconds), multiplied by the speed of light 299,792,458 m/s. This is the IAU-recommended convention. The “solar year” light-year or “Gregorian year” light-year would differ by a few tens of thousands of km over that astronomical distance — close to rounding error for all practical purposes.

What this tool does not do

It doesn’t handle mixed units like “5 feet 8 inches”. You’d need to convert each component separately and sum. A dedicated imperial-height converter handles the composite case.

It doesn’t support surveying units — rods, chains, furlongs, and so on. Those have exact relationships to the inch (e.g., 1 furlong = 660 ft) but aren’t common enough to include in the main table.

It doesn’t include astronomical units (au), parsecs, or Hubble-length units. Astronomy-specific conversions belong in a dedicated astro calculator.

It doesn’t handle geographic coordinates. Converting between degrees of latitude and metres requires spherical trigonometry and varies with latitude — a different tool entirely. For flat Cartesian distances instead, the distance between points calculator does the Pythagorean math.

It doesn’t display mixed units in the output. The tool gives you a single decimal value in the target unit; for “5 ft 8.9 in” style output, you’d need a dedicated imperial-height display.

Frequently asked questions

Which conversions are exact?

All of them, up to floating-point precision. The metric units (mm, cm, m, km) are exact powers of ten. The Imperial / US customary units (inch, foot, yard, mile) come from the 1959 international yard-and-pound agreement, which fixed the inch at exactly 0.0254 metres. So 1 foot = 0.3048 m exactly, 1 yard = 0.9144 m exactly, 1 mile = 1609.344 m exactly. Nautical miles are 1852 m by international definition. Light-years use the Julian-year convention (365.25 days × 86400 s × c), which is the IAU standard.

Why is a nautical mile different from a regular mile?

They measure different things. A statute (regular) mile is 1609.344 m exactly, derived from land-based units. A nautical mile is 1852 m, historically defined as one minute of latitude along any meridian — which is more useful for navigation because it lets you convert between angular distance on a map and ground distance directly. Aviation and maritime navigation use nautical miles exclusively; ground-based travel uses statute miles. If you're looking at ship or aircraft speed in knots (= nautical miles per hour), you want nautical miles, not statute.

How far is a light-year in plain numbers?

About 9.46 × 10¹⁵ metres, or 9.46 trillion kilometres, or about 5.88 trillion miles. It's the distance light travels in one year — technically a Julian year of 365.25 days. The nearest star other than the sun (Proxima Centauri) is 4.246 light-years away, which is 40.2 trillion km. Astronomy uses light-years and parsecs (1 pc ≈ 3.26 ly) for interstellar distances because metres become inconveniently large.

Why do I get floating-point imprecision on round trips?

Because the conversions use IEEE 754 double-precision arithmetic, which represents most decimal fractions only approximately. 1 ft = 0.3048 m is exact, but 1/0.3048 ≈ 3.2808398950131... can't be stored exactly. Round-tripping through metres introduces tiny errors at about the 15th decimal place. For any practical purpose this is invisible, but if you're comparing two converted values for exact equality, use an epsilon comparison instead.

Can the tool handle scientific notation?

Yes. Enter 1e3 for 1000, 4.2e15 for 4.2 × 10¹⁵, 1.5e-6 for 1.5 millionths, etc. The input is a standard HTML number field, which accepts scientific notation. The output is formatted in fixed-point by default (up to 6 decimal places). For very large or very small values where fixed-point would be unhelpful, you'll see extra zeros — but the underlying precision is preserved.