Meters to feet converter
100 meters are about 328 feet, worked out by dividing by exactly 0.3048 rather than multiplying by a rounded 3.28. Use it for room sizes, building heights, clearance notes or catalogs sold in feet. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Meters
- 0.3048
- Result
- 1 ft
- Converted
- 1
- Feet
- 1
- From unit
- m
A metres-to-feet converter turns a metric length into the international foot value used on US construction drawings, building heights, room dimensions, aviation clearance notes, and product specifications sold in feet. Approximate mental shortcuts such as multiply by three point two eight are rejected in favour of the 1959 yard and pound agreement constant, so homework checks and product tables match engineering definitions.
Why metres and international feet still meet at 0.3048
Metres belong to the SI base unit for length used in science, metric construction drawings, athletic track markings outside the United States, and most international product specifications. International feet remain standard on US architectural plans, building height labels, room dimensions, furniture catalogs, and many aviation and maritime clearance notes that still quote imperial length.
The bridge between them is not a survey approximation: since the 1959 international yard and pound agreement, one international foot is defined as exactly zero point three zero four eight metres, because one yard is zero point nine one four four metres and one yard equals three feet. That makes the conversion a single exact division, feet equals metres divided by zero point three zero four eight, or equivalently metres times the reciprocal factor one over zero point three zero four eight.
Teachers and trades often still teach the rough rule of thumb multiply by three point two eight, but that introduces a scale error that shows up immediately on a one-hundred-metre facade or a fifty-metre cable run.
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 a known textbook value such as zero point three zero four eight metres and confirm you receive exactly one foot after rounding, or convert one hundred metres and confirm roughly three hundred twenty-eight point zero eight three nine eight nine five feet.
When teaching, pair the exact path with the mental shortcut so students see the drift on long lengths. Stay inside the absolute range so the division cannot overflow into a non-finite result the solver must reject. This landing targets people searching for meters to feet, convert metres to feet, or an exact zero point three zero four eight calculator; it is not a general multi-unit length hub, not a feet-to-metres primary form, not a yards or inches tool, and not an astronomical distance converter.
Prefer this capability when the input is already in metres and you only need international feet; if you must convert among many units in one call, use a broader unit converter instead.
What you can do with it
Construction and architectural plan checks
Turn metric facade heights and room lengths from international drawings into international feet for US-facing schedules, permit notes, and site layout with the same exact factor every row.
Product specs and retail size charts
Merchants convert metre cable, pipe, and furniture lengths to feet and compare hand work against deterministic steps before publishing size charts.
FAQ
What formula converts meters to feet?
Feet = metres ÷ 0.3048. One international foot is defined as exactly 0.3048 metres by the 1959 international yard and pound agreement.
Is 0.3048 exact or approximate?
Exact. This tool uses the international foot definition, not a US survey foot or a rough multiply-by-3.28 estimate.
Can I convert feet back to metres?
This capability is metres → feet only. Multiply feet by 0.3048 on your side, or use a bidirectional length converter for other units.
Is the meters to feet converter free?
The browser tool is free and runs locally.
How many feet is 100 meters?
About 328 feet. The converter divides 100 by 0.3048, the exact length of one foot in meters, and keeps the decimals that a rounded 3.28 would lose.
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/meters-to-feet \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"meters":0.3048}'const res = await fetch("https://api.kit.forhosting.com/conv/meters-to-feet", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"meters": 0.3048
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/meters-to-feet",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"meters": 0.3048
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/meters-to-feet", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"meters":0.3048}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"meters":0.3048}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/meters-to-feet", 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": 0.3048
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.meters_to_feet",
"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
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 meters. Aliases metres, m, value, length, meters_value, and distance are accepted so SDK clients and form posts can use the name that fits the product. On success the response echoes rounded meters, sets feet, result, and converted to the same rounded foot magnitude, unit to the token ft, from_unit to m and to_unit to ft, factor to the rounded reciprocal one over zero point three zero four eight, meters_per_foot to the exact constant zero point three zero four eight, formula to the string feet equals meters divided by zero point three zero four eight, 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 meters or pass text.
Integration use cases
Homework and unit-test fixtures
Students and engineers convert classroom metre readings to feet and pin golden JSON so browser and API arithmetic never drift.
Technical questions
What happens on missing or non-numeric input?
The API returns invalid_input naming the problem (for example a missing meters field). Failed tasks are not charged.