Home / Geo & Coordinate Tools / Latitude Longitude to UTM Converter
Geo & Coordinate Tools

Latitude Longitude to UTM Converter

Convert WGS84 latitude/longitude to UTM with explicit zone logic, Norway/Svalbard exceptions, easting/northing evidence, project-zone overrides, reverse verification and repeatable batch handoff.

UTM Zone, Easting & Verification Studio

Project one WGS84 point into UTM, make the zone decision visible, compare project-zone overrides, reverse the result, then carry the same rules into a batch.

WGS84 · 80°S…84°N · browser-local

1. Enter latitude / longitude

Structured fields

Projection policy

Ready.
—WGS84 coordinate
—zone number
—latitude band
—hemisphere
—easting
—northing
—projected CRS

2. Prove the zone decision

Automatic grid zone—
Zone rule—
Central meridian—
Longitude offset—
Applicable longitude interval—
Reverse round-trip—
Independent in-page engine delta—
Normalized DMS—
Automatic UTM zone selected.
EPSG codeWGS84 UTM
PROJ string—

3. Compare the automatic zone with adjacent project zones

Near a zone edge, the same point can be projected into a neighbouring zone for project continuity. That is an explicit override, not a new geographic location.

ZoneCentral meridianLongitude offsetEasting (m)Northing (m)EPSG

4. Reverse-verify any WGS84 UTM coordinate

—Latitude, longitude

Forward check will appear here.

Enter UTM values or use the forward result prefilled above.

5. Repeat-use project workflow

LabelLat / lonZone policyAction

Nothing is auto-saved. Saved coordinates stay in this browser until you remove them.

6. Batch conversion — auto-zone each row or force one project zone

Automatic mode may assign different UTM zones to different rows.

#Lat / lonZoneHemisphereEastingNorthingEPSGPolicy

7. Export the projection evidence

Truth boundary: This Studio projects WGS84 latitude/longitude into WGS84 UTM. UTM is normally used from 80°S to 84°N. A latitude band letter such as T is not the same thing as the N/S hemisphere used by EPSG:326xx/327xx. Forcing a neighbouring zone can preserve one project grid near a boundary, but moving far from that zone’s central meridian increases distortion and may produce unusual eastings. Round-trip agreement checks the math, not the accuracy of the original GPS/survey measurement. No datum transformation, address lookup, device-location capture or survey adjustment is performed.

How to convert latitude / longitude to UTM without hiding the important assumptions

Zone number is part of the coordinate

UTM divides longitude into 60 zones. Easting and northing alone are incomplete because the same numbers can describe different places in different zones.

Band letter and hemisphere are different

Latitude bands C–X help label grid zones. EPSG UTM CRSs instead distinguish northern and southern hemispheres: EPSG:326xx north and EPSG:327xx south.

Norway and Svalbard have special zones

Automatic selection applies the standard UTM Norway and Svalbard exceptions instead of blindly using the six-degree longitude formula everywhere.

Project-zone overrides are deliberate

A dataset that straddles a boundary may intentionally use one neighbouring UTM zone for continuity. The Studio keeps the automatic zone visible so an override cannot masquerade as the default zone.

Reverse verification catches transcription errors

Every forward result can be decoded back to latitude/longitude and projected forward again. A small numerical round-trip error is evidence that zone, hemisphere and metre values were interpreted consistently.

Precision is not source accuracy

Showing millimetres does not make a phone GPS or survey input accurate to a millimetre. Keep the datum, measurement method and appropriate significant digits with the coordinate.

UTM details that matter in GIS, surveying and field work

The central meridian of each normal UTM zone is assigned a 500,000 m false easting. Southern-zone northings use a 10,000,000 m false northing so displayed northings stay positive. The central-meridian scale factor is 0.9996. WebToolArc exposes the selected zone, latitude band, hemisphere, EPSG code, central meridian, longitude offset and the PROJ definition so copied numbers keep their coordinate-reference context.

When to force one zone

Do not force a zone merely because another dataset uses different eastings. Use a deliberate project zone only when the workflow requires one projected CRS across nearby points, especially around a zone edge. Large offsets from the selected zone’s central meridian deserve extra projection review.

Privacy

Projection, reverse verification, batch conversion and saved project points run locally. Share links carry display settings only, not the entered coordinates. External map providers receive a coordinate only if you choose to open their generated map link.

Search by task, tool name, or category. Press Esc to close.
Start typing to find a tool.