Learn

Why Web Mercator Distorts Area

Web Mercator enlarges area towards the poles because its scale increases with latitude in two dimensions.

Geobble
intermediateexplainerWorld Map Projections & CRS

Own both the visual and analytical Web Mercator area-distortion intent, including the material consolidated from the retired area-calculation article.

Why Web Mercator Distorts Area

Web Mercator distorts area because its scale increases with latitude. Away from the equator, it stretches the map east–west and north–south; the two stretches multiply, so area grows faster than length. High-latitude regions therefore occupy far more screen space than their share of the Earth's surface.

The same mechanism makes planar area calculated directly from EPSG:3857 coordinates unreliable. Metres are the grid unit, but a square metre on that grid is not a constant square metre on the ground.

The scale factor explains the effect

For the spherical Mercator equations used by Web Mercator, the local linear scale factor is:

k = 1 / cos(latitude)

At the equator, k = 1. At 60° latitude, cos(60°) = 0.5, so k = 2: a small ground distance is represented at roughly twice the equatorial map scale in both directions.

Because area responds to both dimensions, its approximate scale factor is:

area scale = k² = 1 / cos²(latitude)

Latitude · Approximate linear scale · Approximate area scale

  • 0° — 1.00× — 1.00×

  • 30° — 1.15× — 1.33×

  • 45° — 1.41× — 2.00×

  • 60° — 2.00× — 4.00×

  • 80° — 5.76× — 33.16×

These figures describe local spherical scale at a latitude; they are not a correction formula for large polygons. A feature can span a substantial latitude range, and EPSG:3857 also combines spherical projection equations with WGS 84 ellipsoidal coordinates. The table is valuable because it shows the pattern: the inflation is systematic and accelerates towards the poles.

Why preserving angles makes the map larger

On the globe, meridians converge towards the poles. On a cylindrical Mercator map, they remain vertical and parallel. East–west scale must therefore increase with latitude.

A Mercator projection is designed to preserve local angles. To avoid squashing a small feature in one direction, it applies the same local enlargement north–south. Small circles remain locally circular, but their diameter grows. Once both dimensions grow, their area grows by the square of the scale factor.

This trade-off made the original Mercator projection valuable for navigation: a route of constant compass bearing appears as a straight line. Web Mercator inherited the recognisable appearance and useful local behaviour, then paired it with a spherical formula and square coordinate space suited to online tiling.

Why the poles disappear

The Mercator y-coordinate approaches infinity as latitude approaches 90°. A finite map cannot include the poles. Standard Web Mercator tile schemes therefore stop near 85.0511° north and south, where the projected width and height can form a square.

That square is extraordinarily convenient for software because it can be divided into four tiles, then sixteen, then sixty-four, creating a consistent pyramid of zoom levels whose coordinates map servers and browsers can request, cache and combine.

The area distortion is not a rendering bug that can be removed while leaving the same projection intact. It is part of the geometry that makes the system work.

Visual distortion and measurement error are the same issue

At world scale, Web Mercator makes Greenland, northern Canada and Russia look disproportionately large beside tropical regions. The familiar comparison between Greenland and Africa is instructive: Africa is about fourteen times Greenland's surface area, yet a Mercator world map can make them appear comparable.

In analysis, the same scale variation changes the numeric area of polygons. Although a GIS can correctly calculate the planar area of an EPSG:3857 geometry and return a value in square metres, that calculation is valid on the projected grid and becomes unsuitable if the value is then described as ground area without correction.

This is a dangerous class of error because nothing necessarily looks broken. The geometry is valid, the unit is familiar and the software reports a precise number. Only the CRS and method reveal that the number answers the wrong question.

Better ways to calculate area

Use an appropriate equal-area CRS

For regional work, choose an equal-area projected CRS whose area of use covers the study region. National mapping authorities may publish an official option. Albers Equal Area and Lambert Azimuthal Equal Area are common projection families, but their parameters need to match the geography.

For broad global comparison, a global equal-area projection can be appropriate. For small parcels or regulated measurements, a world CRS is usually too blunt; use an authoritative local method and follow the required standard.

Calculate geodesic area

Many spatial libraries can calculate polygon area on an ellipsoid. This avoids forcing a large or dispersed dataset into one planar projection and is useful for features that cross projection zones or the antimeridian.

“Geodesic” is still a method that should be recorded. Results depend on the ellipsoid, polygon interpretation and treatment of features that wrap or contain a pole.

Use a local projected CRS with quantified distortion

An equal-area projection is not the only way to achieve an acceptable result. A well-chosen national grid or UTM CRS may keep scale distortion sufficiently small for a local task, even if it is conformal. The accuracy requirement and official practice determine whether “sufficiently small” is defensible.

How to audit an existing EPSG:3857 area

If a published result may have been measured in Web Mercator:

  1. preserve the original geometry and result;

  2. identify the latitude range of the feature;

  3. confirm whether the tool used planar geometry or a geodesic/geography method;

  4. recalculate using an appropriate equal-area CRS or ellipsoidal method;

  5. compare results for low- and high-latitude reference features;

  6. replace the value and record the revised method if the discrepancy is material.

Do not divide every result by one constant. Scale changes with latitude and may vary substantially within a polygon. A correction evaluated only at the centroid is an approximation, not a general substitute for a proper area calculation.

Web Mercator can remain the display CRS

There is no contradiction in calculating area elsewhere and displaying the result on an EPSG:3857 basemap. Rendering and analysis serve different purposes.

A reusable result should retain the method that produced its area field, including the source CRS, the analytical CRS or geodesic operation, and any transformation. The map can still use a familiar interactive basemap, but the number should not inherit the basemap's coordinate assumptions silently.

For a global thematic publication, there is a further choice: render the overview in an equal-area projection so that the visual footprint and the calculated values tell a consistent story. If the reader then moves into neighbourhood-level exploration, Web Mercator can take over where its interactive ecosystem is strongest.

References

  1. PROJ: Web Mercator / Pseudo Mercator. Formula and implementation notes.

  2. PostGIS ST_Area. Documents the distinction between planar geometry area and spheroidal geography area.

  3. EPSG Geodetic Parameter Dataset. Authoritative registry for EPSG:3857 and its area of use.

Related content