Kilometers per hour to Miles per hour

Kilometers per hour to Miles per hour: exact formula, common values and reverse conversion. Free, no sign-up.

Result
0.621371

1 km/h = 0.621371 mph

Conversion formula

1 km/h = 0.621371 mph

Common Kilometers per hour to Miles per hour values

Kilometers per hourMiles per hour
1 km/h0.621371 mph
2 km/h1.2427 mph
3 km/h1.8641 mph
5 km/h3.1069 mph
10 km/h6.2137 mph
20 km/h12.4274 mph
50 km/h31.0686 mph
100 km/h62.1371 mph

Every conversion runs in your browser. Nothing you type is uploaded to BroBroGo.

FAQ

How do you convert Kilometers per hour to Miles per hour?

Use the formula below, or just type a value above and the result updates instantly.

Is this converter accurate?

Yes. It uses the internationally-defined exact conversion factor, computed in your browser — nothing is rounded away or sent to a server.

The exact conversion factor and why it has two roles

The core of this page is a fixed mathematical relationship: 1 km/h = 0.621371192237 mph. Multiply any speed in kilometres per hour by that factor to get miles per hour exactly. The inverse, used when converting from mph to km/h, is 1 mph = 1.609344 km/h.

What sets this conversion apart from most other speed conversions is that the time unit is already the same on both sides. Both km/h and mph express distance per hour, so the hour cancels out of the ratio entirely. The only quantity that changes is the length unit. In that sense, converting km/h to mph is simpler than converting m/s to mph, where you must also change seconds to hours.

Yet there is a second length-versus-length relationship embedded in the factor that many users overlook: the kilometre and the mile are defined using different reference standards. The kilometre is 1 000 metres, and the international (statute) mile is exactly 1 609.344 metres. The conversion factor 0.621371192237 is simply the ratio 1 000 / 1 609.344, carried to enough decimal places for practical precision. This page uses that exact ratio; no rounding is applied to the multiplication itself, only to the displayed output.

Because the time unit does not need conversion, the factor is linear and works identically for any real number, positive or negative. A speed of –50 km/h becomes –31.06855961185 mph; zero in either unit gives zero in the other.

How the page handles inputs and edge cases

The page accepts a numeric value in either unit and a direction selection (km/h → mph or mph → km/h). The conversion is then performed using the exact factor or its reciprocal. The displayed result shows a practical number of decimal places – typically six or seven significant figures – but the internal calculation preserves full precision.

The tool is designed to handle the full range of numeric input that a user might plausibly supply:

  • Negative speeds are allowed. There is no physical prohibition against a negative speed if direction is considered (e.g., a velocity vector component). The conversion applies linearly, so the magnitude is preserved with the same sign.
  • Zero input returns zero output. This is a trivial case but one that beginners sometimes expect to produce an error; it does not.
  • Very large or very small numbers – on the order of 10¹² km/h or higher – are processed mathematically. The output may be displayed in scientific notation if the result exceeds a threshold (e.g., more than 10⁶ or fewer than 10⁻⁴). This prevents the interface from displaying a string of zeros.
  • Non‑numeric or empty input triggers an error state that defaults the value to 0 or shows a warning. The page does not attempt to interpret text like “fast” or “30 mph” as a number.

One subtle edge case concerns the number of display digits. The exact factor has 12 decimal places, but displaying 12 decimals for a speed like 60 mph → 96.56064 km/h would be misleading because the input itself is rarely that precise. The page therefore rounds the output to a sensible number of significant figures – usually six or seven – depending on the magnitude of the result. This is not a rounding of the multiplication; it is a display convenience.

Where the knot confuses the picture

This page sticks strictly to statute miles and kilometres. A frequent source of error in speed conversion is the confusion between statute miles and nautical miles. The knot (kn) is a speed unit defined as one nautical mile per hour. A nautical mile is exactly 1 852 metres – different from the statute mile’s 1 609.344 metres.

Because the conversion factor from km/h to knots is 1 km/h = 0.539956803456 kn (using 1 000 / 1 852), it is a distinct number. Anyone working with aviation or maritime speeds should not use this page for knot conversions. The tools look similar – both involve “per hour” – but the length reference is different. This page holds the line at the statutory mile.

To illustrate the difference:

