Create QR codes that look yours and stay scan-aware.

The symbol has no built-in expiry. It remains usable while the encoded destination or contact information stays valid and the printed or digital asset remains readable. There is no Motifuse redirect or subscription between the scanner and the content.

Yes. Codes you generate are yours to use on packaging, menus, adverts, signage and anything else, with no attribution, watermark, account or licence.

PDF or SVG for anything a printer will handle — both are vector and stay sharp at any size, and PDF carries an exact physical width. PNG for screens, slides and documents. EPS for older print workflows, remembering it is written with flat colour and no logo. JPEG only where PNG is refused.

About one tenth of the distance it will be scanned from: roughly 20mm on a business card, 45mm on a table card, 120mm on an A3 poster. The Studio computes it exactly for your data — the print check reports the width of a single module in millimetres and names a recommended size, because a long URL needs a larger code than a short one at the same distance.

Yes, with a size guard. A logo erases the modules underneath it, and error correction is what rebuilds them — level H can restore about 30% of a symbol. Because a logo removes one solid block rather than scattered damage, the Studio warns above roughly 16% coverage and blocks export guidance above the level's full budget. It also refuses to call level L with a logo acceptable.

Density is a function of how much you encoded. A long URL at a high error-correction level produces a fine grid that has to be printed larger to scan. The encoded-data check shows how much of the symbol's capacity you are using and how many characters are left before the version — and therefore the grid — steps up.

Not through the code itself: it is a static image with no analytics layer, and Motifuse cannot see it being scanned. If you want scan statistics, encode a URL on a domain you control and measure the visits in your own analytics. The built-in UTM builder tags the link for exactly that.

Treat it as public. A QR code is a visible encoding, not encryption — anyone who photographs the card can read the password out of it in seconds. That is fine for a guest network with no access to your internal machines, and a bad idea for the network your accounts and backups sit on.

No. The symbol is generated in your browser, logos are read into memory rather than uploaded, and the camera scanner reads frames from a canvas in the page. Recent codes are stored in your browser's local storage and are never synced.

Not directly — that needs a hosted redirect, which is what commercial 'dynamic QR' subscriptions are selling. You can get the same result for free: encode a short URL on a domain you own and change where it redirects. The printed code never has to change. The Static versus dynamic section above sets out the whole trade-off.

Because a preview is 400 pixels of backlit screen and a printed code may be 20 millimetres of ink under difficult lighting. High risk means several settings are marginal at once — usually thin contrast, a reduced quiet zone and a small print size together. A code may scan up close yet fail at its intended distance.

Yes. Open the scanner to use your camera, or upload a screenshot or photo. Decoding runs in the page — on browsers with a built-in barcode detector it uses that, and everywhere else it uses the Studio's own decoder. It reports the decoded content, the symbol version and the error-correction level.