What EXIF Data Does Twitter/X Store or Strip?

Stored, Stripped, or Still on Your Phone

Almost every argument about X and metadata comes from mixing up three different copies of the same photo. They contain different things, and only one of them is public.

So "does X store your EXIF data" has two honest answers. It does not store it in anything the public can reach. It certainly received it. The difference matters if your threat model includes anyone other than a random person saving your picture.

What X Keeps vs. Strips, Field by Field

The bottom two rows are where people get caught out. EXIF stripping is thorough and it is also narrow: it cleans the file and leaves everything you attached around the file completely intact. A post with no photo metadata at all can still say where you were, because you wrote it in the alt text.

How Twitter's Metadata Policy Got Here

The stripping is old, but it was not always there, and the pieces around it have moved more than the stripping itself:

• Before 2011, Twitter did not host photos at all. Images went through third-party services — TwitPic, yfrog, and others — and each one made its own call about metadata. Several passed EXIF through untouched, which is why archived photos from that era can still carry GPS today. If you are examining an old link rather than a modern post, check the file rather than assuming.
• Native photo hosting arrived in 2011, and with it a media pipeline that re-encodes uploads and serves them from Twitter's own image CDN. Re-encoding is what discards the EXIF block; the privacy result is a side effect of a bandwidth decision, which is worth remembering when you rely on it.
• Per-post location tagging was a separate feature and always has been. It was opt-in, it was visible on the post, and Twitter narrowed precise location tagging years before the rebrand. It has never been connected to your photo's EXIF — a post can carry a place label on a photo with no metadata, or carry no label on a photo that reached X with coordinates in it.
• The images kept getting bigger. Successive changes raised the resolution X serves, and higher-quality upload options have come and gone with subscription tiers. This does not affect EXIF, but it does affect what a reader can see: street signs, house numbers, and reflections that were unreadable in a 2013 render can be legible now.

What Changed After the Rebrand to X

Twitter became X in 2023 and the primary domain moved to x.com. For metadata specifically, the rebrand was cosmetic:

Treat "X strips EXIF" as an observation you can re-run in two minutes, not a guarantee anybody made you. Pipelines change without announcement, and a habit built on one is only as good as the last time you tested it.

How to Check if GPS Data Survived Your Upload

This is the test that answers the question for your own photo, on today's pipeline, without taking anyone's word for it:

1. Establish a baseline. Open the original photo — the one in your camera roll, not a screenshot — in our EXIF viewer and confirm you can see GPSLatitude / GPSLongitude on the map. If there is no GPS to begin with, the test proves nothing.
2. Post it somewhere you control. A protected account works, or post publicly and delete it straight after. Remember that the upload has already happened either way — deleting the post does not un-send the file.
3. Save the published image back down.Right-click and "Save image as…" on desktop, or long-press and save on mobile. This is the copy every other user gets.
4. Test the largest render, not a preview. Copy the image address, and change the name= parameter at the end of the URL to name=orig. That fetches the biggest version X will hand anyone — so a clean result cannot be dismissed as "you only checked the thumbnail."
5. Run both saved files through the viewer. On a properly stripped image there is no GPS block, no Make or Model, and no DateTimeOriginal. Pixel dimensions and color space still show up — those are properties of the image itself, not the EXIF block, and their presence does not mean the stripping failed.
6. If GPS is still there, check which file you opened. Nearly always it is the original from your own camera roll, or a copy somebody sent you as a file attachment rather than one downloaded from a post. A file sent as an attachment is the untouched original, not X's copy.

The viewer parses files locally in your browser, so you can run this on a photo containing your real home coordinates without uploading it to us or anyone else. And be clear about what a clean result proves: the published image is clean. It says nothing about what X received, because that upload already happened in step two.

Can You See What X Holds From Past Uploads?

Partly. X lets you request an archive of your data from the account settings, and it includes the media from your posts. Download it and run a few of those files through the EXIF viewer — it will tell you what the archive returned, which is worth knowing.

What it will not tell you is what X derived from your originals on the way in, how long anything is retained, or whether the stripped copy is the only one kept. An export shows what a company chooses to give back. Nobody can determine the rest from the outside, and a page that gives you a confident number for it is guessing. That uncertainty is the argument for the next section rather than a reason to shrug: what you never upload cannot be retained.

Geotagging Risks for Journalists and Activists

For most people, EXIF stripping closes the case: no stranger can pull coordinates out of your photo. If you are reporting from a protest, documenting abuses, or posting from somewhere you are not supposed to be, the residual risks are the ones that matter, and none of them are solved by the platform:

• The pixels geolocate you, not the metadata. This is how open-source investigators actually place photos: signage, architecture, vehicle plates, shop fronts, the shape of a skyline, shadow angles against a known time. Stripping EXIF does nothing here, and the higher-resolution images X now serves make it easier, not harder.
• Timing is a location signal. A post published minutes after the shutter fired puts you at the scene at a public, precise, permanently recorded time — attached to your handle. The capture timestamp was redundant.
• Your own labels leak more than EXIF would.A place tag or an alt-text description like "from my window on Rue X" is plain text anyone can read, no forensic tooling required. It is also entirely under your control.
• The original file outlives the post. You uploaded it with coordinates in it, and deleting the post does not recall it. Where sources or safety are involved, plan for the upload itself, not for the published result.
• Cross-posting breaks the assumption. The same photo sent to a colleague as an email attachment, a chat document, or a cloud-drive link travels with full EXIF — those paths strip nothing. One habit that survives every platform is cleaning the file, not remembering which service is safe.
• Faces and identifying detail are not metadata problems. Blur or crop before posting. No metadata tool addresses who is recognizable in the frame, and for people photographed at a protest that is usually the higher-stakes exposure.

The practical version: strip the file first, post the clean copy, and treat everything outside the file — your caption, your alt text, your posting time, and what is visible in the frame — as the part that actually needs a decision. Our photo privacy guide covers the platform-by-platform picture, including the services that strip nothing at all, and the photo privacy checklist is the short version to run before a sensitive post.

Keep the Metadata Out of the Upload

Because X strips on the way out and not on the way in, the only way to keep a field away from it is to remove the field before you post:

• Strip the file in your browser. Our metadata remover rewrites the photo locally and gives you back a clean copy to post. Nothing is uploaded to us, and X gets an image with no EXIF to strip.
• Turn geotagging off at the source.On iPhone: Settings → Privacy & Security → Location Services → Camera → Never. On Android, disable location tags in the camera app's own settings. Photos taken afterwards never have coordinates to remove — details in our iPhone and Android guides.
• Check before posting, not after. Opening a photo in the viewer takes seconds and is the only step that tells you what is actually in this file rather than what is usually in files like it.
• Use a pre-share routine. Our strip metadata before sharing guide is the checklist, and it applies wherever the photo is headed next.

A file you cleaned yourself is safe on every platform at once — on the day the pipeline changes, and on the day you tap the wrong attach button.

Related Guides

Frequently Asked Questions