Private Online Tools for Everyday Tasks: What Happens to Your Files?

Most of us use a handful of free online tools without thinking about it. Shrink a photo so a form will accept it. Count the words in an essay. Work out a loan repayment. Generate a password. Split a restaurant bill. Each one takes a few seconds, and each one asks you to hand over something: a picture, a draft, a salary figure, a secret.

Almost nobody asks where it goes. This guide explains what actually happens, how to tell the difference between tools, and why for most everyday jobs the answer should be “nowhere”.

Two kinds of online tool

Every web tool works in one of two ways.

Upload tools send your file or text to the company’s server, process it there and send the result back. Your photo, document or numbers now exist on a computer you do not control, for as long as that company decides to keep them, under whatever policy it happens to have this year. Free plans that limit you to so many files a month or so many megabytes each are usually a sign of this model: every file costs the company server time.

In-browser tools send you the program instead of receiving your data. The page loads once, and from then on the work happens on your own phone or computer. Your file is read by your browser, changed by your browser and saved by your browser. There is nothing to delete afterwards because nothing was ever sent.

Ten years ago the second kind was often impractical. Today’s browsers can decode and re-encode images, do precise financial maths, generate cryptographic randomness and handle files of tens of megabytes, all without a server. For most everyday tasks, uploading is no longer a technical necessity. It is a business model.

What is more sensitive than it looks

It is easy to think “it is only a photo” or “it is only a word count”. The details say otherwise.

Photos carry a location. A picture taken on a phone usually records the GPS coordinates of where it was taken, along with the time and the device. Share the original file of a photo taken at home and you may be sharing your address. Re-encoding an image drops this data, and an EXIF remover shows you exactly what is there.

Documents you shrink are often the private ones. People mostly compress images to get them under a size limit — and the forms with size limits are job applications, visa portals, rental applications and insurance claims. That means passport scans, payslips and ID cards. The guide to compressing images without losing quality covers how to do it well, on your own device.

Numbers describe your life. The amount you are thinking of borrowing, what you earn and who you split bills with are exactly the kind of data that is valuable to someone else. A calculator has no reason to know any of it. How much loan overpayments save walks through the maths without a server involved.

Passwords must never travel. A password generated on someone else’s server has, by definition, been seen by that server. The explanation of how long a password should be covers why in-browser generation with the operating system’s cryptographic randomness is the only sensible default.

Drafts are unpublished. A cover letter, a tender, a chapter or a confidential report pasted into a word counter is writing that nobody else has seen yet. It should stay that way.

How to tell which kind you are using

You do not have to take a website’s word for it. Three checks work in any browser:

1. Watch the network. Open your browser’s developer tools (F12 on most computers), choose the Network tab, then use the tool. An upload tool shows a request carrying your file. An in-browser tool shows nothing new.
2. Go offline. Load the page, turn off Wi-Fi, then use it. An in-browser tool keeps working; an upload tool fails.
3. Read the limits. “500 images a month” or “files deleted after one hour” describes a server. Unlimited use with no deletion policy usually means there is nothing to delete.

On this site, every tool that runs on your device is marked Runs in your browser, and they are all listed together under private tools. Where a future tool genuinely needs a server — heavy video processing, for example — its page has to say so and state what happens to the file, instead of borrowing the in-browser promise.

Everyday jobs that never need a server

A practical starting set, all of which run entirely on your device:

• Images: compress photos in batches or to a target size, and strip location data before sharing.
• Writing: count words and characters, with reading time, readability and limits for posts and text messages.
• Money: work out loan repayments and overpayments, or split a bill by what people actually ordered.
• Security: generate passwords and passphrases with their real strength shown.
• Dates: calculate an exact age or date difference without typing a date of birth into anyone’s database.

If you work with code and APIs, the same reasoning applies with higher stakes, because the things pasted into developer tools are often production data and live credentials. That side is covered in the companion guide to browser-based developer tools.

The short version

Before you drop a file or a figure into a free online tool, ask whether the job actually needs a server. For shrinking a photo, counting words, doing loan maths, splitting a bill or making a password, it does not. Prefer tools that work on your device, check with the network tab when it matters, and keep the upload tools for the jobs that genuinely require one.