# How do I encrypt files before uploading them to the cloud?

> Encrypt files on your computer before they reach cloud storage: Cryptomator, rclone crypt or restic, with the steps for each and what stays visible.

- URL: https://privates3.com/guides/how-to-encrypt-files-before-cloud-upload/
- Last updated: 2026-11-17
- Publisher: PrivateS3 (https://privates3.com)

**Quick answer — How do I encrypt files before uploading them to the cloud?**

Use a tool that encrypts on your computer and uploads only ciphertext: Cryptomator for drag-and-drop, rclone crypt for folder sync, restic for backups. All three keep the key with you. On a **PrivateS3** S3-compatible bucket, $2.23/TB-month on 12 months, the operator then sees scrambled data, sizes and upload times only.

**In brief**

- **Cryptomator**: a vault you drag files into; upload the vault folder with Cyberduck or rclone.
- **rclone crypt**: a remote that encrypts names and contents on the fly during sync.
- **restic**: backups that are always encrypted, with snapshots and deduplication.
- **One rule for all**: the password is the only key; write it down twice.

## Which method fits which job?

*Three ways to encrypt files before cloud upload: interface, what they suit and what stays visible to the storage seller*

| Method | Interface | Suits | Visible to the seller |
| --- | --- | --- | --- |
| Cryptomator vault | Desktop app, virtual drive | Documents and photos you open often | Encrypted file sizes, times |
| rclone crypt | Command line | Mirroring folders, large media | File length, modification time |
| restic | Command line | Scheduled backups with history | Pack sizes, upload times |

## Method 1: how do you encrypt with a Cryptomator vault?

**Create a vault, put files in it, and upload the vault's folder.** Cryptomator's security architecture page, read on 17 November 2026, describes a virtual drive that encrypts and decrypts files on the fly, with no unencrypted copies on disk. A key derived from the vault password with scrypt protects the vault's master keys.

1. In Cryptomator, create a new vault in a local folder.
2. Set a strong password; if Cryptomator offers a recovery key, store it apart from the password.
3. Unlock the vault and copy files into the drive it opens.
4. Upload the vault folder (not the unlocked drive) to the bucket with Cyberduck or rclone.

The [Cyberduck guide](https://privates3.com/guides/how-to-connect-cyberduck-to-s3/ "How do I connect Cyberduck to S3-compatible storage?") covers the upload.

## Method 2: how do you encrypt with rclone crypt?

**Wrap a bucket folder in a crypt remote and copy through it.** Rclone's crypt docs say contents are sealed with NaCl SecretBox (XSalsa20 and Poly1305) and names are encrypted by default. File length and modification time stay readable. The full setup is in the [rclone crypt guide](https://privates3.com/guides/how-to-set-up-rclone-crypt-with-s3/ "How do I set up rclone crypt with S3?").

*Copy through a crypt remote named secret, then verify*

```bash
rclone copy ~/Pictures secret:pictures --progress
rclone cryptcheck ~/Pictures secret:pictures
```

## Method 3: how do you encrypt backups with restic?

**Run restic against the bucket: it has no unencrypted mode.** The restic design document says all data in a repository is encrypted with AES-256 in counter mode and authenticated with Poly1305-AES. Each backup is a snapshot, so earlier versions of a file stay restorable. The [restic guide](https://privates3.com/guides/how-to-back-up-with-restic-to-s3/ "How do I back up with restic to S3?") schedules it nightly.

*Encrypted backup of a home folder*

```bash
export AWS_ACCESS_KEY_ID=ACCESS_KEY
export AWS_SECRET_ACCESS_KEY=SECRET_KEY
export AWS_DEFAULT_REGION=eu-central-1
restic -r s3:https://s3.privates3.com/BUCKET/home init
restic -r s3:https://s3.privates3.com/BUCKET/home backup ~/
```

## What does encryption before upload not hide?

**Sizes, times and the fact that you use the bucket.** Rclone's docs note file length and modification time stay readable; restic and Cryptomator leave encrypted sizes. On top of that, the seller keeps its own records. At PrivateS3: Request logs (source IP, time, bucket, operation, bytes) are kept 14 days for abuse handling and quota accounting, then deleted.

The endpoint and region are shown with the keys in the client area. According to PrivateS3's survey of 17 November 2026, a terabyte of S3-compatible storage costs from $6.00 to $23.00 a month at nine other sellers. Encrypted or not, data is billed by size: at PrivateS3, $5.40/TB-month on monthly plans. The [encrypted storage page](https://privates3.com/encrypted-cloud-storage/ "What is encrypted cloud storage, and who holds the key?") explains server-side versus client-side keys.

## Encrypting before upload: common questions

### Is a zip file with a password enough?

It protects one archive, but any change means re-uploading the whole file. Vaults, crypt and restic encrypt file by file or chunk by chunk.

### Can I recover files if I forget the password?

No. Restic and rclone both warn that a lost password means lost data. For Cryptomator, keep any recovery key it gives you apart from the password.

### Does PrivateS3 offer encryption itself?

Disks encrypted at rest with AES-256 on the server; for privacy from the operator, files are meant to be encrypted on the customer's side (restic, rclone crypt, Kopia, Cryptomator) before upload.

### Will encryption break deduplication?

Restic still deduplicates encrypted backups, so unchanged data is not sent again. Cryptomator and rclone crypt upload changed files whole.

### Can I use more than one method in the same bucket?

Yes, in separate folders: a restic repository in one, a crypt folder in another.

**Verdict**

- **Pick by habit**: Cryptomator if you click, rclone crypt if you sync, restic if you back up.
- **Any of the three** turns a PrivateS3 bucket into storage the operator cannot read, from $2.23/TB-month on 12 months.

## Sources

1. [Security architecture](https://docs.cryptomator.org/security/architecture/) — Cryptomator (read 17 November 2026)
2. [Crypt](https://rclone.org/crypt/) — rclone (read 17 November 2026)
3. [References: design](https://restic.readthedocs.io/en/stable/100_references.html) — restic documentation (read 17 November 2026)
4. [Preparing a new repository](https://restic.readthedocs.io/en/stable/030_preparing_a_new_repo.html) — restic documentation (read 17 November 2026)

**Storage for encrypted files: 1 TB for 12 months, $26.77** Bring your own encryption, paid in crypto, no ID. [Get a bucket](https://privates3.com/app/checkout/?plan=s3-1t-12m&product=storage&from=how-to-encrypt-files-before-cloud-upload&lang=en)

---

PrivateS3: PrivateS3 sells S3-compatible object storage billed per terabyte for backups and files (restic, rclone, Veeam, Cyberduck, Nextcloud), meant to be encrypted on the customer's side before upload. A terabyte costs $5.40 a month or $26.77 for 12 months, 10% under the lowest comparable offer read on 17 November 2026, with no API or egress fees up to 3 times the stored size, paid in crypto with no ID document.
