Best free lat/long to UTM converters in 2026, tested on one coordinate

Every free "lat long to UTM" page on the first page of Google does the same arithmetic, and most of them get it right. The differences that matter are elsewhere: whether the tool tells you which datum it assumes, whether it accepts the format your coordinates actually arrive in, whether it handles a whole spreadsheet, and whether it sends your project coordinates to someone's server.

We tested each tool on the same point, a wind-turbine location in Madhya Pradesh at latitude 24.00252, longitude 76.023785, which should come out as UTM zone 43, easting 604131.98 m, northing 2654884.00 m on WGS84.

The mistakes people actually make

Converters do not fail on the maths. They fail on the inputs. The public record is full of the same handful of problems.

Ambiguity: Did I forget the N/S? Is it supposed to be +/-? Did I get Lat and Lon flipped? Is it decimal degrees or degrees minutes seconds? The decimal degrees vs DMS is the big one, by the way. Especially since it's not always obvious that it's one or the other.

Another fun one: *FALSE: A coordinate that looks like 15 45 38 is Degrees, Minutes, Seconds. (Sometimes it's degrees, decimal minutes. Happily, the maps in question had some "seconds" values greater than 59, which tipped us off.)

I have data in EPSG:4326 as WKT points in a CSV file, e.g. POINT (-17.2280391687 138.9716497577), which have lat lon order. I have created a VRT file for this CSV and am running through gdal_grid and the output file ends up being rotated 90 degrees [...]

A position read off this map is a lon/lat pair, which is the form nothing else at the site uses. The archaeological record is in UTM, and a grid reference is what gets written in a notebook next to a find or handed to someone with a handheld GPS.

Zone selection has its own traps, especially the Norway and Svalbard exceptions and the difference between a grid convention and an EPSG code.

I wrote the MGRS conversion from scratch using the DMA Technical Manual 8358.1 rather than pulling in a library. The trickiest part was handling the Norway/Svalbard UTM zone exceptions and getting the 100km square letter cycling right.

The MGRS exceptions are a grid-naming convention and do not govern which EPSG UTM CRS a point belongs to — so earthlens's zone selection was arguably wrong for two regions.

And the reason to bother with UTM at all is that distances in degrees are not distances.

The direct plotting from geographic coordinates (e.g., WGS84) can lead to visual distortions, especially for parks located further from the equator, where circles will appear flattened. A practical solution would be to reproject the data to the Mercator projection or the appropriate local UTM Zone, ensuring accurate distances in cartesian units with no visible distortions of angles.

Does anyone know how to convert coordintates in epsg:26985 to regular lat lon coordinates? I believe the correct projection is WGS84.

Comparison at a glance

"Not verified" means the tool's page could not be loaded by our tooling on the day of writing, so we describe only what the tool's own listing says.

1. reneGIS Coordinate Converter

Best for: single coordinates that arrive in messy formats, and for anyone who does not want project coordinates leaving their machine.

Our converter accepts decimal degrees, DMS in most notations (symbols, letters, colons, hemisphere letters before or after), degrees with decimal minutes, and UTM with a zone, band letter and hemisphere. It returns all three formats at once, detects the UTM zone including the Norway and Svalbard exceptions, lets you project into a neighbouring zone, and reports grid convergence and scale factor. The map is interactive: click or drag to pick a point. Everything runs in the browser; nothing is uploaded.

Test point: zone 43R, easting 604131.98, northing 2654884.00.

Pros: the most forgiving input parser on this list; states its datum; browser only; shareable result URLs; maps show India's official boundaries.

Cons: single point only; WGS84 only, so it cannot fix an Everest 1830 source; the zone shown follows the grid convention, so for an EPSG code near Norway use the plain formula.

2. epsg.io Transform (MapTiler)

Best for: converting between named coordinate reference systems, including datum changes, with an EPSG code on each side.

epsg.io/transform is maintained by MapTiler on top of the EPSG database (version 12.029 at the time of writing). You choose a source and target CRS by code, paste coordinates, and it applies the best available transformation, with alternatives selectable. It has a batch mode, and the same function is available through the MapTiler Cloud Coordinates API.

Pros: the right tool when the datum is the problem; batch mode; authoritative EPSG definitions.

Cons: every request goes to MapTiler's servers; you need to know the EPSG code; less forgiving of DMS notation.

3. NGS NCAT

Best for: United States work where NAD27 and NAD83 realisations matter.

NCAT is the National Geodetic Survey's official converter. It handles lat/long, UTM, State Plane, USNG and XYZ, and transforms between US datums. Coverage is the US, its territories and nearby areas, so it is not a tool for India. A multi-point mode accepts comma-delimited text uploads, and a downloadable Java version supports command-line batch processing.

Pros: authoritative for US datums; free; official.

Cons: US coverage only; no DMS parsing in the web form; requests go to NOAA.

4. QGIS

Best for: anything beyond a handful of points, and the only free option that does proper datum transformations offline.

QGIS is free desktop GIS. Load a CSV of coordinates as a layer, set its CRS, and export it in any other CRS, including WGS84 UTM zones and, with the right transformation grid, Indian datums. It is the tool to reach for when a land team hands you three hundred corner points.

Pros: unlimited batch; every CRS; nothing leaves your machine; free.

Cons: a desktop install and a learning curve; overkill for one coordinate.

5. MapScaping Latitude Longitude to UTM Converter

Best for: quick bulk conversion of decimal-degree pairs without a spreadsheet.

MapScaping's converter takes a list of comma-separated latitude, longitude pairs and returns a table of zone, easting and northing, with an interactive map for picking points. Its own notes describe the 0.9996 scale factor and the 60 zones.

Pros: paste a list and go; map picking.

Cons: decimal degrees only; the page does not state its datum; no CSV export.

6. CoordinateMapper

Best for: people who need MGRS, UK grid or State Plane as well as UTM.

CoordinateMapper lists conversion between lat/long, UTM, MGRS, UK grid references and State Plane, with plotting and export tools. We could not load the product page on the day of writing to verify export formats or plan limits, so treat the listing as unverified.

7. LatLong.net

Best for: a fast single conversion when you already have clean decimal degrees.

LatLong.net's converter is widely linked and ranks near the top for this search. It converts decimal degrees to UTM in one step. The page could not be loaded by our tooling on the day of writing, so we do not describe features beyond that.

8. Earthpoint

Best for: Google Earth users who want coordinates in several formats at once.

Earthpoint's Convert Coordinates page is a long-standing tool that returns decimal degrees, DMS, UTM and MGRS together and links to Google Earth. Batch conversion from Excel is part of its paid subscription. We could not load the page on the day of writing to verify the current price, so check it on the site.

Which converter should you use?

• One coordinate, messy format, sensitive data: reneGIS.
• Different datums or a specific EPSG code: epsg.io Transform.
• US State Plane or NAD27 to NAD83: NCAT.
• A whole spreadsheet, or Indian datum shifts: QGIS.
• A quick pasted list in decimal degrees: MapScaping.
• MGRS or UK grid: CoordinateMapper or Earthpoint.

Methodology

Each tool was checked on 8 September 2026. Where a page could not be loaded by our tooling, we say so and describe only the tool's own listing. Quotes are verbatim from public posts, linked to the original, with omissions marked by brackets. reneGIS makes the first tool on the list and no vendor paid for placement.

Frequently asked questions

What is the most accurate lat/long to UTM converter?+

Any converter that implements the transverse Mercator projection correctly on WGS84 gives the same answer to the millimetre. Accuracy differences come from the datum of your input coordinates and how many decimal places you supply, not from the converter. Check that the tool states WGS84 and that your source data is on WGS84.

Which UTM zone should I use?+

The zone is floor((longitude + 180) / 6) + 1. Most converters apply the Norway and Svalbard exceptions used by the military grid system. If you need an EPSG code for GIS software, note that EPSG UTM codes follow the plain 6-degree formula without those exceptions.

Why does my UTM northing look wrong?+

Southern-hemisphere UTM adds a false northing of 10,000,000 m. If a converter was told the wrong hemisphere, the northing is off by exactly that amount. The letter S in a zone like 17S is a latitude band in northern Florida, not the southern hemisphere, which is a common cause.

Can I convert coordinates in bulk for free?+

Yes. QGIS converts whole layers, epsg.io has a batch mode, NCAT accepts multi-point text files for US locations, and MapScaping accepts pasted comma-separated pairs. The reneGIS converter is single-point today; a batch version is planned.

Do online converters upload my coordinates?+

It depends on the tool. Converters that run in the browser, such as reneGIS, never send coordinates to a server. Tools backed by an API, such as epsg.io and NCAT, send each request to their servers. For sensitive project data, prefer a browser-only tool or QGIS.