How to Convert MGRS to Latitude and Longitude (and Back)

The fastest way to convert MGRS to latitude and longitude is to paste the coordinate into the free web MGRS converter. Type or paste an MGRS string such as 18S UJ 23480 06473 and it returns the lat/long instantly. Paste a lat/long instead and it returns the MGRS. No account, no sign-up, and no data leaves the page once it has loaded.

That covers the practical answer. The rest of this article explains what the converter is doing under the hood, why a round-trip conversion can land you a few meters or a few hundred meters away from where you started, and how to run the same conversion fully offline when you have no signal at all.

Why You Would Convert at All

MGRS is the better coordinate to work with on the ground. The numbers are meters, the precision is explicit, and a 1 km square is something you can actually search or sweep. But most of the technology around you does not speak MGRS natively. Consumer phone GPS, mapping apps, drone ground stations, fitness watches, and the geotags on photographs all store and display positions as latitude and longitude. So you constantly need to move between the two.

A few concrete cases:

• A teammate sends you a pin from a mapping app as decimal degrees, and you want to plot it on a gridded topographic map.
• You read an 8-digit MGRS grid off a paper map and need to drop it into an app that only accepts lat/long.
• A search-and-rescue dispatcher logs incidents in MGRS, but the helicopter avionics expect lat/long.
• You exported a GPX track full of lat/long waypoints and want the MGRS grids for a radio brief.

In every case the underlying position is identical. Only the notation changes.

The Conversion Pipeline, Explained Plainly

MGRS does not convert directly to latitude and longitude in one step. It passes through Universal Transverse Mercator (UTM) as an intermediate stage. The full pipeline runs in both directions:

MGRS  →  UTM  →  Latitude/Longitude
MGRS  ←  UTM  ←  Latitude/Longitude

Going from MGRS to lat/long, the steps are:

1. Read the grid zone. The leading part of the string, like 18S, is the UTM zone number (18) and the latitude band letter (S). This tells the converter which 6° wide projection zone and which hemisphere it is working in.
2. Expand the 100 km square. The two letters, like UJ, identify a 100 km × 100 km square inside that zone. The converter looks up the column and row letters to recover the leading digits of the full UTM easting and northing.
3. Add the easting and northing. The numeric pair, like 23480 06473, is the offset in meters within the square. Combined with the square's base values, this produces a complete UTM coordinate (zone 18S, 323480 mE, 4306473 mN).
4. Invert the projection. The converter runs the inverse Transverse Mercator equations on the WGS 84 ellipsoid to turn that flat grid coordinate back into latitude and longitude in decimal degrees.

Going the other way, from lat/long to MGRS, the same steps run in reverse: project lat/long into UTM, then chop the UTM coordinate into the zone, the square letters, and the truncated easting/northing pair. The grid zone and 100 km square letters absorb the leading digits, which is why an MGRS string is so much shorter than the raw UTM it represents.

Doing It in the Browser

The free web MGRS converter packages that entire pipeline into a single page. Using it takes seconds:

1. Open the converter in any browser, on a phone or a desktop.
2. To go from grid to coordinates, paste an MGRS string into the MGRS field. Spaces are optional, so 18SUJ2348006473 works as well as 18S UJ 23480 06473.
3. Read the latitude and longitude out of the lat/long fields. They update as you type.
4. To go the other way, clear the fields and enter a decimal-degree latitude and longitude instead. The MGRS field fills in.

Because the converter is a self-contained page, you can load it once on a connected network and keep using it afterward. There is no per-conversion server call, so nothing about your coordinates is transmitted anywhere.

The Accuracy Caveat: Southwest Corner, Not Center

This is the part that surprises people, and it is not a bug. An MGRS coordinate names the southwest corner of its square, not the center. The standard truncates the easting and northing rather than rounding them.

Truncation is deliberate. It is what lets the same syntax express different precisions just by changing how many digits you write. The more digits, the smaller the square the coordinate points at:

Here is why this matters for round-tripping. Suppose your true position is in the middle of a kilometer square. If you write it as a 4-digit (1 km) MGRS grid, the standard drops every digit finer than a kilometer, so the grid points at the southwest corner of that square. Convert that grid back to lat/long and you get the corner, which can be hundreds of meters from where you actually stood. Convert the corner forward to MGRS again and you get the same grid. The system is perfectly consistent; the apparent drift is just the size of the square you chose to express.

The difference you see on a round-trip is the resolution you asked for, not the error of the tool. A 1 km grid is honest about being a 1 km grid.

To shrink the gap, use more digits. A 10-digit MGRS string (5 digits per pair) pins the position to a 1-meter square, so the southwest-corner offset is at most about 1.4 meters diagonally, which is well inside normal GPS error anyway.

One more thing to check in any tool you trust: a correct implementation truncates. The DMA Technical Manual 8358.1 algorithm, the same one used by NGA GeoTrans and by military receivers like the DAGR and PLGR, truncates intermediate UTM values rather than rounding them. A converter that rounds will sometimes hand you a coordinate one square over from what a military receiver shows. The web converter and the Red Grid MGRS app both follow the truncating standard, so their output matches GeoTrans and a DAGR to the meter.

Doing It Fully Offline, With No Signal

Coordinate conversion is pure math. It needs the WGS 84 ellipsoid constants and the projection equations, both of which fit in a few kilobytes of code. Nothing about it requires a network connection, a tile server, or a lookup table hosted somewhere.

That is exactly how the Red Grid MGRS app does it. Your position is computed on-device from the GPS chip, converted on-device, and held in memory only. The app makes zero network calls for its core features, keeps no account, and runs no analytics or tracking. So you can be in airplane mode, deep in a canyon with no bars, or operating with the radio deliberately off, and the conversion still works the instant you need it.

The free tier already converts to 6-digit MGRS (100 m resolution), which is enough for most navigation and reporting. Pro unlocks the full 10-digit (1 m) precision along with extra coordinate formats, so you can read out a position to the meter or hand off a grid that matches a DAGR exactly.