Quick Answer

Free online tools are safe when they process your data in your browser and never transmit it. They're risky when they upload it to a server you know nothing about. The price tag tells you nothing. What matters is whether your data leaves your device, and you can check that in about thirty seconds.

Free online tools are safe when they do their work inside your browser and never send your data anywhere. They're a genuine risk when they quietly upload whatever you paste to a server run by people you've never heard of, under a retention policy you've never read. The confusing part is that the two kinds look identical. Same box, same button, same instant result. So the real question isn't whether free tools are safe in general, it's how to tell them apart, and that turns out to be a thirty-second check anyone can run. Here's how.

Free Tool

Everything on this site runs in your browser. Paste into the Text Diff tool or the JSON Formatter and watch the Network tab stay empty. Your data never leaves your device.

Browse the Free Tools →

Are Free Online Tools Actually Safe?

It depends on one thing, and it isn't price. It's where the processing happens.

A browser-based tool loads its code onto your machine and runs it there. You paste something in, JavaScript does the work locally, and the result appears. Nothing was transmitted, so there's nothing on a server to leak, subpoena, or sell.

A server-based tool sends your input across the internet to be processed and returns the answer. Now your data sits on hardware you don't control, for a period you don't set, protected by security you can't audit. That's not automatically bad. It's a different risk profile, and you deserve to know which one you're accepting.

What's the Difference Between Client-Side and Server-Side?

Client-side means your browser does the work. Server-side means someone else's computer does.

QuestionClient-sideServer-side
Does your data leave your device?NoYes
Can the operator read your input?NoYes, in principle
Affected by their data breach?NoYes
Works with no internet?Yes, once loadedNo
Handles very large files?Limited by your RAMUsually better
Heavy processing, like OCR or video?Sometimes too slowBetter suited

Client-side isn't universally better. Some jobs genuinely need a server, because your laptop can't transcode a two-hour video or run a large model. But a text formatter, a JSON validator, a case converter, or a base64 encoder has no technical reason to upload your content. If one does, that's a choice someone made.

The W3C File API defines interfaces like FileReader that read a selected file into memory on your own device. Reading and transmitting are separate steps, so a developer has to deliberately add the upload.

How Can You Tell Which Kind a Tool Is?

Three checks, in order of effort.

  1. Watch the network. Press F12, open the Network tab, clear it, then use the tool. If your content is being uploaded you'll see a POST request appear, and you can click it and read exactly what was sent. If nothing shows up beyond fonts and scripts, the work happened locally.
  2. Pull the plug. Load the page, then turn off your wifi (or switch on airplane mode on a phone) and use the tool anyway. A genuine client-side tool carries on working. A server-based one breaks instantly.
  3. Read the privacy policy for one specific thing. Search it for "upload", "store", "retain", and "third party". If a tool claims local processing but its policy describes storing your files, believe the policy.

The network check is the one that's hardest to spin. Marketing copy is words. A POST request carrying your document is evidence. It has limits, though.

What Can't the Network Tab Test Tell You?

A clean Network tab is strong evidence, not a guarantee. It tells you what a page did once, on your machine, in that moment.

Almost no tool ships only its own code. Pages pull in analytics, ad code, fonts and libraries from other people's servers. The W3C's Subresource Integrity specification puts the problem in one line: an attacker who can replace the file on the CDN server has the ability to inject arbitrary content.

The polyfill.io compromise showed what that looks like. Security firm Sansec reported on 25 June 2024 that over 100,000 sites, among them JSTOR, Intuit and the World Economic Forum, embedded scripts from a domain a Chinese company had bought in February 2024. Per Sansec, the injected payload targeted only mobile users, stayed quiet when it found admin cookies, depended on the hour of the day, and delayed itself when it detected web analytics. Someone opening devtools on a desktop would have seen nothing at all.

The offline test has a blind spot too. Working with the network off proves the processing is local, not that nothing is sent later. Mozilla's documentation on the Background Synchronization API describes how web apps can defer tasks so they run in a service worker once the user has a stable connection again, so a tool could queue an upload and send it when you reconnect. If the data matters, keep the Network tab recording after you turn the network back on and wait a minute.

So treat both tests as a snapshot rather than a certificate. Recheck tools you use with sensitive material, because code and ownership change. Prefer pages that load few third-party scripts. And match the effort to the stakes: formatting sample JSON needs none of this, a client contract deserves a fresh look or an offline tool.

Can a Page Prove It Won't Send Your Data Anywhere?

Closer than anything above. The Network tab tells you what a page did once. A Content Security Policy tells you what the browser will refuse to let it do at all.

The policy is a header the page sends and the browser enforces. The directive that matters here is connect-src, which the MDN reference describes as restricting the URLs that can be loaded using script interfaces such as fetch(), XMLHttpRequest, WebSocket and navigator.sendBeacon(). A page serving connect-src 'none' takes that route away from every script on the page, including one that arrives compromised from a CDN tomorrow.

