admin@likeapro.dev: ~/qr — zsh

// admin tools · 30

QR code generator

Links, Wi-Fi logins, contact cards, email, SMS, phone and map pins — encoded in your browser with a from-scratch ISO/IEC 18004 encoder, exported as crisp PNG or SVG.

// runs locally — nothing is uploaded

options

error correction
module style
centre logo (optional · forces ECC H)

encoded payload


                            
NORMAL local only · 0 bytes sent --:--:--

How it works

What it does

This generator turns a link, a Wi-Fi login, a contact card, an email, an SMS, a phone number or a map location into a QR code, then exports it as a PNG at the size you choose or as a scalable SVG. The encoder is written from scratch to ISO/IEC 18004 (QR Code Model 2) and runs entirely in your browser — nothing you type, and no logo you add, is uploaded.

How to use it

  1. Pick a content type tab and fill in the fields. The preview updates as you type.
  2. Choose an error-correction level, a module style and colours. Dark modules on a light background scan most reliably.
  3. Optionally add a centre logo. Error correction is forced to H so the hidden modules can be rebuilt.
  4. Download a PNG for documents and screens, or an SVG for print, signage and anything that gets scaled.

What the payload formats look like

Wi-Fi
WIFI:T:WPA;S:ssid;P:password;H:false;; — the de facto format read by iOS and Android cameras. \ ; , : " in the name or password are escaped with a backslash.
vCard
vCard 3.0 (RFC 2426) with name, organisation, title, phones, email, website and address. Commas, semicolons and backslashes are escaped.
Email
A mailto: URI with a percent-encoded subject and body (RFC 6068).
SMS
SMSTO:number:message by default, or an RFC 5724 sms: URI.
Phone · geo
tel:+61… and geo:lat,lng (RFC 5870), or an OpenStreetMap link that opens in any browser.

How the encoder works

The text is split into segments using whichever mix of numeric, alphanumeric and byte (UTF-8) modes gives the fewest bits, then the smallest of the 40 versions that fits at your error-correction level is chosen. Data is split into blocks, each protected with Reed–Solomon codewords over GF(256), and the blocks are interleaved so a scratch or logo damages several blocks a little rather than one block fatally. All eight mask patterns are tried and the one with the lowest penalty score — fewest long runs, 2×2 blocks and finder-like patterns, most balanced dark/light ratio — is kept. Format and version information are written last.

The stats panel shows the version, module count, mask, segment modes and how much of the symbol's capacity your data uses.

FAQ

Which error-correction level should I use?

M (about 15% recovery) suits most screens and print. Use Q or H for codes on stickers, outdoor signage or anything that might get scuffed, and H whenever a logo covers part of the code. Higher levels need more modules for the same data, so the code gets denser.

Do these QR codes expire?

No. The content is encoded directly in the image — there is no redirect service or tracking link in between, so the code works for as long as the URL or details inside it are valid.

How big should I print it?

A common rule of thumb is a code width of about a tenth of the scanning distance, and never much under 2 cm. Keep the quiet zone (the plain margin, four modules by spec) and always test-scan the final print with more than one phone.

Why is my coloured or logo code hard to scan?

Scanners need strong contrast between dark and light modules. The tool warns when contrast drops below 4:1, when colours are inverted, or when a logo covers more than about a fifth of the data area.