Small tools that don't upload your files.

Why nothing gets uploaded

The conventional way to build a file converter is to accept an upload, process it on a server, and hand back a download. That was necessary when browsers could not decode an image on their own. It has not been necessary for years — the Canvas API, WebAssembly and the File API can do all of it locally.

Building it that way is better on every axis that matters. It is faster, because a 20 MB photo never crosses the network twice. It works on a plane, because once the page has loaded there is nothing left to fetch. And it removes an entire category of question about what happens to a contract, a passport scan or a medical record after you hand it to someone else's server.

You can verify the claim rather than trusting it: open your browser's Network tab and convert something. The file is not in the list, because there is no endpoint here that would accept it.