Your files never leave this tab.
Most "free online converters" upload your documents to their servers. FileMorf ships the conversion engine to your browser instead — your files are processed on your device, and you can watch the Network tab to prove it.
Prove it yourself
A privacy claim you can check in 30 seconds.
No trust required — your browser's own developer tools show every network request a page makes.
- 1
Open the Network tab
Press F12 (or right-click → Inspect) and select the Network tab. This lists every single request the page makes.
- 2
Convert a file
Drop in an image or PDF on any local tool and hit Convert.
- 3
Watch what doesn't happen
No POST request with your file. No upload progress. The conversion ran in your tab's memory — you can even flip DevTools to "Offline" first and it still works.
Full transparency
Exactly which tools run where.
A handful of heavyweight jobs still need a server. We say so on every page — and here's the complete list.
100% in your browser
Files never transmitted. Works offline once loaded.
Secure server jobs
TLS in transit, isolated processing, automatic deletion after the download window, passwords scrubbed after use.
Questions
How local processing works.
The technical story, in plain language.
Bonus of doing it this way: conversions start instantly (no upload wait), keep working on flaky connections, and cost us almost nothing to run — which is why the local tools are free without artificial daily limits.
Modern browsers can run near-native code through WebAssembly. FileMorf ships the actual conversion engines — image codecs, a PDF library, even a full audio engine — to your browser, where they process your file in the tab's own memory. The file is read locally, converted locally, and saved locally.
Open your browser's DevTools (F12), switch to the Network tab, then convert a file. You'll see the page load its code and assets — but no request carrying your file ever leaves. You can even switch DevTools to 'Offline' after the page loads and most tools keep working.
A few jobs need engines that don't fit in a browser yet: OCR at quality, AES-256 PDF encryption, PDF→PowerPoint reconstruction, and very large files. Those run in isolated server jobs over TLS, files are deleted automatically after the download window, and anything sensitive (like passwords) is scrubbed from job records immediately after processing. Every tool page tells you plainly which kind it is.
Usually the opposite. There's no upload time and no queue — a 20MB photo converts in the time it would take just to upload it elsewhere. Very large videos are the exception, which is why big transcodes can optionally run on our servers.
Largely, yes. Once a tool page has loaded, the conversion engines are cached by your browser — image conversion, PDF tools, and the editor keep working with no connection at all.