Skip to content
LooparaLoopara
Productivity9 min read1,428 words

Free online tools that upload your files, and when that matters

Some browser tools do the work on your machine and some send your document to a server. The difference is invisible in the interface and easy to check yourself.

Loopara
Traditional server infrastructure
Traditional server infrastructurePhoto: Ramu50 · CC BY 3.0 · Wikimedia Commons

Short answer

Many free converters and compressors run entirely in your browser and never transmit the file; others upload it to a server, process it there and send it back. Open your browser's network panel and watch whether the file is sent. For anything containing personal or commercial information, prefer a tool that works with the network disconnected.

On this page
  1. Why both designs exist
  2. Checking it yourself, in thirty seconds
  3. When it matters
  4. Reading the privacy claim
  5. Local options for the common tasks
  6. A rule that fits in a sentence
  7. What are browser-based online tools?
  8. Which design does what?
  9. How do you check in 10 seconds?
  10. When does it actually matter?
  11. What the privacy promise is worth
  12. Local alternatives for the 4 common jobs
  13. The habit worth forming
  14. The numbers that decide it

Free online tools are everywhere. Search for "compress PDF" or "convert HEIC to JPG" and you will find dozens of free tools that look identical. Some do the work on your own machine. Others upload your file to a server you know nothing about.

Both are legitimate approaches. The problem is that the interface never says which one you are using, and the difference matters a great deal for some documents and not at all for others.

Why both designs exist

Browsers can do serious work now. WebAssembly runs image codecs, PDF libraries, video transcoders and archive tools at close to native speed, entirely in the tab. A tool built this way needs no server, costs nothing per user, and never sees your file.

Server-side processing is still chosen for good reasons: very large files, formats with no browser implementation, anything needing more memory than a tab gets, or simply because the developer already had the code running on a server.

The honest tools tell you. Most do not.

Checking it yourself, in thirty seconds

The network panel. Open developer tools with F12 or Cmd+Option+I, select the Network tab, and process a file. Sort by size. If a request appears carrying roughly your file's size, it was uploaded.

The offline test — easier and just as conclusive. Load the page, disconnect from the network, then use the tool. If it works, the processing is local. If it fails, the file was going somewhere.

That second test needs no technical knowledge and is the one worth remembering.

When it matters

It usually does not. A meme resized, a screenshot converted, a public PDF compressed — the practical risk of these passing through someone's server is close to zero.

It matters for:

  • Anything with a name, address, date of birth or account number — bank statements, payslips, invoices, medical letters, tax documents.
  • Identity documents. Passport and licence scans are directly valuable to fraud.
  • Commercial documents under any confidentiality obligation — contracts, unreleased material, client data.
  • Anything covered by an employer's data policy, which in many organisations includes most work documents.

For those, the question is not whether the site is trustworthy. It is that you cannot tell, and there is usually a local option that removes the need to decide.

Reading the privacy claim

Tools that upload files often promise deletion after an hour. Consider what that promise covers:

  • Where is the server? Data protection obligations differ by jurisdiction, and the site rarely says.
  • Deleted from where? Backups, logs and caches are commonly excluded from such statements.
  • Who else sees it? Many small tools run on infrastructure operated by someone else.
  • Is anyone accountable? A site with no company details, address or contact has no enforceable obligation to anyone.

None of this makes such sites malicious. It means the promise is unverifiable, and unverifiable promises are worth what you paid for them.

Local options for the common tasks

Most things people reach for a website to do have an offline answer:

  • Images — resize, convert and compress in your operating system's built-in viewer, or with an offline tool. Modern browsers handle HEIC, WebP and AVIF locally in several browser-based converters.
  • PDF — merge, split and rotate are available in Preview on macOS and in several free desktop applications elsewhere. Browser-based PDF tools using pdf.js do the work locally.
  • Video — ffmpeg does essentially everything, offline, and several browser front-ends run it through WebAssembly without uploading.
  • Text — cleaning, converting and comparing text is a category where local tools are both faster and more private, since large pastes never leave the tab.

A rule that fits in a sentence

If the file would embarrass you or someone else in a breach, use a tool that works with the network disconnected.

Everything else is fine either way, and the point of the rule is that it takes the decision out of the moment when you are in a hurry and just want the file converted.

What are browser-based online tools?

