FileMorf
Verifiably local

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.

Try a conversion

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. 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. 2

    Convert a file

    Drop in an image or PDF on any local tool and hit Convert.

  3. 3

    Watch what doesn't happen

    For a tool marked as local, no request carries your file to FileMorf. Code and engine assets may still load from the network before the conversion runs in your tab.

Full transparency

Exactly which tools run where.

Server-backed categories are listed here and disclosed again at the relevant file input. New server workflows must be added to this shared registry.

100% in your browser

Files are not transmitted. Many tools work offline after required engine assets have loaded and remain cached.

Server-backed workflows

These workflows send the necessary input over TLS. Each linked page states its own processor, account requirement, provider, and retention behavior.

Questions

How local processing works.

The technical story, in plain language.

Local conversion removes file-upload wait and can keep working on a flaky connection after required engine assets have loaded. Performance depends on the file, operation, device, browser, and cache state.

Modern browsers can process files with browser APIs, JavaScript libraries, and near-native WebAssembly engines. For tools marked as local, FileMorf sends the required code and engine assets to your browser, where the file is read, converted, and saved without being sent to FileMorf.