Mic Suspended Return to this tab to resume

Drop to Beam

Release to encrypt & chirp.

chirpfile

Tap to Listen

Enable mic to receive, or drop a file anywhere to send.

Upgrade to Pro

Unlock power-user features for professional workflows.

Send files up to 1 GB
Batch transfer multiple files via auto-zip
Keep files available for 15 minutes
Subscribe · $2.99/mo

Instantly beam files to your Corporate Laptop. Windows Rig. iPhone. Android Phone. MacBook. iPad. Teammate. Corporate Laptop.

Secure, zero-knowledge proximity transfers. No USBs. No WiFi pairing. No Bluetooth handshakes. No cloud logins.

Works Across Any Two Devices

Mac to Windows, phone to tablet, personal to corporate. Devices don't need to share a network, account, or OS. Just open a tab, drop your file, and let the WebAudio API do the rest.

No Key Ever Leaves the Room

Files are encrypted right on your device using military-grade AES-GCM cryptography. The key is transmitted as a brief sound wave. If the receiving device isn't physically present to hear it, the file remains mathematically impossible to crack.

The Server Never Sees Your Files

Every file you send is routed through our relay server as a blind, encrypted blob. Once the receiver catches the audio key and unlocks the file, the blob is instantly deleted from our servers.

Under the Hood

Algorithm & Protocol

chirpfile uses ggwave, a specialized library for Data-over-Sound (DoS). It encodes the AES decryption key into audio samples using Frequency-Shift Keying (FSK).

  • Audio Protocol: High-frequency whistle (~7–15 kHz) or Ultrasound (inaudible to adults).
  • Encryption: AES-GCM via the Web Crypto API, entirely in-browser.
  • Limitation: Requires a functioning microphone and speaker. Loud environments may require switching from Ultrasound to the 'Audible' protocol.

Built on Open Primitives

chirpfile is built entirely on independently verifiable, open-source primitives. Our moat isn't proprietary math, it's the frictionless UX tying it all together. Feel free to "Inspect Element" to watch the network tab, or verify the core audio protocol on GitHub.