QR Code Generator — Text, URL, WiFi & vCard to PNG / SVG

Real-world use cases

• WeChat follow QR on a printed flyer

  You're producing 5,000 flyers and want a "scan to follow our WeChat" QR on the corner. Generate the QR from your official account URL at 512 px PNG, drop it into InDesign at ~25 mm square (about 1 inch). Before sending to print, do the actual test: tape one flyer to a wall, walk back 50 cm with your phone — if it scans on the first try, you're fine. Most print shops downsample art under 300 DPI, so generate at 2x the final size and let the RIP scale down. Black on white only; coloured backgrounds drop scan rate by 30%+ even when the contrast looks fine on screen.

• vCard QR on the back of a business card

  One scan, the contact lands in the other person's phone without typing. Use vCard mode, fill name + phone + email + company + title + website. Keep it tight — vCard payloads over ~600 characters push the QR past version 10, which makes the modules tiny and unscannable at typical card sizes (2-3 cm square). Skip the photo field, skip the long bio. Pick error-correction M, foreground black, background white, print at 600 DPI minimum. Hand the card to a colleague before the print run and watch them try it.

• WiFi QR taped to the cafe counter

  Guests scan, phone auto-joins, no asking "what's the password?" for the 40th time today. Use WiFi mode, fill SSID + password, pick WPA / WPA2 / WPA3 (this is what 99% of routers use). The tool emits `WIFI:T:WPA;S:YourSSID;P:yourpass;;` with proper escaping for special characters. Print at A6, laminate, stick on the wall. Tip: put it within arm's reach of where people sit down, not by the door — phones lock between counter and table.

• Single-use check-in QR for an event

  Each ticket holder gets a QR whose payload encodes a server- signed token plus a timestamp: `https://evt.example.com/c?t=abc123&ts=1716700000`. At the door, your scanner hits the URL, the server marks the token used, and returns "valid / already used / expired". This stops resale and screenshot-forwarding cold. Generate the QRs server-side at PDF rendering time so each ticket is unique; this tool is for the design mock or the one-off VIP pass, not the bulk run.

• Product traceability QR on outer packaging

  Each carton gets a QR linking to a product page that includes the batch number: `https://brand.com/p/sku-7788?batch=2026-W21-A`. End customers scan to verify authenticity and see manufacturing date; QC scans the same code to pull batch history. Print at 15 mm square minimum on a flat surface (avoid the seam of the carton — folds destroy QR modules). Use error-correction Q so a scuff during shipping doesn't kill the scan.

Common pitfalls

• Stuffing too much content (over 1,000 characters) into one QR. The module density rockets up, the visible squares get tiny, and budget Android cameras stop reading it. Shorten the URL via a redirector and encode the short link instead.

• Designers swap the centre of the QR for a logo and accidentally cover the timing patterns or finder patterns. Some phones will still read it, many won't. Keep the logo under 30% of total area and crank error-correction to H so the surrounding modules can rebuild what's hidden.

• Printing the QR too small (under 2 cm square) or with weak contrast (grey background, white modules). Real-world scan distance drops to almost touching the paper. Before sending to print, render at the actual final size, print one on an office printer, and try scanning from 30 cm away.

Privacy