mapbench
Interactive toolCoordinates

Coordinate Converter

Paste a coordinate pair and switch between common human and machine formats.

By Aryan Khan, Founder & Editor · Updated October 2026

✓ No account required✓ Worldwide✓ No installation required
Tool workspace
Enter your inputs and review the result
Loading tool…

For example, Times Square is 40.7580, −73.9855 in decimals, 40°45′28.8″N 73°59′07.8″W in DMS, and 40°45.480′N 73°59.130′W in degrees-minutes — one point, three dresses, all converted here.

Simple workflow

How to use Coordinate Converter

One point, every common format, no hand arithmetic:

The Coordinate Converter takes a coordinate pair and switches it between the common human and machine formats — decimal degrees, degrees-minutes-seconds, and degrees with decimal minutes. Paste the pair, read every format at once, and copy the one your chart, form or software actually wants.

  1. 1Enter coordinates.
  2. 2Choose output format.
  3. 3Copy the result.

What people use Coordinate Converter for

1. Charts to GIS

Paper and PDF charts speak DMS; GIS eats decimals. The converter is the customs post between them — single values ride the DMS to Decimal and Decimal to DMS lanes.

2. GPS unit settings

Handhelds offer all three formats; matching the unit's display to your notes' format ends transcription errors at the source.

3. Forms that demand a format

Some portal wants DMS with hemisphere letters; another wants signed decimals. Convert once, paste exactly, never retype digits.

4. Checking mystery coordinates

A pair in an unknown dress? The Coordinate Format Detector names it; this page converts it.

Worked examples

Example · Times Square, three ways

Decimal: 40.7580, −73.9855. DMS: 40°45′28.8″N, 73°59′07.8″W. Degrees-minutes: 40°45.480′N, 73°59.130′W. The minus sign and the W are the same fact in two dialects.

Example · The sign trap

−73.9855 already means west. Writing '−73.9855 W' double-negates the point to the wrong hemisphere in strict parsers — convert here and let the format carry one convention at a time.

Convert coordinates while keeping datum, order and precision visible

Coordinate conversion is easy to get wrong because several valid formats can describe the same location and some systems reverse longitude and latitude order. MapBench converts WGS84 coordinates across decimal degrees, degrees-minutes-seconds, degrees and decimal minutes, UTM, MGRS, Geohash and Plus Code representations while keeping the selected point visible on a map. Batch conversion and CSV export make the same workflow useful for small datasets rather than only one coordinate at a time.

Changing notation does not improve positional accuracy. A GPS point measured to roughly ten metres remains a roughly ten-metre observation even if it is displayed with many decimal places or encoded into a long grid string. Precision controls should therefore match the quality of the source data rather than creating false confidence through extra digits.

Datum also matters. The main MapBench converter is built around WGS84, the reference used by ordinary GPS and most web maps. Coordinates from a local survey datum or projected engineering grid can shift if they are treated as WGS84 without a proper datum transformation. For professional GIS or surveying work, confirm the coordinate reference system before conversion.

How to interpret the result

The most common errors come from using a correct result to answer the wrong geographic question. Keep these points in mind for Coordinate Converter:

  • Match precision to source: consumer GPS earns about five decimals; quoting six or seven implies a survey you didn't do. Rounding deliberately is honesty, not loss.
  • Adopt one storage format — decimal degrees, WGS84, five or six decimals — for every dataset you own, and convert at the edges for display. Mixed notations in one column are the root of nearly every coordinate bug.

Limits & appropriate use

Coordinates are lossless in principle and lossy in practice, and every loss is human: swapped axes, wrong hemispheres, datum relics, precision theatre. The converters eliminate the notation problem completely — DMS, UTM, MGRS and Plus Codes are exact translations on WGS84 — but they cannot eliminate the provenance problem: a number without its datum and its source is a rumour. Old NAD27-era documents, hand-typed sheets and seven-decimal CSVs each carry their own failure signature, and the honest tool answers with validation errors and visible pins rather than silent corrections.

The practical boundary is therefore organisational, not mathematical: teams that standardise storage (decimal, WGS84, sane precision) and ritualise the map check enjoy a lossless system; teams that don't accumulate expensive folklore. For work beyond consumer frames — control points, machine guidance, legal description — the escalation is geodetic: licensed surveyors, published transformations and national datums. Everything between a pasted waypoint and that door is exactly where this toolset lives.

  • Datum-critical legacy data → published grid transformations (NTv2/HTDP).
  • Control points and machine guidance → licensed geodetic survey.
  • Aviation/marine charts → the chart's own datum and notation, verbatim.

