How we can't see your files.
Most converters ask you to trust them. This one asks you to test it. Your files are converted by code running in your own browser, so there is no server that could keep, read or leak them. Here are three ways to prove that to yourself in about a minute.
Convert with the internet off.
This is the whole promise in one test. Convert a photo once so your browser saves the app, then cut the connection and do it again. A tool that needs to upload your file would stop working. This one doesn't.
- 1 Add a photo below and let it convert once, so your browser saves the app.
- 2 Switch on airplane mode, or just turn off Wi-Fi. Nothing to sign out of.
- 3 Convert again. It still works, because nothing was ever being sent.
The converter shows a small "You're offline" note when the connection drops. That note is the good news: it means the work is happening here, on your device, exactly as it does online.
Watch the Network tab stay empty.
Your browser can show you every request a page makes. Open that panel, convert a file, and watch: no upload appears, because none happens.
- 1 Open developer tools. On Chrome, Edge or Firefox press F12, or Command+Option+I on a Mac. On Safari, enable the Develop menu first, then choose Show Web Inspector.
- 2 Switch to the Network tab and leave it open. It records every byte that leaves or enters the page.
- 3 Convert a file. You'll see the page's own assets load once, and after that nothing that carries your file. No POST, no upload, no request with your photo in it.
Your browser blocks uploads for us.
We don't just choose not to upload your files. We ask the browser to forbid it. Every page here is served with a Content Security Policy, a rule the browser enforces on our behalf. The part that matters is short:
connect-src 'self'connect-src controls where a page is allowed to send data. Setting it to 'self' means the page can only talk to its own origin: no other server, anywhere, can receive anything. The one exception is the cookieless analytics endpoint that counts page views and never sees a file. If our code ever tried to send your photo somewhere, the browser would refuse the request. It's a lock we can't quietly open.
You can verify the headers on a live page with an independent scanner like securityheaders.com, which reads the same policy your browser does.
The questions worth asking.
The code is closed. Why should I trust you?
Because you don't have to. Trust the behavior, which you can check yourself. Turn off Wi-Fi and the converter keeps working, so there is clearly no server involved. Open the Network tab and it stays empty, so nothing is being sent. A closed engine can't change what your browser allows a web page to do, and the page is asking for nothing. The proof is the same whether the source is open or not.
Does anything at all get sent when I convert?
No. Not the file, not part of it, not the filename, not a hash of it. The page loads once, then your device does all the work. After the first visit it doesn't even need to load again: the app is saved for offline use.
You mention analytics. Isn't that tracking?
It's Cloudflare Web Analytics, which is cookieless. It counts anonymous page views so we know which tools people use. It never sees your files and never builds a profile of you. Block it and the converter behaves in exactly the same way.
Does offline really work, or is that marketing?
It really works. Open this page once with a connection, then switch to airplane mode and convert. The airplane-mode test above is the honest version of the claim: if it runs with the network off, the files were never leaving your device.
Your files never leave your device.