The short answer: probably not — but "probably" is the problem
If you post a photo to Threads or Bluesky, the version other people can download almost certainly won't carry your GPS coordinates. Both platforms strip EXIF metadata from public images. But "almost certainly" is doing a lot of work in that sentence, and the only way to know for sure with any given photo is to check the file yourself.
Here's exactly what each platform does in 2026, where the gaps are, and how to verify it in thirty seconds.
First, what's actually in your photo
Every photo your phone takes carries EXIF metadata — a hidden block recording the camera, the settings, the timestamp, and, if location services were on, the exact GPS coordinates where you stood. That last part is the privacy risk. A single vacation photo can pin your hotel; a photo from your couch can pin your home.
Social platforms handle this one of two ways: they strip that data when they process your upload, or they leave it in. Threads and Bluesky both strip — but they do it differently, and for different reasons.
Threads: it behaves like Instagram
Threads is a Meta product built on Instagram's account system, and it inherits Instagram's image pipeline.
When you upload a photo, Meta re-encodes and compresses it, and that process removes GPS and most EXIF from the copy other users see or download. So the public file people can save off your Threads post generally won't leak your location. That's the good news.
The catch — and it's a real one — is what happens on Meta's side. Meta reads and keeps the original. The platform ingests your full-metadata file at upload, stores it on its servers, and can use that information for its own features and advertising. Stripping EXIF from the download protects you from strangers; it does nothing to hide your data from Meta itself.
So: Threads protects you from other users seeing your GPS, not from Meta having it.
Bluesky: stripped at the server, by design
Bluesky, built on the open AT Protocol, also strips EXIF from uploaded images — and its developers have been unusually transparent about it.
Bluesky's image server (it uses imgproxy) is configured to strip metadata, including EXIF, when images are processed and served. Community testing has repeatedly confirmed that photos posted to Bluesky come out the other side without GPS or camera metadata. The team framed it explicitly as a privacy-preserving default so people don't accidentally broadcast their location.
There's an ongoing tension in the Bluesky community about this: photographers want some metadata preserved (copyright, alt text, licensing), and there are open feature requests to make preservation opt-in with a clear preview of what would be shared. As of 2026, the default remains strip everything.
So: Bluesky strips by default and has been open about it — but defaults can change, and any preservation feature would alter this.
Why you should still not fully trust either
Both platforms strip EXIF today. So why the caution? Three reasons:
- Behavior changes without announcement. Image pipelines get re-engineered. A feature that preserves metadata for photographers could ship next quarter. The "safe" default you rely on is a policy, not a law.
- Stripping the download isn't the same as privacy from the platform. As with Threads, "other users can't see it" and "the company doesn't have it" are very different guarantees.
- The photo's content can still locate you. Even a perfectly stripped file shows a street sign, a storefront, a skyline. Metadata is only one of the two ways a photo reveals location.
How to check any photo yourself — in 30 seconds
Never take a platform's word for it on a file that matters. Verify:
- Before posting, open your photo in an EXIF viewer. If you see a GPS latitude and longitude, that photo currently carries your location.
- After posting, download your own image back from Threads or Bluesky and run it through the same EXIF viewer. Compare. If the GPS block is gone, the platform stripped it.
- Want to see the location on a map before you decide? A tool that will find where a photo was taken plots the embedded coordinates so you can see exactly what you'd be revealing.
This takes under a minute and turns "I think it's fine" into "I checked."
The safest habit: strip before you upload
The cleanest approach doesn't depend on any platform's behavior: remove the location data yourself before the photo ever leaves your device. Then it doesn't matter whether Threads, Bluesky, or some future app preserves EXIF — there's nothing sensitive left to preserve.
You can remove GPS from a photo in a couple of clicks, keeping the image and dropping only the location. Do that once as a habit and you've closed the metadata risk on every platform at once, present and future.
Bottom line
- Threads strips EXIF/GPS from the downloadable copy (like Instagram) — but Meta keeps your original.
- Bluesky strips EXIF/GPS at the server by default, and has said so openly — but defaults can shift.
- Neither protects you from location clues visible in the photo itself.
- The only guarantee that survives policy changes is stripping the data yourself before you post.
Don't guess. Check the file, and if in doubt, strip it first.
Want to see what your photos are actually carrying? Drop one into our EXIF viewer — it's free, and it takes seconds.