A Photographer's Guide to Geotagging: Pros, Cons, and Privacy

Every photograph your camera or phone takes can carry a small, precise secret: the exact latitude and longitude where the shutter fired. For photographers that is either a superpower or a liability, depending on what happens to the file next. Used privately, geotagging turns years of scattered shooting into a searchable map of your own work. Published carelessly, it hands a stranger the spot you were standing in — which for a landscape frame may not matter at all, and for a photo taken on your own doorstep may matter a great deal.

The decision deserves more than a default camera setting, because the tradeoffs cut in real directions depending on what and where you shoot.

1. 1.Record coordinates, publish regions. Full precision belongs in your catalogue; a caption rarely needs more than a city or a valley.
2. 2.Audit your export presets once. Most people have never checked whether their export pipeline carries GPS fields through, and the default answer varies by application.
3. 3.Treat homes and habitats as special cases. Nesting sites, private property and anywhere with a safety concern stay untagged in both metadata and caption.
4. 4.Post after you leave. A live location post says where you are, not merely where you have been.
5. 5.Remember the picture itself is evidence. Stripping the tag does not make the scene unreadable.

The organisational case is strong. If you shoot travel, landscape or wildlife, GPS data makes your archive filterable by location instead of only by date — every sunset from one mountain range, every venue photographed in a given city, all in one query. It also solves a problem every working photographer eventually hits: staring at a good frame from three years ago with no memory of where it was taken, and no way to return in better light or recommend the spot to a client. For anyone licensing images, a specific place in the caption adds real value, because editors and stock buyers usually want the location rather than just the country.

The catch is precision. A coordinate embedded in Exif — the metadata standard published in 1995 and inherited by every phone camera since — is not "somewhere in this neighbourhood": a phone combines GPS with Wi-Fi and cell positioning and typically lands within about 5 metres, and the same block can also record altitude and the compass bearing the camera was facing. A handful of ordinary situations turn that into a genuine risk. A photo taken on your own balcony and posted publicly effectively publishes your address. A wildlife photographer who tags a rare nesting site can point crowds, or worse, straight at it, which is why many nature photographers now withhold exact coordinates for sensitive species as a matter of course. And any frame posted while you are still on location tags your present whereabouts rather than your past ones.

• —Keep exact coordinates in your private catalogue. Lightroom, Capture One and most asset managers store full GPS locally for your own search — that copy never has to leave your drive.
• —Strip metadata on export. Large platforms re-encode and drop Exif, but direct file shares, personal galleries and some portfolio hosts do not. A single pass with ExifTool or an export preset closes the gap.
• —Generalise in captions. "Shot in the Dolomites" gives context and searchability without a pin anyone can walk to.
• —Treat sensitive locations as a special case. Nesting sites, private property, a friend's home: no metadata, no caption, no exceptions.
• —Delay location posts from live trips. Publish the coordinates once you have left, not while you are still standing there.

It is worth being honest about what metadata stripping buys. Raven, at withraven.net, never reads Exif at all: it is shown the pixels and estimates a location from what is visible — architecture, vegetation, road markings, signage, light. The image is processed in memory and never stored, and the result is an entertainment-only guess that can be wrong. Running one of your own supposedly anonymised photos through it is a useful gut check. If a model can still name the region from the scene alone, stripping the tag bought less privacy than you assumed. The piece on what data Raven actually sees when you upload sets out exactly which parts of the file are involved, and the step-by-step walkthrough covers reading the confidence indicator on the result.

For a sense of how the tag gets written in the first place — and how to switch it off at source on both iOS and Android — see why phones add GPS data to photos. If you would rather run the gut check from the phone that took the photo, the free Geospy AI app does the same visual reasoning without a desk involved.

The honest answer is not "always geotag" or "never geotag". It is knowing which of your photographs are working documents for your own archive and which are public statements about where you have been, then giving each one the precision it deserves. Most photographers end up with a simple two-speed habit: everything tagged at capture, almost nothing published at full resolution of place. That is a small amount of discipline for a large reduction in what you give away by accident.