How to Add GPS Location to Photos — Choosing the Right Method (2026)

There isn't one right way to add GPS coordinates to a photo. There's a fast way, a free way, a precise way, a batch way, and a private way — and which one you should pick depends on what the photo is, how many you have, and what you're going to do with the result. This guide walks through each method honestly, so you can stop guessing.

The Quick Decision Tree

If you only read one section, read this one.

• One JPEG, you don't already have software installed: use the in-browser Add GPS to a photo tool. Drop in, pick the spot, download. ~30 seconds.
• Several photos from the same place (a trip, a wedding, a property shoot): the batch geotag tool applies the same coordinates to a set in one pass.
• A whole folder of hundreds or thousands of files: ExifTool from the command line or GeoSetter on Windows. Slower to learn, but the only sane option at that scale.
• You shoot RAW (CR2, NEF, ARW, DNG): Lightroom, Capture One, digiKam, or ExifTool. Browser tools and most mobile apps don't touch RAW.
• The photo is already on your phone and you want to fix it there: iPhone's Photos app and Google Photos on Android both have a built-in location editor — no extra apps needed.
• The photo's GPS is already wrong (not missing): use the geo tag editor page — it's set up to read existing GPS and let you correct it.

What Actually Happens When You "Add GPS" to a Photo

Behind the scenes, every method does the same handful of things to the file. Knowing what those are helps you understand why some methods work and some don't.

A JPEG is a container. The image pixels live in one section; metadata lives in a small EXIF segment near the start of the file. Adding GPS means writing six values into that segment:

• GPSLatitude and GPSLatitudeRef — the latitude as degrees-minutes-seconds, plus an N or S marker.
• GPSLongitude and GPSLongitudeRef — same for longitude with an E or W marker.
• GPSAltitude and GPSAltitudeRef — optional, marked above or below sea level.

Three things to internalise:

1. The pixel data is not touched. There's no quality loss between the input and the output, no matter which tool you use.
2. You enter coordinates in decimal degrees (40.7128, -74.0060) but the EXIF stores them as DMS (40° 42' 46" N, 74° 0' 22" W). Every decent tool converts automatically.
3. The format is JPEG-specific. PNG can carry textual metadata but doesn't have a standard GPS tag; HEIC (the iPhone format) does, but most browser tools haven't caught up. RAW formats use sidecar files (.XMP) or vendor-specific containers.

Method by Method: When Each One Earns Its Place

In-browser tools (this site, and a couple of competitors)

Best for one-off edits and small batches. The file is read, GPS bytes are rewritten, and a new copy is offered as a download — all inside the browser tab, with no server upload. Nothing to install, works on any device with a modern browser, and the original on your disk is never modified.

Tradeoffs: most browser tools cap you at a few files at a time, and they don't handle RAW. If you have a thousand photos, this isn't the right tool.

The phone's built-in editor (iPhone Photos, Google Photos)

Best when the photo is already on the phone and you don't need precise coordinates. iPhone lets you search a place name or drag a pin in Photos → info → Adjust. Google Photos has the same flow on Android.

Tradeoffs: neither lets you type exact decimal coordinates. If you have a survey-grade lat/lng to enter, you need a tool that accepts numeric input. Also, on iPhone the change is applied to the file when you share it; on Android, Google Photos updates the original.

Desktop apps that already manage your photos (Lightroom, Photos, digiKam)

Best when geotagging is part of your existing workflow. In Lightroom, the Map module lets you drag photos onto a location or import a GPX track and snap photos to it by timestamp. Apple Photos has a per-photo location field. digiKam's Geolocation editor is the open-source equivalent.

Tradeoffs: they assume the photos are already in the catalog. Adding a one-off photo from outside your library means importing first, which is a lot of friction for a small task.

ExifTool (command line)

Best for batch jobs and scripting. The single command:

exiftool -GPSLatitude=48.8584 -GPSLatitudeRef=N \
         -GPSLongitude=2.2945 -GPSLongitudeRef=E \
         -overwrite_original photo.jpg

…handles one file. Point it at a folder, glob a pattern, drive it from a shell loop, or hand it a CSV — it'll tag thousands of files in seconds. Free, works on Windows/macOS/Linux, supports RAW.

Tradeoffs: it's a command-line tool. If you've never opened a terminal, the learning curve is real. The official docs are dense but accurate.

GeoSetter (Windows desktop, free)

Best when you want a GUI for batch tagging on Windows without paying for Lightroom. It loads a folder of photos, shows a map, and lets you assign locations either by clicking the map or by syncing a GPX track. Output is written back to the original files.

Tradeoffs: Windows only, hasn't seen heavy development in a while, and the interface looks dated. Still works fine for the job it does.

Mobile geotagging apps (Photo Exif Editor, Metapho, etc.)

Best when you're stuck on mobile and don't want to use Safari/Chrome to reach a web tool. Most of these apps are basically a phone-shaped wrapper around the same EXIF rewriting that a browser tool does.

Tradeoffs: many free versions are ad-supported. Privacy varies — some apps upload photos for processing instead of doing it locally. Read the app's permissions before installing.

Picking the Right Coordinate Precision

Not all GPS coordinates need to be exact to seven decimal places. A quick guide:

• 2 decimals (~1 km): good enough for "this photo was taken in Brooklyn".
• 4 decimals (~10 m): the precision a typical phone GPS records. Identifies a building.
• 5 decimals (~1 m): identifies a room. This is what most photo-management software cares about.
• 6+ decimals (<10 cm): beyond the noise floor of consumer GPS — fine to use, but the extra precision is fictitious.

If you're copying coordinates from Google Maps' right-click menu, you're already getting 7 decimals. Just paste them in; don't agonise over rounding.

Things That Will Surprise You

• Instagram and Facebook strip your GPS on upload. If your goal is "make this photo show up in location-based searches on Instagram", adding GPS to the file won't do anything — the platforms re-encode and discard EXIF. Use the platform's own location-tagging UI instead.
• Google Photos respects EXIF GPS, but it also has its own internal location field. If your photo had no GPS when you uploaded it but you typed a location into Google Photos, that location lives in Google's database, not in the file. Download the file and the GPS is still empty. To make it permanent, edit the file before uploading.
• WhatsApp's "send as photo" recompresses and strips EXIF; "send as document" preserves it. If you're handing off geotagged files, choose the document option.
• iCloud's "Share Original" toggle controls whether GPS travels with the photo. If recipients aren't seeing the location you set, check the share-sheet options.

Companion Reading on This Site

• The single-photo browser tool. The fastest way to do this if you don't want to read any further.
• Batch geotagging. If you have a set from one location.
• Fixing wrong GPS coordinates. If the location is there but it's incorrect.
• The full step-by-step cross-platform guide. If you want explicit click-by-click instructions for iPhone, Android, Windows, and macOS in one place.
• EXIF explained. If the metadata side is the part you find confusing.