- Home
- How It Works
- How It Works
How tools can work without ever taking your files
No trick and no marketing. Here is what actually happens when you use a tool here, and three ways to check it for yourself.
- Runs on your device
- No sign up
- Ready in seconds
The usual way, and this way
An ordinary online converter is a website with a machine behind it. You hand over your file, it travels to that machine, waits its turn behind everybody else, gets processed, and a download link comes back. Most of the time you spend is spent on the travelling and the waiting rather than the work.
Here the machine comes to you instead. The page downloads a small piece of software, that software runs inside your own browser tab, and your file is opened where it already sits.
The difference is not a clever trick. It is simply that browsers became capable enough to do this work about a decade ago, and most sites never changed their approach.
What happens when you open a tool
Three steps, and only one of them involves the network at all.
The page loads
Ordinary HTML, styling and a small script, the same as any web page. Nothing has happened to your files yet because you have not chosen any.
network usedThe tool downloads itself
A small open source library arrives, the piece that knows how to read a PDF or decode an image. Between about 70 KB and a few megabytes depending on the job, and your browser keeps it for next time.
network used onceYour file is opened where it is
You choose a file, the browser hands the page permission to read it, and the work happens in the tab. The result is written on your machine and offered to you as a download.
no network at allWhat makes it possible
Four browser features, none of them new or experimental. Every current browser has all four.
The File API
Lets a page read a file you have chosen without sending it anywhere. This is the foundation. Choosing a file grants read access to that tab, and nothing more.
WebAssembly
Runs compiled code in the browser at close to native speed. It is what makes serious PDF and media work practical in a tab rather than merely theoretically possible.
Canvas
Decodes, redraws and re-encodes pictures. Every resize, conversion and compression on the site goes through it, which is also why formats a browser cannot display will not open.
Web Audio
Decodes sound into raw samples the page can work with, which is how audio gets pulled out of a video and encoded as an MP3 without a server touching it.
Three ways to check for yourself
A website claiming it does not upload your files is just a claim. These take a minute each and none of them can be faked by the page.
Watch the network
Press F12, or right click and choose Inspect, then open the Network tab. Use any tool on the site. You will see the library come down and you will see nothing go up. Look for anything with your file size next to it: there will not be one.
Pull the plug
Load a tool page, then switch your wifi off entirely. Now use it. Most of these keep working, which would be impossible if a server were doing the job. This is the simplest test and it needs no technical knowledge at all.
Read the source
Right click and choose View Source, or open the Sources tab in the developer tools. The code for each tool is plain and readable rather than hidden behind a build system. The libraries it uses are named openly and you can look them up.
What this approach cannot do
Working locally has real costs. Here they are, so nothing comes as a surprise halfway through a job.
Your device is the ceiling
All the work happens in memory on your own machine, so a laptop handles far more than a phone. Where a tool has a sensible cap it tells you the number and the reason rather than failing quietly.
Some formats will not open
A browser can only read what it already understands. MKV, AVI, WMV and HEIC have never had decoders in browsers, so no page can open them. Converting to MP4 or JPEG first solves it.
A few jobs are slower
Trimming video takes as long as the clip, because the instant method needs a video engine whose licence does not suit a commercial site. We say so on that tool rather than letting you discover it.
The first run downloads something
A library, a language file or a speech model, depending on the tool. It happens once and is then cached, which is also why these keep working offline afterwards.
See it for yourself
Pick any tool and try the offline test on it. Five sets, all built the same way.
Questions about these tools
The technical questions people ask once they understand the idea.
The tool itself. Each page pulls in a small open source library that knows how to read a PDF, decode an image or encode audio, and that library then runs inside your tab. It is the same idea as a website loading a font or a chart script, only these do heavier work. The libraries range from about 70 KB to a few megabytes, your browser caches them after the first visit, and none of them send anything back.
For most jobs it is faster, because the slow part of an online converter was never the conversion. It was uploading a large file and then waiting in a queue behind everybody else. Removing both of those usually beats a faster machine at the far end. The exception is genuinely heavy work on a weak device, where a server with proper hardware would win if you were willing to send your file to it.
Four, mostly. The File API lets a page read a file you choose without sending it anywhere. Canvas decodes and redraws images. Web Audio decodes sound. And WebAssembly runs compiled code at close to native speed, which is what makes serious PDF and media work practical in a tab. None of these are new or experimental, and every current browser has them.
Most of them, yes, once the page and its library have loaded. Switch your connection off and try it. That is also the simplest proof that no server is involved, because a tool that needed one would stop working immediately.
Three worth knowing. Your device does the work, so its memory sets the ceiling and a phone manages less than a laptop. Browsers can only open the formats they already understand, which is why MKV, AVI and HEIC will not load. And a few jobs, such as trimming video, have to be done in a slower way because the fast method needs a licence that does not suit this site. Every tool with one of these limits says so on its own page.
A site could, which is why we would rather you checked than trusted us. Open your browser developer tools, watch the network panel while a tool runs, and you will see the library arrive and nothing leave. Switch your connection off and watch the tool keep working. Neither of those can be faked by the page.