Does Instagram strip your metadata? Check first.

Drop a photo to see the GPS location, date, and device it carries, then read a verified table of what Instagram, Facebook, X, WhatsApp, TikTok, Telegram, Discord and more do with that metadata on upload. Nothing uploads, no signup.

  • 100% browser
  • Files never leave your device
  • No signup, no caps
  • GDPR & CCPA friendly
Social Media Metadata Checker

Drop a photo to see what it reveals

JPG, PNG, HEIC, or TIFF. We read the metadata in your browser. The file never leaves your device.

What each platform does on upload

Last verified June 2026. "Removes" means others cannot read it from the downloaded file. Platforms may still read and store it server-side.

PlatformEXIF / GPSWhat happens
InstagramRemovesRe-encodes every upload. EXIF and GPS are gone from the public file. Meta still reads and stores the original server-side.
FacebookRemovesHas stripped EXIF since 2012. GPS is removed from the downloadable file, but Meta reads it on upload.
X (Twitter)RemovesStrips all EXIF on upload. Images sent in DMs or via some third-party API clients can retain metadata.
TikTokRemovesRemoves EXIF from photo and video uploads as part of its transcoding pipeline.
SnapchatRemovesStrips EXIF from everything shared: Snaps, Stories, Chat, and Spotlight.
LinkedInRemovesRe-processes uploaded images and strips EXIF. Profile and post images use different pipelines, so results can vary.
RedditRemovesImages hosted on i.redd.it are re-encoded, which removes EXIF and GPS.
SignalRemovesPrivacy-first by default. Strips all EXIF including GPS before the image is sent.
WhatsAppDependsSent as a Photo: strips EXIF and GPS. Sent as a Document (to keep quality): preserves 100% of the metadata.
TelegramDependsSent as a Photo (compressed): strips EXIF and GPS. Sent as a File: preserves the original metadata completely.
DiscordPartialStrips EXIF from JPEG uploads in most cases, but PNG files can still carry metadata. Inconsistent across upload methods.
iMessageKeepsSends the full original file. The recipient gets your EXIF and exact GPS. Apple does not strip photo metadata.
Google PhotosKeepsPreserves all metadata in storage and on download or share, including GPS, timestamps, and camera info.
FlickrKeepsPreserves EXIF on purpose for photographers and can display it. Privacy settings control who can see it.

See what leaks, then decide.

A browser-side metadata reader plus a verified, dated table of how every major platform handles EXIF and GPS on upload. No upload, no signup.

See what your photo reveals

GPS location, date taken, device, and total tag count, read from your own file in the browser.

Verified platform table

What Instagram, Facebook, X, WhatsApp, TikTok, Telegram, Discord and more do with metadata on upload. Checked June 2026.

Location made real

If the photo has GPS, the tool shows the coordinates and a map link, so you can see exactly what would leak.

One-click cleanup path

Found something? Jump straight to the EXIF Remover and strip it before you share.

Works with HEIC

Reads iPhone HEIC, JPEG, PNG, and TIFF. The files most likely to carry GPS.

No upload, no signup

Everything runs in your browser. The file never leaves your device. No accounts, no logging.

Common questions about social media and EXIF.

Does Instagram strip EXIF metadata?
Yes. Instagram re-encodes every uploaded photo, so the file other people can download has no EXIF and no GPS. Important caveat: Meta still reads and stores the original metadata on its own servers before stripping it from the public file, and uses it internally. So other users cannot see your location, but Instagram can.
Which platforms remove EXIF and which keep it?
Most social feeds strip it: Instagram, Facebook, X (Twitter), TikTok, Snapchat, LinkedIn, Reddit, and Signal all remove EXIF from the downloadable file. WhatsApp and Telegram depend on how you send (Photo strips, Document or File keeps). Discord is partial (strips JPEG, can keep PNG). iMessage, Google Photos, and Flickr keep your metadata, including GPS. See the full table on this page.
How does this checker work?
Drop a photo and the tool reads its metadata in your browser using the same parser a forensic viewer would. It shows whether the file carries a GPS location, the date taken, the device, and the total tag count, then compares what each platform would do with it. Nothing uploads.
Does my photo upload anywhere?
No. The metadata is read entirely on your device. The file is never sent to a server, never logged, and never stored. Close the tab and it is gone.
If platforms strip EXIF, why should I care?
Three reasons. First, the platform still reads your location even if it strips it from the public file. Second, the keepers (iMessage, Google Photos, Flickr) and the Document or File send modes do expose your GPS. Third, if you share the original by email or cloud link, it carries everything. Removing metadata yourself before sharing is the only way to be sure.
How do I remove the metadata before posting?
Use our EXIF Remover. It strips every tag in your browser and gives you a clean copy to upload anywhere, so you do not have to trust each platform to do it for you.
Is the platform data accurate and current?
The table was verified in June 2026 against platform help centers and independent upload tests. Platform behavior changes, so treat it as current best knowledge and re-check for anything critical. WhatsApp, Telegram, and Discord in particular depend on how you send the file.
Can I check iPhone HEIC photos?
Yes. The parser reads HEIC, JPEG, PNG, and TIFF directly. iPhone photos often carry GPS and a precise timestamp, so they are exactly the files worth checking before you post.

Want the location to survive every strip?

Platforms strip the EXIF GPS, so a shared photo often loses its place and time. The iOS app does the opposite: it renders the date, GPS, and address onto the visible image at the shutter, so the context stays readable even after Instagram re-encodes the file.

Download on theApp Store
iOS 15.6+ · iPhone, iPad, Mac & Vision Pro
  • Visible date, time, GPS, and address burned into the image
  • Survives upload, re-encode, and screenshot
  • Atomic (network-synced) timestamps
  • JPEG output ready to share