Skip to content

Location QR Code Generator

Encode a precise geographic point in a provider-neutral geo URI without a server-side map lookup.

Private by design

Generated in your browser

Scalable SVG download

High-resolution PNG download

Build your Location code

Fields stay on this device while the QR image is generated.

QR payload details

Decimal degrees from -90 to 90.

Decimal degrees from -180 to 180.

QR appearance

Higher recovery adds more modules. Medium suits most clean prints.

Choose the square pixel size for PNG and the preview viewport.

Four modules is the conservative print default.

Color contrast is 19.9:1. Print testing is still required.

Preview

This preview matches the current downloads.

Generating the initial preview…

Payload preview

The encoded payload will appear here.

How to make this QR code dependable

Practical guidance for payload accuracy, privacy, compatibility, and real-world print testing.

Encode a precise point with a geo URI

A location QR code stores latitude and longitude in the geo URI format defined by RFC 5870. A compatible phone can offer to open that point in a mapping application. Add an optional place label to make the handoff more recognizable in apps that understand the common q query convention. This is useful for trailheads, venue entrances, delivery gates, meeting points, public art, field equipment, and destinations without a dependable street address.

Latitude must be between minus 90 and 90; longitude between minus 180 and 180. Enter decimal degrees using a period as the decimal separator. The first coordinate is latitude and the second longitude. Reversing them can produce another valid-looking point far away, so compare the payload preview with the source and test the opened map before distributing anything.

Choose coordinates for the arrival experience

The center of a building is not always the right destination. For visitors, use the public entrance rather than an office centroid. For deliveries, select the loading gate. For an outdoor gathering, choose a safe meeting point accessible from established paths. Satellite imagery, address search, and GPS readings can disagree, so validate the point against local knowledge and the route a visitor will actually take.

Coordinate precision should match the task. Five decimal places represents roughly meter-level detail in many contexts and is normally enough for entrances. Excessive digits imply accuracy the source may not have. A phone GPS fix beside tall buildings, cliffs, or dense tree cover can drift; take several readings or use an authoritative mapping source when safety or logistics depend on the result.

Understand mapping-app differences

The geo URI identifies a location independently of one map provider, but devices decide which app opens and how the optional label is displayed. Some desktop scanners show the raw coordinates. Some mobile apps search for the label rather than pinning the exact point if the query syntax is interpreted differently. Keep the label short and verify that the pin remains at the coordinates on your target devices.

A location code does not contain turn-by-turn directions, opening hours, parking rules, accessibility details, or live hazards. Place critical arrival guidance beside the code or link to a maintained venue page instead. Never use a static QR as the sole navigation aid for emergency evacuation, remote backcountry travel, or changing construction access.

Protect sensitive places

Generation is local, so the coordinates and label are not uploaded to create the image. The exported symbol is readable by anyone who obtains it. Do not encode private homes, protected habitats, vulnerable infrastructure, confidential work sites, or a person’s real-time whereabouts for a public audience. Consider whether the physical placement itself reveals a location you should not publish online.

For an invitation to a private address, distribute the code only to intended guests and avoid social-media photos that include it. If access rules may change, use an authenticated event page instead of permanent coordinates. A geo QR has no revocation mechanism and no way to know who decoded it.

Print for outdoor and operational conditions

Location codes are often used outdoors, where glare, distance, weather, dirt, and damaged signs matter. Use strong contrast, an undisturbed four-module margin, and enough physical size for the expected viewing distance. High correction can improve tolerance to limited damage, but it also increases density. A weather-resistant matte surface and sensible placement usually deliver more value.

SVG is suitable for signs and large-format output. If a fabricator converts it, request a proof that preserves square modules and quiet space. Do not allow mounting holes, folds, reflective tape, or a frame to overlap the code. Pair it with the written place name and coordinates so the sign remains informative when scanning is unavailable.

Test the pin and the route

Scan the actual proof with several phones and open it in the mapping apps your visitors commonly use. Inspect the pin at close zoom, request a route from multiple directions, and confirm that navigation ends at the correct side of the site. Walk or drive the final approach when practical; a mathematically accurate point can still lead through a locked gate or unsafe road.

Retest after entrances move, roads change, or event layouts are revised. Date the source artwork and record where the coordinates came from. For temporary events, remove signs promptly so late scanners are not directed to an inactive or unsafe location. Include a contact fallback for people who arrive but cannot find the intended entrance.

Example: Venue entrance

This sample shows the exact kind of text encoded by this route.

geo:43.6577,-70.2547?q=43.6577,-70.2547(Harbor%20entrance)

Questions people ask

Which coordinate comes first?

Latitude comes first, followed by longitude, as specified for geo URIs.

Does this force a particular map app?

No. The operating system chooses how to handle the provider-neutral geo URI.

How many decimal places should I use?

About five decimal places is usually enough for an entrance-level point; validate it against the real arrival path.