Losing a recovery phrase with no other copy is the single most common way people lose access to a self custody wallet for good. To cut down on that, several major wallet apps now offer an optional feature that uploads an encrypted copy of your phrase to a cloud service like iCloud or Google Drive. It sounds like it solves the backup problem cleanly. It does, for one specific failure mode, and it does not for another. Knowing the difference is what actually matters here.
Why wallets started offering this
Our guide to keeping your recovery phrase safe recommends writing it on paper and storing that paper somewhere durable. That advice works, but it assumes the user actually does it, and a lot of people do not get around to it before a phone is lost, dropped in water, or stolen. For a wallet provider, every one of those cases turns into a support request from someone who can no longer prove the wallet was ever theirs, because a non custodial wallet has no account recovery path by design. Our article on self custody covers why that tradeoff exists in the first place.
An encrypted cloud backup is an attempt to reduce that specific kind of loss without asking the provider to hold your keys. Coinbase Wallet introduced an option to store an encrypted copy of your recovery phrase in iCloud or Google Drive, and Trust Wallet offers a similar encrypted cloud backup and recovery feature. Both frame it as optional, not a default.
How the encryption actually works
The mechanism in both cases follows the same basic pattern. Before anything leaves your device, the app encrypts the recovery phrase using a key derived from a password you choose, commonly with a strong algorithm such as AES-256-GCM. Only the encrypted file gets uploaded to your personal iCloud or Google Drive storage. The wallet provider does not hold a copy, and Apple or Google, as the storage provider, cannot read the contents either, because they never receive the password or the unencrypted phrase. Without your backup password, the file sitting in your cloud storage is unreadable.
This is a meaningfully different design from simply pasting your recovery phrase into a notes app that happens to sync to the cloud, which our guide on keeping your recovery phrase safe specifically warns against. A synced notes app stores the phrase in plain text wherever it lands. A purpose built encrypted backup does not, as long as the backup password itself is strong and kept separate from the phrase.
The part the encryption does not cover
Here is the catch. The backup file is protected by your backup password, but getting to that file in the first place only requires access to your iCloud or Google account. If someone compromises that account, through a phished password, a reused password found in a data breach, or a SIM swap that lets them reset it, they can see the encrypted file sitting there and then try to guess or phish the backup password separately. The cloud account is not the vault. It is the location of the vault, and a vault sitting in a location an attacker can reach is only as safe as the lock on it.
Our guide to SIM swap attacks covers how attackers take over a phone number specifically to reset accounts like these. The same account that holds your photos and documents, if it also quietly holds an encrypted wallet backup, becomes a more valuable target than it looks.
A real incident worth knowing about
In 2022, MetaMask warned users about a specific version of this problem. Many Apple devices back up app data to iCloud automatically by default, including each app's local storage. For some users this meant a copy of MetaMask's locally stored, password encrypted wallet vault ended up in iCloud without anyone deliberately choosing a cloud backup feature. Attackers who phished a victim's Apple ID password were then able to pull that vault file down and attempt to crack the password offline, at their own pace, with no rate limit from the wallet app itself. MetaMask published guidance on disabling iCloud backups specifically for the app in response.
The lesson is not that any particular wallet is unsafe. It is that an automatic, device level backup you never chose can create the exact same exposure as a feature you opted into on purpose, with none of the deliberate password setup that a dedicated backup flow walks you through. It is worth checking, on your own phone, which apps are included in your device's automatic cloud backup.
A reasonable way to think about this
An encrypted cloud backup, used deliberately with a strong and unique backup password, protects you well against losing a phone, dropping it in a lake, or having it stolen with no other copy of the phrase anywhere. It does very little to protect you against someone who already controls your cloud account, and a cloud account is a more common thing to lose control of than most people assume, since it is often protected by nothing more than a password and a phone number that can be ported away in a SIM swap.
Treat an encrypted cloud backup as one additional layer, not a replacement for an offline copy. Our guide on splitting a recovery phrase with Shamir backup and the simpler approach of writing it down on paper still cover the failure mode a cloud backup cannot: your cloud account itself being compromised. If you do use a cloud backup, turn on two factor authentication for that Apple or Google account specifically, and pick a backup password you have never used anywhere else.
The bottom line
Client side encryption before upload is a real security property, not marketing language. It means the storage provider cannot read your phrase, and that is worth something. But the backup is only as strong as the password protecting it and the account it lives in. Before relying on any cloud backup feature, confirm your cloud account has its own strong, unique password and two factor authentication turned on, and keep at least one copy of your recovery phrase that does not depend on any account being secure at all.