GPS Coordinates Format for Photos: Decimal vs DMS Explained

Open a geotagged photo in five different tools and you may see five different versions of the same location: 40.748817, -73.985428 in one, 40°44'55.7"N 73°59'07.5"W in another, and 18TWL8553213 in a GIS report. They all describe the Empire State Building, but they are not interchangeable when accuracy or downstream tooling matters. This guide explains every GPS coordinate format you will encounter in photo metadata, when each is appropriate, and how to convert between them without losing precision.

What Photos Actually Store

Inside the EXIF metadata of a JPEG, HEIC, or RAW file, GPS is stored in a fixed format defined by the EXIF specification:

• GPSLatitude — three rationals representing degrees, minutes, seconds
• GPSLatitudeRef — "N" or "S"
• GPSLongitude — three rationals representing degrees, minutes, seconds
• GPSLongitudeRef — "E" or "W"
• GPSAltitude — a single rational in meters
• GPSAltitudeRef — 0 (above sea level) or 1 (below)

So at the file level, photos always use degrees, minutes, seconds (DMS) — even when your phone shows you a decimal value. Every viewer converts on the fly. Understanding this matters when you write your own pipelines or debug "off-by-a-tiny-amount" coordinates between tools.

Format 1: Decimal Degrees (DD)

The format most humans and most APIs prefer. The Empire State Building in DD:

40.748817, -73.985428

• Latitude: positive = North, negative = South
• Longitude: positive = East, negative = West
• Always six decimal places for sub-meter precision (the USGS publishes a precision table showing 6 decimals ≈ 11 cm)

Use DD when: plugging into Google Maps, OpenStreetMap, Mapbox, Leaflet, or any modern web mapping API. Our bulk geotagger and find-photo-location tools both display DD by default.

Format 2: Degrees, Minutes, Seconds (DMS)

The format EXIF stores natively, and the format most aviation and maritime charts still use:

40°44'55.74"N 73°59'07.54"W

• 1 degree = 60 minutes
• 1 minute = 60 seconds
• Hemisphere indicator (N/S/E/W) replaces the negative sign

Use DMS when: transcribing from a paper map, reading older survey reports, or importing into legacy GIS software. Avoid DMS when typing into a web form — punctuation parsing is brittle and a single missing quote will silently fail.

DD ↔ DMS Conversion

DD = degrees + (minutes / 60) + (seconds / 3600) DMS: degrees = floor(DD) minutes = floor((DD - degrees) * 60) seconds = ((DD - degrees) * 60 - minutes) * 60

For southern or western hemispheres, do the math on the absolute value, then reapply the negative sign or N/S/E/W indicator.

Format 3: Degrees and Decimal Minutes (DDM)

The format favored by GPX track files, marine GPS, and many handheld Garmin units:

40°44.929'N 73°59.126'W

No seconds — just decimal minutes. This is the format you will see if you open a Garmin GPSMAP or a Strava export raw. When matching a GPX track to photos with our GPX sync tool, the conversion happens automatically; you never need to type DDM by hand.

Format 4: UTM (Universal Transverse Mercator)

A projected grid system used by surveyors, the U.S. military, and most professional GIS workflows:

18T 585262 4511263

• Zone (1–60, plus a latitude band letter)
• Easting (meters from a reference meridian)
• Northing (meters from the equator)

UTM is not stored in EXIF. If you need UTM for engineering or mapping deliverables, export from a tool that converts on the fly — QGIS is the free open-source standard, and the USGS National Map provides authoritative datum references.

Use UTM when: producing engineering drawings, environmental reports, or anything that will be opened in ArcGIS or AutoCAD Civil 3D.

Format 5: Plus Codes (Open Location Code)

Google's URL-friendly format, increasingly used in addressing-poor regions:

87G8P27Q+JX

Plus Codes are not stored in EXIF either, but they're useful for sharing photo locations in messages or emails because they are short and unambiguous. Convert any of the above formats at plus.codes.

Format 6: What3Words

Three-word location format covering every 3×3 m square on Earth:

///daring.lion.race

