Are My Files Private When I Use MetaStrip?

Updated

Yes. MetaStrip processes every file entirely in your browser using JavaScript. There is no upload, no server, and no temporary cache, so the file you drop in stays on your device from start to finish. This applies to all supported formats — photos, videos, PDFs, and Office documents — and to batch runs of up to 100 files at once.

What "in your browser" actually means

When you drop a file onto the page, MetaStrip reads its metadata locally using its own parsers and libraries such as pdf-lib. It shows you exactly what is embedded, then writes a clean copy back out to your device. The original file is never transmitted anywhere.

The practical consequence: privacy does not depend on trusting a company's promise about its servers. There is no server in the path to trust.

How to verify it yourself

The site invites you to check the claim directly rather than take it on faith:

  1. Open your browser's DevTools (usually F12, or right-click → Inspect).
  2. Switch to the Network tab.
  3. Process a file in MetaStrip as you normally would.
  4. Watch the request list. No request carrying your file should appear.

If the tool were uploading your files, you would see outbound requests during processing. Seeing none is the confirmation.

A second check: the source code

MetaStrip is open source under the MIT license, with the code published on GitHub. If you want to go beyond network observation, you can read the parsing and stripping logic itself to confirm what runs on your machine.

Where the privacy claim matters most

The in-browser design is most relevant in situations where a file leaving your device is itself the risk:

  • Contracts and documents sent to opposing counsel — author names and tracked changes stay off someone else's server.
  • Photos posted to forums or marketplaces — GPS coordinates and device serial numbers are removed before the file is shared.
  • AI-assisted work submitted to clients — C2PA content credentials and AI generation tags are stripped locally.
  • Journalism submissions and anonymous publishing — nothing about the file passes through a third party on the way to being cleaned.

Limits worth knowing

  • Privacy of processing is not the same as anonymity of use. The tool keeps your files off its servers; it does not control what you do with the cleaned file afterward.
  • Offline use is supported, which is consistent with local processing — but confirm the page has loaded fully before going offline.
  • Pricing and account requirements are listed on the site's Pricing page; check there for current terms rather than assuming the tool is free or login-free for your use case.

For a quick decision: if your concern is "does this file get uploaded somewhere," the answer is no, and you can confirm it in under a minute with DevTools.