QR codes, paper-ready.

No. The QR is generated entirely in your browser via JavaScript. Whatever you type — URL, Wi-Fi password, vCard contact info — never leaves your device.

QR codes contain redundant data so they still scan when partially damaged. Level L recovers ~7%, M ~15%, Q ~25%, H ~30%. Higher levels mean more dots in the code (denser pattern). For print, H is safest because the code might survive coffee spills, folds, or scratches.

Because we read it back. After each change the tool renders the code and runs a QR decoder over the pixels, then compares what came out against what you typed. If a colour pair, a narrow quiet zone or an over-long payload produces something a reader cannot resolve, the panel says so rather than handing you a code that fails on a printed menu.

Rule of thumb: 1cm × 1cm minimum for a phone scan from arm's length. 3×3cm for posters scanned from across a room. Bigger always works; smaller might fail in low light. The download-size slider lets you pick the pixel resolution that prints sharp at any physical size.

QR codes have versions 1-40, each with more capacity. Add more text, the encoder picks a higher version with more rows and columns. The pattern becomes denser. You can also drop the error-correction level to fit more text into a less-dense code.

Not in v1 — keep an eye out. With high error correction (Q or H), QR codes can lose ~25% of the dots and still scan, which is how center-logo QRs work. For now, run the result through Add Text to Photo or your design app to drop a logo over the center.

WIFI:T:WPA;S:network;P:password;; — the prefix tells the phone these are Wi-Fi credentials. The catch is that the semicolon and colon are delimiters, so a password containing either has to be escaped with a backslash or the phone reads it short. Type it in the fields here and the escaping is handled: a password of p;a:ss becomes P:p\;a\:ss, which reads back correctly instead of arriving as just "p".