Yard conversion
Type a length in yards and get its four companions at once: one yard is exactly 3 feet, 36 inches, 0.9144 meters and 91.44 centimeters. Built for sports pitches, fabric bolts and site layouts that mix units. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Yards
- 1
- Feet
- 3
- Inches
- 36
- Meters
- 0.9144
- Centimeters
- 91.44
The international yard is a defined length, not a guess. When a sports pitch, fabric bolt, construction layout, or school worksheet already quotes yards, the next question is almost always the same four companions: how many feet, how many inches, how many meters, and how many centimeters. This dedicated yard conversion answers that search with one required number. You send yards; you receive the four converted lengths from exact SI-and-imperial identities, not from a rounded survey table. Zero is a legal length and maps to zeros in every column.
Why a yard converts with exact international factors
The international yard is not a folk estimate. Since 1959 the yard used in science, sport, and most engineering in English-speaking countries is defined as exactly 0.9144 meters. That single SI identity is enough to derive every column this capability returns.
One international yard is three international feet by definition, so feet equal yards times three. Each international foot is twelve international inches, so one yard is thirty-six inches and inches equal yards times thirty-six. Meters equal yards times 0.9144.
Centimeters follow the SI milli-prefix on the meter: one meter is one hundred centimeters, therefore centimeters equal yards times 91.44. There is no US survey yard in this landing, no “about three feet” mental shortcut that later disagrees with a drawing, and no hidden round through statute miles. Zero yards maps to zero feet, zero inches, zero meters, and zero centimeters.
Negative lengths are rejected: a length converter is not a signed-delta calculator, and a minus sign on a form is almost always a typo rather than a physical length. If you need a survey-yard or chain-and-link path, this is the wrong page; the contract here is the international yard and those four companion units. Keep that distinction in mind when a legacy drawing still quotes a survey foot: this calculator will not silently mix the two systems, and that honesty is the whole point of a dedicated landing.
What you can do with it
Sports fields and mixed-unit reports
Pitch and field lengths stored in yards convert to feet, inches, meters, and centimeters for mixed-unit diagrams, broadcast graphics, and international reports.
Fabric, sewing, and textile yardage
Bolts and cutting plans quoted in yards become inches and centimeters for hems, patterns, and shop tickets without a general unit hub.
Linear construction and site layouts
Running yards on a layout convert to feet and SI meters or centimeters for drawings that must speak both customary and metric.
FAQ
Why is one yard exactly 0.9144 meters?
The international yard has been defined as exactly 0.9144 meters since the 1959 yard and pound agreement. One yard is also exactly three international feet and thirty-six international inches. There is no survey-yard mode.
Are negative lengths allowed?
Zero is allowed and converts to zero in every column. Failed tasks are not charged.
Is the yard conversion free?
The browser tool is free and runs locally.
How many feet, inches and meters are 10 yards?
10 yards are 30 feet, 360 inches, 9.144 meters and 914.4 centimeters. Converting one yard and ten yards is a quick way to check that a drawing or worksheet uses the exact yard.
Does this use the US survey yard?
No. It uses only the international yard defined in 1959 as 0.9144 meters. If a legacy drawing quotes survey units, this page will not mix the two systems.
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/yard-conversion \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"yards":10}'const res = await fetch("https://api.kit.forhosting.com/conv/yard-conversion", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"yards": 10
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/yard-conversion",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"yards": 10
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/yard-conversion", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"yards":10}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"yards":10}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/yard-conversion", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"yards": 10
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.yard_conversion",
"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
A negative value is rejected as invalid_input, because a length converter is not a signed-delta tool.
Why a yard converts with exact international factors
Results are rounded only to keep JSON stable across runtimes, not because the factors themselves are approximate.
Input contract, response shape, and error behaviour
Prefer sending bare numbers when you control the client. Round-trip sanity checks are easy: convert one yard and confirm you receive three feet, thirty-six inches, 0.9144 meters, and 91.44 centimeters; convert ten yards and confirm thirty feet, three hundred sixty inches, 9.144 meters, and 914.4 centimeters. If those identities fail, the input was not a finite non-negative yard value. Send a JSON body with one required finite number field named yards. Aliases yd, value, length, yards_value, and distance are accepted so SDK clients and form posts can use the name that fits the product. The value must be a JSON number or a strict numeric string without units, thousand separators, or currency symbols. On success the response echoes rounded yards and returns feet, inches, meters, and centimeters as four finite numbers, plus formula, method, from_unit, a short English message, and an ordered steps array that shows each identity. Failed validation—missing fields, non-finite numbers, bare plus or minus signs, non-numeric strings, negative lengths, 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. Authors who wrap the API in a form should surface the yards field as a number control, not a free-text unit parser, because this capability never reads a unit suffix.
Where a dedicated yard-conversion landing earns its keep
Prefer this landing when the search intent is specifically yard conversion, not a general multi-unit hub, not a yards-to-feet-only school step, and not a cubic-yard volume calculator for mulch or concrete. American football and rugby notes that list field lengths in yards but also need meters for mixed-unit reports, fabric and sewing plans that quote yardage and then need inches and centimeters for hems, construction layouts that still mark running yards on a site that also publishes SI drawings, landscaping linear runs that must appear in feet and meters, and classroom worksheets that ask students to convert the same yard value into four companion units all need the same deterministic four-column contract. Stay inside the published range so the centimeter multiply cannot overflow. Pair the exact path with a mental check: multiply by three for feet, by thirty-six for inches, by 0.9144 for meters, and by 91.44 for centimeters; if the API disagrees, the input was not a finite non-negative yard value. Failed tasks that return invalid_input do not consume prepaid balance, which keeps exploratory scripts cheap when learners deliberately omit yards or pass text. Successful conversions bill as one item at $0.002; validation failures are free.
Technical questions
How do I convert yards to feet, inches, meters, and centimeters?
Send JSON with yards set to a non-negative finite number (for example yards: 10). The response returns feet, inches, meters, and centimeters from the exact identities ft = yd×3, in = yd×36, m = yd×0.9144, and cm = yd×91.44.
What happens on missing or non-numeric input?
The API returns invalid_input naming the problem (for example a missing yards field or a non-finite number). Failed tasks are not charged.