How Beamcode QR file transfer works
Learn how Beamcode beams multi-file, end-to-end encrypted transfers via QR or link on Cloudflare’s edge. AES-256-GCM, any network, no same-Wi‑Fi requirement.
Choose files to beam
Pick one file, many files, or a folder. Beamcode supports multi-file transfers as separate files or an optional zip package — useful for phone-to-phone handoffs and desk-to-laptop shares.
Encrypt end-to-end
AES-256-GCM runs in the browser before upload. The encryption key stays in the URL fragment (#k=…) or compact QR — the server stores ciphertext only, never the key.
Show a QR or share a link
Receivers scan the QR code, upload a saved QR image on /scan, or open the short-lived link. Use Anywhere for any network, or Nearby when both devices are on the same Wi‑Fi. Share the QR to WhatsApp, Telegram, and other networks from a live Anywhere beam. Optional 8-digit room PIN helps when camera scanning is awkward.
Download and decrypt on the other device
The receiver decrypts in the browser and saves the files. You can set lifetimes, max downloads, auto-delete, and watch open or delivery receipts while the beam is live.
Security model in plain language
- Ciphertext lands in Cloudflare R2 for Anywhere beams; keys stay client-side in #k=…
- Nearby mode sends file bytes device-to-device (WebRTC); the server only sees short connection messages
- Download tickets are short-lived and HMAC-signed
- Optional password gate, rate limits, and Turnstile abuse controls
- Auto-delete can purge after the last package download
Ready to try? Open the QR file transfer send page, scan a QR code, or read the Beamcode FAQ.