QRL WEB — SENDER

CHUNK SIZE (BYTES) ?

Payload bytes per QR frame. Smaller = more reliable codes; larger = fewer total frames. 400–600 B suits most setups — reduce if codes are failing to scan.

FPS ?

Target frames per second. Higher FPS transfers faster but the receiver camera must keep up. 3–5 fps is reliable; go higher only in good lighting conditions.

ERROR CORRECTION ?

Reed-Solomon redundancy baked into each QR code. Higher levels recover from more scan noise but shrink usable payload per frame. L is fine in good lighting; use M–H if scanning is unreliable.

QR SIZE (PX) ?

Rendered canvas size in pixels. Larger makes it easier to scan from a distance. 420–600 px suits most screens; go bigger if the receiver struggles to focus.

FRAMES PER CHUNK ?

How many consecutive frames each chunk is held before advancing. Set to 2–3 if the receiver is missing many chunks at your current FPS. ETA scales proportionally.

FOUNTAIN MODE ?

Generates infinite XOR-coded packets instead of sequential chunks. The receiver decodes the full file from any sufficient subset — no manual replay needed. Best for poor or intermittent scanning.

Select a file and press
Start Transfer —
QR codes appear here