Land area converter
Compare parcels from deeds, leases and listings in square meters, hectares, acres or square feet: a hectare is exactly 10000 m² and an acre 4046.8564224 m². Every conversion passes through square meters, so nothing drifts. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Value
- 1
- From
- Ha
- To
- Acre
- Result
- 2.4710538147
- Converted area
- 2.4710538147
- From label
- hectares
- To label
- acres
Land deeds, farm leases, and cadastral extracts rarely share a single unit. A surveyor in a metric country records a parcel in square meters or hectares, while a US listing quotes acres or square feet, and anyone comparing the two needs a conversion that does not drift with a rounded pocket-calculator factor. This land area converter accepts a numeric value, a source unit, and a target unit among square meters (m2), hectares (ha), acres (acre), and square feet (ft2), then returns the converted area using exact international SI factors.
Which land units this converter understands and how the result is built
A land-area conversion answers a narrow question: given a parcel magnitude in one of the four units that dominate deeds and listings, what is the equivalent magnitude in another of those units. This calculator accepts a numeric value, a source unit, and a target unit, then returns the converted area together with canonical unit ids, human-readable labels, and the intermediate size in square meters so you can audit the arithmetic. Canonical ids are m2 for square meters, ha for hectares, acre for international acres, and ft2 for square feet.
Conversion always bridges through square meters using fixed international factors: one hectare is exactly ten thousand square meters; one international foot is exactly zero point three zero four eight meters, so one square foot is exactly zero point zero nine two nine zero three zero four square meters; one international acre is forty-three thousand five hundred sixty square feet, which is four thousand forty-six point eight five six four two two four square meters.
Square miles and square kilometers are intentionally out of scope because this landing is for lots and parcels, not country-scale map tiles.
Input contract, exact factors, and error behaviour
Each of from and to must resolve to m2, ha, acre, or ft2. Numeric strings in ordinary decimal or scientific notation are allowed when they parse as a finite number; embedded spaces, hex prefixes, and non-numeric tokens fail with a message that names the field. Zero is a valid value and simply yields zero in the target unit.
Negative land area is rejected because a parcel cannot have a negative size. Negative zero is collapsed to plain zero. Failed validation is not billed.
Where a dedicated land-area converter earns its keep
Real-estate listings often mix square feet in one market and square meters or hectares in another, while agricultural leases still quote hectares or acres depending on the country, so a single deterministic converter prevents hand-calculator drift when a buyer, surveyor, or agent compares parcels. Farm managers convert a field recorded in hectares into acres for a US-style lease schedule, then into square meters for a local cadastral filing, without rounding each hop by a different rule of thumb.
Site engineers convert lot plates between imperial plan sets and metric material takeoffs; teachers assign homework that needs a fast, offline check of acres to square feet without trusting opaque apps that silently change precision. Developers call the same contract from scripts to seed deterministic test vectors for mapping UIs, to normalize user-entered lot sizes before pricing demos, or to satisfy programming-challenge statements that demand exact international factors rather than a hand-waved estimate.
Product tools use the rewrite when a learner or agent types two acres and the UI must show hectares and square meters side by side. Keep requests small, pin the rounded converted area in tests, and you get reproducible land sizes for listings, leases, and worksheets without standing up a GIS stack of your own.
What you can do with it
Property listings across markets
Convert lot sizes between square feet, square meters, acres, and hectares when a listing, offer, or appraisal mixes metric and imperial land units.
Farm leases and cadastral filings
Turn a field recorded in hectares into international acres for a lease schedule, or into square meters for a local cadastral extract, with the same exact factors.
FAQ
How are acres defined in this converter?
The international acre is used: 43 560 square feet, equal to 4046.8564224 square meters exactly via the international foot of 0.3048 m. The US survey acre is not applied.
What happens if I send an unsupported unit?
Unknown or misspelled units are never silently mapped.
Can I convert hectares directly to square feet?
Yes. Set from to ha (or hectare) and to to ft2 (or sqft). The engine bridges through square meters with the exact SI and international-foot factors.
How many acres is one hectare?
One hectare is 2.471053814672 international acres. The tool also shows the area in square meters along the way, here 10000 m², so you can check the arithmetic yourself.
Can I convert square miles or square kilometers?
No. This converter is meant for lots and parcels, so it works only with square meters, hectares, acres and square feet. Country-scale units are left out on purpose.
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/land-area \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"value":1,"from":"ha","to":"acre"}'const res = await fetch("https://api.kit.forhosting.com/conv/land-area", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"value": 1,
"from": "ha",
"to": "acre"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/land-area",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"value": 1,
"from": "ha",
"to": "acre"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/land-area", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"value":1,"from":"ha","to":"acre"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"value":1,"from":"ha","to":"acre"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/land-area", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"value": 1,
"from": "ha",
"to": "acre"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.land_area",
"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_value | 1000000000000000 |
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 path is deterministic: every successful call with the same inputs yields the same JSON, with no network, no sampling, and no date-dependent shortcuts. Unknown units fail with invalid_input instead of a silent guess.
Which land units this converter understands and how the result is built
Everyday spellings such as square_meters, hectare, hectares, acres, sqft, and square_feet normalize to those ids so forms, query strings, and spreadsheets can reuse the same contract. There is no map-projection path, no survey-acre variant, and no currency-style rounding table: the engine either multiplies and divides by those constants inside the documented magnitude range or rejects the input with invalid_input. Rejected cases include a missing value, from, or to; a non-finite or negative magnitude; a value above the declared ceiling; and any unit string that is not on the supported land-area list.
Input contract, exact factors, and error behaviour
POST a JSON body with three required fields: value, the non-negative land-area magnitude; from, the source unit of that magnitude; and to, the target unit you want the converted area in. Aliases such as area, amount, and n for the magnitude, source, from_unit, and source_unit for the source unit, and target, to_unit, and target_unit for the target unit are accepted so heterogeneous clients can share one contract. Computation multiplies value by the source factor in square meters, then divides by the target factor, and rounds every numeric field to twelve decimal places so JSON goldens stay stable across runtimes. If from or to is missing, empty, or a unit this converter does not support, the task fails with invalid_input naming the field and listing the four supported units. Pair the free browser run on this page with the priced API when you need the identical mathematical result inside an automated pipeline without re-implementing unit tables yourself.
Where a dedicated land-area converter earns its keep
On this page the work runs entirely in your browser; through the API each successful lookup costs $0.002, failed validation is not charged, and nothing is stored after the response returns. That split — free interactive exploration and a priced, identical API — lets you move from a classroom demo to an automated pipeline without changing the mathematical result.
Integration use cases
Homework and CI fixtures
Generate reproducible land-area conversions for worksheets, tutoring software, and unit tests that assert fixed international SI factors.
Technical questions
Which land area units are supported?
Square meters (m2), hectares (ha), international acres (acre), and square feet (ft2), including common aliases such as sqm, hectare, acres, and sqft. Other area units are rejected as unsupported.
What does the land area converter cost?
The browser tool is free. API requests use prepaid balance at $0.002 per successful call; invalid input is not billed.