If a site says "we delete your file after 24 hours," is that safe enough?

It means the file existed on their servers for up to 24 hours, was likely logged by their infrastructure provider, and its deletion depends on that specific promise being kept. For most everyday files that risk is acceptable. For anything you would not want a stranger to read, it is a risk worth avoiding entirely rather than trusting a policy.

Can a browser-based tool see or transmit my file without me noticing?

A malicious page could, if it wrote code to do so — client-side processing is a technique, not a guarantee, and it depends on the site actually not sending your data anywhere. You can verify it yourself with your browser's network inspector: watch for outgoing requests while the tool runs.

Guide

Why Client-Side PDF Tools Are Safer for Sensitive Documents

At some point almost everyone has typed "merge pdf online" or "compress pdf free" into a search bar and clicked the first result, without thinking much about what happens next. For a flyer or a public form, that's fine. For a signed lease, a tax return, a medical referral letter, or a document with a client's personal details on it, it's worth twenty seconds of thought — because most of those tools work in a way that hands your file to a stranger's server before you get anything back.

What happens when you "upload to convert"

A typical upload-based PDF tool works like this: your browser sends the full file to the provider's servers over the internet, a process there performs the operation, and the result comes back down to you. In between, your document exists on infrastructure you have no visibility into. It may sit in a temporary storage bucket, get written to logs by the web server or a CDN in front of it, be scanned by an automated content-moderation system, or be retained for some period under a terms-of-service clause about "improving our services." None of this requires bad intent from the provider — it's simply what happens by default when a file crosses a network boundary onto someone else's machine.

The provider's privacy policy might be perfectly reasonable. The problem is that you're now trusting a party you likely know nothing about — their security practices, their breach history, their staff's access controls, whether their "free" tier is monetized by scanning file contents. For most files, that trust is a small, acceptable convenience cost. For documents that contain financial details, medical information, legal terms, or anyone's personal data, it's a cost worth questioning.

What "runs in your browser" actually means

Client-side tools take a different approach: instead of sending your file anywhere, the processing code runs using your browser's own JavaScript engine, on your own device. The PDF's bytes are read into your browser's memory, transformed there, and written back out as a new file — all without a single network request carrying the file's contents. Nothing needs to be "sent" because nothing needs to leave.

This isn't a claim you have to take on faith. Every browser ships a network inspector (usually under Developer Tools) that shows every request a page makes. Open it, load a client-side PDF tool, and process a file — you'll see the page's own code load once, and then silence while your file is worked on locally. If a tool actually uploaded your document, that request would show up plainly, with a payload size roughly matching your file.

Questions worth asking before you upload anything

Does the tool say, in plain language, what happens to your file — not just "we care about your privacy," but the actual mechanism?
Does it need an internet connection to do the work? If disconnecting your device breaks the tool, your file is very likely leaving it.
Is there a retention or deletion policy, and does it describe a promise about someone else's server, or the simple fact that nothing was ever sent?
Would you be comfortable if this exact file appeared in a server log somewhere, even briefly?

Where client-side tools have honest limits

This approach isn't free of tradeoffs, and it's worth being direct about them. Operations that need heavyweight processing — OCR across a thousand-page scan, AI-based summarization, syncing a result to cloud storage — generally do need a server somewhere, because that's more computing than a browser tab can reasonably do. The privacy benefit of client-side tools applies specifically to operations that don't need that: merging, splitting, rotating, re-saving, and converting between PDF and image formats are all things a browser can do entirely on its own, which is why they're a natural fit for this approach and heavy AI-driven document processing generally isn't.

Try it

Every tool on HerePDF — merge, split, rotate, compress, and conversion between PDF and images — runs this way. Start with Merge PDF or Compress PDF , or read more about the site on the About page.