how-tosecurity

How to Encrypt Files Before Uploading to Any Cloud

Server-side encryption protects files from attackers, not from your provider. Here's a practical guide to adding client-side encryption before you upload.

What “Encrypted” Usually Means — And What It Doesn’t

When a cloud storage provider says your files are encrypted, they almost always mean encrypted on their servers. Your files are unreadable to anyone who breaks into the data center. They are not unreadable to the provider itself.

The technical term for this is server-side encryption. The provider holds the encryption key. If a court order arrives, if a data breach exposes the key management system, if an employee acts improperly, or if the provider changes its privacy policy — the provider can decrypt your files.

This is not a hypothetical concern. It’s the default state of nearly every mainstream cloud storage service.

The alternative — encrypting files on your own device before uploading, so the cloud service receives only ciphertext it cannot read — is called client-side encryption. It requires more effort. For sensitive files, it offers meaningfully stronger protection.

What Client-Side Encryption Actually Protects Against

Before choosing a tool, it helps to be precise about what you’re protecting:

Provider access. A cloud provider with server-side encryption can read your files. With client-side encryption, they receive encrypted data with no key to open it.

Provider policy changes. If a service changes its terms to allow AI training on user content, files you’ve pre-encrypted are unaffected — the provider can’t read them, so there’s nothing to train on.

Law enforcement requests (partially). A properly executed client-side encryption scheme means the provider can only hand over ciphertext — which is useless without the key you hold. This isn’t a guarantee of privacy against law enforcement, but it limits what a provider can be compelled to disclose.

Breach of the cloud service. If an attacker steals your files from a cloud server, pre-encrypted files are unreadable without your key.

What client-side encryption does not protect against: a compromised device, a weak encryption key, or losing your key with no recovery option.

The Tradeoffs

Client-side encryption is not free:

You are responsible for key management. If you lose your encryption key or passphrase, your files are gone. There’s no “forgot my password” option for client-side encryption done correctly.

Search and preview are limited. Most cloud providers’ in-browser viewers can’t display encrypted files. You need to download and decrypt to view them.

Collaboration is harder. Sharing an encrypted file requires getting your encryption key (or a derivative of it) to the recipient.

Setup has a learning curve. The tools below are designed for non-experts, but none are as simple as drag-and-drop.

For genuinely sensitive files — legal documents, medical records, identity documents, financial records, unreleased creative work — this tradeoff is worth making. For vacation photos you want to browse easily from any device, it’s usually not.

Tools for Client-Side Encryption Before Upload

Cryptomator is specifically designed for pre-encrypting cloud storage. You create a “vault” folder — a directory on your device that Cryptomator mounts as an encrypted virtual drive. Any file you drag into the vault is automatically encrypted before it syncs to whichever cloud folder the vault lives in.

The vault folder contains only encrypted files and can sit inside your Dropbox, Google Drive, OneDrive, or any other synced folder. The cloud provider syncs the ciphertext without being able to read it.

Key properties:

  • Open source, regularly audited by security researchers
  • Works on Windows, macOS, Linux, iOS, and Android
  • Files are encrypted individually, so the cloud can sync only changed files rather than re-uploading everything
  • Passphrase-protected vault key stored locally

Setup:

  1. Download Cryptomator from the official site (cryptomator.org)
  2. Create a vault — choose a folder inside your existing cloud sync directory
  3. Set a strong passphrase (20+ characters, no dictionary phrases)
  4. Unlock the vault and drag files in — the cloud syncs the encrypted versions automatically

VeraCrypt (Free, Open Source — Power Users)

VeraCrypt creates encrypted containers — single files that act as virtual encrypted drives. You can store a VeraCrypt container in cloud storage, but syncing is less efficient: any change to any file inside the container changes the entire container file, so the full container uploads on every change.

This works for a static archive — documents you store but rarely modify. It’s awkward for active files you open regularly. VeraCrypt is better suited to external drives and local backups than to cloud sync.

Picocrypt (Free, Open Source — Simple and Audited)