To check, reload with the Network tab open, click the first request (the document itself) and look under Response Headers for Content-Security-Policy. In connect-src, 'none' is the strongest thing you'll see, and 'self' means the page can talk to its own origin and nowhere else.

It's a strong signal rather than a proof. connect-src covers scripted connections only, so a page with a permissive img-src could still leak something by requesting an image with your data in the URL. Read the whole policy, and remember it can change on the next deploy.

Can a Browser Extension See What You Paste?

Yes. And the Network tab can't catch it, because the leak doesn't go through the page's own requests.

Google's documentation on content scripts says they run in the context of web pages and can read details of the pages the browser visits, make changes to them, and pass information to their parent extension. So you paste a contract into a genuinely client-side tool, the tool never transmits it, and an extension with permission for that site reads it straight out of the page.

Trusted extensions can turn. Sekoia published an analysis on 22 January 2025 of a campaign that phished extension developers with fake Chrome Web Store emails and pushed tainted updates into extensions people already had installed, including Cyberhaven's on 24 December 2024. The payloads went after OpenAI API keys, ChatGPT session tokens and Facebook Business credentials.

Audit your extensions and remove what you don't use. Set the rest to run on click or only on specific sites. For genuinely sensitive work, use a private window, where extensions are typically disabled unless you explicitly allow them.

What Stays Behind on Your Own Device?

More than most people expect. "Your data never leaves your device" is a claim about the network, not about what's still sitting on the device once you close the tab. On a shared or work machine, that's the actual exposure.

  • localStorage. The WHATWG's HTML Standard describes it as storage that spans multiple windows and lasts beyond the current session, and tells browser makers to treat persistently stored data as potentially sensitive.
  • sessionStorage. The better-behaved sibling, cleared when the tab closes.
  • The URL. Some tools encode your input into the address so you can share a result, which puts it in your history, autocomplete, and whatever your browser syncs.

To check, use the same DevTools as the network check: open the Application tab and look under Local Storage and Session Storage for the site. If a tool kept what you typed, it's there in plain text. Clear it after anything sensitive, and on a shared machine use a private window and close every private window when you're done. On a work device it's a policy question too, which the section on doing this at work covers.

Do AI Chatbots Count as Online Tools?

They do, and the client-side test doesn't help here. The chatbots people actually use don't run in your browser, because their models are far too large. Every prompt goes to somebody else's server.

The NCSC's 2023 guidance on the risks of large language models is blunt: the query will be visible to the organisation providing the LLM. It notes that an LLM does not, as of writing, automatically add information from your queries to its model for others to query, but that queries are stored and will almost certainly be used for developing the service or the model at some point. Its advice is not to submit queries that would lead to issues were they made public.

So redact before you paste: swap real names, account numbers and client identifiers for placeholders. Find out whether your plan trains on your data. And at work, treat an unapproved AI tool as shadow IT like any other.

What Should You Never Paste Into an Online Tool?

Some things don't belong in a browser text box regardless of how the tool works, because the exposure isn't only about transmission.

  • Live passwords and API keys. Even locally, the value now sits in your clipboard, possibly your browser history, and maybe an autofill cache. If you already did it, rotate the key rather than hoping.
  • Personal data belonging to other people. Customer lists, patient records, employee details. That's not yours to risk, and in most jurisdictions there are rules about where it can go.
  • Unreleased or confidential material. Contract drafts, proprietary source code, anything under NDA.
  • Identity documents. Passport scans, national ID numbers, bank statements.

For credentials specifically, generate them properly rather than testing them in random utilities. Our password security guide covers how to do that, and the hash generator guide explains what hashing does and doesn't protect.

What If You Already Pasted Something Sensitive?

Most people reading a guide like this already have. What reduces the damage depends on whether the thing can be changed.

Credentials, keys and tokens: rotate immediately. The UK National Cyber Security Centre lists rotating exposed or potentially exposed credentials as an immediate action. Revoke the old one rather than just issuing a new one alongside it. Change passwords, and change them anywhere you reused them.

Things you can't rotate: limit the damage. A client contract, medical details, an unreleased document. If the operator falls under UK or EU data protection law, you can ask for erasure in certain circumstances, and under Article 12 of the UK GDPR they must respond within one month. But you can't verify that a deletion happened, backups and logs are harder to purge, and plenty of free tools name no operator to ask. If the data belonged to a client or an employer, tell them, because organisations usually have reporting duties with clocks attached.

Write down the tool, the URL, the time and what was in it. Clearing your browser history only clears your side. And keep it proportionate: marketing copy in a word counter is not an incident, a production database connection string is.

What Changes If You're Doing This at Work?

The stakes, and who has to report it.

