Mph to knots converter
Bring a road or wind speed into the unit used at sea and in the air: 1 mph is 0.868976241901 knots, taken from the exact 1609.344-meter mile and 1852-meter nautical mile, not the rough 0.87 rule. 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.8689762419 kn
- Converted
- 0.8689762419
- Knots
- 0.8689762419
- Kn
- 0.8689762419
A miles-per-hour-to-knots converter turns a statute road or land-speed reading into the nautical unit used by marine charts, aviation winds aloft, and maritime forecasts. Approximate mental shortcuts such as multiply by zero point eight seven are rejected in favour of the defined constants, so homework checks and navigation app exports match engineering and Admiralty tables.
Why miles per hour and knots still meet at 1609.344/1852
Miles per hour remain the default road-speed unit in the United States and in large parts of transport media that quote vehicle limits, surface 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.
A knot is one international nautical mile per hour, and the international nautical mile is defined as exactly one thousand eight hundred fifty-two metres. Dividing those two metre lengths yields the exact conversion factor: knots equal miles per hour times one thousand six hundred nine point three four four over one thousand eight hundred fifty-two. Marine charts, shipping notices, aviation METAR winds, and yacht race handicaps almost always speak in knots, so a driver or coach who only has an mph reading still needs a precise bridge.
Teachers and skippers often still teach a rough rule of thumb near zero point eight seven, but that introduces a scale error that shows up immediately on a sixty-mile-per-hour storm gust or a ten-mile-per-hour light breeze.
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 the rounded value of one thousand six hundred nine point three four four over one thousand eight hundred fifty-two knots, or convert sixty miles per hour and confirm the product of sixty times that exact ratio after twelve-decimal rounding.
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 knots, convert miles per hour to knots, or an exact nautical conversion calculator; it is not a general multi-unit speed hub, not a knots-to-mph primary form, not a Beaufort scale force converter, and not a kilometres-per-hour tool.
Prefer this capability when the input is already in statute miles per hour and you only need knots; if you must convert among many speed units in one call, use a broader speed converter instead.
What you can do with it
Marine and yacht race logs
Turn coastal or road-side mph wind and boat-speed readings into knots for logbooks, race handicaps, and Admiralty-style reports with the same exact factor every row.
Aviation and weather briefings
Convert surface wind and ground-speed figures quoted in mph into knots for METAR-style notes, dispatch briefs, and international weather products.
FAQ
Is the factor exact or approximate?
Exact. This tool uses the international statute mile (1959 yard and pound agreement) and the international nautical mile of 1852 m, not a rough “about 0.87” estimate.
Can I convert knots back to mph?
This capability is mph → knots only. Divide knots by (1609.344/1852) on your side, or use a bidirectional speed converter for other units.
Is the mph to knots converter free?
The browser tool is free and runs locally.
Why do sailors and pilots use knots instead of mph?
A knot is one nautical mile per hour, and marine charts, shipping notices, aviation wind reports and yacht race handicaps all quote speed in knots. An mph reading has to be converted before you can compare it.
Is rounding to 0.87 good enough?
For a quick idea, yes, but the error grows with speed and shows on a 60 mph storm gust. The exact ratio, 1609.344 divided by 1852, keeps the result in line with nautical 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-knots \
-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-knots", {
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-knots",
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-knots", 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-knots", 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_knots",
"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 knots, kn, result, and converted to the same rounded knot magnitude, unit to the token kn, from_unit to mph and to_unit to kn, factor and knots_per_mph to the exact ratio after fixed rounding, metres_per_statute_mile to one thousand six hundred nine point three four four, metres_per_nautical_mile to one thousand eight hundred fifty-two, formula to the string kn equals mph times open parenthesis one thousand six hundred nine point three four four slash one thousand eight hundred fifty-two close parenthesis, 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
Homework and unit-test fixtures
Students and engineers convert classroom mph readings to knots and pin golden JSON so browser and API arithmetic never drift.
Technical questions
What formula converts mph to knots?
kn = mph × (1609.344 / 1852). One international statute mile is exactly 1609.344 metres and one international nautical mile is exactly 1852 metres, so 1 mph = 1609.344/1852 kn 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.