Share files (.nt2share)
Last updated: 28 Jun 2026
Mode C—offline transport for vault openers.
Who this is for
Senders and recipients who want fully offline transport—AirDrop, USB stick, corporate file share, or email attachment—without relying on a live HTTPS link.
What you need
| Tier | Free |
| Vault state | Unlocked to create; recipient unlocks to import |
| Network | Not required—encryption and decryption are local |
| Feature toggle | None |
Steps
Create a .nt2share from an asset
- Open the asset → Share → Share file (.nt2share).
- Select fields and attachments to include.
- Set a share passphrase (recommended)—distinct from your master password—or acknowledge no-passphrase mode for low-risk payloads.
- Download .nt2share or use the system share sheet (Share file…).
- Send the file and passphrase (or decryption key when shown) in separate channels.
Create from Send hub
- Go to
https://se.nt2.me/send/file. - Choose any file, set passphrase, Create file.
- Same out-of-band passphrase rules apply.
Recipient import
| Path | Steps |
|---|---|
| Receive → File | https://se.nt2.me/receive/file → select .nt2share → enter share passphrase → view → save to vault or Inbox |
| PWA file handler | Opening .nt2share on installed PWA lands on /receive/file automatically |
| Public import page | Read-only decrypt in browser; unlock vault to persist as an asset |
Local vault on same device
From Receive → File, Send to a vault on this device delivers the artifact to another vault's Inbox without leaving the machine.
Tips and common mistakes
.nt2shareis not.nt2backup—share files carry one handoff; backups migrate the whole vault (Backup export and import).- Share passphrase ≠ master password—treat the passphrase like a one-time wire transfer code.
- Large attachments increase file size—prefer field selection on structured assets.
- Fragment-key mode splits file and key—both pieces are required.
- After import, the sender cannot remotely delete your copy—hosted link revoke does not apply to files you already saved.