Privacy by architecture

We can't see your files.
By design.

MetaStrip is a metadata removal tool built on a simple principle: a privacy tool should be private. Your files are processed entirely in your browser. We never see, store, or transmit them.

0bytes
uploaded to any server
0
accounts required
0
ads, ever
100%
client-side processing
Why MetaStrip exists
Portrait of Lars Holmstrom

MetaStrip is built by Lars Holmstrom — an indie developer and cyber security graduate based in Melbourne, Australia.

The cyber security background is why I care about this problem in the first place. Most people have no idea what's embedded in the files they share every day, and the tools meant to help them either upload your files to someone else's server or look like they were last updated when Ubuntu still shipped with Unity. I wanted something better, so I built it.

I'm a believer in FOSS for privacy tools — keeping big tech out of personal information shouldn't require trusting another company. The whole tool is on GitHub under MIT licence. Audit it, fork it, run it locally, contribute. The code is the proof.

Also a fan of dogs and tacos.

Find me on X
Privacy principles

Not just promises — architectural guarantees.

Your files never leave your device

MetaStrip processes files entirely in your browser using client-side JavaScript. We don't upload, store, transmit, or even see your files. There is no server that receives your data — the processing engine runs locally in your browser tab.

Zero network requests during file processing

No accounts, no tracking, no profiles

We don't ask for your name, email, or any identifying information. There are no accounts, no sign-ups, and no tracking. We don't build user profiles or track individual behavior.

PostHog Analytics — cookieless, Do Not Track respected

No ads, no data selling, ever

MetaStrip is funded by voluntary tips, not advertising. We will never sell data, show ads, or monetize through any mechanism that compromises user privacy. A privacy tool that violates privacy is worthless.

Free forever, supported by community tips via Ko-fi

Verifiably private

Because MetaStrip runs client-side, you can verify our privacy claims yourself. Open your browser's network inspector while using the tool — you'll see zero outbound file transfers. We don't ask you to trust us blindly; we've built the tool so trust isn't required.

Open DevTools → Network tab → process a file → zero outbound requests
Under the hood

The complete data flow.

Verify it yourself with browser DevTools.

1. Your browser

You drag a file into MetaStrip. It's read as an ArrayBuffer entirely within your browser tab. The file never leaves this context — it exists only in local memory.

2. Processing engine

Depending on file type, one of three open-source libraries processes the file. piexifjs strips EXIF from images, pdf-lib clears PDF properties, and JSZip modifies Office XML metadata. All processing happens in JavaScript on your device.

3. Output

A new, clean file is generated in memory. The browser triggers a download of the stripped file. Your original file is never modified, and no data is transmitted anywhere.

No server involved. No API calls. No file uploads. Verify in DevTools.
Open source

Built on trusted, auditable libraries.

pdf-lib

Pure JavaScript PDF manipulation. Reads and clears all standard PDF metadata fields — author, creator, producer, dates, keywords, and custom properties.

View on GitHub →
JSZip

ZIP file reader/writer used to unpack DOCX, XLSX, and PPTX files (which are ZIP archives) and modify their internal XML metadata files directly in the browser.

View on GitHub →
piexifjs

Lightweight EXIF parser that reads and removes EXIF, IPTC, and GPS metadata from JPEG images without quality loss or re-encoding.

View on GitHub →

Questions, feedback, or feature requests?

MetaStrip is built by one person. I read every message.