Feet converter
Enter a length in feet and get it in inches, yards, meters and centimeters at once: 1 ft is 12 in, 0.3048 m and 30.48 cm, all exact factors. Handy for carpentry, fabric orders and metric drawings. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Feet
- 1
- Inches
- 12
- Yards
- 0.3333333333
- Meters
- 0.3048
- Centimeters
- 30.48
A feet converter turns a length measured in international feet into the four companions people actually need on the same page: inches for tape measures, lumber, and product specs; yards for fabric, sports fields, and landscaping; meters for SI drawings and international shipping; and centimeters for school work, garments, and packaging. Enter a finite number of feet.
Why feet still need four companion units on one page
The international foot remains the everyday length unit for US rooms, lumber yards, door heights, athletic fields, and DIY plans, yet people who search for a feet converter almost never want only one other unit. A carpenter needs inches to mark a cut on a tape measure, a fabric buyer needs yards to order a bolt, an architect needs meters for an SI drawing, and a student needs centimeters for a science lab write-up.
Serving those four companions from a single feet input is the landing that matches that search, not a general hub that asks the visitor to pick from and to units they may not remember. The factors are definitional, not estimates. One foot is exactly twelve inches.
One yard is exactly three feet, so yards equal feet divided by three. Since the 1959 international yard and pound agreement, one international foot is exactly zero point three zero four eight metres, so meters equal feet times 0.3048. One metre is one hundred centimeters, so centimeters equal feet times 30.48.
Approximate mental shortcuts such as treating a foot as thirty centimeters introduce a scale error that shows up on a long wall, a fabric order, or a shipping label. Non-finite input is rejected because a length that is NaN or infinite is not a measurement anyone can cut, ship, or grade.
Where a feet converter earns its keep, and what it is not
Carpentry and finish work convert board and opening lengths in feet into inches for a tape mark and into meters when the same job also files SI drawings. Sports and landscaping crews convert field and fence lengths in feet into yards for paint and turf orders, then into centimeters for equipment specs that arrived from a metric catalog. Teachers and exam generators need a deterministic oracle that rejects a non-numeric answer instead of silently returning NaN a buggy grader might treat as success.
Logistics teams convert crate and pallet heights quoted in feet into meters and centimeters for international bills of lading. This landing targets people searching for feet converter, feet to inches, feet to yards, feet to meters, or feet to centimeters with exact factors. It is not a general multi-unit length hub, not a reverse centimeters-to-feet 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 the input is already in feet and you need the four companions in one call; if you must convert among many units with a from and a to selector, use a broader length converter instead. Stay inside the absolute range so the multiplies cannot overflow into a non-finite result the solver must reject.
What you can do with it
Carpentry, lumber, and openings
Builders convert board, door, and ceiling lengths from feet into inches for tape marks and into meters or centimeters for SI drawings and hardware catalogs.
Sports, fabric, and landscaping
Coaches, sewers, and grounds crews convert field, bolt, and fence lengths in feet into yards for orders and into centimeters for metric equipment specs.
Homework, shipping, and product specs
Students, shippers, and catalog editors verify feet-to-metric answers with exact 0.3048 and 30.48 factors and a clear error when a non-numeric value is submitted.
FAQ
What happens if I send non-numeric input?
Missing fields, NaN, Infinity, and non-numeric strings are rejected and not charged.
Is the feet converter free?
The browser tool runs free on your device.
Why not just count a foot as thirty centimeters?
Because a foot is exactly 30.48 centimeters, and the shortcut drops almost half a centimeter on every foot. On a long wall, a fabric order or a shipping label, that scale error adds up quickly.
How many feet are in a yard?
Exactly three. That is why the converter divides feet by 3 to get yards, so 1 foot shows as 0.333333333333 yards and 3 feet as exactly 1 yard.
Why is a foot exactly 0.3048 meters?
Because the 1959 international yard and pound agreement fixed it that way. Since then the international foot has been defined as exactly 0.3048 meters, so the conversion is a definition, not an estimate.
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/feet-converter \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"feet":1}'const res = await fetch("https://api.kit.forhosting.com/conv/feet-converter", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"feet": 1
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/feet-converter",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"feet": 1
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/feet-converter", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"feet":1}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"feet":1}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/feet-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
{
"feet": 1
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.feet_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.
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
The solver multiplies by exact definitional factors—twelve inches per foot, one yard per three feet, zero point three zero four eight metres per international foot, and thirty point four eight centimeters per foot—then returns all four converted lengths in one JSON object. Missing values, NaN, Infinity, and non-numeric strings fail with invalid_input instead of inventing a length.
Input contract, exact factors, and what the response contains
Round-trip sanity checks are easy: convert one foot and confirm twelve inches, one third of a yard, zero point three zero four eight meters, and thirty point four eight centimeters; convert three feet and confirm one yard; convert zero and confirm four zeros. Prefer sending bare numbers when you control the client; string numbers are accepted only when they match a strict finite numeric pattern without unit suffixes, thousand separators, or mixed phrases such as five feet seven inches. Send a JSON body with one required finite number named feet. Aliases ft, value, length, and foot are accepted so SDK clients and form posts can use the name that fits the product. Absolute values must stay within the published magnitude ceiling so a Worker isolate cannot overflow into a non-finite result. On success the response echoes rounded feet and returns inches, yards, meters, and centimeters as the four equivalent lengths, plus a formula string restating the four exact factors and a short English message you can paste into a worksheet. Failed validation—missing fields, non-finite numbers, bare plus or minus signs, non-numeric strings, values above the absolute limit, 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.
Where a feet converter earns its keep, and what it is not
Failed tasks that return invalid_input do not consume prepaid balance, which keeps exploratory scripts cheap when learners deliberately omit feet or pass text. Successful API calls bill as one item at $0.002.
Technical questions
How do I convert feet to inches, yards, meters, and centimeters?
Send JSON with feet set to a finite number (for example feet: 1). The response returns inches = feet × 12, yards = feet ÷ 3, meters = feet × 0.3048, and centimeters = feet × 30.48, plus a formula string.
What conversion factors does this feet converter use?
Exact international-foot factors: 1 ft = 12 in, 1 yd = 3 ft, 1 ft = 0.3048 m, and 1 ft = 30.48 cm. There is no survey-foot or approximate mode.
Can I use aliases instead of the field name feet?
Yes. ft, value, length, and foot are accepted aliases for the same required length field.