Why browser-based file tools are safer than upload sites (and how to tell which you're using)
Most 'free online' converters upload your file to a server and keep it for a while. What that means for ID proofs, contracts and client photos, how in-browser processing works instead, the two-second test to check any tool, and what the trade-offs are.
· 3 min read · 1.1K views · by the Cortex Digital Hub team
Every Cortex image, PDF and video tool runs on your device. Unplug the network after the page loads and it still works.
Try an in-browser tool → Opens Image Compressor · runs in your browser
Search for "compress PDF" or "HEIC to JPG" and the first page is full of tools that are free, fast and quietly upload your file to a server. That is not a scandal; it is just how most of them are built. But it matters more than people assume for the files they actually convert, which are ID proofs, salary slips, contracts, client photos and unreleased product shots.
What "upload" actually means
When you drop a file onto a typical converter, the browser sends it to the company's server, the server does the work, and you download the result. In between, the file exists on a machine you do not control, for a period set by the company's policy (commonly "deleted after 1–24 hours", occasionally longer), protected by their security, visible to their staff and to anyone who breaches them. The privacy policy usually permits more than you would expect, including using files to improve the service.
For a holiday photo, none of that matters. For a passport scan being compressed to 50 KB for a visa form, it is exactly the file you would least like to be in a stranger's temporary folder.
How in-browser processing works
Modern browsers can do real work: decode images and video, run PDF engines, even run machine-learning models, using the computer's own CPU and GPU through JavaScript and WebAssembly. A tool built this way sends you the code once, as part of the page, and then everything happens on your device. The file is read from your disk, processed in memory, and written back to your disk. The site never receives a byte of it.
The Cortex tools are built this way. The image compressor, converter and resizer use the browser's own encoders; the PDF tools run a PDF engine in the page; the video tools use the browser's hardware video codecs; background removal downloads a small ML model once and runs it locally. The only exception on the site is the AI floor-plan render, where the plan image genuinely has to go to a rendering engine, and the tool page says so.
The two-second test
Load the tool page. Turn off Wi-Fi (or pull the cable). Run the tool. If it works, the file stayed with you. If it spins or errors, it was being uploaded. No privacy policy needed.
A second tell: speed with large files. A 300 MB video that starts processing instantly is being handled locally; one that shows an upload progress bar is not.
The trade-offs, honestly
In-browser tools are not better at everything:
- Your device does the work. A ten-year-old laptop will compress a 2 GB video slowly; a server farm would not.
- Memory limits on phones. Very large videos can fail on a phone; images and PDFs are fine.
- Browser support. Video tools need WebCodecs (Chrome, Edge, Brave, Safari 17+). Firefox is still catching up.
- Some jobs need a server. OCR of a 300-page scan, AI image generation, anything with a model too large to download. Good sites say which tools are which.
What to do with the files that matter
- ID proofs, bank statements, signed contracts, medical reports: in-browser tools only.
- Client photos and unreleased products: in-browser tools, or your own software.
- Anything you would not e-mail to a stranger: the same rule.
- Everything else: whatever is convenient, but it costs nothing to use the in-browser one.
Why we built it this way
Cortex Digital Hub started inside a real-estate marketing team that handled floor plans, customer documents and unreleased brochures every day and did not want them on third-party servers. The tools were built to run on the device first; being free without limits or watermarks followed from that, because there are no per-file server costs to recover. The one tool that needs a server, the 2D-to-3D render, is priced per render and says exactly what happens to the plan.
Frequently asked questions
How do I know if a tool uploads my file?
Load the page, disconnect from the internet, then run the tool. If it still works, it is processing in your browser. If it fails or spins, the file was going to a server.
Are upload-based tools illegal or unsafe?
Not illegal, and the big ones are reasonably run. The issue is that your file leaves your control: it sits on their server for minutes to days, under their policy, subject to their breaches. For a holiday photo that is fine; for a passport scan or a client contract it is a needless risk.
Why are browser-based tools free?
Processing happens on your computer, so the site pays only to serve a web page, not to run servers per file. That is why they can be free without watermarks or limits.
Do browser-based tools work on phones?
Yes, with limits: a phone has less memory, so very large videos (over about 500 MB) may fail, and some video features need a recent browser. Images and PDFs work on any current phone browser.