Here's a question that should make you uncomfortable: where does your file go when you use an online encryption tool?
If the answer is "to a server somewhere," you have a problem. The entire point of encryption is to prevent anyone from reading your file. If the file reaches a server in readable form before it's encrypted, the encryption is theater. It protects against everyone except the server that saw the original.
The Two Models of Online Encryption
There are two fundamentally different architectures for browser-based encryption tools, and most users can't tell them apart from the interface alone.
**Server-side encryption:** You select a file. The file uploads to a server. The server encrypts it with the password you provided. The server sends back the encrypted file. Your browser downloads it.
**Client-side encryption:** You select a file. The file stays in your browser. JavaScript running on your machine encrypts the file using the Web Crypto API. The encrypted file is generated locally. Nothing is uploaded. You download the result directly.
Both produce an encrypted file. Both look identical from the user's perspective. But the security properties are completely different.
In the server-side model, the server sees your original file. It sees your password. It sees the encrypted output. If the server logs requests — and most do — your file and password may exist in server logs, in backups of those logs, in analytics pipelines that process those logs. The encryption protects the file after it leaves the server. It does not protect the file from the server itself.
In the client-side model, the server never sees your file. It never sees your password. It never sees the original or the encrypted output. The server's only role is to serve the web page — the HTML, CSS, and JavaScript that run in your browser. Once the page loads, you could disconnect from the internet and the encryption would still work.
How to Tell the Difference
You can't always tell from the UI. But there are clues.
If the tool works offline after the page loads, it's client-side. Try this: open the encryption tool, disconnect your internet, then select a file and encrypt it. If it works, the encryption is happening in your browser. If it fails with a network error, the tool is sending your file to a server.
If the tool has a file size limit that seems arbitrary (10 MB, 50 MB), it's likely server-side. The limit exists because the server has to process and store your file temporarily. Client-side tools can handle much larger files because the only limit is your device's memory.
If the tool's privacy policy mentions "processing" or "temporarily storing" your files, it's server-side. A truly client-side tool has nothing to say about file storage because it doesn't store files.
The file encryption tool on this site is client-side. Your files never leave your browser. The page loads, the JavaScript runs, the encryption happens, and the result downloads. No server in the middle.
Why Server-Side Encryption Tools Are Risky
Let me be specific about the risks, because vague warnings don't change behavior.
**Data retention.** Server-side tools process your file on their infrastructure. Even if they promise to delete the file immediately after encryption, "immediately" in server terms might mean "within 30 days when our log rotation runs." Backups, error logs, crash dumps, and analytics pipelines can all retain copies of files that the application itself has "deleted."
**Password exposure.** If you type your encryption password into a web form that submits to a server, the password travels over the network and is processed server-side. Even with HTTPS, the password exists in the server's memory and potentially in logs. A client-side tool processes the password entirely in your browser's JavaScript runtime.
**Business model conflicts.** Free server-side encryption tools have to make money somehow. If they're not charging you, they may be analyzing your files, training models on your data, or selling aggregated metadata. A client-side tool can't do any of this because it never sees your data.
**Breach exposure.** If a server-side encryption service is breached, the attacker may gain access to files in transit, files in temporary storage, and potentially the encryption passwords submitted by users. A client-side tool has nothing to breach — there's no server storing files or passwords.
The Offline Encryption Alternative
Client-side encryption has another property that's easy to overlook: it works offline. Once the web page is loaded, the JavaScript that performs the encryption runs entirely on your machine. You can turn off your internet connection and the tool still works.
This matters for several scenarios. If you're working with classified or proprietary data in a secure environment where internet access is restricted, a client-side tool loaded in advance still functions. If you're traveling and have intermittent connectivity, you can encrypt files without waiting for a server. If you're paranoid about network monitoring — and in some environments, that's reasonable paranoia — you can encrypt files without any network traffic beyond the initial page load.
This is what "offline file encryption" means in a browser context. It's not a desktop application. It's a web page that, once loaded, needs no server to function. The client-side encryption approach uses the Web Crypto API built into every modern browser, which provides the same AES-256-GCM implementation that desktop software uses.
Verifying Client-Side Encryption
How do you know a tool is actually client-side and not just claiming to be? A few checks:
Open your browser's developer tools (F12 in most browsers). Go to the Network tab. Encrypt a file. Watch the network requests. If you see a request uploading your file to a server, the tool is not client-side. If the only network activity is the initial page load, the encryption is happening locally.
This takes 10 seconds and tells you definitively whether your file is leaving your machine. I do this with every new encryption tool I encounter. Most server-side tools are obvious once you look at the network tab. The file upload is right there in the request payload.
The Bottom Line
Server-side encryption tools aren't inherently malicious. Some are run by well-intentioned developers who haven't thought through the security implications. Some are run by companies that genuinely try to protect user data. But the architecture itself is fundamentally weaker than client-side encryption, because the architecture requires trusting a server with your unencrypted data.
Client-side encryption requires trusting no one. The math happens on your machine. Your file stays on your machine. Your password stays in your browser's memory. The encrypted output is generated locally and downloaded directly.
When the choice is between "trust this server" and "trust the math," the math wins every time. Use a client-side encryption tool. Verify it with the network tab. Encrypt with confidence that your file is yours alone.,