Online tools are single-purpose web pages that convert, compress or edit a file. Some do the work inside the tab using compiled code; others upload the file to a server, process it there, and send the result back. The interface is identical in both cases, which is the entire problem.

Which design does what?

In the browserOn a server
Your file leaves the deviceNoYes
Works with the network offYesNo
First loadSlow — the code downloads onceFast
Very large filesLimited by tab memoryHandles more
Privacy policy mattersNot reallyEntirely
Cost to the operatorNear zeroPer file

The last row explains why so many free tools upload: someone is paying for the processing, and that cost is recovered somewhere.

How do you check in 10 seconds?

Load the page, disconnect the network, then use the tool. If it works, the processing is local. If it fails, the file was going somewhere.

For more detail, open developer tools with F12, select the Network tab, and sort by size — a request carrying roughly your file's size is an upload. But the offline test needs no technical knowledge and answers the same question.

When does it actually matter?

  • Bank statements, payslips, invoices, medical letters — anything with a name, an address or an account number.
  • Identity documents. Passport and licence scans are directly valuable to fraud.
  • Contracts and unreleased material under any confidentiality obligation.
  • Anything covered by an employer's data policy, which in many organisations is most work documents.

For a meme, a screenshot or a public PDF, the risk is close to zero and the convenience is real. The rule that fits in a sentence: if the file would embarrass you or someone else in a breach, use online tools that work with the network disconnected. See file tools, image tools and free utilities.

What the privacy promise is worth

Online tools that upload files often promise deletion after an hour. Consider what that covers: which jurisdiction the server is in, whether backups and logs are excluded, who operates the infrastructure, and whether any company details exist that would make the promise enforceable.

None of this makes such sites malicious. It means the promise is unverifiable, and an unverifiable promise is worth roughly what you paid for it.

Local alternatives for the 4 common jobs

  • Images — your operating system's viewer resizes, converts and compresses without any download.
  • PDF — merge, split and rotate are built into macOS Preview and available free elsewhere; browser tools built on pdf.js run locally.
  • Video — ffmpeg does essentially everything offline, and several browser front-ends run it through WebAssembly.
  • Text — cleaning and converting text is the category where local tools are both faster and more private, since large pastes never leave the tab.

Bookmark one local option for each, verify it once with the airplane-mode test, and the decision is already made the next time you are in a hurry.

The habit worth forming

Decide once, per category, when you are not in a hurry. Bookmark 4 local online tools — one each for images, PDFs, video and text — verify each with the airplane-mode test, and use those by default.

That removes the decision from the moment when you have a deadline and a file to convert, which is the moment when nobody reads a privacy policy. Online tools that work offline are not scarce; they are simply not the first search result, because a page that costs nothing to run has nothing to spend on ranking. Online tools are not the problem; not knowing which kind you are using is, and that takes ten seconds to establish.

The numbers that decide it

  • 10 seconds to run the airplane-mode test.
  • 4 categories worth bookmarking a local option for: images, PDFs, video, text.
  • 1 question that settles the rest: would this file embarrass anyone in a breach?
  • 0 privacy policies you need to read once the tool works offline.

Free online tools are not the problem. Not knowing which of the 2 designs you are using is, and that is answerable in less time than reading this paragraph took.

Frequently asked questions

How do I tell if a tool uploads my file?
Load the page, disconnect from the network, then process the file. If it still works, the processing happens on your machine. The browser's Network tab shows the same thing with more detail.
Are browser-based tools slower than server-based ones?
Sometimes, for very large files, because a tab has less memory than a server. For everyday images, PDFs and documents the difference is usually not noticeable, and there is no upload or download time.
Is a site promising to delete files after an hour trustworthy?
It is unverifiable. The claim usually says nothing about logs, backups or the infrastructure provider, and a site with no company details has no obligation you could enforce.
Does a padlock in the address bar protect my uploaded file?
It protects the file in transit, so nobody in between can read it. It says nothing about what happens to the file once it arrives.

Sources

  1. WebAssemblyWebAssembly
  2. File APIW3C
  3. pdf.jsMozilla
  4. WebAssemblyWebAssembly

Published by

Loopara

Practical guides, free tools, workflows, and resources for productivity, files, images, video, text, creators, and everyday digital tasks.

About the publication

Related reading

Keep going