How It Works
We claim your files never leave your device. We'd rather show you than ask you to believe us — here's the whole mechanism, plus two ways to catch us if we were lying.
Your browser is the server
The usual "online converter" is a courier service: you hand your file over, it rides to a data center, gets converted on hardware you'll never see, and a download link comes back. Whatever was in that file — contracts, medical scans, family photos — made the round trip.
We skipped the courier. We compile the same engines that power desktop software to WebAssembly and ship them to your tab, where they run on your own CPU:
- FFmpeg handles the video, audio and GIF compressors — the same engine studios use
- pdf.js, pdf-lib and mammoth cover PDFs and Word documents
- libarchive unpacks RAR, 7Z and TAR archives
- Our calculators, generators and text tools are a few kilobytes of plain JavaScript — they never had a server to phone
Your file is read into your tab's memory, processed there, and saved straight to your Downloads folder. We never receive a byte of it — we have no upload endpoint to receive it with.
Catch us in the act (you can't)
- Press F12 (or Cmd+Option+I) and open the Network tab.
- Run any conversion on this site.
- Read the traffic: the site fetches its own code and the engine it needs — and sends nothing out. No POSTs, no third-party domains, no beacons.
The airplane-mode test
Our favourite proof needs no DevTools: visit once, convert one file so your browser caches the engine, then switch off your internet entirely and convert another. It still works. A tool that uploads your files can't do that — ours doesn't notice the network is gone.
What this means in practice
- We never see your files, file names, sizes or types
- We run no analytics scripts, no tracking pixels, no ad networks
- There's no account system, so there's no profile of you to leak