How browser tools work without ever uploading your file

WebAssembly lets browsers run compiled code at close to native speed. That made it practical to port the same libraries servers had been using — image codecs, PDF engines, video transcoders, even entire database engines — directly into a web page.

Alongside it, the File System Access API and Canvas gave pages a way to read and write local files properly, and WebRTC gave two browsers a way to send data to each other without a server holding it in the middle. Together these cover most of what a file-processing tool needs.

The obvious gain is privacy: a scanned passport, a bank statement, a medical report or an unreleased document processed on-device has not been transmitted anywhere, so there is no retention policy to read and no breach that can involve it.

The less obvious gains are speed and size. There is no upload wait and no download wait, so a large file is often faster locally than remotely even on modest hardware. And because the operator is not paying for bandwidth or compute, on-device tools tend to have far more generous limits — frequently none at all.

Anything that needs a large model, a licensed database or a lot of sustained compute still belongs on a server. High-quality machine translation, most video transcoding at scale, and anything that has to check your input against a dataset the tool cannot ship to you are all genuinely server-side problems.

Battery and memory are real constraints too. A phone will run out of memory on a file a laptop handles comfortably, which is why some tools offer on-device processing on desktop and fall back to upload on mobile — worth knowing, because the privacy property silently changes with the device.

Load the page, turn off your network connection, then use the tool. If it completes, nothing was uploaded — there was nowhere for the file to go. This is the whole test, it takes ten seconds, and it cannot be faked.

For a more precise view, open the network panel in developer tools before you drop the file in and watch the outbound request sizes. A tool doing the work locally sends nothing larger than a few kilobytes of telemetry.