Open-source, fully offline file sharing over QR codes.
Show a stream of QR codes on one screen, scan it with another device, and the file arrives. No internet, no server, no upload. Add a passphrase and it is encrypted too.
Claude Chappe (1763–1805) was a French engineer who built the optical telegraph, first demonstrated in 1792. It was the first practical system for sending messages across long distances by sight.
A line of towers stood on hilltops, each within telescope range of the next. Every tower had movable wooden arms. An operator set the arms to a position that stood for a symbol in a shared codebook. The operator at the next tower read it through a telescope and repeated it. News from the front reached Paris in hours instead of days, and the word telegraph ("far writer") was coined for this system.
This app does the same thing 230 years later. The arms become QR codes, the telescope becomes a phone camera, and the codebook becomes a fountain code. Nothing travels over a wire or a network. The message moves as light.
flowchart LR
subgraph then["1792 · Chappe's optical telegraph"]
direction LR
t1["Tower<br/>arms set to a symbol"] -- "telescope" --> t2["Next tower<br/>reads and repeats"] -- "telescope" --> t3["Paris<br/>decodes with the codebook"]
end
subgraph now["Today · Chappe the app"]
direction LR
s1["Sender screen<br/>QR codes"] -- "camera" --> r1["Receiver phone<br/>decodes with the fountain code"]
end
Cloud sharing hands your file to a third party. Chappe never does. The file is encoded in your browser and read back by the other device's camera. It works with wifi off, so you can check for yourself that the data went nowhere but the lens.
- No upload, no account, no server.
- Optional passphrase: AES-256-GCM (PBKDF2, 210k iterations) before the first code is drawn. The file name and type are encrypted too.
- SHA-256 check on arrival, so a damaged transfer is reported instead of saved.
- Nothing to install on the sending machine. It is a web page.
flowchart LR
subgraph sender["Sender · browser"]
direction TB
f["File or text"] --> z{"Compresses well?"}
z -- yes --> g["gzip"]
z -- no --> p{"Passphrase set?"}
g --> p
p -- yes --> e["AES-256-GCM"]
p -- no --> fe
e --> fe["Fountain encoder<br/>endless blocks"]
fe --> q["One QR code at a time<br/>on screen"]
end
subgraph receiver["Receiver · browser"]
direction TB
c["Camera"] --> d["Peeling decoder<br/>any blocks, any order"]
d --> x["Decrypt and unzip"]
x --> h{"SHA-256 matches?"}
h -- yes --> ok["Save the file"]
h -- no --> bad["Report it as damaged"]
end
q -. "light only, no network" .-> c
The sender never waits for the receiver, and the receiver never talks back. It joins whenever it likes, misses frames freely, and finishes once it has caught enough blocks:
sequenceDiagram
participant S as Sender screen
participant R as Receiver camera
S-)R: manifest (name, size, salt), repeated every few codes
loop until the receiver has enough
S-)R: fountain block n
Note right of R: some frames are missed, the rest still count
end
R->>R: rebuild, decrypt, check SHA-256
Note over S,R: nothing is ever sent from the receiver back to the sender
- Fountain code (LT, systematic). The sender streams an endless set of blocks. The receiver rebuilds the file from any sufficient subset, in any order, so missed frames cost a little time and never stall the transfer.
- One code at a time. A single large QR code changes several times a second, with a full quiet zone, so phone cameras lock on quickly.
- Two decoders. The browser's
BarcodeDetectorwhere it exists (Chrome on Android and macOS), andjsQReverywhere else, including iPhone. - No network, enforced. A
connect-src 'none'Content Security Policy in the production build, plus a runtime guard that refusesfetch, XHR, WebSocket and beacons. - Works offline. A small service worker caches the app on the first visit, so it opens with wifi off and can be installed to the home screen.
bun install
bun dev # http://localhost:5173
bun test # transport, crypto, codec and end-to-end QR tests
bun run typecheck
bun run lint
bun run build # static site in dist/
bun run build:single # dist/chappe.html, the single-file offline copyThe camera and Web Crypto need a secure context: localhost or https. To test
from a phone during development, serve the dev server over https.
bun run build produces a static dist/ folder with no server code. Any
static host with https works: Cloudflare Pages or Vercel with build command
bun run build and output directory dist.
Set your public address in .env (VITE_SITE_URL). The build uses it for the
canonical URL, link previews, robots.txt and sitemap.xml.
Each release includes
chappe.html: the whole app in one file, with no network needed at all. Open
it in a browser, or pass it on over Bluetooth, a USB stick or a memory card.
The release notes list its SHA-256 fingerprint so anyone can check their copy.
To publish a release, push a version tag. A GitHub Action runs the tests, builds the file and attaches it with its fingerprint:
git tag v0.1.0
git push origin v0.1.0Read SECURITY.md for the threat model: what Chappe protects, what an observer can still learn, and how to check that your copy is genuine. Chappe has not had an independent security audit yet.
MIT © 2026 Alok Gupta
- Files up to 5 MB. Larger files work in principle but take minutes to beam.
- Speed depends on the screen, the camera and the light. Start with the defaults.