Unit Length definition Common use
Statute mile 1 609.344 m Road distances (US, UK)
Nautical mile 1 852 m exactly Aviation, maritime, nautical charts
km/h → mph factor 0.621371192237 Land vehicle speeds
km/h → kn factor 0.539956803456 Ship and aircraft speeds

If a conversion from km/h to knots is needed, a separate tool must be used. The factor sheet emphasises this distinction because it is a common mix‑up.

Common errors and how real users get tripped up

Despite the simplicity of a linear factor, mistakes happen – particularly when people rely on memory rather than the exact number.

Using 0.621 instead of 0.621371 introduces an error of about 0.06 % – negligible for a rough estimate but enough to matter when converting a speed limit that is enforced. For example, 100 km/h becomes 62.1 mph instead of 62.1371 mph. Over a long distance, the difference compounds.

The 5/8 approximation – km/h × 5 / 8 = mph – is a common rule of thumb because 5 / 8 = 0.625, which is close to 0.6214. It is useful for mental arithmetic but not for precise work. The factor sheet mentions this: when exact accuracy is not needed, 0.62 or 5/8 is acceptable; when it is needed, the full 12‑decimal factor must be used.

Mixing up the direction – dividing by 1.609344 instead of multiplying, or vice versa. A simple test: since 1 km/h is roughly 0.6 mph, converting from km/h to mph should give a smaller number. If instead you get a larger number, you have inverted the factor.

Confusing km/h with m/s – a different category of error. 1 m/s = 3.6 km/h, which involves a time change. This page does not handle that.

Precision underestimation – some users assume that because a speedometer needle is imprecise, they need only one decimal place. But when converting data for scientific or legal reporting, the exact factor should be used and only then rounded according to the requirements of the application.

Real‑world applications: speed limits, vehicles, and data logging

The most frequent use case for this page is converting speed limits when travelling between countries.

  • In most of the world, speed limits are posted in km/h. A common limit on motorways is 120 km/h; the page converts that to 74.564543 mph (or, rounded to the nearest whole number, 75 mph). In contrast, a US highway limit of 70 mph becomes 112.65408 km/h.
  • Cyclists and runners who train with metric data but report performance in imperial units need conversion for pacing. A pace of 30 km/h is about 18.64114 mph.
  • Automotive journalists and car enthusiasts reviewing vehicles from different markets convert speedometer readings. A car whose speedometer reads 200 km/h will show 124.27423 mph on the page.
  • Logistics and fleet managers convert GPS‑derived speed data from international drivers. If a European truck logs 88 km/h, the page tells management that equals 54.68066 mph – useful for comparing with US‑based regulations.

The conversion factor is also used indirectly: sometimes a speed is given in mph but a vehicle’s trip computer reports fuel economy in km/L or L/100 km. Speed itself is not fuel economy, but speed influences fuel consumption, and conversions of speed data help feed into those calculations.

FAQ

1. Why is the conversion factor 0.621371192237 and not something simpler?
Because it is the ratio of 1 000 m (one kilometre) to 1 609.344 m (one statute mile). That ratio does not simplify to a nice fraction; it is an irrational number in practice because the mile definition was chosen independently of the metric system.

2. Can I use this page for knots or nautical miles?
No. The knot uses the nautical mile (1 852 m exactly), not the statute mile. The conversion factor from km/h to knots is approximately 0.53996 – a different number. This page only handles statute miles.

3. Why does the page allow negative speeds?
Speed is a scalar, but velocity can be negative if a direction is considered. The conversion factor is linear, so a negative input simply yields a negative output of the same magnitude. The tool does not impose a sign restriction.

4. How many decimal places should I trust?
The internal calculation uses the exact factor. The displayed result is usually rounded to six or seven significant figures. That is far more precise than any typical speedometer or GPS reading, so it is safe for all practical purposes.

5. Does the page account for changes in the definition of the mile?
No. The international statute mile is fixed at 1 609.344 m since 1959. There is no variation for US survey miles (which differ by about 2 parts per million); this page uses the standard international mile.

6. What happens if I enter a very large number like 10⁹ km/h?
The page will multiply by 0.621371192237 and try to display the result. The output may appear in scientific notation (e.g., 6.2137 × 10⁸ mph) to keep the display readable. The multiplication itself is exact.