Signal Adds Secure Cloud Backups and Paid 100GB Option

Signal introduces encrypted cloud backups

Signal announced a major change: users can now back up their conversations to the cloud. For the first time, the privacy-first messenger offers a built-in backup path to prevent data loss from lost or broken devices while preserving end-to-end privacy guarantees.

The free tier gives each user 100MB of storage for compressed text messages and includes the last 45 days of media. Signal says 100MB should be enough even for "heavy" message users, as messages are compressed before storage.

For users who want full media history, Signal is launching a paid plan: $1.99 per month for up to 100GB of storage. This is the app’s first paid feature and is billed as a privacy-preserving way to cover storage costs.

Signal secures backups with zero-knowledge encryption. Backups aren’t tied to your account or payment method, and unlocking them requires a 64-character recovery key generated on the device. That key must be saved by the user to recover data.

The feature is rolling out in the Android beta now, with cross-platform availability promised later. Signal also plans to let users store archives wherever they prefer and to enable cross-platform message transfers in future updates.

How does this compare with rivals? WhatsApp already offers optional end-to-end encrypted backups, while Signal historically avoided cloud backups entirely. This change closes a usability gap without abandoning the privacy model that sets Signal apart.

• Benefit: Protects users from data loss when devices fail or are replaced.
• Benefit: Maintains end-to-end privacy through zero-knowledge encryption.
• Benefit: A low-cost paid tier gives power users predictable storage without compromising encryption.
• Trade-off: Users must securely store a 64-character recovery key—losing it may mean losing their backups.
• Trade-off: Even with zero-knowledge safeguards, some metadata about backup timing and size could be observable by providers.

For organizations, adoption requires policy work. Security teams should decide which users are allowed to enable cloud backups, set guidance for recovery-key handling, and define retention or export rules for regulated data. User education is essential: the strongest encryption can’t help if keys are lost or shared insecurely.

Operationally, teams should consider: threat modeling the backup lifecycle, auditing backup storage and access patterns, and integrating backup policies with incident response playbooks. For service providers and nonprofits handling sensitive communications, a clear migration and recovery workflow is critical.

QuarkyByte’s approach is to translate technical guarantees into practical plans: we map encryption claims to compliance requirements, simulate key-loss scenarios, and produce rollout plans that minimize user friction while preserving privacy. That includes cost projections for storage tiers and communication templates that teach users how to secure recovery keys.

Signal’s move narrows the convenience gap with other apps while keeping privacy front and center. The key questions now are about execution: how users store recovery keys, how organizations adapt policy, and how Signal implements cross-platform transfer and user-controlled archives. That will determine whether this change truly balances usability with the strong privacy posture users expect.