Length units converter
Five everyday lengths, one exact answer: 1 meter is 3.280839895013 feet, not the rounded 3.28 that drifts on a long wall. Meters, feet, inches, yards and miles all pass through the meter with the 1959 international yard. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Value
- 1
- From
- Meters
- To
- Feet
- Result
- 3.280839895 feet
- Input
- 1
- Meters
- 1
This length units converter takes a finite length and a source unit, then returns the same physical distance in a target unit chosen from meters, feet, inches, yards, and miles. Those five names cover the everyday mix of SI and US customary lengths: a drawing in meters, a room in feet, a screen in inches, a sports field in yards, and a road in miles. The solver converts through the international metre using exact 1959 yard-and-pound factors, so one inch is 0.0254 m, one foot is 0.3048 m, one yard is 0.9144 m, and one international mile is 1609.344 m.
The five units and the exact SI factors behind every pair
Meters, feet, inches, yards, and miles are the five length names people actually type into a converter when a plan, a tape, a product spec, a pitch, or a road sign disagrees with the unit they need next. This landing is that closed set: it does not ask the visitor to pick from kilometres, centimetres, millimetres, nautical miles, or survey feet, because those are different searches.
Every pair is reduced to metres with definitional factors from the 1959 international yard and pound agreement, then divided by the target factor, so there is no pairwise matrix that can drift. One international inch is exactly 0.0254 metres. One international foot is twelve inches, so 0.3048 metres.
One international yard is three feet, so 0.9144 metres. One international mile is 5280 feet, so 1609.344 metres. Those identities are exact, not survey-foot variants and not the old 3.28-feet-per-metre shortcut that accumulates error on a long wall, a fabric order, or a road log.
Zero in any source unit maps to zero in the target. Signed lengths are accepted when you model offsets or deltas rather than physical cuts. Prefer this path when both units are in the five-name set; a broader hub is the wrong landing if the visitor already knows they want feet, inches, yards, miles, or metres.
Where a five-unit length converter earns its keep
Architects and site crews convert drawing metres into feet and inches for a US tape, then back again when the same opening must be filed on an SI schedule. Sports and landscaping teams convert field lengths in yards into metres for international equipment and into miles when a course is logged on a road computer. Teachers and exam generators need a deterministic oracle that rejects an unknown unit name instead of silently returning NaN a buggy grader might treat as success.
Logistics teams convert crate heights quoted in inches into metres for an international bill of lading, and product catalogs convert screen diagonals in inches into centimetres-worth of metres for a metric spec sheet. This landing targets people searching for a length units converter among meters, feet, inches, yards, and miles with exact factors. It is not a kilometre-to-mile primary form, not a centimetre-to-inch primary form, not a US survey-foot path, and not a mixed-unit parser for strings such as five foot seven.
Prefer this capability when both units are already in the five-name set and you want one call; if you must convert kilometres, centimetres, or millimetres, use a broader length hub instead. Stay inside the absolute range so the multiplies cannot overflow.
What you can do with it
Drawings, rooms, and tape measures
Convert plan metres into feet and inches for a US tape, or room feet into metres when the same opening must be filed on an SI schedule.
Sports fields, roads, and landscaping
Convert pitch yards into metres for international equipment, or road miles into metres and yards when a course log has to match a metric drawing.
Homework, catalogs, and shipping specs
Check textbook conversions among meters, feet, inches, yards, and miles with exact 0.0254 / 0.3048 / 0.9144 / 1609.344 factors and a clear error on a bad unit name.
FAQ
What happens if the value or unit name is invalid?
Missing fields, NaN, Infinity, non-numeric strings, and unknown names such as furlongs or kilometres are rejected and not charged.
How do I convert 1 meter to feet?
The result is 1 ÷ 0.3048 feet (about 3.280839895013), plus the intermediate length in metres.
How many feet and yards are in a mile?
One mile is 5280 feet or 1760 yards. Because a foot is exactly 0.3048 meters, the same mile is exactly 1609.344 meters, and the converter uses those exact values for every pair.
Why not just multiply meters by 3.28 to get feet?
Because 3.28 is a rounded shortcut. A meter is 3.280839895013 feet, and the missing part adds up on a long wall, a fabric order or a road log. The converter keeps the exact factor.
Which length units are not included here?
Kilometers, centimeters, millimeters, nautical miles and survey feet are left out on purpose. This converter covers only meters, feet, inches, yards and miles, the five names people mix up most on plans and signs.
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/length-converter \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"value":1,"from":"meters","to":"feet"}'const res = await fetch("https://api.kit.forhosting.com/conv/length-converter", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"value": 1,
"from": "meters",
"to": "feet"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/length-converter",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"value": 1,
"from": "meters",
"to": "feet"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/length-converter", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"value":1,"from":"meters","to":"feet"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"value":1,"from":"meters","to":"feet"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/length-converter", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"value": 1,
"from": "meters",
"to": "feet"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.length_converter",
"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.
Limits
max_abs | 1000000000000000 |
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 numbers and unknown unit names fail with invalid_input instead of inventing a length.
The five units and the exact SI factors behind every pair
The response echoes the parsed input, the canonical from and to names, the converted result, the intermediate length in metres, a formula string restating the four exact companions of the metre, and a short English message you can paste into a worksheet.
Input contract, rounding, aliases, and error behaviour
The documented names are meters, feet, inches, yards, and miles. On success the body includes input (the rounded source number), from and to as canonical names, result (the converted length), unit (the same canonical target), meters (the SI pivot), formula, and message. Round-trip checks are easy: one mile is 1760 yards and 5280 feet; twelve inches is one foot; three feet is one yard; 0.3048 metres is one foot. POST a JSON body with three required fields: value, a finite number or a strict numeric string; from, the source unit; and to, the target unit. The solver also accepts the compact aliases m, ft, in, yd, and mi, plus the singular forms meter, metre, foot, inch, yard, and mile, then normalizes them to the canonical plural before returning. Absolute values must stay inside the published magnitude ceiling so a Worker isolate cannot overflow a multiply into a non-finite result. Failed validation—missing fields, empty strings, NaN, Infinity, bare plus or minus signs, non-numeric phrases, unknown unit names such as furlongs or kilometres, values above the absolute limit, or a non-finite converted result—returns invalid_input naming the field and is never charged. Pricing is a flat $0.002 per successful request with unit item.
Where a five-unit length converter earns its keep
Failed tasks that return invalid_input do not consume prepaid balance, which keeps exploratory scripts cheap when learners deliberately omit value or pass a misspelled unit. Successful API calls bill as one item at $0.002.
Technical questions
Which length units can I convert?
Meters, feet, inches, yards, and miles. Aliases m, ft, in, yd, mi and the singular names are accepted and normalized to those canonical plurals.
What conversion factors does this length units converter use?
Exact 1959 international-yard identities via metres: 1 in = 0.0254 m, 1 ft = 0.3048 m, 1 yd = 0.9144 m, 1 mile = 1609.344 m. There is no survey-foot or approximate mode.
What does the length units converter cost?
The browser tool is free. API requests use prepaid KIT balance at $0.002 per successful call; invalid input is not billed.