Mph to meters per second
Put a road or wind speed into the SI unit physics uses: 1 mph is exactly 0.44704 m/s, because a mile is 1609.344 meters and an hour is 3600 seconds, so 60 mph comes out as 26.8224 m/s. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Mph
- 1
- Result
- 0.44704 m/s
- Converted
- 0.44704
- Mps
- 0.44704
- From unit
- mph
A miles-per-hour-to-metres-per-second converter turns a statute road-speed or wind reading into the SI unit used by physics problems, sensor documentation, and engineering reports. Approximate mental shortcuts such as multiply by zero point four five are rejected in favour of the defined constant, so homework checks and telemetry exports match published tables.
Why miles per hour and metres per second still meet at 0.44704
Miles per hour remain the default road-speed and many weather-media unit in the United States, the United Kingdom in everyday contexts, and large parts of transport reporting that quote vehicle limits, wind gusts, or pacing in mph. One mile per hour is one statute mile of travel in one hour.
The international statute mile has been fixed at exactly one thousand six hundred nine point three four four metres since the 1959 yard and pound agreement, and one hour is exactly three thousand six hundred seconds, which makes one mile per hour equal to exactly zero point four four seven zero four metres per second after dividing one thousand six hundred nine point three four four by three thousand six hundred.
Metres per second are the SI base-derived speed unit that physics curricula, fluid-dynamics notes, automotive sensor datasheets, and most international engineering product copy expect. The bridge between them is therefore a single exact multiplication, metres per second equals miles per hour times one thousand six hundred nine point three four four divided by three thousand six hundred, not a survey approximation or a memory of “about zero point four five.”
Teachers and engineers often still teach a rough rule of thumb, but that introduces a scale error that shows up immediately on a sixty-mile-per-hour highway limit or a hundred-mile-per-hour storm gust.
Practical tips, checks, and related searches
Prefer sending bare numbers when you control the client; string numbers are accepted only when they match a strict finite numeric pattern without units, thousand separators, or currency symbols. Round-trip sanity checks are easy: convert one mile per hour and confirm you receive exactly zero point four four seven zero four metres per second after rounding, or convert sixty miles per hour and confirm twenty-six point eight two two four metres per second.
When teaching, pair the exact path with a rough mental shortcut so students see the drift on higher speeds. Stay inside the absolute range so the multiplication cannot overflow into a non-finite result the solver must reject. This landing targets people searching for mph to meters per second, convert miles per hour to m/s, or an exact zero point four four seven zero four calculator; it is not a general multi-unit speed hub, not an m/s-to-mph primary form, not a knots tool, and not a Beaufort scale force converter.
Prefer this capability when the input is already in statute miles per hour and you only need metres per second; if you must convert among many speed units in one call, use a broader speed converter instead.
What you can do with it
Physics and engineering homework
Turn textbook mph examples into SI metres per second for kinematics problems, free-body checks, and lab write-ups with the same exact factor every row.
Sensor and vehicle telemetry
Convert road or wind speeds quoted in mph into m/s for simulation configs, CAN-bus documentation, and SI-facing dashboards.
FAQ
Is 0.44704 exact or approximate?
Exact. This tool uses the international statute mile definition (1959 yard and pound agreement) and 3600 seconds per hour, not a rough “about 0.45” estimate.
Can I convert m/s back to mph?
This capability is mph → m/s only. Multiply m/s by 3600/1609.344 on your side, or use the dedicated meters-per-second-to-mph converter for the inverse landing.
Is the mph to meters per second converter free?
The browser tool is free and runs locally.
How many meters per second is 60 mph?
60 mph is 26.8224 meters per second. Each mile per hour adds exactly 0.44704 m/s, so a highway limit turns into the figure a physics problem or a sensor datasheet expects.
What goes wrong with the 0.45 shortcut?
It overshoots a little on every mile per hour, and the gap adds up as the speed climbs, so a storm gust of 100 mph lands visibly off. The exact 0.44704 keeps the result in line with published tables.
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/mph-to-meters-per-second \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"mph":60}'const res = await fetch("https://api.kit.forhosting.com/conv/mph-to-meters-per-second", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"mph": 60
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/mph-to-meters-per-second",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"mph": 60
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/mph-to-meters-per-second", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"mph":60}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"mph":60}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/mph-to-meters-per-second", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"mph": 60
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.mph_to_meters_per_second",
"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.
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
Invalid or missing input fails with a clear invalid_input error instead of inventing a number.
How to call the API and what comes back
Absolute values must stay within the published limit of one trillion. Send a JSON body with one required finite number field named mph. Aliases mi_h, mi_per_h, miles_per_hour, value, speed, mph_value, and mi_per_hour are accepted so SDK clients and form posts can use the name that fits the product. On success the response echoes rounded mph, sets mps, result, and converted to the same rounded metres-per-second magnitude, unit to the token m/s, from_unit to mph and to_unit to m/s, factor and mps_per_mph to the exact constant zero point four four seven zero four after fixed rounding, metres_per_mile to one thousand six hundred nine point three four four, formula to the string m/s equals mph times one thousand six hundred nine point three four four divided by three thousand six hundred, message to a short English summary, and steps to an ordered array of substitution lines. Failed validation—missing fields, non-finite numbers, bare plus or minus signs, non-numeric strings, values outside absolute limits, or a non-finite converted result—returns invalid_input and is never charged. Pricing is a flat $0.002 per successful request with unit item and zero marginal unit price.
Practical tips, checks, and related searches
Failed tasks that return invalid_input do not consume prepaid balance, which keeps exploratory scripts cheap when learners deliberately omit mph or pass text.
Integration use cases
Unit-test fixtures and golden JSON
Students and engineers pin mph-to-m/s golden outputs so browser and API arithmetic never drift across CI runs.
Technical questions
What formula converts mph to meters per second?
m/s = mph × 1609.344 / 3600. One international statute mile is defined as exactly 1609.344 metres, and one hour is 3600 seconds, so 1 mph = 0.44704 m/s exactly.
What happens on missing or non-numeric input?
The API returns invalid_input naming the problem (for example a missing mph field). Failed tasks are not charged.