Convert mph to m/s

mph
0.44704m/s

1 mph = 0.44704 m/s

One mile per hour is exactly 0.44704 metres per second, because a mile is exactly 1,609.344 metres and an hour is 3,600 seconds. This page is for taking an American figure in mph into the SI a formula or an international standard expects, where the question is not the factor but how much of it to carry.

  • Where it runs In your browser. The number you type is never part of a request.
  • Exact by definition 1 mph is exactly 0.44704 m/s — a definition, not a rounded factor.
  • Answers as you type No button, no wait. The worked answer is already on the page before any script runs.

Mile per hour to Metre per second in practice

  • 70 mph is 31.29 m/s

    — the British motorway limit.

  • 30 mph is 13.41 m/s

    — a British urban speed limit.

  • 767.3 mph is 343 m/s

    — the speed of sound in air at room temperature.

  • 22.37 mph is 10 m/s

    — a world-class sprinter at full speed.

Mile per hour to Metre per second at a glance

Every figure here is computed from the same definition the calculator uses, so the table cannot drift away from the answer above it.
mphm/s
10.44704
20.89408
31.34112
52.2352
104.4704
208.9408
5022.352
10044.704

Mile per hour and Metre per second

Miles per hour is the road speed of the United States and the United Kingdom, which is a rare pairing — the UK uses miles for road speed and metric for nearly everything else.

Metres per second is the SI unit and the one physics is done in, which is why it turns up in wind readings and in almost nothing a driver would look at.

What it costs to round the factor

The factor is 0.44704, and almost nobody carries that around. Rounded to 0.45 it is off by 0.66 % — which stays invisible on small numbers and turns into a whole unit somewhere around 1,000 mph.

That is the number worth knowing before you round: not the error itself, but where it stops being ignorable. Below that point the shorter factor is the sensible one; above it, use the field above, which never rounds until it prints.

Two conversions at once, pulling opposite ways

A speed is a distance over a time, so going from a mile per hour to a metre per second converts both — and the two corrections work against each other. That is why the factor is 0.44704 rather than either of the numbers you would guess from the distance alone.

It also explains why the answer feels wrong the first time. Making the distance unit larger should make the number smaller, and making the time unit larger should make it bigger; what you see is only what is left after the two have cancelled.

The factor is a definition, not a measurement

The mile per hour has been defined in metric terms since the international yard and pound agreement of 1959, and in this page's units that comes out at 0.44704 m/s to one. The definition is exact by stipulation — it was not measured, and it cannot be refined by measuring it better. The decimal above is the whole of it, with nothing rounded away at the end.

Before that agreement the US and the British versions differed slightly, and old survey figures still carry the older definition. For anything outside land surveying the difference is far below the precision anybody is working to.

Where the digits of 0.44704 stop, and why

The factor terminates after five decimal places, which is unusual enough to be worth stating: 1,609.344 metres divided by 3,600 seconds is 0.44704 and then nothing. Both inputs are stipulated values, so there is no measurement uncertainty underneath and no sixth digit waiting to be discovered by a better experiment.

That makes the rounding question purely one of your own tolerance. Carrying 0.447 costs 0.0089 per cent, which at 100 mph is four thousandths of a metre per second. Carrying 0.45 costs 0.66 per cent, which is around 0.3 m/s at the same speed and is the first level at which the shortcut would show up in a reported result. Anything intended for a specification should take the full five digits and round once, at the end.

Sixty miles an hour is eighty-eight feet a second

Before American engineering had any reason to reach for SI it converted mph into feet per second, and the identity that made it easy is exact: one mile per hour is 22/15 ft/s, so 60 mph is exactly 88 ft/s and 30 mph is exactly 44. Sight-distance tables, signal timing and accident reconstruction in the United States are still built on that number.

It is worth knowing which of the two conversions your calculation wants before you do either. A traffic formula written in feet and seconds will accept 88 and reject 26.82; a drag or energy calculation with a density in kg/m³ will accept 26.82 and produce nonsense from 88. The mistake that is hard to catch is converting to one and then using a constant that assumed the other, because both answers are plausible-looking numbers in the tens.

What SI removes from a dynamics calculation

The reason a formula asks for metres per second is rarely the speed itself; it is the units it will be combined with. In SI a mass in kilograms times an acceleration in metres per second squared gives a force in newtons directly. In US customary units, pound-mass and pound-force share a name and differ by a factor of about 32.17, and every dynamics formula has to carry a constant to reconcile them or be silently written for one convention.

A worked example makes the size of it clear. A 3,500 lb car at 65 mph is 1,588 kg at 29.06 m/s, so its kinetic energy is half of 1,588 times 29.06 squared — about 670 kilojoules. Getting there in customary units means converting the weight to slugs or carrying the gravitational constant through, and the conversion to SI at the start is the shorter and less error-prone path even for a reader who thinks in pounds.

Wind speed crosses this boundary more than anything else

American structural design states basic wind speed in miles per hour as a three-second gust, and the physics of wind loading is a dynamic pressure of half the air density times velocity squared, with density in kilograms per cubic metre. That mismatch is resolved on almost every project, and it is resolved by converting the speed.

