TL;DR: Almost certainly yes for public posts, but Meta has never published a Threads-specific statement confirming it. Threads runs on Instagram's account system and media infrastructure — the same login, the same blocklists, and by every indication the same image-processing pipeline that recompresses uploads and discards EXIF data, including GPS coordinates, camera make/model and timestamps, from the copy other users can download. That inference comes from Threads' documented architecture, not from a Meta engineering blog that spells it out field by field, which matters because we can't verify the same holds for photos sent through Threads' newer direct-message feature (mobile since July 2025, web since May 2026) — DMs on other platforms don't always get the same recompression treatment as public feed posts. Meta's own Threads Supplemental Privacy Policy describes what the company collects and uses, not what it strips from files before other users see them. As with every platform in this series, the dependable move is to strip metadata yourself before the file leaves your device, regardless of which posting surface you use.
Does Threads remove photo metadata?
Almost certainly, for anything posted publicly — but "almost certainly" is doing real work in that sentence, and it's worth being honest about why. Meta has not published a Threads-specific document describing EXIF removal, GPS stripping, or any metadata-handling behavior unique to the app. The Threads Supplemental Privacy Policy covers what data Meta collects and how it's used across the product, not what happens to the bytes inside an uploaded JPEG.
What we do know, from Meta's own description of the app at launch, is that Threads was built by the Instagram team as an extension of an Instagram account rather than a separate product with its own infrastructure. You don't create a Threads-specific account — you use your Instagram identity, your Instagram followers can be imported, your Instagram block list carries over automatically, and posts can be cross-shared directly to Instagram Stories. That level of integration is a strong signal that media uploads flow through Meta's existing image pipeline rather than a parallel system built from scratch for Threads. We've already documented in Does Instagram Actually Remove EXIF Data When You Upload? that Instagram re-encodes and resizes every uploaded photo, and that re-encoding step is what discards the original EXIF block. If Threads shares that pipeline — and everything about its architecture suggests it does — public Threads photos should lose the same fields for the same reason.
The gap in that logic is the word "should." We are reasoning from architecture, not quoting a policy that says "Threads strips EXIF." Treat the conclusion as well-supported, not proven by primary source, and act accordingly: don't rely on it for anything sensitive.
How photos actually move through Threads
When you attach a photo to a Threads post, the app uploads the file to Meta's servers, generates the resized versions needed for feed display, thumbnails and link previews, and serves those processed versions to anyone who views the post. That processing step — resizing, recompressing to Meta's standard JPEG parameters, generating multiple resolutions for different device sizes — is also the step that incidentally drops the original EXIF block, XMP packet and embedded thumbnail. It's the same mechanism Instagram uses, not a special Threads feature, which is exactly why we'd expect the same outcome without Meta needing to say so explicitly.
That mechanism has a blind spot common to every platform we've covered in this series: the original file, with full metadata, still reaches Meta's servers before any processing happens. Nothing about "the public copy loses EXIF" tells you what the company retains internally, uses for content moderation, or associates with your account for ranking and ad-targeting purposes. The public-facing strip is a byproduct of image processing, not a privacy feature designed with you in mind.
Photo by Bastian Riccardi on Pexels
What about Threads direct messages?
This is the part of the picture Meta hasn't addressed at all, and it's newer than most people realize. Threads shipped direct messaging on mobile in July 2025 and extended it to the web with a dedicated Messages tab in May 2026, adding one-on-one and group chats plus message requests and conversation search. That's a meaningfully different code path than the public feed — DMs are a private file hand-off between two accounts, not content served to an open audience — and on other platforms we've covered, the DM path doesn't always get the same treatment as the public post path.
We saw this exact split with Microsoft Teams, where direct uploads get scrubbed but cloud-storage links hand out the untouched original, and it's a pattern worth watching on Threads too as its messaging feature matures. Until Meta documents how media is processed inside Threads DMs specifically, don't assume a photo sent privately gets the same recompression a public post does. If anything, treat DMs as the less trustworthy path, since Meta's incentive to standardize image sizes for a public feed doesn't apply the same way to a one-off private file transfer.
How Threads compares with Instagram and X
Threads sits closest to Instagram by design, and the comparison mostly confirms what you'd expect: both apps share the same account, the same media backend, and — as far as public evidence supports — the same EXIF-stripping-by-recompression behavior for feed content. The difference is documentation. Instagram has been public about its image processing for over a decade of third-party analysis and its own help-center content; Threads inherits the behavior but not, so far, an explicit public statement about it.
X (formerly Twitter) takes a comparable approach from a different codebase — we detailed in What Metadata Does X (Twitter) Strip from Photos? that X transcodes every upload server-side and the bulk of EXIF data doesn't survive to the downloadable copy, though the stripping happens after your original file reaches X's servers, not before. Facebook, Threads' sister app under the same parent company, behaves similarly — we covered the specifics in What Metadata Does Facebook Keep When You Upload a Photo?. Across all three, the pattern holds: public feed images lose EXIF in transit, but the platform's own copy is untouched, and none of it is a substitute for cleaning the file yourself.
What metadata Threads generates on its own
Independent of what happens to a photo's EXIF block, using Threads generates its own metadata trail. Every post carries a timestamp, and depending on your settings, an optional location tag you add manually — which is fully public the moment you attach it, camera GPS data or not. Your account activity, likes, reposts, and the accounts you interact with feed into Meta's broader advertising and ranking systems, the same systems that power Instagram and Facebook. Message metadata — who you messaged, when, and how often — is generated the moment Threads DMs are used, regardless of what's inside the files exchanged. None of this is unique to Threads; it's standard for any Meta product, and it's worth remembering that "the photo itself is clean" doesn't mean your activity on the platform isn't building a detailed profile through other means. The EFF's overview of why metadata matters is a useful primer on how activity metadata can reveal as much as file metadata, sometimes more.
Photo by MART PRODUCTION on Pexels
Cross-posting: the edge case that resets the rules
Threads makes it easy to share a post directly to Instagram Stories, and Meta's broader ecosystem encourages cross-posting between its apps. Each time an image crosses from one surface to another — Threads feed to Instagram Story, Threads DM to a saved photo, a screenshot of either — it may go through a fresh round of processing with its own behavior. A screenshot, in particular, strips nothing of the original's EXIF because it isn't the original file at all; it's a brand-new image carrying the screenshotting device's own metadata instead. Don't assume that because a photo "went through Threads once," every subsequent copy of it has been treated the same way. Each hop is a new event.
The dependable fix: strip before you post
Because Threads' public-post behavior is inferred rather than documented, and its DM behavior is undocumented entirely, the only path you can verify with certainty is the one before the file leaves your device. Run the photo or video through Metadata Cleaner first — the tool rewrites images, video and audio without their EXIF blocks, GPS IFDs, XMP and IPTC packets, PNG text chunks and embedded thumbnails, and it runs entirely in your browser, so the file is never uploaded anywhere to be cleaned. Post the clean copy to your public Threads feed, send the clean copy in a Threads DM, and cross-post the clean copy to Instagram. Once nothing sensitive is in the file, it doesn't matter whether Meta's pipeline would have caught it or not — there's nothing left to catch.
Conclusion
Threads almost certainly strips EXIF and GPS data from photos posted publicly, because it shares Instagram's account system and, by every available signal, Instagram's media-processing pipeline — but Meta has never confirmed this in writing for Threads specifically, and its year-old direct-messaging feature is a documentation blank spot with no evidence either way. The safest assumption is that public posts behave like Instagram's and DMs are unproven. Rather than betting on inferred behavior for anything that matters, strip the file yourself before it reaches any Meta app — public feed, DM, or cross-post alike.