Yard to meter conversion
Change yards into meters with the exact 1959 definition: one yard is precisely 0.9144 meters, never the rough 0.91 that drifts on long lengths. Handy for football fields, golf course markers, fabric sold by the yard and metric plans. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Yards
- 1
- Result
- 0.9144 m
- Converted
- 0.9144
- Meters
- 0.9144
- From unit
- yd
A yard-to-meter conversion turns an imperial length into the SI metre used on metric construction drawings, athletic track markings, laboratory notebooks, and international product specifications. Approximate mental shortcuts such as multiply by zero point nine one are rejected in favour of the 1959 yard and pound agreement constant, so homework checks and product tables match engineering definitions.
Why yards and metres still meet at exactly 0.9144
Yards remain everyday length on American football fields, many United States golf course markers, fabric bolt labels sold by the yard, and some civil plans that still quote imperial linear measure. 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. The bridge between them is not a survey approximation: since the 1959 international yard and pound agreement, one international yard is defined as exactly zero point nine one four four metres.
That makes the conversion a single exact multiplication: metres equals yards times zero point nine one four four. Teachers and coaches often still teach the rough rule of thumb multiply by zero point nine one, but that shortcut introduces a scale error that shows up immediately on a one-hundred-yard pitch or a fifty-yard fabric roll. Zero yards maps cleanly to zero metres.
Negative lengths are rejected because a physical length in this landing is non-negative; signed deltas belong in a different tool. When you need the opposite direction, divide metres by the same constant rather than inventing a second unofficial factor.
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 one yard and confirm you receive exactly zero point nine one four four metres after rounding, or convert one hundred yards and confirm ninety-one point four four metres. When teaching, pair the exact path with the mental shortcut so students see the drift on long lengths.
Stay inside the published range so the multiplication cannot overflow into a non-finite result the solver must reject. This landing targets people searching for yard to meter conversion, yards to meters, or convert yards to metres with an exact zero point nine one four four calculator; it is not a general multi-unit length hub, not a meters-to-yards primary form, not a feet or inches tool, and not an astronomical distance converter.
Prefer this capability when the input is already in yards and you only need SI metres; if you must convert among many units in one call, use a broader unit converter instead. Keep requests small, pin the rounded metre value in tests, and you get reproducible results for homework, LMS plugins, and automation scripts without standing up a computer-algebra system of your own.
What you can do with it
Sports field and pitch planning
Turn US football, golf, and track yardages into SI metres for metric stadium drawings, coaching notes, and equipment layout with the same exact factor every row.
Fabric, textile, and retail length checks
Merchants convert yard bolt lengths and pattern pieces to metres and compare hand work against deterministic steps before publishing metric size charts.
FAQ
What formula converts yards to meters?
Meters = yards × 0.9144. One international yard is defined as exactly 0.9144 metres by the 1959 international yard and pound agreement.
Is 0.9144 exact or approximate?
Exact. This yard-to-meter conversion uses the international yard definition, not a survey-yard or a rough multiply-by-0.91 estimate.
Can I convert meters back to yards?
This capability is yards → meters only. Divide metres by 0.9144 on your side, or use a dedicated metres-to-yards converter for the reverse search.
Is the yard to meter conversion free?
The browser tool is free and runs locally.
How many meters are 100 yards?
100 yards are exactly 91.44 meters. That value is a quick check for a 100-yard pitch and for any table or worksheet that should be using the exact factor.
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-to-meter-conversion \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"yards":1}'const res = await fetch("https://api.kit.forhosting.com/conv/yard-to-meter-conversion", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"yards": 1
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/yard-to-meter-conversion",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"yards": 1
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/yard-to-meter-conversion", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"yards":1}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"yards":1}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/yard-to-meter-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": 1
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.yard_to_meter_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.
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, negative, or missing input fails with a clear invalid_input error instead of inventing a number.
How to call the API and what comes back
The value must be greater than or equal to zero and must stay within the published limit of one trillion. Send a JSON body with one required finite non-negative number field named yards. Aliases yard, yd, value, length, yards_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 yards, sets meters, result, and converted to the same rounded metre magnitude, unit to the token m, from_unit to yd and to_unit to m, factor to the exact constant zero point nine one four four, meters_per_yard to that same constant, formula to the string meters equals yards times zero point nine one four four, message to a short English summary, and steps to an ordered array of substitution lines. Failed validation—missing fields, non-finite numbers, negative lengths, 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. Prefer sending bare JSON numbers when you control the client; numeric strings are accepted only when they match a strict finite numeric pattern without units, thousand separators, or currency symbols.
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 yards or pass text.
Integration use cases
Homework and unit-test fixtures
Students and engineers convert classroom yard readings to metres and pin golden JSON so browser and API arithmetic never drift.
Technical questions
What happens on missing, negative, or non-numeric input?
The API returns invalid_input naming the problem (for example a missing or negative yards field). Failed tasks are not charged.