Meters to feet converter
Get the exact feet behind a metre reading: a 10.0584-metre storey comes out at exactly 33 feet, because the converter divides by 0.3048 instead of multiplying by a rounded 3.28. Made for plans, labels and import papers. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Meters
- 1
- Result
- 3.280839895 ft
- Converted
- 3.280839895
- Feet
- 3.280839895
- From unit
- m
People who type m to ft want one number: how many international feet match a length already measured in metres. Rough classroom shortcuts such as multiply by 3.28 are not used, because that approximation drifts on building heights, cable runs, and athletic marks.
What m to ft means and why the factor is exactly 0.3048
Metres and international feet describe the same physical length in two unit systems that still have to meet on drawings, labels, and import documents. The metre is the SI base unit of length. The international foot is the imperial length printed on US architectural plans, interior elevations, ceiling schedules, furniture catalogs, and many aviation clearance notes.
Searchers who type the shorthand query m to ft are not looking for a survey treatise; they want the exact factor that turns a metre reading into feet without a remembered 3.28 shortcut. That factor is not a floating estimate. The 1959 international yard and pound agreement defined one yard as exactly 0.9144 metres.
Because one yard contains three feet, one international foot equals 0.3048 metres exactly. The conversion is therefore a single division: feet equals metres divided by 0.3048, equivalently metres multiplied by the reciprocal 1/0.3048, which expands to about 3.280839895013. Classroom memory of times 3.28 already drops digits, and those dropped digits show up on a hundred-metre facade, a fifty-metre cable, or a 10.0584-metre storey height that should be exactly thirty-three feet.
This capability hard-codes 0.3048. It does not apply the obsolete US survey foot, does not read a factor from a table, and does not depend on the clock. Zero metres converts to zero feet.
Checks, teaching use, and when to pick this converter
Send a bare number when you control the client. String numbers are accepted only when they match a strict finite numeric pattern, without unit suffixes, thousand separators, or currency symbols. Two sanity checks are worth baking into tests: 0.3048 metres must return one foot after rounding, and one metre must return 1/0.3048 feet, about 3.280839895013.
When teaching, show the 3.28 shortcut next to the exact path so students see the drift on a 100-metre facade or a 50-metre cable run. Stay inside the published maximum of one trillion metres so the division cannot overflow into a non-finite result the solver must reject. This page is for the query m to ft and related phrases such as convert meters to feet or metres to feet calculator; it is not a general multi-unit length hub, not a feet-to-metres primary form, and not a yards or inches converter.
Prefer it when the input is already metres and you only need international feet.
What you can do with it
Architectural heights and room notes
Turn metric elevation marks into international feet for US drawing title blocks, ceiling schedules, and clearance notes without a 3.28 approximation.
Homework and lab conversions
Students convert metre readings to feet and compare hand work against deterministic steps that use the exact 0.3048 definition.
Product specs and import labels
Export warehouse lengths stored in metres to foot fields on US-facing spec sheets with a stable twelve-decimal contract.
FAQ
Why 0.3048 instead of multiplying by 3.28?
One international foot is defined as exactly 0.3048 metres. Times 3.28 is a rounded reciprocal and drifts on long lengths; this tool divides by 0.3048.
Does 0.3048 metres equal one foot?
Yes. After twelve-decimal rounding, 0.3048 m returns 1 ft. One metre returns about 3.280839895013 ft.
How many feet is one meter?
One meter is 3.280839895013 feet. That figure is 1 divided by 0.3048, the exact length of an international foot in meters, so it does not drift on long runs.
Can I convert a negative number of meters?
No. This converter is meant for physical sizes, so negative meters are refused instead of being treated as a signed difference. Zero meters simply gives zero feet.
Does it use the US survey foot?
No. It uses only the international foot of exactly 0.3048 meters, fixed by the 1959 yard and pound agreement. The obsolete US survey foot is never applied, so results match current plans and labels.
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/m-to-ft \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"meters":1}'const res = await fetch("https://api.kit.forhosting.com/conv/m-to-ft", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"meters": 1
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/m-to-ft",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"meters": 1
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/m-to-ft", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"meters":1}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"meters":1}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/m-to-ft", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"meters": 1
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.m_to_ft",
"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 | 1000000000000 |
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
Negative lengths and non-finite values fail with invalid_input instead of a silent invented number.
Input contract, response shape, and what fails
Negative metres also fail: a signed delta is not a length in this landing, which exists for physical sizes rather than vector components. Failed validation is not billed. Keep requests small, pin the rounded feet value in tests, and you get a reproducible m to ft contract for worksheets, CAD notes, and edge scripts. Send a JSON body with one required field named meters, a non-negative finite number. Aliases metres, m, value, and length are accepted so forms and SDKs can send the name that matches the rest of the product, including the shorthand m that people type after searching m to ft. Missing fields, empty strings, NaN, infinities, bare plus or minus signs, and non-numeric strings fail with invalid_input and name the field. On success the response echoes rounded meters; sets feet, result, and converted to the same rounded foot magnitude; sets unit to ft, from_unit to m, and to_unit to ft; sets factor to the rounded reciprocal 1/0.3048; sets meters_per_foot to 0.3048; sets formula to the string feet equals meters divided by 0.3048; sets message to a short English summary; and sets steps to an ordered substitution list you can print next to a homework check. Pricing is a flat $0.002 per successful request with unit item.
Checks, teaching use, and when to pick this converter
If you actually measured centimetres, inches, or yards, use a dedicated one-way converter for that pair instead of pre-scaling by hand and then calling this endpoint. Failed tasks that return invalid_input do not consume prepaid balance, which keeps classroom scripts cheap when learners omit meters or type words such as ten. Because the path is pure parse, there is no model, no outbound fetch, and no clock in the result, so repeating the same metres value always yields the same feet JSON.
Technical questions
How do I convert m to ft?
Send a non-negative finite number in meters (aliases m, metres, value, length). The API returns feet = meters ÷ 0.3048, the exact international-foot definition.
Why are negative metres rejected?
This landing converts a physical length. A negative value is not a length here, so the task fails with invalid_input and is not billed.
What does the m to ft converter cost?
The browser tool is free. API requests use prepaid KIT balance at $0.002 per successful call; invalid input is not billed.