DMS to Decimal
Paste DMS coordinates to get decimal degrees for GIS and web maps.
By Aryan Khan, Founder & Editor · Updated October 2026
For example, 40°45′28.8″N, 73°59′07.8″W pastes in from a chart and comes out as 40.7580, −73.9855 — ready for every map and database on earth.
How to use DMS to Decimal
Classical dress in, machine dress out:
DMS to Decimal converts degrees-minutes-seconds coordinates into decimal degrees for GIS and web maps. Paste the DMS pair and read the signed decimals — hemispheres folded into signs, minutes and seconds divided by 60 and 3,600, all the carries handled by the converter instead of your patience.
- 1Enter DMS.
- 2Copy decimal degrees.
What people use DMS to Decimal for
1. Chart-to-GIS transcription
The daily pipeline of everyone digitising anything. Pair with the Coordinate Parser when the chart's text is messier than its numbers.
2. Guidebook and document mining
Peaks, wrecks, springs and sites are published in DMS for a century's worth of print. Decimals make them mappable.
3. Verifying a conversion
Convert, then convert back with Decimal to DMS — the round trip must return your string, seconds and all.
4. Data entry rescue
A form gave you DMS fields and your source gave decimals — or the reverse. Convert the source once; never retype a digit.
Worked examples
40°45′28.8″ = 40 + 45/60 + 28.8/3600 = 40 + 0.75 + 0.008 = 40.7580°. The longitude: 73 + 59/60 + 7.8/3600 = 73.9855, signed negative for W. Two divisions and a sign — easy to say, tedious at scale.
Seconds written as 60 or more in a source (40°45′60″) signal a rounding artefact upstream. The converter normalises the arithmetic; the value's provenance is your eyebrow's job.
The formula, once and for all
Decimal = degrees + minutes/60 + seconds/3600, sign from hemisphere.
| Component | Divisor | Times Square latitude |
|---|---|---|
| Degrees | × 1 | 40 |
| Minutes | ÷ 60 | 45 → 0.75 |
| Seconds | ÷ 3,600 | 28.8 → 0.008 |
| Hemisphere | N/E positive, S/W negative | N → +40.7580 |
Every DMS conversion on earth is this table. Automation exists because humans transpose the 45 and the 28.8 at 1 a.m. — the converter does not have a 1 a.m.
Why and how to convert DMS to decimal degrees
Degrees-minutes-seconds is the notation of paper charts, old surveys and many handheld GPS screens; decimal degrees is what every web map, API and spreadsheet wants. Paste values like 40°26'46"N 79°58'36"W — hemisphere letters, minus signs or mixed separators all accepted — and get clean signed decimal pairs ready to copy. The parser validates ranges (latitude ≤ 90, longitude ≤ 180) and explains failures instead of guessing.
The arithmetic is the classic sexagesimal expansion — degrees plus minutes over 60 plus seconds over 3600 — with south and west becoming negative, and the page shows the mapping explicitly so students learn rather than just copy. Precision is preserved to the sub-metre level your input carries. When the source is already decimal and the destination must be chart notation, the decimal-to-DMS tool runs the conversion in reverse; for UTM, MGRS or Plus Code targets, the all-in-one converter covers the rest of the family.
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 DMS to Decimal:
- Sanity-check every pasted pair by eye on a map before using it: latitude/longitude swaps land you in the ocean so reliably that 'the Null Island bug' has a name. A two-second visual check costs nothing and catches most transcription errors.
- 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.
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
The shared converter parses supported DMS or coordinate pairs locally and displays decimal degrees and other supported formats; verify axis order and hemisphere.
For source details, licences and model limitations, see Data Sources and Methodology.
Key terms worth knowing
- UTM
- Metre-based zone/easting/northing grid on the WGS84 ellipsoid.
- Plus Code
- Open Location Code: keyless short codes for any spot, by open math.
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
- The shared converter parses supported DMS or coordinate pairs locally and displays decimal degrees and other supported formats; verify axis order and hemisphere.
- 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.
Frequently asked questions
Clear answers about the calculation, accuracy and appropriate use.
Mixed formats?
Use clear degree/minute/second markers for best parsing.
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.
Can it handle mixed formats?
DMS pairs in the common dresses (symbols, spaces, letters) parse here; truly mangled strings go through the Coordinate Parser first, which is built for mess.
Hemisphere letters or leading signs?
Both read correctly; letters set the sign, and a minus with a W would double-negate — the parser family flags the contradiction.
Seconds as decimals?
28.8″ style is native here — fractional seconds are the modern chart norm.
Batch conversion?
Pairs one at a time; columns belong to GIS imports, spot-checked against this page's arithmetic.
Degrees-minutes (no seconds)?
That is DDM — the Coordinate Converter dresses pairs that way; the division is minutes/60 alone.
It rejected my string.
Check order (lat first), ranges (minutes and seconds under 60 in honest data) and symbols — the failure points at the component that broke.
Why does GIS hate DMS?
Because text formats invite a thousand parsers' disagreements; numbers invite none. Decimals are the interchange; DMS is the literature.
Antarctic and polar pairs?
Latitude to ±90 converts mechanically; longitude at the pole is a formality the arithmetic indulges.
Related tools and resources
Reverse: Decimal to DMS; all formats: the Coordinate Converter; messy strings: the Coordinate Parser.
More free tools
Sources, methodology & editorial trust
- ✓ Browser-first processing where supported
- ✓ External sources are documented
- ✓ No account required for public tools
- ✓ Review data sources
Calculations are documented with their assumptions, limitations and source context rather than presented as unexplained answers.
Reviewed and maintained by Aryan Khan, Founder & Editor of MapBench.
Part of our coordinates hub
DMS to Decimal 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
How to Find the Latitude and Longitude of Any Place — Search an address, click a map, or use GPS — then read decimal degrees the way software expects, without swapping lat and lng.