JoseFitani
🧭 Coordinate Converters

Coordinate Converter

Convert between decimal degrees, degrees-minutes-seconds (DMS), UTM, MGRS and Open Location Codes (Plus Codes).

This page explains how the coordinate converter works, the data and formulas behind it, and how to interpret the result. Coordinate conversions are exact to machine precision; the only source of error is the precision of the input. All formats describe the same location - the notation just differs. The tool is one of 329 free, open tools on JoseFitani for maps and geography. It runs in your browser with no sign-up needed. Use the search field or click the map to drop a pin - the tool uses standard mathematical formulas for each format, all based on the WGS84 datum (EPSG:4326) and returns the result in seconds. Below you'll find a step-by-step guide, real use cases, the methodology, FAQs, and data sources.

Decimal Degrees
48.858400°, 2.294500°
Degrees Minutes Seconds
48° 51' 30.24" N, 2° 17' 40.2" E
UTM
31N 448252E 5411955.03N
MGRS
31UDQ 48252 11955
Plus Code
8FW4V75V+9R

MGRS is derived from the WGS84 ellipsoid series used on this site (accurate to a few metres) — suitable for reference and education, not for survey-grade work. Plus Codes follow the Open Location Code specification.

How to use this tool

1
Enter your input

Type your query, paste coordinates, or click on the map. The tool uses standard mathematical formulas for each format, all based on the WGS84 datum (EPSG:4326) to process your input locally in the browser.

2
View the result

The result appears instantly with the map showing your location. You can adjust by clicking elsewhere or searching a new place.

3
Copy or share

Click Copy to save to clipboard, or Share to send a direct link with the exact inputs.

What people use this tool for

Bridging GPS data and GIS layers

Field teams collect points in decimal degrees on handheld GPS units, but project GIS databases often store everything in UTM. Converting between the two lets field data drop cleanly onto existing metre-based map layers without positional mismatch.

Example: An analyst in Nairobi converts field GPS points from decimal degrees to UTM so they align with the project's existing infrastructure layers in QGIS.
Plotting historical survey records

Old deeds, survey notes, and expedition logs describe locations in DMS, a format modern web maps cannot read directly. Converting those historical coordinates to decimal degrees lets them be plotted and verified on today's mapping tools.

Example: A historian in Edinburgh converts a 1960s land deed written in DMS to decimal degrees and plots the parcel boundary on a modern map to check it against current records.
Translating shared location codes

Location sharing increasingly arrives as Plus Codes or grid references rather than street addresses, especially where addressing is informal. Converting the received code into decimal degrees lets it be pasted into whatever mapping app the team already uses.

Example: A rescue volunteer in the Alps receives a Plus Code by text message from a hiker and converts it to decimal degrees to enter into the team's mapping app.
Cleaning a mixed-format spreadsheet

Supplier lists, asset registers, and site databases often accumulate coordinates in a mixture of DMS and decimal formats from different contributors. Converting everything to one consistent decimal-degrees column makes the data sortable, mappable, and safe to import elsewhere.

Example: A logistics coordinator in Mumbai standardises a supplier spreadsheet that mixes DMS and decimal formats into a single decimal-degrees column before importing it into the routing system.

How it's calculated

Different coordinate systems serve different purposes: DD for web maps, DMS for traditional navigation, UTM for metric-based mapping, MGRS for military use, and Plus Codes for locations without addresses.

The calculation runs in your browser - no data is sent to our servers. Map tiles come from OpenStreetMap (ODbL license), geocoding uses Nominatim (1 request/second limit), and elevation uses the Open-Elevation API backed by SRTM data. All are free, open services.

All calculations use the WGS84 datum (EPSG:4326), the same as GPS. For other datums (NAD27, NAD83, ETRS89), a separate conversion is needed. The difference is typically under 1 metre - negligible for most uses but important for survey-grade work.

The formulas match those in professional GIS software (QGIS, ArcGIS, Global Mapper), just in a browser-friendly form. For sub-metre accuracy, use professional software with ellipsoidal calculations. Results are shown in multiple units: km and miles for distance, km²/m²/hectares/acres for area, metres and feet for elevation. Conversion factors are exact (1 mile = 1.609344 km), so the only error source is input precision.

Related tools and resources

For more tools in this category, explore the related tools listed below. Each tool includes full documentation, examples and FAQs. Explore related tools in our Coordinates category for complementary functionality. See the Tools index for all 329 tools, or read our blog for in-depth articles on geography and maps.

Frequently asked questions

What is UTM?

Universal Transverse Mercator - a grid-based system dividing Earth into 60 zones.

What are Plus Codes?

Open Location Codes by Google - short codes for any place, usable offline.

Which coordinate formats can it convert between?

Decimal degrees, degrees-minutes-seconds (DMS), UTM, MGRS, and Plus Codes. Choose any of them as the input and any as the output. This covers the formats used by consumer maps, professional GIS, military grids, and modern location-sharing codes in one place.

Does the converter work offline?

Yes, fully. Every conversion is pure mathematics executed in your browser: no server, no lookup, no connection required. The only feature needing the internet is place-name search, if you use it to find your starting coordinates.

Which map datum does it use?

WGS84, the datum behind GPS and virtually all web mapping. Coordinates referenced to older datums, such as NAD27 in North America or ED50 in Europe, can differ by tens of metres from their WGS84 equivalents. If your source uses a legacy datum, convert the datum separately before converting the format.

Why does my UTM result look wrong near a zone edge?

A point near a zone boundary can legitimately be expressed in either adjacent zone, and the converter picks one by the standard rule. Both are correct; the choice only matters for consistency. Use whichever zone your map, project, or colleagues are already working in.

How precise is a Plus Code?

A full Plus Code identifies an area roughly 3 by 3 metres, precise enough to find a specific building entrance. Short codes are relative to a nearby locality and need that context to resolve. They are designed for places with no street addressing, where even a small area is a huge improvement over nothing.

Can I convert a whole list of coordinates at once?

The tool converts one point at a time, which suits checking and translating individual positions. For bulk work with hundreds of points, use the same mathematics in a spreadsheet formula or a GIS tool, which are built for batch processing.

What is the relationship between MGRS and UTM?

MGRS is built directly on UTM: it uses the same Transverse Mercator projection and zones, but replaces raw easting and northing numbers with a two-letter 100 km grid-square identifier followed by digits. Military and rescue teams prefer the compact MGRS form for radio and print, while UTM's plain numbers suit computation.

What does the N or S after the UTM zone mean?

It marks the hemisphere: north or south of the equator. The letter selects the false northing applied to the grid: 0 metres at the equator in the northern hemisphere, versus 10,000,000 metres at the equator in the southern hemisphere, which keeps all southern northings positive.

Data sources & methodology