Data & methodology

Parses supported decimal/DMS, UTM, MGRS, Plus Code and geohash inputs locally and displays several formats. Grid codes and displayed coordinates are rounded; cell centres are not the original exact point.

For source details, licences and model limitations, see Data Sources and Methodology.

Key terms worth knowing

DMS
Degrees-minutes-seconds notation; 1° = 60′ = 3600″.
UTM
Metre-based zone/easting/northing grid on the WGS84 ellipsoid.

Editorial guidance: MapBench explains the method and limitations so the tool can be used as a transparent reference, not as a black-box answer. For legal boundaries, safety-critical routing, surveying, engineering, regulated decisions or official statistics, verify the result with the responsible authority or a qualified professional.

Category: Coordinates. Results are intended for everyday analysis and planning unless a page explicitly states otherwise.

Method, assumptions & limits

This tool’s method
Parses supported decimal/DMS, UTM, MGRS, Plus Code and geohash inputs locally and displays several formats. Grid codes and displayed coordinates are rounded; cell centres are not the original exact point.
Before relying on the answer
Record the coordinate order, signs, format and datum where specified. In GeoJSON, positions are longitude first; many input forms ask for latitude first.
What the result cannot establish
A format conversion preserves the source measurement's uncertainty. Extra digits do not improve the original GPS fix.

Coverage: Worldwide. Search, basemap and external data requests may use third-party services; browser-based does not mean every operation is offline. Read the source and licence notes, calculation methodology and privacy policy. If a result looks inconsistent, report a correction with the inputs and mode used.

Common questions

Frequently asked questions

Clear answers about the calculation, accuracy and appropriate use.

Datum?

WGS84 assumed unless noted.

Which datum do these coordinate tools use?

MapBench location tools generally use WGS84 latitude and longitude, the same global reference system commonly used by GPS and web maps.

Do more decimal places always mean better accuracy?

No. More digits increase numeric precision, but they cannot improve the accuracy of the original GPS, survey or source data.

Can I copy the result into GIS software?

Usually yes. Check the format, axis order and datum expected by the destination software before importing.

Which datum does it use?

WGS84 — conversions change the format, never the datum. A point in another datum needs a datum transformation first, which format conversion is not.

Hemisphere letters or signs?

Both are produced; use letters with DMS/DDM and signs with decimals, one convention per value — the sign trap example on this page shows why.

Batch conversion?

One pair at a time here — lists belong to spreadsheet formulas or GIS, with this page as the spot-checker of their output.

It rejected my input.

Separators and symbols vary; the Coordinate Parser loosens messy strings into clean values first, then conversion proceeds.

Radians included?

The degrees-radians lane has its own converter for the pure angle case; pairs in radians convert through the same subdivision arithmetic.

Zero and pole edge cases?

0,0 and the poles convert mechanically — formats survive where geography gets philosophical.

Which format should I store?

Signed decimal degrees, full precision, WGS84 noted. Every other format is one conversion away; originals in any other dress invite transcription archaeology.

Minutes can exceed 60 in my input?

That signals degrees-minutes misread as DMS or a typo — the parser and detector pages help untangle which.

Related tools and resources

Single lanes: DMS to Decimal and Decimal to DMS; detect: the Coordinate Format Detector; parse: the Coordinate Parser.

Keep measuring

More free tools

How this page is maintained

Sources, methodology & editorial trust

Data & privacy
  • ✓ Browser-first processing where supported
  • ✓ External sources are documented
  • ✓ No account required for public tools
  • ✓ Review data sources
Method & review

Calculations are documented with their assumptions, limitations and source context rather than presented as unexplained answers.

Editor & category

Reviewed and maintained by Aryan Khan, Founder & Editor of MapBench.

Coordinates
Browse all Coordinates →

Part of our coordinates hub

Coordinate Converter sits in the coordinates cluster, alongside 63 other tools that answer neighbouring questions with different methods or datasets.

You may also need

When this answer is only part of the job, these clusters cover the next step.

Read the guide behind this tool

Understanding GPS Coordinates: Formats, Datums and Precision — A practical guide to latitude/longitude: what decimal degrees and DMS really mean, why datums matter, and how many decimal places you actually need.