Feet to yards converter
Divide by exactly 3 to turn feet into yards: 9 ft is 3 yd, with no rough mental shortcut. Handy for football field markings, fabric orders, golf yardages and landscaping beds. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Feet
- 9
- Result
- 3 yd
- Converted
- 3
- Yards
- 3
- From unit
- ft
A feet-to-yards converter turns a length measured in feet into the international yard value used on American football fields, fabric and textile orders, golf course plans, landscaping beds, and US construction notes. Mental shortcuts that roughly divide by three are unnecessary here because the factor is an exact integer definition, so homework checks and product tables match engineering practice without drift.
Why feet and yards still meet at the exact factor three
Feet remain the everyday imperial length on US construction drawings, property surveys, tape measures, and many school math exercises. International yards remain standard on American football fields, many US golf course yardages, fabric bolt labels sold in yards, and landscaping or mulch notes that quote bed length in yards rather than feet. The bridge between them is not a survey approximation: by long-standing definition, one international yard equals exactly three feet.
That makes the conversion a single exact division, yards equals feet divided by three, or equivalently feet times the reciprocal factor one third. Teachers sometimes still treat the conversion as optional rounding of a rough mental estimate, but because the constant is an integer there is no scale error to hide—three feet is one yard on every textbook row.
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 nine feet and confirm you receive exactly three yards after rounding, or convert one hundred feet and confirm thirty-three point three repeating yards rounded to twelve decimals.
When teaching, pair the exact path with a tape-measure demo so students see that every three-foot stick is one yard with no leftover. 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 feet to yards, convert feet to yards, or an exact three-feet-per-yard calculator; it is not a general multi-unit length hub, not a yards-to-feet primary form, not a metres or inches tool, and not an astronomical distance converter.
Prefer this capability when the input is already in feet and you only need international yards; if you must convert among many units in one call, use a broader unit converter instead.
What you can do with it
Sports field and pitch planning
Turn tape-measure lengths in feet into international yards for US football markings, coaching notes, and equipment layout with the same exact factor every row.
Fabric, textile, and retail length checks
Merchants convert foot measurements and pattern pieces to yards and compare hand work against deterministic steps before publishing size charts.
FAQ
What formula converts feet to yards?
Yards = feet ÷ 3. One international yard is defined as exactly three feet.
Can I convert yards back to feet?
This capability is feet → yards only. Multiply yards by 3 on your side, or use a bidirectional length converter for other units.
Is the feet to yards converter free?
The browser tool is free and runs locally.
How many yards is 100 feet?
About 33.333 yards, with the 3 repeating forever, because 100 does not divide evenly by 3. The converter rounds such results to twelve decimals, so you can round further to suit a fabric order or a field plan.
Where are yards used instead of feet?
Mainly on American football fields, in many US golf course yardages, on fabric bolt labels and in landscaping or mulch notes that give bed length in yards. Feet stay common on construction drawings and tape measures.
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-to-yards \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"feet":9}'const res = await fetch("https://api.kit.forhosting.com/conv/feet-to-yards", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"feet": 9
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/feet-to-yards",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"feet": 9
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/feet-to-yards", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"feet":9}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"feet":9}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/feet-to-yards", 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": 9
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.feet_to_yards",
"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 feet. Aliases ft, value, length, feet_value, distance, and foot are accepted so SDK clients and form posts can use the name that fits the product. On success the response echoes rounded feet, sets yards, result, and converted to the same rounded yard magnitude, unit to the token yd, from_unit to ft and to_unit to yd, factor to the rounded reciprocal one third, feet_per_yard to the exact constant three, formula to the string yards equals feet divided by three, 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 feet or pass text.
Integration use cases
Homework and unit-test fixtures
Students and engineers convert classroom foot readings to yards and pin golden JSON so browser and API arithmetic never drift.
Technical questions
Is the factor 3 exact or approximate?
Exact. This tool uses the definition 1 yd = 3 ft, not a rough estimate or survey variant.
What happens on missing or non-numeric input?
The API returns invalid_input naming the problem (for example a missing feet field). Failed tasks are not charged.