How it worksSecure sharing

Secure file sharing between iPhone and Android

Share encrypted files or a vault snapshot with a separate secret. Keep your personal vault keys private across iOS and Android.

Download RevaultSecurity model
Illustrative preview. Screens vary by platform.

A passport scan for a family member. Personal photos for your partner. Documents for someone helping you move. Share the files they need without giving them the pattern or recovery key to your own vault.

A separate key for every share

Revault creates a new share key and secret on your device. By default, it wraps only the selected file-version keys under that share key and transfers their existing encrypted contents. This avoids re-encrypting large files while keeping your vault master key private. Extra isolation can create fresh encrypted file contents when you choose it.

One invitation, a private secret

Send the invitation link to your recipient, then pass the decryption secret through a separate private channel. The link opens Revault’s shared-vault flow. Recipients enter that secret, without your personal pattern or a Revault account, and see an isolated shared vault.

Choose the right sharing route

Controlled shares use Revault’s server on both platforms, including iPhone-to-iPhone when you need access limits or expiry. iOS also offers private, read-only CloudKit invitations between Apple accounts. Those CloudKit invitations do not enforce access counts or automatic expiry.

Share a snapshot, keep your private organization

Recipients receive the files captured when you create the share. Later edits to your source vault are not synced into it. Folder membership, tags, and favourite status are omitted from the shared file metadata. Deleting the original file does not revoke the separate share; manage the invitation itself.

The recipient needs a share secret, not access to your vault

A sharing invitation identifies an encrypted snapshot and the right to request it; the separate secret decrypts its contents. Your own vault pattern and recovery phrase are not part of that handoff. The recipient opens an isolated shared vault rather than browsing your personal collection. Verify the person receiving the secret, because anyone who obtains the required invitation material can potentially use the remaining access.

Choose controlled sharing or an Apple-only invitation

Use the server route for iPhone–Android and Android–Android sharing, and for iPhone–iPhone shares that need expiry, session limits or a first-access timer. The optional CloudKit route is a private read-only invitation between Apple accounts; it does not provide those server-enforced deadlines or counters. Choose based on the controls needed for this handoff, not simply the phone brand of the sender.

Example: share one document without sending the whole vault

A trusted person needs a lease copy for a short task. Select the lease rather than unrelated files, review its filename and visible information, then choose the required deadline and export permission. Send the invitation by message and communicate the secret through a separate private conversation. Ask the recipient to confirm they can read the needed pages. Revoke the invitation when the task ends if access should stop earlier.

Practical checklist

  • Review the selected file contents, filename and metadata before creating the snapshot.
  • Send the invitation and secret separately; never substitute your vault recovery phrase.
  • Use separate invitations for recipients who need independent access counters or deadlines.

Frequently asked questions

What happens when someone opens the invitation on a computer?

The website provides a QR code for the mobile shared-vault flow. Scan it with the intended phone and open Revault, then enter the separately supplied secret. The invitation does not turn the desktop browser into an unlocked personal vault.

Do later edits to my source document appear in the share?

No. Sharing captures a snapshot. A later rename, edit or metadata cleanup in your personal vault does not update that copy. Create a fresh invitation for a changed document and revoke the older one when appropriate.

Why offer Extra share isolation?

The normal route rewraps selected file-version keys while reusing encrypted bytes for efficient sharing. Extra isolation encrypts a fresh copy so matching ciphertext cannot link the source and share at storage level. It needs more preparation time and temporary space, without changing the need to trust the recipient.

Keep exploring

Put this into practice in your vault

Choose the settings that fit your files, and keep a recovery plan before you rely on a single device.

Download Revault

Secure sharing guides

How to share files securely between iPhone and AndroidExpiring file links and self-destructing shared vaults explained
Secure sharing

Share a file. Keep your vault private.