Picocrypt is a lightweight, single-file encryption tool. You drag a file onto the application, set a passphrase, and it outputs an encrypted version. No key management, no cloud integration — just encrypted files you can upload anywhere.

It’s well-suited for people who want to encrypt a specific set of files before archiving them without learning a full key management system. The tradeoff is that it’s manual — there’s no automatic sync or vault.

GPG (Free, Open Source — Flexible but Technical)

GPG (GNU Privacy Guard) is the open-source implementation of the OpenPGP standard. It encrypts individual files from the command line, or through GUI front-ends like Kleopatra on Windows or GPG Suite on macOS.

The workflow: encrypt a file locally, upload the encrypted version, download and decrypt when needed.

GPG is powerful and well-audited. It’s also the most manual option — there’s no automatic sync, and you’re managing key pairs rather than passphrases. For most people, Cryptomator is simpler.

A Practical Setup for Sensitive Documents

Here’s a workflow that balances security with usability:

Step 1: Identify what actually needs pre-encryption. Go through your cloud storage and categorize files by sensitivity. Identity documents, medical records, legal contracts, financial statements, and anything you’d be seriously harmed by if made public — these warrant client-side encryption. Family photos, shared work documents, and app backups typically don’t.

Step 2: Install Cryptomator and create a vault in your cloud storage folder. Name it something nondescript.

Step 3: Move sensitive files into the vault. The original locations should be cleared once the encrypted versions exist in the vault and you’ve confirmed they’re synced.

Step 4: Store your vault passphrase securely. A password manager (Bitwarden, 1Password) is appropriate for one copy. Write down a paper copy and store it somewhere physically secure — not photographed and stored in the same cloud service you’re encrypting.

Step 5: Test recovery before you depend on it. On a different device, install Cryptomator, point it to the same cloud-synced folder, enter your passphrase, and confirm you can open the vault and read the files. This test, done once, removes uncertainty about whether this will work if you ever need it.

Choosing a Cloud Service That Reduces the Need for This

Client-side encryption is a DIY solution to a problem created by cloud services that treat your files as infrastructure they manage, not content they’re custodians of.

Some services are designed with explicit data-use commitments that reduce the need for a workaround layer:

  • Storage encrypted with AES-256 at rest and TLS 1.3 in transit
  • No AI training on your files
  • No advertising business model that benefits from knowing what you store
  • GDPR and CCPA compliance as a baseline
  • Clear, permanent data deletion on account closure

Daftei falls into this category — it uses AES-256 at rest and TLS 1.3 in transit, never sells user data, and doesn’t train third-party AI systems on your stored content. This isn’t end-to-end encryption where daftei holds zero keys — it’s server-side encryption with strong access controls and explicit no-data-sale commitments. For most people’s most sensitive files, combining a trusted provider with Cryptomator for the highest-sensitivity subset gives you a practical two-layer approach.

Matching the Tool to the Threat

Different files warrant different levels of protection:

File typeRisk if exposedRecommended approach
Vacation photosLowStandard cloud storage with trusted provider
Tax returnsHighClient-side encryption (Cryptomator vault)
Passport scansHighClient-side encryption or encrypted folder with strict access
Medical recordsVery highClient-side encryption + minimal copies
Legal contractsVariesClient-side encryption if they contain sensitive personal details
Work filesDepends on employerCheck your employment agreement; consider a dedicated work storage

The goal isn’t maximum friction for every file. It’s matching your protection level to the actual risk.

The Bottom Line

Server-side encryption is a floor, not a ceiling. It protects you against data center break-ins and opportunistic attackers. It doesn’t protect your files from the service itself.

Client-side encryption raises that floor significantly, at the cost of key management responsibility and some convenience. For identity documents, legal records, medical files, and anything you’d classify as genuinely sensitive — the extra step is worth it.

Cryptomator is the most practical option for most people: free, open source, works with any cloud folder, and maintains the automatic sync you’re used to. The vault passphrase is the one thing you must not lose.

Start by picking one category of files that deserves better protection. Set up the vault, move those files in, and test recovery. The whole process takes under an hour. The peace of mind is indefinite.

Your memories deserve better than an ad platform.

Try daftei free →
← All posts