How browser-based file tools work and protect your privacy

6 min read

Many online converters work by uploading your file to their server, processing it there and sending a result back. That is convenient, but it means a copy of your contract, ID scan or family photo travels across the internet and sits, at least for a while, on a computer you do not control. Browser-based tools take a different route. This guide explains how that works, what it protects, and — just as important — what it does not.

How in-browser processing works

When you open a tool page, your browser downloads the page and the program code that does the work, written in JavaScript and sometimes WebAssembly (a fast, compact format for code). When you pick a file, the browser reads it into the memory of your own device. The tool then decodes, changes and re-encodes it right there, and the result is handed to you as a download created locally.

No step in that sequence needs to send the file anywhere. On ELV59 Tools, every tool — from Merge PDF to the HEIC converter — works this way. Some tools download extra program code the first time you use them (for example, the HEIC decoder for browsers that cannot read HEIC on their own); that download is code coming to you, never your file going out.

What this protects

  • Your file contents: they are not uploaded, stored or seen by us.
  • Your file names: they are not sent to our analytics.
  • Speed on slow connections: there is no upload or download wait for large files.

When you close or reload the tab, the browser releases the file from memory. Files you downloaded stay wherever your browser saved them, like any other download.

What still reaches the internet

Being honest about privacy means being clear about this part too. Visiting any website involves some data exchange, and ours is no exception:

  • Page requests: loading the site sends standard technical information (such as your IP address and browser type) to the hosting provider.
  • Google Analytics: records anonymous usage such as pages visited, which tool was used, whether it succeeded and a rough file-size range. Cookies are only used if you allow analytics.
  • Google AdSense: the advertising script loads from Google. Advertising cookies and personalised ads depend on your consent choices.

Details are in our privacy policy and cookie information, and you can change your choices at any time from “Cookie settings” in the footer.

Limits of in-browser tools

  • Your device does the work. Very large PDFs or long image batches can be slow on older phones and may hit memory limits; tools show a clear message rather than failing silently.
  • Some tasks need a server. Converting PDF to Word with faithful layout, or AI image generation, requires heavy software that does not run well in a browser. We do not offer those today.
  • A compromised device is still a risk. Local processing protects against uploading, not against malware or browser extensions already on your device.

How to check it yourself

You do not have to take our word for it. On a computer:

  1. Open a tool such as Resize Image.
  2. Open your browser's developer tools (F12 or right-click → Inspect) and choose the “Network” tab.
  3. Select a file and run the tool.
  4. Watch the list of requests: you will see page assets and possibly analytics pings, but no request carrying your file.

Another simple test: load the tool page, switch off your Wi-Fi or mobile data, then process a file. Tools that do not need extra code will still work, because everything happens on your device.

Tools mentioned in this guide

More guides