Quick guide and practical context
Two modes for two different jobs
The simple mode is designed for short payloads such as links, temporary passwords, Pix payloads, crypto addresses, terminal commands, and compact JSON. The QR itself carries the content or a client-side URL fragment.
The advanced mode handles larger text and files. It uses QR codes only for the initial handshake and then moves the main payload through a WebRTC DataChannel.
When the QR mode is the best choice
If you only need to move something small from one screen to another, QR is the fastest option. It avoids account creation, avoids manual typing, and works well on mobile and desktop.
When content grows beyond practical QR limits, the tool can split it into multiple parts, but larger payloads are usually better served by the P2P mode.
How the WebRTC transfer works
One device creates a WebRTC offer, the other responds with an answer, and both browsers open a direct data channel. Files are sent in chunks so the receiving browser can reconstruct them safely.
This implementation can use STUN for route discovery, but it does not include a TURN relay. That keeps the tool closer to direct transfer, while also meaning some restrictive networks may fail to connect.
Privacy and practical limits
Short-text QR processing stays local in the browser. In P2P mode, the main payload travels through the browser data channel after manual pairing. Network topology still matters, and direct connectivity is not guaranteed on every firewall or NAT setup.
QR capacity is also finite. If a payload becomes too large, splitting or switching to P2P is the correct fallback.