How to Put GPS Coordinates in a QR Code
Turn GPS coordinates into a QR code that opens the exact spot in Google, Apple or Waze maps. Formats, free setup, and the mistakes to avoid.

To put GPS coordinates in a QR code: copy the latitude and longitude from your maps app, paste them into a location QR code generator, and download the code — scanning it opens that exact spot in the person's maps app. It's free, and the whole thing takes about two minutes.
The part worth slowing down for is how the location gets encoded, because the two methods behave differently on iPhones — and one of them can't be fixed after printing.
An address works fine for a storefront on a named street. Coordinates win everywhere addresses get fuzzy:
- Trailheads, beaches, festival fields — places with no street address at all
- Parking entrances and loading gates — the address points at the building's front door; the coordinates point at the gate around the corner
- New construction and rural properties — geocoding often lags reality by months
- Large venues — "Hall 4, north entrance" is a coordinate, not an address
The failure mode of an address-based link is silent: the maps app confidently routes people to the wrong spot. Coordinates remove the guesswork — the pin is exactly where you dropped it.
- Google Maps (desktop or phone): press and hold (or right-click) the exact spot → the coordinates appear → tap to copy.
- iPhone: the built-in Compass app shows your current coordinates; or drop a pin in Apple Maps and swipe up.
- Format: decimal degrees, latitude first:
56.94965, 24.10519. South and west are negative numbers. Five or six decimal places is plenty — that's meter-level precision.
The classic mistake is swapping the pair. Latitude comes first and is always between −90 and 90; if your first number is bigger than 90, they're reversed.
1. A raw geo: link (static). The code contains the coordinates themselves, like geo:56.94965,24.10519 — a real internet standard (RFC 5870, if you enjoy that sort of thing). Scanning hands the coordinates directly to a maps app, self-contained and even offline-capable. The catch is on iPhones: Apple Maps doesn't register the geo: scheme at all — iOS passes these links to whichever third-party app happens to claim them, so what a scanner sees depends on the phone's installed apps and iOS version. Android is friendlier and typically shows a maps chooser. And because the coordinates are printed into the pattern, the location can never be changed.
2. A trackable code that opens a map page. The code contains a short link; scanning opens a page showing the pin on a map with Google Maps, Apple Maps, and Waze buttons — the person taps their preferred app and navigation starts. This behaves identically on every phone, the location stays editable after printing, and every scan is counted, so you know whether the sign at the car park is actually being used.
For anything printed and public-facing, the second method is the safe default. Reserve raw geo: codes for cases where offline scanning genuinely matters.
- Open the location QR generator.
- Drop the pin on the map — or paste your coordinates — and give the place a name (that's the label people see, so "Warehouse entrance B" beats raw numbers).
- Style it if you like, then download the SVG for print (it scales cleanly to any size).
- Test on both an iPhone and an Android before the print run. Scan, tap through to navigation, and confirm the pin is where you meant — not roughly where you meant.
- Swapped latitude and longitude — the #1 error, and the pin usually lands in another country, so it's caught fast if you test.
- Encoding the address instead of the spot — you inherit every geocoding error. Use the pin.
- Truncated decimals —
56.95, 24.11is a ~1 km-wide area, not a gate. - Testing on one platform only — the
geo:inconsistency between iOS and Android is invisible until someone else's phone does something different. - Printing a static code for a temporary location — event moved, venue changed, and 500 printed invitations now point at the old spot. A dynamic code would have been a 10-second dashboard edit; this exact scenario is why open house and event signage should default to trackable codes.
One related thing worth clearing up: putting a location into a QR code is the opposite of QR location tracking — one broadcasts a spot you chose, the other measures where scans happen. If you came here for the tracking side, that's a different article.
Got the coordinates ready? Drop a pin and get your QR code — free, no scan limits, and if the venue changes, so can the pin.