Do not trust us. Check.
Every online file tool claims to respect your privacy. Here is how to verify ours in about thirty seconds.
The standard promise from an online converter is some version of "your files are deleted from our servers after one hour." That may well be true. The problem is that it is unfalsifiable — the file did go to their server, and what happened next is entirely a matter of trust.
Filery makes a different claim, and it is one you can test: your file is never transmitted at all. Here is how to confirm it.
The 30-second check
- Open your browser's developer tools. Press F12, or Ctrl+Shift+I on Windows and Linux, or Cmd+Option+I on a Mac.
- Switch to the Network tab. Click the clear button so you are starting from an empty list.
- Now use any tool on this site. Pick a file, set your options, run it, download the result.
- Look at the list. You will see the page's own assets — HTML, CSS, JavaScript, and for some tools a one-time WebAssembly engine download. What you will not see is a request carrying your file. Sort by size if you like: nothing outbound will be anywhere near the size of what you just processed.
For an even stricter test: load a tool page, then disconnect from the internet entirely — turn off Wi-Fi, unplug the cable — and use the tool. It will keep working. That is not something a service which needs to reach a server can do.
Why it works this way
Modern browsers can run compiled code at close to native speed through WebAssembly. The libraries that power professional media and document software — FFmpeg, MuPDF's permissive cousins, the reference JPEG and AVIF encoders, Tesseract for OCR — have all been compiled to run in that environment.
So there is no longer a technical reason to send a file to a server to compress a PDF or trim a video. The processing can happen on the machine that already has the file. We read it into browser memory, your own processor does the work, and the result is written back to your downloads folder.
What this rules out
- Data retention. We cannot retain what we never receive.
- Breaches. There is no bucket of user files to leak, because there is no bucket.
- Subpoenas and requests. We have nothing to hand over.
- Training data. Your documents cannot end up in anyone's dataset.
- Third-party processors. There is no data-processing relationship to disclose, because we do not process your data.
Where we are honest about the limits
Two things to be clear about, because a privacy claim with an asterisk hidden in the footer is worse than no claim at all.
Some tools download an engine. Video and OCR and the on-device AI tools need a WebAssembly module or a model file, which is fetched from a public CDN the first time you use them. That is a download to you, not an upload from you — it carries no information about your file. It is cached afterwards, which is what makes offline use possible. If you would rather have zero third-party requests, the project can be configured to serve those assets from your own domain instead.
We use basic analytics if enabled. Page views and which tools get used, so we know what to build next. Never file names, never file contents, never anything derived from what you processed.
Compare that to the alternatives
| Service | Where your file goes | Free limit |
|---|---|---|
| Smallpdf | Their servers, deleted after 1 hour | 2 tasks per day |
| iLovePDF | Their servers, deleted after 1–24 hours | Ad-supported, size limits |
| CloudConvert | Their servers | 10 per day, 1 GB max |
| Convertio | Their servers | 10 per day, 1 GB max |
| Kapwing / VEED | Their servers | Watermark on every export |
| Filery | Nowhere. It stays on your device. | None |
Those services are not being dishonest. They cap the free tier because every conversion genuinely costs them CPU time and bandwidth, and that cost has to be recovered somewhere. Our cost per conversion is zero, because the work runs on your hardware. That is the whole reason we can offer 96 tools with no limits and mean it.