Privacy by design, not just by promise.
Most online converters quietly send your photos, videos and documents to a computer you cannot see. Filezaar does the work inside your browser, on your own phone or laptop.
Four promises
Four things you can check for yourself
None of these need you to take our word for it. Open the network panel and look at what actually leaves your device.
1. Files are gone when you close the tab
Your file only exists in the tab while the tab is open. Close it or refresh the page and the working copy is discarded. Nothing is saved on our side, because nothing was ever sent to us.
2. Provable, not promised
Open the Network tab in your browser's developer tools. Process any file. No request carries your file. The only message this site sends about your work is a short same-origin one naming the tool and the number of files it produced; the analytics script named below also loads, but it does not carry your file. Privacy you can measure beats privacy policies.
3. Works completely offline
Once loaded, the tools keep working on trains, flights and spotty hotel connections. Your work never stops because an upload stalled.
4. Free, independent and straight with you
No paywall, no surprise subscription, and no size trap that appears halfway through a job. All tools run 100% free on your device with zero file uploads.
What we store and track
Locally in your browser, in this site's own storage: your theme preference (filezaar-theme); your recently used tools (filezaar-recent-tools); saved tool setups (filezaar-saved-presets, a label and a settings hash, never any file content); a coarse "first seen" month (filezaar-first-seen, a YYYY-MM value) used only to tell a new visit from a returning one; the last known public file count (filezaar-counter-cache) so the stats page can still show a number offline; and a local activity buffer (filezaar-beacon-buffer) holding up to 200 recent events — page views and tool actions — each stamped with a timestamp, a per-page-load session id and that "first seen" month, with page views also recording the page path. That buffer is a record of the pages you visit on this site, kept on your own device. Nothing in this list is sent anywhere today: the site ships with no telemetry endpoint configured, so the buffer is written only to your browser's storage. Switching transmission on would take an endpoint added to the site's own configuration — until then, the code has nowhere to send it.
Analytics
One third-party service runs on this site: Cloudflare Web Analytics. It is cookieless — it sets no cookie, keeps no local storage, and does not fingerprint visitors from their IP address or browser in order to produce its numbers. No other analytics, tag-management or advertising service is loaded on any page, and no advertising or cross-site tracker runs here. Nothing described on this page ever receives your files, your filenames, or anything you type into a tool.
The public file count
The number of files processed is published on the stats page. When a tool finishes, your browser sends one short message: the name of the tool and how many files came out. No filename, no file size, no file content and no identifier of any kind goes with it. Cloudflare, the network that serves this site, may process connection details such as your IP address for security and rate limiting as traffic reaches us.
Third-party code
The code that reads and rewrites your files is open-source and served from this same site: SheetJS for spreadsheets, PDF.js and pdf-lib for documents, libheif for HEIC photos, and a video and audio engine built on WebAssembly. None of it is loaded from another host, and the full licence list sits in our open-source notices.
Questions
Can you see the files I process?
No. Your file is read by your browser and worked on in the same tab, and no code path in the tools sends file data anywhere — the telemetry layer rejects filenames and file contents by name before they can leave. So there is nothing for us to see or keep.
Do you use cookies or trackers?
We do not identify you, we do not sell anything about you, and we do not use analytics for advertising. But we will not claim we keep no record of behaviour: your browser keeps a local buffer of up to 200 recent events — including which pages you were on — on your own device, and that buffer is never transmitted. There is no _ga cookie and no advertising or cross-site tracking cookie on any page; the one analytics service we load (Cloudflare Web Analytics) is cookieless. Block the analytics with any content blocker and every tool still works. Nothing about your files is collected either way.
Do you log or transmit my filenames or file contents?
Never. Your file is read and rewritten inside your browser tab, on your own device. The only message this site sends about your work names the tool and says how many files came out — no filename, no file size and no file content.
What is the “files processed” number?
It is a running tally reported by visitors’ browsers each time a tool finishes. It is not a checked figure — anyone can open developer tools and send a number — so read it as a rough signal, not a certificate. It carries nothing about any file. See the stats page.
How do I remove what is stored?
Clear your browser's site data for this site and it is all gone. There is no account to delete, because there is no account.
Check it the easy way.
Open a tool, turn off your connection, and keep working. That is the whole test.