UTM coordinates look reassuringly precise — 630084 E, 4833438 N — right up until someone asks you to put them on a web map, which speaks latitude and longitude. Then you discover the two facts that define every UTM conversion: the numbers are meaningless without a zone, and ambiguous without a hemisphere.

The 60-zone problem

UTM divides the world into 60 north–south strips, each 6° of longitude wide, and restarts its easting count in every one. That same 630084, 4833438 pair exists in all 60 zones — in zone 18 it’s on the US East Coast; in zone 30 it’s in Spain. If a dataset arrives as bare UTM coordinates with no zone in the metadata, the zone has to come from context (the .prj file, the data provider’s docs, or knowing roughly where the data should be).

The classic failure mode is subtler: southern-hemisphere data without the hemisphere flag. Southern UTM northings are offset by 10,000,000 m; forget the flag and your Australian survey points land in the North Pacific.

Converting a single point

For one-off checks, this UTM to lat/long converter takes easting, northing, zone and hemisphere and returns decimal degrees, with the point plotted on a map so you can see immediately whether the zone guess was right. The reverse direction — lat/long to UTM — works out the correct zone for you from the longitude.

Converting a whole spreadsheet

Field data usually arrives as a CSV with hundreds of rows, not one point. Rather than scripting pyproj for a one-time job, a batch coordinate converter transforms an entire CSV between coordinate systems in the browser — pick the source EPSG (a UTM zone like EPSG:32618), the target (usually EPSG:4326), and download the result with new columns appended. Because it runs client-side, the coordinates never leave your machine — relevant for survey and utility data with location-privacy constraints.

Which EPSG code is my UTM zone?

The pattern is worth memorising: 326xx for northern zones and 327xx for southern, where xx is the zone number. Zone 18 N is EPSG:32618; zone 55 S is EPSG:32755. (NAD83-based UTM, common in US government data, uses a different series — 269xx — and yes, mixing WGS84-UTM and NAD83-UTM introduces a metre-scale offset that has ruined many a survey comparison.)

UTM is only one corner of the coordinate-system story — for how it relates to Web Mercator and WGS84, and why your web map and your GPS disagree, see our practical guide to coordinate systems.