S3-compatible storage per TB · no API fees · encrypt before upload · pay in BTC, USDT, USDC, ETH, SOL, LTC, XMR
Get storage

Tutorial · rclone crypt · 6 steps · checked 17 November 2026

How do I set up rclone crypt with S3?

Last updated: · 4 min read

Quick answer

How do I set up rclone crypt with S3?

Create an S3 remote for the bucket, then a crypt remote that wraps a folder of it, such as privates3:BUCKET/crypt. Copy files through the crypt remote and rclone encrypts names and contents first. On a PrivateS3 bucket, $2.23/TB-month on 12 months, the operator then sees only scrambled names and sizes.

In brief
  • Two remotes: privates3 (type s3) stores; secret (type crypt) encrypts and points into it.
  • Cipher: NaCl SecretBox (XSalsa20 and Poly1305); key from scrypt, per rclone's docs.
  • Still visible: file length (to within 16 bytes) and modification time.
  • Lose the password, lose the files: PrivateS3 cannot recover it.

What does each crypt setting change?

rclone crypt options that matter on an S3-compatible bucket, their choices and the value used in this guide
SettingChoices (per rclone.org/crypt)This guide
remoteAny remote and pathprivates3:BUCKET/crypt
filename_encryptionstandard, obfuscate, offstandard
directory_name_encryptiontrue, falsetrue
passwordYour own or generatedGenerated, stored in a password manager
password2 (salt)OptionalGenerated

Step 1: how do you add the S3 remote?

Run rclone config, choose n for a new remote, type s3, then provider Other. Enter the access key, secret key, region and endpoint. The endpoint and region are shown with the keys in the client area. The result in rclone.conf looks like the block below; the rclone page explains each line.

S3 remote in rclone.conf
[privates3]
type = s3
provider = Other
access_key_id = ACCESS_KEY
secret_access_key = SECRET_KEY
region = eu-central-1
endpoint = https://s3.privates3.com

Step 2–3: how do you add the crypt remote and its password?

Run rclone config again, create a remote named secret of type crypt, and point it at a folder of the bucket. The rclone crypt docs advise wrapping a specific bucket rather than the root of the S3 remote, so the bucket name itself stays readable and valid.

Keep standard file name encryption and directory name encryption on. Let rclone generate the password and the salt, then copy both to a password manager before you continue. Rclone's docs say content written with one password cannot be read after the password changes.

Crypt remote as rclone writes it
[secret]
type = crypt
remote = privates3:BUCKET/crypt
filename_encryption = standard
directory_name_encryption = true
password = *** ENCRYPTED ***
password2 = *** ENCRYPTED ***

Step 4–5: how do you upload and check what the bucket sees?

Copy through secret:, then list the same folder through privates3: to see the ciphertext. Through secret: you see normal names; through the raw S3 remote you see scrambled names. That second view is what PrivateS3 holds. Without client-side encryption, the operator can technically read stored files, file names and sizes; with it, the operator sees only encrypted blobs, their sizes and upload times.

Upload, then compare the two views
rclone copy ~/Documents secret:documents --progress

rclone ls secret:documents        # readable names
rclone ls privates3:BUCKET/crypt   # scrambled names, as stored

rclone cryptcheck ~/Documents secret:documents

Step 6: how do you protect the rclone config itself?

Set a configuration password, because rclone only obscures the crypt password in rclone.conf. The crypt docs say the stored password is lightly obscured, not encrypted, and recommend encrypting the whole config. In rclone config, choose s to set a configuration password. The encryption how-to compares crypt with Cryptomator and restic.

Use rclone cryptcheck, not rclone check, to verify uploads: the docs explain that plain check cannot compare hashes through encryption. According to PrivateS3's survey of 17 November 2026, the API calls this check sends are billed at some sellers, such as Amazon S3 at $0.005 per 1,000 LIST requests; at PrivateS3 they are free.

rclone crypt on S3: common questions

Can I add crypt to files already in the bucket?

No, crypt only reads what it wrote. Copy the plain files through the crypt remote, check them, then delete the plain copies.

Can another computer read the encrypted files?

Yes, with the same crypt settings, password and salt in its rclone.conf.

Does crypt hide file sizes?

No. Rclone's docs say file length can be worked out to within 16 bytes, and modification times stay readable.

Can I mount the crypt remote?

Yes: rclone mount secret: /mnt/secret shows decrypted files while they stay encrypted in the bucket.

Should I use obfuscate instead of standard?

Standard is stronger. Rclone describes obfuscate as very simple name obfuscation, useful only when names must stay short.

Verdict
  • Six steps put rclone crypt between your files and the bucket: PrivateS3 then stores only scrambled names and contents.
  • Back up the password and salt before the first upload; read why on the encrypted storage page.
Sources (3)
  1. Crypt — rclone (read 17 November 2026)
  2. Amazon S3 Storage Providers — rclone (read 17 November 2026)
  3. Amazon S3 pricing aws.amazon.com/s3/pricing — Amazon Web Services (read 17 November 2026)

A bucket for rclone crypt: 5 TB for 12 months, $133.87

No fee for LIST or cryptcheck calls, paid in crypto.

$5.40/TB-month · no KYC

Get storage