Not an EXIF field. Useful for human communication ("meet me at ///daring.lion.race"), useless for machine processing. Convert with the What3Words API when interoperability matters.

Datums: The Hidden Trap

Every coordinate format depends on a datum — the mathematical model of Earth's shape used to anchor the grid. Photos overwhelmingly use WGS84, the same datum as GPS satellites, Google Maps, and OpenStreetMap.

The exception: scientific archives and very old photos may use NAD27 (North American Datum 1927) or local datums. The difference between WGS84 and NAD27 in the continental U.S. can exceed 100 meters — enough to put a photo on the wrong side of a road. The EXIF tag GPSMapDatum records which datum was used; if it's blank, assume WGS84.

Precision: Don't Lie to Your Users

It is tempting to display 12 decimal places of latitude. Don't. Real-world GPS accuracy on a 2026 smartphone is 3–5 meters outdoors, which corresponds to roughly 5 decimal places of decimal degrees. Showing more digits implies a precision the data does not have, and downstream tools may misinterpret false precision as a survey-grade fix.

| DD precision | Real-world distance | |---|---| | 0 decimals | ~111 km | | 2 decimals | ~1.1 km | | 4 decimals | ~11 m | | 5 decimals | ~1.1 m | | 6 decimals | ~11 cm | | 7 decimals | ~1 cm |

For consumer photos, 5–6 decimals is the practical ceiling. Our EXIF Viewer caps display at 6.

Pasting Coordinates: A Survival Guide

If you copy coordinates from a photo and paste them into Google Maps, the search bar accepts:

• DD with comma: 40.748817, -73.985428
• DD with space: 40.748817 -73.985428
• DMS with quotes: 40°44'55.7"N 73°59'07.5"W
• Plus Codes: 87G8P27Q+JX

It does not reliably accept DDM, UTM, or What3Words. If a paste fails, your fastest path is to convert to DD first.

Negative Numbers vs Hemisphere Indicators

The single most common conversion bug: forgetting that southern latitude is negative and western longitude is negative. Sydney is -33.8688, 151.2093. Rio is -22.9068, -43.1729. If your map shows the photo in the wrong hemisphere, this is almost always why.

EXIF avoids the bug entirely by storing positive numbers paired with N/S/E/W, but every conversion to DD must reapply the sign. Our bulk geotagging API and tools handle this automatically; if you write your own pipeline, add a unit test for southern and western hemisphere photos.

How Coordinate Format Affects Local SEO

For real estate, hospitality, and local-services photos, the coordinate format embedded in EXIF doesn't directly affect ranking — Google Image Search reads the values, not the format. What matters is consistency across your uploads:

1. Always tag from the same address (front door of a property, not the kitchen)
2. Always use the same datum (WGS84 — the default)
3. Always store at full GPS precision rather than rounding

For more on the SEO mechanics, see our guides on bulk geotagging for local SEO and Google Business Profile geotagging.

Frequently Asked Questions

What format does Google Maps use for photo coordinates?

Google Maps displays decimal degrees and accepts DD, DMS, and Plus Codes in its search bar.

What format do iPhone and Android cameras write to EXIF?

Both write DMS internally (the EXIF spec requires it) but display DD in the photo info screen.

How do I convert UTM coordinates from a survey report to a photo's EXIF?

Use QGIS or the NOAA NGS coordinate conversion tool to convert UTM → WGS84 DD, then write to EXIF with our bulk geotagger.

Why do my photos and my GPX track show slightly different coordinates for the same moment?

Datum drift, satellite-fix lag, or GPX time-zone mismatch. Our GPX sync tool handles all three automatically.

Can I store What3Words or Plus Codes inside a photo?

Not in standard EXIF. You can add them as IPTC keywords or XMP custom fields, but no major image viewer reads them.

Conclusion

Photos store DMS internally, humans prefer DD, surveyors prefer UTM, and casual sharers prefer Plus Codes. Knowing which format each tool expects — and respecting the limits of GPS precision — separates a clean photo-mapping workflow from one that quietly corrupts data. When in doubt, convert everything to WGS84 decimal degrees, store six digits, and let downstream tools translate as needed.