A real, scannable QR assembling module by module while a laser line sweeps down the tile.
The ask a camera answers rather than a tap, for the end of a video where the link cannot be a link. The code is generated from whatever address you put in the field — modules edge to edge, error correction at the level that survives being filmed off a screen — so the thing on screen is the thing that scans. Keep the destination short and worth the effort of picking up a phone; a QR pointing at a home page is a QR nobody scans twice.
The code is generated from whatever address you put in the link field, so keep the destination short and worth picking up a phone for. A QR pointing at a home page is a QR nobody scans twice. The kicker is the instruction and the headline the reason. The sweep colour is the laser line.
QR Scan is built at 640 × 360, a 16:9 landscape frame, the shape of a YouTube video, a stream layout and most editing timelines, and runs 3 seconds at 30 frames per second. It arrives in 0.2 seconds, holds for 2.0 and clears in 0.8, so cue it a beat before the moment it labels. Export it as an MP4 for a timeline or a feed, a GIF where video will not embed, or a MOV with an alpha channel to lay it over footage with nothing behind it. Renders go up to 4K, and the free plan exports at 720p with a watermark.
Yes. It is built module by module from your link at an error-correction level that survives being filmed off a screen. Test it once from the exported video before you publish.
No. A phone cannot scan its own screen. Use the link-in-bio card there and save the QR for content watched on a screen that is not the viewer's phone.
