How Do You Convert Between Acres, Hectares, and Square Metres?

Area conversion between acres, hectares, and square metres is just unit swapping with fixed factors. If you need a clean number fast, try our free area converter and skip the head math.

The three units, decoded

Square metres are the base unit here: the plain metric way to measure area. Hectares are metric too, but scaled for land, while acres come from the imperial side of the fence and still show up in property listings, farm records, and planning docs.

The important thing is that all three measure the same thing. Only the scale changes. If you know one trusted conversion factor, the rest is just multiplication or division.

• 1 hectare = 10,000 square metres
• 1 acre = 4,046.8564224 square metres
• 1 hectare = 2.4710538147 acres
• 1 acre = 0.4046856422 hectares

If you work with land data in spreadsheets, APIs, or CSV exports, normalize to one unit before doing anything else. That keeps rounding errors and mixed-unit chaos from leaking into your results. The same habit applies when you handle our guide on converting JSON to CSV: pick one shape, convert once, then process.

Use the right direction: multiply or divide

Most people trip because they mix up which way the factor goes. The fix is simple: when converting to a smaller unit, multiply by the larger unit’s value; when converting to a larger unit, divide.

That means:

• acres to square metres: multiply by 4046.8564224
• hectares to square metres: multiply by 10000
• square metres to hectares: divide by 10000
• square metres to acres: divide by 4046.8564224

If you want acres from hectares, multiply by 2.4710538147. If you want hectares from acres, multiply by 0.4046856422. Same information, different direction.

A useful mental model: square metres are the low-level representation, hectares are the aggregation layer, and acres are the legacy interface. Same land, different display.

Quick estimates that don’t need a calculator

Exact conversion factors are best when you need legal or financial accuracy. But rough estimates are often enough for planning, comparison, or a sanity check before you paste numbers into a tool.

Here are the shortcuts people actually use:

• 1 hectare ≈ 2.5 acres
• 1 acre ≈ 4,000 m²
• 10,000 m² = 1 hectare
• 2 hectares ≈ 5 acres

These are close enough for estimating whether a parcel is “small field,” “decent block,” or “why is this listing so cheap.” They are not close enough for land transfer documents, survey work, or anything where a decimal place can turn into money.

Rule of thumb: round for planning, not for anything that gets signed.

Code it once, stop retyping the math

If you’re pulling area values from data feeds or scraping property pages, the safest pattern is to convert in one place and store a canonical unit. In code, that usually means square metres internally, with hectares or acres only for display.

// acres to square metres
const acres = 3;
const squareMetres = acres * 4046.8564224;

// square metres to hectares
const hectares = squareMetres / 10000;

console.log({ squareMetres, hectares });

For batch work, the same logic can be dropped into a spreadsheet formula or a pipeline step. If you’re cleaning up tabular data, use the conversion in a dedicated column, then round only when you present the result. That keeps your source values intact and your output predictable.

A lot of bugs come from mixing rounded display values back into later calculations. Don’t do that. Keep the raw number, derive the display value, and move on.

When land data gets messy

Real-world area data is rarely tidy. You’ll see entries like 2.4 ha, 3 acres, 15,000 m², or worse, a spreadsheet where the unit lives in a separate column and half the rows are inconsistent.

Before you convert anything, standardize the input. Strip labels, normalize separators, and confirm whether commas are thousands separators or decimal marks. This matters more than the math itself, because 2,5 means different things depending on locale.

For mixed-unit datasets, a simple workflow works well:

1. Detect the unit in each row.
2. Convert everything to square metres.
3. Store the original value and unit for traceability.
4. Only convert back to hectares or acres when needed for display or reporting.

That approach plays nicely with survey exports, GIS reports, and property databases. It also makes it much easier to debug when a row looks wrong.

How to sanity-check the result

You do not need to remember every decimal place. You do need a fast way to tell whether a number is plausible. If the result looks wildly off, the input probably used the wrong unit or the decimal point moved.

Use these checks:

• 1 hectare should be exactly 10,000 m², not 1,000 or 100,000.
• 1 acre should be a bit bigger than a football pitch, not the size of a city block.
• 100 hectares should be roughly 247 acres.
• 50,000 m² should be 5 hectares or about 12.36 acres.

If you work with planners, surveyors, or agricultural datasets, these checks save time. They catch the classic mistakes: swapped units, missing zeros, and “helpful” rounding that wasn’t helpful.

A Worked Example

Say you get a property export with three rows and need one consistent unit for analysis. The source data mixes acres, hectares, and square metres, so the first step is to convert everything to square metres.

Input data

parcel_id,area,unit
A-104,3,acres
B-220,2,hectares
C-331,25000,m2

Converted to square metres

A-104,12140.5692672,m2
B-220,20000,m2
C-331,25000,m2

Now the same data can be compared directly. If you want hectares for reporting, convert the square metres once more:

Output for report

parcel_id,area_hectares
A-104,1.21405692672
B-220,2
C-331,2.5

If you want acres instead, use the hectare-to-acre factor on the normalized value:

parcel_id,area_acres
A-104,3
B-220,4.9421076294
C-331,6.1776326768

That workflow scales cleanly whether you have three rows or three million. Normalize first, convert second, round last.

Frequently Asked Questions

How many square metres are in one acre?

One acre equals 4,046.8564224 square metres. If you only need a rough estimate, 4,000 m² is close enough for casual planning. For anything formal, keep the full factor and round at the end.

How many acres are in a hectare?

One hectare equals 2.4710538147 acres. The quick mental version is 2.5 acres, which is good for back-of-the-envelope checks. Use the exact value when converting official land records or survey data.

What is the easiest way to convert hectares to square metres?

Multiply the hectare value by 10,000. For example, 2.5 ha becomes 25,000 m². This is the cleanest conversion of the lot because hectares are already metric.

Should I store land area in acres, hectares, or square metres?

Store the canonical value in square metres if you can. It makes conversions predictable and keeps your system from juggling multiple unit systems internally. Show acres or hectares only in the UI, reports, or exports that need them.

The Bottom Line

Area conversion gets easy once you pick a base unit and stop converting back and forth on the fly. Square metres are the simplest internal format, hectares are the neat metric summary, and acres are the imperial reference you still need to handle.

If you’re working with land listings, survey exports, or any mixed-unit dataset, normalize first and round last. When you just want the number without the mental arithmetic, use the area converter tool and let it do the boring part.

That leaves you free to check the actual question: whether the plot is big, small, or suspiciously described in three different units.