QR codes have moved from novelty to infrastructure. Restaurant menus, payment systems (DuitNow QR, GrabPay), event tickets, Wi-Fi sharing, contact cards, marketing campaigns — all encode their data into a square pattern that any modern phone camera can read in under a second. A QR generator turns a URL, text, or structured data into the image you can print or display.

This guide covers QR code basics, what to encode, the design considerations, and the practical points that determine whether scans succeed.

What QR Codes Encode

  • URLs — Most common; opens website on scan
  • Plain text — Displayed to scanner
  • Contact card (vCard) — Saves contact to phone
  • Wi-Fi credentials — Connects phone to network without typing
  • Email — Opens compose with prefilled address/subject
  • SMS — Opens compose with prefilled number/message
  • Phone number — Opens dialler
  • Geolocation — Opens map at coordinates
  • Payment — DuitNow QR encodes merchant payment details

Common Use Cases

  • Restaurant menus (post-COVID standard)
  • Event check-in tickets
  • Marketing — print to landing page
  • Wi-Fi sharing in cafes, offices, homes
  • Business cards with vCard or LinkedIn
  • Product packaging linking to documentation
  • Museum displays linking to extended info
  • DuitNow QR payment

Error Correction Levels

  • L (Low) — ~7% recovery; smallest code
  • M (Medium) — ~15%; common default
  • Q (Quartile) — ~25%; for branded codes with logo overlay
  • H (High) — ~30%; maximum damage tolerance

Higher correction = larger code but readable even when partially damaged or covered.

Design Considerations

  • Size — Print at least 2×2 cm; larger for distance scanning
  • Contrast — Dark code on light background; reverse can work but is less reliable
  • Quiet zone — Margin around code (4 modules wide) needed for scanning
  • Logo in centre — Possible with Q or H correction; keep small
  • Colour customisation — Brand colours fine if contrast preserved
  • Rounded corners / fancy patterns — Possible; test scan from multiple devices

Print Considerations

  • Print at 300 DPI minimum
  • Test scan from final printed material before mass production
  • Matte finish scans better than reflective glossy
  • Account for ink bleed on cheap paper

URL Considerations

  • Shorter URL = simpler, more reliable code
  • Use URL shortener (bit.ly, your own) for long destinations
  • Use https not http
  • Track scans with UTM parameters or shortener analytics
  • Have a fallback if destination URL changes

Common Pitfalls

  • Code too small to scan. Minimum 2×2 cm for arms-length scanning
  • No quiet zone. Border too tight; scanners fail
  • Low contrast. Subtle colours don't read on phone cameras
  • Logo too large. Blocks essential pattern data
  • URL changes after printing. Use redirector you control
  • Glossy lamination. Reflections defeat scanners
  • Not tested. Always scan with multiple phones before production

Security Considerations

  • QR codes can encode anything — including malicious URLs
  • Users can't visually verify a QR's destination
  • For payment QR codes, ensure tamper-resistant placement
  • Don't scan random QR codes from untrusted sources

Quick Tips

  • Use M or Q error correction for branded codes
  • Minimum 2×2 cm print size; bigger for distance
  • Maintain quiet zone around the code
  • Test scan with multiple phones before printing
  • Use URL redirector so destination can be updated post-print

Use the QR Generator on Popupnote

The QR Generator on Popupnote provides a clean tool for creating QR codes from URLs, text, vCards, Wi-Fi credentials, and more — for restaurants, marketers, events, businesses, and personal use. The tool runs in your browser without any account required.