The UK's National Cyber Security Centre calls this shadow IT, defined as unknown IT assets used within an organisation for business purposes. It says shadow IT is rarely the result of malicious intent, and normally due to staff struggling to use sanctioned tools or processes to complete a specific task. The problem is the aggregate: if shadow IT is prevalent, risk management becomes very difficult.

If what you pasted contained personal data about identifiable people and it went to a server, that may be a personal data breach. Under Article 33 of the UK GDPR, organisations must report certain breaches to the ICO without undue delay and, where feasible, within 72 hours of becoming aware of them. That clock belongs to your employer, so report it the same day.

Find out what's sanctioned before you need it. Client-side tools are far easier to justify, because the data never went to a third party. And if you manage people, NCSC warns that if you blame or punish staff, their peers will be reluctant to tell you about their own unsanctioned practices.

Can the Free Tool Itself Be the Scam?

Yes, and it's a bigger risk than a genuine tool keeping a copy of your file. Some sites exist to hand you malware, and the conversion is the bait.

In March 2025 the FBI's Denver Field Office warned of an increasing number of sites offering free online file converters, as Malwarebytes reported. They usually do convert your file, but the file you get back can carry hidden malware that can lead to ransomware, and the tools can harvest information such as Social Security numbers, banking credentials and passwords.

  • You found it through an ad. Scroll past the "Sponsored" results, or go straight to a tool you already know.
  • The result is a download you didn't expect. You asked for a PDF and got a .exe, a .zip, or a document asking you to "enable macros". Stop there.
  • It wants you to install something. A genuine browser tool doesn't need anything installed.

A client-side tool closes most of this off by design, because the output is built on your own device. Our sister site IWantFreePDFTools does common PDF jobs this way. If you've already run something from a suspect site, the FBI's advice is to contact your bank, change your passwords from a clean, trusted device, and report it at ic3.gov. Our password security guide walks through the password part.

How Do You Vet a Tool Before Trusting It?

Seven checks, and the first three take under a minute:

  1. Is it HTTPS? Without it, everything is readable in transit.
  2. Does the Network tab stay quiet? The single most reliable signal there is.
  3. Does it still work offline? Quick confirmation of local processing.
  4. Is there a real privacy policy? It should say whether your input is stored and for how long.
  5. Does it demand a signup it doesn't need? A case converter asking for your email is collecting something other than what it needs.
  6. Can you tell who runs it? A named operator with a contact route is accountable. An anonymous page is not.
  7. What's watching from your own browser? If an extension can read every page, the tool's privacy properties stop being the whole story.

Do it once for the tools you use regularly. For a starting set that already passes, our online developer tools guide runs through them.

Try It Now

Run the Network tab test on us. Open the Base64 encoder, paste something, and watch. Nothing goes out, because the encoding happens in JavaScript on your machine.

Open the Base64 Tool →

What Else Do People Ask?

Are free online tools safe to use?

Many are, but safety depends entirely on where your data goes. A tool that processes everything in your browser never sees your data at all. A tool that uploads to a server has your data on someone else's machine, subject to their retention policy and their security. The word free tells you nothing either way. Check how it handles data, not what it costs.

Do online tools upload your files to a server?

Some do and some don't. Browser-based tools use JavaScript APIs like the W3C File API to read files into memory on your own device, so nothing is transmitted. Server-based tools send the file away to be processed and returned. Both look identical from the outside, which is why you have to check rather than assume.

How can you tell if a tool processes data in your browser?

Open your browser's developer tools, go to the Network tab, and use the tool. If your data is being uploaded you'll see a POST request carrying it. If nothing appears beyond the page assets, the work happened locally. You can also disconnect from the internet after the page loads. A truly client-side tool keeps working.

Is it safe to paste passwords or API keys into an online tool?

No, not as a habit. Even a genuinely client-side tool leaves the value in your clipboard, your browser history, and possibly a form autofill cache. For live credentials the answer is simply don't. Rotate the key instead of testing it, or use an offline tool. Treat any secret you paste anywhere as potentially compromised.

Does free mean they're selling your data?

Not necessarily. Plenty of free tools are funded by advertising, which pays for the page rather than the data you type into it. But free with a mandatory signup is a different proposition, because now they have an identity to attach behaviour to. The question worth asking is what the business model is, and whether it needs your content to work.

Sources: W3C File API and Subresource Integrity drafts; Sansec on the polyfill.io attack, 25 June 2024; MDN on CSP connect-src and Background Synchronization; Chrome for Developers on content scripts; Sekoia on the Chrome extension campaign, 22 January 2025; WHATWG HTML Standard; UK GDPR Articles 12 and 33; UK National Cyber Security Centre; Malwarebytes on the FBI Denver warning. All linked above.

This guide describes how browser-based and server-based tools generally differ. Any individual tool's behaviour can change without notice, so the Network tab check is worth repeating if you're handling something genuinely sensitive. This is general information, not security or legal advice.