CLOUD BACKUP & PHOTO LIBRARIES
The crypt layer encrypts files before they reach another rclone remote. The storage account remains necessary, but its password alone cannot unlock your encrypted collection.
Quick answer
Create a normal remote, wrap a dedicated folder with a crypt remote and use the crypt name for uploads and restores.
Steps to follow
-
Before you start
Keep the original data available while following this procedure. Record the application version, account, source path and destination you are actually using. If an error is involved, save its exact wording. Use a small, non-sensitive sample first so that an unexpected result is easy to inspect without disturbing your working library.
-
Set up the right scope
In rclone config, configure and test the underlying storage first. Allocate an empty folder or prefix for encrypted files so ordinary files and ciphertext are not mixed.
-
Apply the relevant settings
Create another remote of type crypt pointing to that dedicated location. Choose filename encryption deliberately. Save both crypt passwords and the configuration securely; a lost encryption secret is not recovered by resetting the provider login.
-
Complete the first run
Upload a small sample with rclone copy /path/sample cryptname:test, then copy it back from cryptname:test to an empty local folder. Access through the underlying remote shows ciphertext rather than your ordinary filenames and contents.
Decisions and checks
The limitation that matters
Do not change crypt passwords on an existing collection expecting old files to be re-encrypted automatically. The crypt layer supplies encryption, not historical versions or protection from a sync command’s deletions.
How to verify the result
Open the recovered sample. Where the backend supports suitable checksums, use cryptcheck for an additional integrity comparison; also test access using the saved recovery configuration.
Keep the result reliable
After the first successful check, repeat the process with an ordinary working session or scheduled run. Record the date and the recovery location. Revisit the setup after changing devices, accounts, storage paths or software versions; yesterday’s successful job does not prove that a new configuration is covered.
Compare the options
| Situation / component | Purpose / action | What to check |
|---|---|---|
| Input | Preserve an unchanged sample | Know which account and location contain the original |
| Operation | Follow the procedure for your installed version | Review errors and skipped items, not only the completion message |
| Result | Open the resulting file or test the documented recovery route | Confirm that the content, version and access rights are correct |
Frequently asked questions
Can I remove the original immediately?
Keep it until you have verified the intended result and have an independent recovery copy where the data matters. A visible file name, a green icon or a completed task alone does not show that every needed item is recoverable.
What information helps if this fails?
Record the version, exact error, affected file type, available space and whether the same small sample works elsewhere. Share sanitized details through the official support route; passwords, recovery keys and private documents are not needed for an initial diagnosis.
Official documentation
This guide combines current official documentation with practical recovery checks. It does not claim hands-on testing of your installation. Menu labels and supported procedures can vary by release; follow the documentation for your installed version.