NT² Vault
EN

Cloud attachment backup

Last updated: 28 Jun 2026

Premium—requires cross-device sync.

Who this is for

Premium users with cloud sync enabled who store files alongside assets—PDFs, images, key exports—and need ciphertext blobs on other devices without re-uploading manually.

What you need

TierNT² Premium with sync enabled
Vault stateUnlocked during upload/download
NetworkOnline; large files may take time on slow links
Feature toggleCloud sync on (https://se.nt2.me/settings/vault/sync)

Steps

How attachment sync relates to item sync

  1. Item metadata (filename, size, mime, encryption IV) lives in per-vault SQLite asset_attachments.
  2. Ciphertext bytes live in local BlobStore (browser OPFS vaults/{vaultId}/attachments/*.bin or Tauri files).
  3. When sync runs, NT² pushes/pulls encrypted blobs to Cloudflare R2 keyed by your Vault Key DID session—same blind model as item replicas.

Upload after adding attachments

  1. Add or replace an attachment on an asset (Attachments guide).
  2. Trigger Sync now on Cloud sync settings—or wait for the automatic attachment pass after item push.
  3. Other devices pull missing blobs on their next sync; decryption uses your local vault key after unlock.

Confirm on a second device

  1. Unlock the same vault replica on device B (bootstrap + password, or enrolled device).
  2. Ensure Cloud sync is enabled and Premium active.
  3. Open the asset; NT² downloads the R2 object on demand or during sync prefetch. Offline mode uses already-fetched blobs only.

Disable or remove attachments

  1. Deleting an attachment locally creates a tombstone in the next replica batch.
  2. Sync propagates deletion metadata; R2 garbage collection is server-side—local delete does not instantly purge all cloud copies.
  3. Disabling sync on one device does not remove blobs already stored in R2.

Tips and common mistakes

  • Attachment sync requires item sync—there is no standalone “attachments only” cloud tier.
  • Initial enable pushes item batches without embedding all blobs in one giant file; attachments stream in follow-up operations.
  • Keep offline .nt2backup exports—R2 is a convenience replica, not your only disaster copy.
  • Large vaults: sync on Wi‑Fi; metered mobile may charge for upload/download volume NT² cannot meter for you.

Related