QR Studio

The problem

Most QR generators will happily hand you a code that looks good and does not scan. Heavy styling, a logo dropped in the middle, low contrast or too small a print size will each quietly break a code, and you usually find out after it has been printed.

The solution

A design tool that treats scannability as the actual requirement. Every code is generated, then decoded again by two independent scanner engines at several different pixel sizes before it is given a rating — so the feedback is empirical rather than a guess. Everything runs in the browser, so the encoded content never leaves the machine.

Technical implementation

An E-PATH tool, built because the useful question about a QR code is not “does it look right” but “will it still scan once it has a logo on it and it is printed 20mm wide”.

Technical implementation

Verification, not assumption. This is the part that makes it more than a generator. Every time the design changes, the rendered code is decoded again by two independent scanner engines — jsQR and ZXing — and tested at several sizes, currently 104px, 120px, 152px and 248px. Only then does it get a rating. Because the check runs against the actual rendered output rather than the encoder’s own model of it, styling that genuinely breaks a code is caught, and styling that merely looks risky is not penalised.

The tool also reports the QR version and error-correction level in use, and a recommended minimum print size, so a code intended for print can be checked before it reaches a printer.

Eight payload types — website, contact card, plain text, email, phone, SMS, Wi-Fi and geographic location — each with the right fields and the correct encoding.

Design controls cover nine style presets, six module shapes, separate shape and colour control for the outer frame and inner ball of each corner eye, foreground and background colours with an optional gradient and transparent background, a logo upload, and frame and label treatments. Error correction (L/M/Q/H) and the quiet zone are exposed directly, since they are the settings that actually decide whether a heavily styled code survives.

Export is PNG, SVG, JPEG or PDF at 512px up to 4K. A design can be shared as a link or a file that reloads the whole thing — logo and every style setting included — back into the editor.

Nothing is uploaded. Generation, decoding, verification and export all happen in the browser, so whatever you encode stays on your machine. That is a deliberate design decision rather than a missing backend: a tool people paste Wi-Fi passwords and contact details into should not be sending them anywhere.