A 115 mph gust is 51.4 m/s. At the standard sea-level air density of 1.225 kg/m³, that gives a dynamic pressure of about 1.62 kilopascals. The order of operations matters more than the digits: convert the speed, then square it. Squaring first and converting the pressure requires the factor squared — 0.199845 — and a reader who reaches for 0.447 at that point is out by a factor of more than two.

Halve it, then shave a tenth

For an estimate without a calculator, halve the mph figure and take about ten per cent off the result. 60 gives 30 less 3, so 27, against a true 26.82. 100 gives 50 less 5, so 45, against 44.70. 35 gives 17.5 less 1.75, so 15.75, against 15.65.

The shortcut runs about two thirds of a per cent high, which is the right size for judging whether a number is in the range you expected. Dividing by 2.24 is the other version and lands 0.14 per cent low, but it is harder to do in your head and buys precision you would not use at that stage. Both are for checking the magnitude of an answer, not for producing one.

The mile that was retired, and the one that was never used here

The United States maintained two feet for most of a century — the international foot of exactly 0.3048 metres and the survey foot of 1200/3937 metres, which is larger by two parts per million. The survey version was withdrawn at the end of 2022 after decades of land records carrying both. It never touched this conversion: speeds have always been expressed with the international mile of exactly 1,609.344 metres.

The mile that does cause trouble here is the nautical one. A figure described loosely as "miles per hour" from a marine, aviation or hurricane source is often knots, built on a nautical mile of exactly 1,852 metres, and it is 15 per cent faster than the same number in statute miles per hour. Confirming which mile the source meant is the only part of this conversion where a mistake is large rather than decimal.

An acceleration figure hidden inside a published time

American performance data is usually a time rather than an acceleration, and converting the speed is what turns one into the other. Sixty miles an hour is 26.82 m/s, so a car reaching it in six seconds has averaged 4.47 m/s² — about 0.46 g. A van taking twelve seconds has averaged 2.24 m/s², or 0.23 g.

Those are averages over the run rather than peak figures, and they are the numbers that go into anything about load, restraint or ride comfort. Braking works the same way in reverse: a car stopping from 60 mph in 120 feet has decelerated from 26.82 m/s over 36.6 metres, which is about 9.8 m/s², or roughly one g. Getting there from the published figures needs both the speed and the distance in SI, and the speed is the one that arrives in the wrong unit.

Reporting the SI figure without inventing precision

A limit written as "70 mph" is a round number in a customary system, and converting it to 31.2928 m/s presents four significant figures that the original never claimed. Where the source value is round in miles per hour, say so and round the SI figure to a comparable coarseness — 31.3 m/s, or 31 if the context tolerates it.

The opposite case is a measurement rather than a limit. A wind tunnel reading of 63.4 mph is a real measurement to three figures and becomes 28.34 m/s, and dropping it to 28 discards information the instrument earned. The rule is the same either way: the number of digits should reflect the source, and the conversion factor is never the constraint because it is exact.

Convert mph to m/s: common questions

What is the exact factor from mph to m/s?

0.44704, and the digits stop there. A mile is exactly 1,609.344 metres and an hour is exactly 3,600 seconds, so the quotient terminates rather than running on. Rounding it to 0.447 is 0.0089 per cent low, which is smaller than almost any measurement it will be applied to.

What is 65 mph in m/s?

29.0576 m/s exactly, which rounds to 29.06. The value turns up constantly because 65 mph is the most common American interstate limit, and it is a useful anchor: a car at 65 mph covers a little over 29 metres in every second.

Should I convert to m/s or to feet per second?

It depends on which system the rest of the calculation is in. One mile per hour is exactly 22/15 feet per second, or 1.46667, which is why 60 mph is exactly 88 ft/s — a figure American traffic engineering has used for a century. Use ft/s to stay inside a US customary calculation, and m/s the moment anything else in the formula is metric.

Why do formulas insist on SI rather than mph?

Because SI is coherent: force in newtons, mass in kilograms and acceleration in metres per second squared relate by F = ma with no conversion constant. US customary dynamics needs a constant to reconcile pound-mass and pound-force, and every formula that omits it is silently assuming one system or the other. Converting the speed first removes the whole question.

How do I convert a wind speed given in mph for a load calculation?

Convert to m/s first, then square. A 115 mph gust is 51.4 m/s, and the dynamic pressure at sea-level air density is about 1.62 kPa. Doing it the other way round — squaring the mph figure and converting the result — needs the factor squared, 0.199845, and getting that wrong is a fivefold error rather than a small one.

Does the US survey mile affect this conversion?

No. The survey foot, retired at the end of 2022, differed from the international foot by two parts per million and applied to land surveying rather than to speed. Speeds in miles per hour have always used the international mile of exactly 1,609.344 metres, so there is no second answer to choose between here.

Going the other way: Metre per second to Mile per hour

One m/s is 2.23694 mph. It is the same relationship read backwards, so an answer from one page put through the other has to come back to where it started.

Where these figures come from

The claims this page makes about speed units are checkable, and these are the documents that settle them.

How this page works

The factor is a constant in the page and the arithmetic is four operations, so nothing is sent anywhere and nothing needs to be. The number you type never leaves the browser — there is no request for it to travel in.