Square yard converter
1 square yard is exactly 9 square feet and 0.83612736 square metres. Enter an area in square yards and get square feet, square metres and acres together for carpet, turf, fabric or land listings. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Square yards
- 1
- Square feet
- 9
- Square meters
- 0.83612736
- Acres
- 0.0002066116
- Square feet per square yard
- 9
A square yard converter turns an area written in square yards into the three companion units people actually need on floor plans, fabric cuts, landscaping quotes, and land listings: square feet, square meters, and acres. Enter one finite non-negative number of square yards; the tool multiplies by nine for square feet, multiplies by the exact international identity 0.83612736 for square meters, and divides by 4840 for international acres.
The three exact square-yard factors and why they never drift
The international square yard is the square of the international yard, not a rounded classroom estimate pulled from memory. After the 1959 yard and pound agreement, one yard is defined as exactly 0.9144 meters and one foot as exactly 0.3048 meters. Three feet make one yard, so nine square feet make one square yard with no remainder and no survey-foot fudge factor.
Squaring 0.9144 meters produces the exact area identity 0.83612736 square meters per square yard. An international acre contains 4840 of those square yards, which is why one acre equals 4046.8564224 square meters and 43560 square feet. One square yard therefore becomes nine square feet, 0.83612736 square meters, and 0.000206611570 acres after twelve-decimal rounding; 4840 square yards become 43560 square feet, 4046.8564224 square meters, and exactly one acre.
There is no table lookup, no US survey-yard option, and no hectare or square-mile bundle on this landing. Zero square yards converts to zero in every listed unit, which is a convenient default for empty forms. If you need a signed plan offset, convert the absolute area here and apply the sign in your own geometry layer rather than sending a negative square-yard magnitude to the converter.
What you can do with it
Flooring, turf, and landscaping take-offs
Contractors convert a carpet, sod, or patio area quoted in square yards into square feet for material lists, square meters for metric suppliers, and acres when a large site sits next to a parcel description.
Real-estate and land listings
Agents and cadastral notes convert a yardage figure on a plat into square feet for living-area copy, square meters for international buyers, and acres for rural lots that still list in both yardage and acreage.
FAQ
What happens if I enter a negative area?
A physical area cannot be negative; signed plan offsets should be applied after converting the absolute magnitude.
Can I send the area as a numeric string?
Empty strings, spelled-out words without a number, NaN, and Infinity are rejected.
How many square yards are in an acre?
Exactly 4840 square yards, which is also 43,560 square feet and 4046.8564224 square metres. Entering 4840 square yards returns exactly one acre.
Which yard does the converter use?
The international yard of exactly 0.9144 metres, fixed by the 1959 yard and pound agreement. Squaring it gives exactly 0.83612736 square metres per square yard, with no survey-yard variant.
Where are square yards still used?
On carpet, sod, turf and patio take-offs, fabric cuts and some land plats. The converter turns those figures into square feet for material lists, square metres for metric suppliers and acres for rural lots.
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/square-yard-converter \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"square_yards":1}'const res = await fetch("https://api.kit.forhosting.com/conv/square-yard-converter", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"square_yards": 1
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/square-yard-converter",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"square_yards": 1
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/square-yard-converter", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"square_yards":1}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"square_yards":1}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/square-yard-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
{
"square_yards": 1
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.square_yard_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.
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
Negative values and non-numeric input fail with invalid_input instead of inventing an area. Successful API calls bill at $0.002 per item; validation failures are not charged.
The three exact square-yard factors and why they never drift
Those three identities are what this square yard converter applies on every request: square feet equal square yards times nine, square meters equal square yards times 0.83612736, and acres equal square yards divided by 4840. Results are quantized to twelve decimal places so JSON goldens stay identical across JavaScript runtimes while remaining far more precise than any tape-measure take-off.
Input contract, aliases, and why negatives fail
Numeric strings, including scientific notation, are parsed; empty strings, missing fields, objects, and arrays are not. The same error is raised for NaN, Infinity, and non-numeric text such as a spelled-out phrase without a number. Failed validation is not billed. Use this landing when the search intent is a square yard converter as a bundle of square feet, square meters, and acres; a dedicated square-meters-to-square-feet-only tool is a different query and a different page. POST a JSON body with the required field square_yards, a finite non-negative number representing an area in square yards. If the value is negative the task fails with invalid_input and a message that names square_yards, because a physical area cannot be negative. Magnitudes above one trillion square yards are rejected so Worker isolates stay inside a published limit. On success the JSON echoes the parsed square_yards value and returns square_feet, square_meters, and acres as three parallel numbers. Companion fields document the exact factors: square_feet_per_square_yard equals nine, square_meters_per_square_yard equals 0.83612736, and square_yards_per_acre equals 4840. A formula string restates the identity in one line for tutoring interfaces, and method is always exact_international_yard so downstream code can pin the definition.
API usage, pricing, and where the three outputs land
Pair the three output fields with your own reverse conversion if a pipeline must round-trip labels, but keep this page focused on converting square yards outward into square feet, square meters, and acres. Source inputs follow the same retention rules as other parse items: they are processed and discarded. Keep requests small, treat negative square yards as a client bug, and you get reproducible areas for homework, LMS plugins, and edge workers without standing up a general unit-conversion library of your own. Call the free in-browser square yard converter for a one-off check, or send the same JSON to the prepaid API when a flooring estimator, landscaping quote, fabric cutter, cadastral note, classroom tool, or spreadsheet add-on needs a stable machine-readable contract. Successful conversions bill as one item at $0.002; invalid_input never consumes balance, so you can validate forms without burning prepaid credit. Authors shipping SDKs can map square_yards into a number field and show square_feet, square_meters, and acres as result badges.
Integration use cases
Homework checks and fabric or sports-field plans
Students, teachers, textile buyers, and grounds crews verify one square-yard-to-three-units answer with exact factors, a readable formula line, and a clear invalid_input error on negative or non-numeric input.
Technical questions
How do I convert square yards to square feet, square meters, and acres?
Send a finite non-negative number in the square_yards field (aliases value, sq_yd, sqyd, yd2, area, square_yard, sq_yards). The API returns square_feet, square_meters, and acres using the exact factors 9 ft², 0.83612736 m², and 4840 yd² per acre.
Which yard definition does this square yard converter use?
The international yard from the 1959 yard and pound agreement (1 yd = 0.9144 m exactly). It does not convert US survey yards; those are a different factor and a different search intent.
What does the square yard converter cost?
The browser tool is free. API requests use prepaid KIT balance at $0.002 per successful call; invalid input is not billed.