# QR Code Examples: What They Look Like and What Data They Hold

> Real QR code examples with raw payloads for URL, Wi-Fi, email, phone, SMS, WhatsApp, payment, business card, menu, and event check-in use cases.

Canonical: https://fast-qr.app/learn/qr-code-examples
Last updated: 2026-05-26

Author: [Rehan Haider](https://fast-qr.app/author/rehan-haider)
Published: 2026-05-26
Tags: qr, examples, payload, url, wifi, menu, vcard, whatsapp

QR codes are everywhere on menus, receipts, packaging, and posters, but most people have never seen what the inside of one actually looks like. The pattern is the visible part. The payload — the string of characters the camera decodes — is the part that decides what happens after the scan. A URL opens a browser. A Wi-Fi string joins a network. A `tel:` link opens the dialer. The visual is the same square grid of dark and light modules either way.

<figure id="wall-of-codes" style="margin: 1.5rem auto; max-width: 720px;">
  <img src="https://fast-qr.app/images/learn/qr-code-wall-of-codes-hero.svg" alt="A wall of nine QR codes for different payload types — URL, Wi-Fi, menu, payment, WhatsApp, vCard, ticket, SMS, phone — all sharing the same square pattern with three corner finder squares." loading="lazy" decoding="async" style="width: 100%; max-width: 720px; height: auto;" />
</figure>

This guide collects real, working examples of every common QR code type. Each example shows what the code looks like, the literal encoded payload, the generator route on Fast QR that creates one, and the practical notes that decide whether to ship PNG or SVG, where to place it, and what failure modes to watch for. If you have ever wondered "what does a QR code look like" or "what information is inside a QR code," this is the visual reference.

## Key takeaways

- **A QR code is a square grid plus three corner squares.** The three large nested squares are finder patterns that orient the scanner; everything else carries data and Reed-Solomon parity. The visual is independent of the payload — a URL QR and a Wi-Fi QR look identical to the eye.
- **Eleven payload types cover almost every business use case.** URL, Wi-Fi, email, phone, SMS, WhatsApp, payment link, vCard business card, restaurant menu, event check-in, and plain text are the patterns you will actually encounter.
- **Two codes can look different and decode to the same data.** Eight masking patterns, four error correction levels, color choices, module shapes, and embedded logos all change appearance without changing the payload.
- **PNG is fine for digital and small print; SVG scales to billboards.** The decision is about output medium, not about the QR data inside.

## What every QR code has in common

Before the type-by-type examples, here is the structural template every QR code follows. Once you can spot these regions in any code, the differences between use cases become obvious.

<figure style="margin: 1.5rem auto; max-width: 720px;">
  <svg role="img" viewBox="0 0 720 360" xmlns="http://www.w3.org/2000/svg" style="width: 100%; max-width: 720px; height: auto;">
    <title>QR code visual anatomy with reading order</title>
    <desc>A labelled QR code with the three corner finder patterns highlighted in red, the timing patterns highlighted in green, the alignment pattern highlighted in yellow, the quiet zone marked around the edge, and the central data area in dark blue. Numbered call-outs show the four-step reading order: detect finders, square the grid, sample modules, repair via parity.</desc>
    <rect width="720" height="360" fill="#FAF7F0"/>
    <text x="360" y="26" text-anchor="middle" font-family="system-ui, sans-serif" font-size="14" font-weight="700" fill="#081e32">Anatomy a scanner sees — regardless of payload</text>
    <g transform="translate(40,50)">
      <rect width="280" height="280" fill="#F2EDE2" stroke="#E8E2D9"/>
      <rect x="30" y="30" width="220" height="220" fill="#FFFFFF"/>
      <g fill="#00476b">
        <rect x="100" y="40" width="10" height="10"/><rect x="130" y="40" width="10" height="10"/>
        <rect x="160" y="40" width="10" height="10"/><rect x="200" y="40" width="10" height="10"/>
        <rect x="100" y="60" width="10" height="10"/><rect x="140" y="60" width="10" height="10"/>
        <rect x="170" y="60" width="10" height="10"/>
        <rect x="110" y="80" width="10" height="10"/><rect x="150" y="80" width="10" height="10"/>
        <rect x="190" y="80" width="10" height="10"/>
        <rect x="100" y="100" width="10" height="10"/><rect x="140" y="100" width="10" height="10"/>
        <rect x="180" y="100" width="10" height="10"/><rect x="210" y="100" width="10" height="10"/>
        <rect x="120" y="120" width="10" height="10"/><rect x="160" y="120" width="10" height="10"/>
        <rect x="200" y="120" width="10" height="10"/>
        <rect x="100" y="140" width="10" height="10"/><rect x="130" y="140" width="10" height="10"/>
        <rect x="170" y="140" width="10" height="10"/><rect x="210" y="140" width="10" height="10"/>
        <rect x="110" y="160" width="10" height="10"/><rect x="150" y="160" width="10" height="10"/>
        <rect x="190" y="160" width="10" height="10"/>
        <rect x="120" y="180" width="10" height="10"/><rect x="160" y="180" width="10" height="10"/>
        <rect x="200" y="180" width="10" height="10"/>
        <rect x="100" y="200" width="10" height="10"/><rect x="140" y="200" width="10" height="10"/>
        <rect x="170" y="200" width="10" height="10"/><rect x="210" y="200" width="10" height="10"/>
      </g>
      <rect x="30" y="30" width="60" height="60" fill="#00476b"/>
      <rect x="40" y="40" width="40" height="40" fill="#FFFFFF"/>
      <rect x="50" y="50" width="20" height="20" fill="#00476b"/>
      <rect x="190" y="30" width="60" height="60" fill="#00476b"/>
      <rect x="200" y="40" width="40" height="40" fill="#FFFFFF"/>
      <rect x="210" y="50" width="20" height="20" fill="#00476b"/>
      <rect x="30" y="190" width="60" height="60" fill="#00476b"/>
      <rect x="40" y="200" width="40" height="40" fill="#FFFFFF"/>
      <rect x="50" y="210" width="20" height="20" fill="#00476b"/>
      <rect x="180" y="180" width="40" height="40" fill="#00476b"/>
      <rect x="190" y="190" width="20" height="20" fill="#FFFFFF"/>
      <rect x="195" y="195" width="10" height="10" fill="#00476b"/>
      <g fill="#00476b">
        <rect x="100" y="90" width="10" height="10"/><rect x="120" y="90" width="10" height="10"/>
        <rect x="140" y="90" width="10" height="10"/><rect x="160" y="90" width="10" height="10"/>
        <rect x="180" y="90" width="10" height="10"/>
        <rect x="90" y="100" width="10" height="10"/><rect x="90" y="120" width="10" height="10"/>
        <rect x="90" y="140" width="10" height="10"/><rect x="90" y="160" width="10" height="10"/>
        <rect x="90" y="180" width="10" height="10"/>
      </g>
      <g fill="none" stroke-width="2" stroke-dasharray="4 3">
        <rect x="26" y="26" width="68" height="68" stroke="#b04a3a"/>
        <rect x="186" y="26" width="68" height="68" stroke="#b04a3a"/>
        <rect x="26" y="186" width="68" height="68" stroke="#b04a3a"/>
        <rect x="176" y="176" width="48" height="48" stroke="#a07000"/>
        <rect x="95" y="86" width="100" height="14" stroke="#4a7c59"/>
        <rect x="86" y="95" width="14" height="100" stroke="#4a7c59"/>
      </g>
    </g>
    <g font-family="system-ui, sans-serif">
      <line x1="320" y1="80" x2="385" y2="60" stroke="#b04a3a" stroke-width="1.2" stroke-dasharray="3 2"/>
      <text x="395" y="58" font-size="13" font-weight="700" fill="#b04a3a">Finder patterns (×3)</text>
      <text x="395" y="74" font-size="11" fill="#4a6070">Camera locks onto these first</text>
      <line x1="100" y1="190" x2="385" y2="110" stroke="#a07000" stroke-width="1.2" stroke-dasharray="3 2"/>
      <text x="395" y="108" font-size="13" font-weight="700" fill="#a07000">Quiet zone</text>
      <text x="395" y="124" font-size="11" fill="#4a6070">≥4-module blank margin — required</text>
      <line x1="200" y1="140" x2="385" y2="160" stroke="#4a7c59" stroke-width="1.2" stroke-dasharray="3 2"/>
      <text x="395" y="158" font-size="13" font-weight="700" fill="#4a7c59">Timing patterns</text>
      <text x="395" y="174" font-size="11" fill="#4a6070">Set module spacing</text>
      <line x1="220" y1="220" x2="385" y2="210" stroke="#a07000" stroke-width="1.2" stroke-dasharray="3 2"/>
      <text x="395" y="208" font-size="13" font-weight="700" fill="#a07000">Alignment pattern</text>
      <text x="395" y="224" font-size="11" fill="#4a6070">Corrects tilt and curve</text>
      <line x1="180" y1="160" x2="385" y2="262" stroke="#00476b" stroke-width="1.2" stroke-dasharray="3 2"/>
      <text x="395" y="260" font-size="13" font-weight="700" fill="#00476b">Data + parity</text>
      <text x="395" y="276" font-size="11" fill="#4a6070">Payload plus Reed–Solomon recovery</text>
      <rect x="390" y="300" width="280" height="40" fill="#F2EDE2" stroke="#E8E2D9" rx="4"/>
      <text x="400" y="318" font-size="11" font-weight="700" fill="#081e32">All QR codes share this layout.</text>
      <text x="400" y="334" font-size="10" fill="#4a6070">Only the data + parity region changes between examples below.</text>
    </g>
  </svg>
  <figcaption style="margin-top: 0.5rem; text-align: center; font-size: 0.85rem; color: #4a6070;">Every QR code carries the same structural skeleton — finder, timing, and alignment patterns, plus a quiet zone. The payload-specific section is the data + parity area in the middle. Once you can spot the shared parts, every example below is just a different payload string in the centre.</figcaption>
</figure>

For a deeper walkthrough of why each region exists, see [what is a QR code](https://fast-qr.app/learn/what-is-a-qr-code) for the anatomy diagram and [how QR codes work](https://fast-qr.app/learn/how-qr-codes-work) for the decode pipeline. The payload examples below assume the basic structure and focus on what is encoded.

## URL QR code example

The most common payload by a wide margin. Around 80% of QR codes in business use carry a plain HTTPS URL. Posters, packaging, business cards, restaurant menus, and product labels almost always fall back to URL once you trace what is actually encoded.

**What you see:** a regular black-on-white QR code, usually 2-5 cm on print, sometimes with a small centered logo.

**What it encodes:**

```txt
https://example.com/sale?utm_source=poster&utm_medium=qr&utm_campaign=spring
```

**Generator route:** [`/static/url-to-png`](https://fast-qr.app/static/url-to-png) for a PNG suitable for digital and small print, or [`/static/url-to-svg`](https://fast-qr.app/static/url-to-svg) for scalable print files. Both pages handle the encoding and let you embed a logo without breaking scans.

**PNG vs SVG:** ship PNG for slide decks, social posts, in-app images, and small flyers up to A5. Ship SVG for posters larger than A5, signage, banners, or anything heading to a designer's InDesign file. SVG also keeps the file size tiny when you scale up.

**Operational notes:**

- Always use HTTPS. Modern phones flag plain HTTP and some browsers warn the user.
- Keep query strings short — long URLs force the encoder to a higher QR version with smaller modules, which scan less reliably.
- If you may want to repoint the destination later without reprinting, route through a short URL or branded redirect domain you control. The [static vs dynamic QR codes](https://fast-qr.app/blog/static-vs-dynamic-qr-codes) comparison covers the trade-off.

## Wi-Fi QR code example

A Wi-Fi QR joins the device to a network without anyone typing the password. iOS 11+ and Android 10+ recognize the format natively and prompt the user with a "Join Network?" sheet.

**What you see:** identical visual to a URL QR. There is no way to tell from the pattern alone that this is a Wi-Fi code.

**What it encodes:**

```txt
WIFI:T:WPA;S:GuestNetwork;P:correct-horse-battery-staple;H:false;;
```

The structured fields are:

- **`T`** — encryption type: `WPA` (covers WPA2/WPA3), `WEP`, or `nopass` for open networks.
- **`S`** — SSID, the network name.
- **`P`** — the password (omit for `nopass` networks).
- **`H`** — `true` if the network is hidden, `false` for broadcast SSIDs.

Special characters in the SSID or password (semicolons, colons, commas, backslashes, quotes) need escaping with a backslash. The [Wi-Fi-to-PNG generator](https://fast-qr.app/static/wifi-to-png) handles the encoding and escaping automatically.

**PNG vs SVG:** PNG for table tents, lobby signs, and laminated cards. SVG for window decals, large counter signs, and anything printed bigger than A4.

**Operational notes:**

- Always use a guest network, never your operational network. A printed Wi-Fi QR is publicly readable by definition.
- Avoid open (`nopass`) networks — modern phones warn users about "unsecured network" and scare non-technical guests off.
- Verify the SSID and password character-for-character before printing. A wrong character means every scan fails silently. See [Wi-Fi QR code best practices](https://fast-qr.app/learn/qr-code-wifi-best-practices) for the full security and operational checklist.

## Email QR code example

A `mailto:` QR pre-fills the recipient, subject line, and body in the device's default mail app. Useful for "request a quote" or "report an issue" prompts on flyers, support stickers, and trade-show one-pagers.

**What it encodes:**

```txt
mailto:sales@example.com?subject=Quote%20request&body=Hi%20team%2C%20I%20saw%20your%20booth%20at%20SaaStr%20and%20would%20like%20pricing%20for...
```

The subject and body are URL-encoded — spaces become `%20`, commas become `%2C`, newlines become `%0A`. The [email-to-PNG generator](https://fast-qr.app/static/email-to-png) handles the encoding and gives you separate fields for recipient, subject, and body.

**Operational notes:**

- Pre-fill the source in the subject ("Quote request — Manchester showroom flyer") so inbound triage knows which placement worked.
- Keep the body short — a 2,000-character pre-fill works on most phones but breaks some Android mail clients.
- For higher-intent inbound, an [SMS QR](https://fast-qr.app/static/sms-to-png) or [WhatsApp QR](https://fast-qr.app/static/whatsapp-to-png) usually outperforms email because reply latency is lower.

## Phone tap-to-call QR code example

A `tel:` QR opens the device dialer with the number pre-filled. The user taps once to call. Useful for service-business signage, emergency contacts, and restaurant reservation cards.

**What it encodes:**

```txt
tel:+14155552671
```

Always use full international format with the country code and a leading plus sign — `+1` for US/Canada, `+44` for UK, `+91` for India, `+55` for Brazil. The [phone-to-PNG generator](https://fast-qr.app/static/phone-to-png) handles formatting.

**Operational notes:**

- The leading plus sign matters. `tel:14155552671` works for some Android devices but iPhones may refuse to dial.
- For businesses with multiple regional numbers, print per-region codes. Routing one number across regions adds latency and call-quality issues.
- Pair the QR with the phone number printed in human-readable form. Some users prefer typing, some prefer the scan, and you want to capture both.

## SMS QR code example

An `sms:` QR opens the messaging app with the recipient and body pre-filled. The user taps Send to deliver. Common for lead capture, support shortcut prompts, and one-tap event confirmations.

**What it encodes:**

```txt
sms:+14155552671?body=Hi%20I%20saw%20the%20flyer%20at%20the%20Manchester%20showroom%20and%20want%20a%20quote%20on%20the%20Cedar%20package
```

The body is URL-encoded the same way as email. The [SMS-to-PNG generator](https://fast-qr.app/static/sms-to-png) handles encoding and lets you preview the message before generating the code.

**Operational notes:**

- For US contexts, SMS usually beats WhatsApp because adoption is mixed. For Latin America, India, the EU, and most of the rest of the world, WhatsApp wins.
- Identify the source in the prefill so your CRM can route the lead to the right team automatically.

## WhatsApp lead QR code example

A `wa.me` QR opens WhatsApp pre-filled with a message and the business number ready. WhatsApp lead QRs are the highest-intent inbound channel for any market where WhatsApp is the dominant messaging app — India, Brazil, Mexico, Spain, Argentina, Germany, Indonesia, and dozens more.

**What it encodes:**

```txt
https://wa.me/15551234567?text=Hi%20I%20saw%20the%20flyer%20at%20the%20Manchester%20showroom%20and%20want%20a%20quote%20on%20the%20Cedar%20package
```

Spaces become `%20`, apostrophes become `%27`. The [WhatsApp-to-PNG generator](https://fast-qr.app/static/whatsapp-to-png) handles the encoding and lets you set the phone number and the prefill text separately.

**Operational notes:**

- Identify the source and intent in the prefill. "Hi" tells the agent nothing; "Hi, I scanned the QR at the Manchester showroom and want a quote on the Cedar package" tells the agent the placement, the product, and the action.
- For deeper deployment notes — including the WhatsApp Business app vs API decision, the 24-hour customer service window, and regional tone — see the [WhatsApp leads playbook](https://fast-qr.app/qr-code-for/whatsapp-leads).

## Payment link QR code example

A payment QR can carry one of several payload formats. The simplest is a regular HTTPS URL pointing at a hosted checkout page. Country-specific standards (EMVCo QR in Brazil's PIX, India's UPI, Singapore's PayNow, Hong Kong's FPS) carry merchant-coded payloads that the local payment app recognizes natively.

**What it encodes (URL fallback):**

```txt
https://checkout.example.com/inv/2026-05-26-ACME-7281
```

**What it encodes (UPI example, India):**

```txt
upi://pay?pa=merchant@bank&pn=ACME%20Coffee&am=4.50&cu=INR&tn=Invoice%202026-05-26-7281
```

The fields in a UPI payload are: `pa` payee address, `pn` payee name, `am` amount, `cu` currency, `tn` transaction note.

**Operational notes:**

- For multi-region deployments, the URL approach is the safest default. The hosted checkout page detects the user's location and currency and falls back to a card form if no local wallet is available.
- Trust matters more for payment QRs than any other type. The landing page must clearly display the business name and the actual domain so the user can verify before tapping through. See the [payment links playbook](https://fast-qr.app/qr-code-for/payment-links) for branded checkout patterns.
- QR phishing — fake QR stickers placed over legitimate ones on parking meters, restaurant tables, and EV chargers — is documented and growing. Print the receiving wallet name or domain near the code so customers can verify visually before scanning.

## Business card (vCard) QR code example

A vCard QR encodes a contact in the standard vCard 3.0 format. Scanning prompts the phone to add the contact to the address book in one step.

**What it encodes:**

```txt
BEGIN:VCARD
VERSION:3.0
N:Haider;Rehan;;;
FN:Rehan Haider
ORG:Fast QR
TITLE:Founder
TEL;TYPE=CELL:+14155552671
EMAIL:rehan@example.com
URL:https://fast-qr.app
ADR;TYPE=WORK:;;123 Market St;San Francisco;CA;94103;USA
END:VCARD
```

The fields use the [RFC 6350 vCard specification](https://datatracker.ietf.org/doc/html/rfc6350). Some older Android phones prefer vCard 2.1 over 3.0; if you need cross-version compatibility, encode the minimum set (FN, TEL, EMAIL, URL) and skip the structured address.

**Operational notes:**

- vCard payloads are long. A full card with address, multiple phone numbers, and a photo can push the QR version high enough that modules become hard to scan at business-card print sizes (2-2.5 cm).
- A shorter alternative: encode a URL to a hosted contact page (`https://example.com/me/rehan`). The hosted page can offer "Save to contacts" as a download, while the QR stays low-density and scans reliably. See the [business cards playbook](https://fast-qr.app/qr-code-for/business-cards) for the vCard vs URL trade-off.

## Restaurant menu QR code example

The QR on a restaurant table tent almost always encodes a URL to a mobile-optimized HTML menu page. PDFs scale badly on phones and create pinch-to-zoom friction; restaurants that link to PDFs see lower engagement and more "can I get a paper menu?" requests.

**What it encodes:**

```txt
https://restaurant.example.com/menu?location=manchester
```

**Operational notes:**

- Link to a mobile-first HTML page, never a PDF. The full reasoning is in [menu QR vs PDF menu](https://fast-qr.app/blog/menu-qr-vs-pdf-menu) and the deployment-side detail is in the [restaurant menu playbook](https://fast-qr.app/qr-code-for/restaurant-menu).
- Route through a stable URL you control. Switching menu platforms a year later should not require reprinting 200 table tents.
- Pair the menu QR with a Wi-Fi QR on the same table tent. Dim dining rooms have unreliable cellular, and the most common cause of menu QR failure is a slow page load on weak signal.

## Event check-in QR code example

Event check-in QRs encode a unique ticket identifier that the door staff's scanner validates against the attendee list. The visual is generic; the payload is what matters.

**What it encodes:**

```txt
https://event.example.com/checkin/EV2026-ATT-8472-T-9F3K
```

The trailing path segment is the ticket ID. Some systems sign the ID with HMAC so the QR cannot be forged.

**Operational notes:**

- Print the ticket ID as a backup string next to the QR. When the door scanner inevitably has a hardware issue, manual lookup needs a typeable fallback.
- Generate codes with error correction level Q or H — tickets get folded, crumpled, and pulled out of pockets in low light, and the extra parity buys reliability.
- The [event check-in playbook](https://fast-qr.app/qr-code-for/event-check-in) covers queue management, offline fallback, and badge-vs-ticket placement.

## Plain text QR code example

Plain text payloads are uncommon in business use because the user still has to act on the message manually — there is no protocol prefix to trigger an OS action. They show up occasionally on internal operations signage, back-of-house notes, or simple memorial plaques.

**What it encodes:**

```txt
Wi-Fi password: ask staff for the daily code (do not post passwords in public areas)
```

For public-facing use cases, a URL or `tel:` payload almost always beats plain text. The exception is short, copy-paste-friendly content like a serial number, a coupon code, or a part number.

## Common payload types at a glance

<figure id="payload-gallery" style="margin: 1.5rem auto; max-width: 720px;">
  <img src="https://fast-qr.app/images/learn/qr-code-payload-gallery.svg" alt="Eleven QR code payload types side by side in a grid — URL, Wi-Fi, email, phone, SMS, WhatsApp, payment, vCard, menu, event check-in, plain text. Every code looks visually identical; only the icon and label differ." loading="lazy" decoding="async" style="width: 100%; max-width: 720px; height: auto;" />
</figure>

| Payload | Visual | Prefix or format | Action on scan | Generator |
|---|---|---|---|---|
| URL | Square grid | `https://...` | Opens browser | [URL → PNG](https://fast-qr.app/static/url-to-png), [URL → SVG](https://fast-qr.app/static/url-to-svg) |
| Wi-Fi | Square grid | `WIFI:T:...;S:...;P:...;H:...;;` | Joins network | [Wi-Fi → PNG](https://fast-qr.app/static/wifi-to-png) |
| Email | Square grid | `mailto:...?subject=...&body=...` | Opens mail composer | [Email → PNG](https://fast-qr.app/static/email-to-png) |
| Phone | Square grid | `tel:+...` | Opens dialer | [Phone → PNG](https://fast-qr.app/static/phone-to-png) |
| SMS | Square grid | `sms:+...?body=...` | Opens messages | [SMS → PNG](https://fast-qr.app/static/sms-to-png) |
| WhatsApp | Square grid | `https://wa.me/...?text=...` | Opens WhatsApp chat | [WhatsApp → PNG](https://fast-qr.app/static/whatsapp-to-png) |
| Payment | Square grid | URL or EMVCo merchant string | Opens wallet or checkout | [URL → PNG](https://fast-qr.app/static/url-to-png) (URL fallback) |
| vCard | Square grid (denser) | `BEGIN:VCARD ... END:VCARD` | Adds to contacts | [URL → PNG](https://fast-qr.app/static/url-to-png) with vCard string |
| Menu | Square grid | `https://restaurant.../menu` | Opens menu page | [URL → PNG](https://fast-qr.app/static/url-to-png) |
| Event check-in | Square grid | `https://event.../checkin/TICKETID` | Validates ticket | [URL → PNG](https://fast-qr.app/static/url-to-png) |
| Plain text | Square grid | Free-form | Shows text | [URL → PNG](https://fast-qr.app/static/url-to-png) |

The pattern is consistent: the QR visual is the delivery mechanism, the payload string decides the action. For deeper context on which payload fits which use case, the [QR code use cases guide](https://fast-qr.app/learn/qr-code-use-cases) walks through six high-leverage business deployments, and the [email, phone, and SMS use cases guide](https://fast-qr.app/learn/qr-code-email-phone-sms-use-cases) covers contact-action QRs in detail.

## Why two codes can look different but open the same page

<figure id="same-payload-different-visual" style="margin: 1.5rem auto; max-width: 720px;">
  <img src="https://fast-qr.app/images/learn/qr-code-same-payload-different-visual.svg" alt="Three side-by-side QR codes that all encode fast-qr.app/menu. The first uses mask 0 at level M, the second mask 4 at level H, the third brand purple with rounded modules and a centred logo. All three decode to the same URL." loading="lazy" decoding="async" style="width: 100%; max-width: 720px; height: auto;" />
</figure>

Re-encode the same URL with two different generators and you can end up with QRs that look visually different to a human eye but decode identically. Three things explain that:

- **Masking patterns.** The QR specification defines eight masks that get XORed onto the data area to break up long runs of same-color modules. The encoder picks whichever mask scores best on standardized scan-friendliness rules. A different mask choice produces a visually different code from the same payload.
- **Error correction level.** Bumping a code from level L (7% recovery) to level H (30% recovery) adds parity modules, which changes the visual density. Same data, denser-looking code.
- **Cosmetic styling.** Brand colors, rounded modules, embedded logos, frame badges, and custom finder shapes all change the appearance without touching the payload. A blue QR with a centered logo and a turquoise frame is the same code as a black-and-white version with the same URL inside.

This is why your designer's mockup and your generator's output can look different yet both work. It's also why a "stylized" code with heavy gradients and uncommon module shapes can occasionally fail to scan — the visual changes confuse the scanner's threshold detection even when the underlying data is intact. The [QR code design best practices](https://fast-qr.app/learn/qr-code-design-best-practices) guide covers the styling choices that hold up versus the ones that look great and fail.

## How to read any QR code's payload

<figure id="scan-preview-banner" style="margin: 1.5rem auto; max-width: 720px;">
  <img src="https://fast-qr.app/images/learn/qr-code-scan-preview-banner.svg" alt="Two phone camera screens showing iOS-style scan preview banners. The left shows a safe matching domain (fast-qr.app/menu) with a green checkmark; the right shows a suspicious bit.ly redirect to a typo-squatted domain with a red warning." loading="lazy" decoding="async" style="width: 100%; max-width: 720px; height: auto;" />
</figure>

To see what is actually inside a QR code you found in the wild:

1. **Use your phone camera's built-in preview.** Both iOS (11+) and Android (10+) show the decoded URL or string in a banner before launching anything. Do not tap through — just read the preview.
2. **Use a decoder web tool.** Sites like the [ZXing online decoder](https://zxing.org/w/decode.jspx) accept an uploaded image and return the raw payload string.
3. **Use a command-line decoder.** `zbarimg` from the `zbar` package decodes QR codes from image files: `zbarimg --quiet --raw code.png` prints the raw string.

This is the right safety habit before scanning unknown QRs. QR phishing attacks rely on users tapping through the decoded preview without reading what it says. If the destination domain does not match what the surrounding signage promises, do not tap. The [are QR codes safe](https://fast-qr.app/learn/are-qr-codes-safe) guide covers the threat model and prevention patterns.

## Build any of these QR codes

Each generator route below produces a QR from the corresponding payload type, with no signup, no watermark, and no email. Pick the type that matches your example.

- [URL → PNG](https://fast-qr.app/static/url-to-png) and [URL → SVG](https://fast-qr.app/static/url-to-svg) for websites, landing pages, menus, payment pages, and ticket check-in URLs.
- [Wi-Fi → PNG](https://fast-qr.app/static/wifi-to-png) for guest networks, lobby signage, and laminated table tents.
- [Email → PNG](https://fast-qr.app/static/email-to-png) for `mailto:` actions with pre-filled subject and body.
- [Phone → PNG](https://fast-qr.app/static/phone-to-png) for `tel:` tap-to-call.
- [SMS → PNG](https://fast-qr.app/static/sms-to-png) for pre-filled text-message lead capture.
- [WhatsApp → PNG](https://fast-qr.app/static/whatsapp-to-png) for `wa.me` chat openers with prefilled context.

For the full catalog of deployment patterns by industry — restaurants, hotels, retail, healthcare, real estate, events — the [`/qr-code-for` directory](https://fast-qr.app/qr-code-for) maps each scenario to a dedicated playbook.

## Sources

- [Wikipedia — QR code](https://en.wikipedia.org/wiki/QR_code) — Comprehensive technical reference covering payload formats, encoding modes, and visual structure.
- [Denso Wave — Examples of QR Code use](https://www.qrcode.com/en/codes/) — Real-world QR deployments and payload examples documented by the inventor of the QR code.
- [RFC 6350 — vCard format specification](https://datatracker.ietf.org/doc/html/rfc6350) — IETF specification for vCard 3.0 contact payloads encoded inside business-card QR codes.
- [ISO/IEC 18004:2015](https://www.iso.org/standard/62021.html) — International standard that defines QR module geometry, masking patterns, and decoder behavior.
- [EMVCo — QR Code Specifications for Payment Systems](https://www.emvco.com/specifications/) — Standardized merchant payload format used in PIX, UPI, PayNow, and other national payment QR systems.

## Frequently asked questions

### What does a QR code look like?

A QR code is a square grid of black and white modules with three large nested squares in the corners — the finder patterns that tell scanners where the code starts and which way is up. Inside the grid sits the actual data, surrounded by a blank quiet zone at least four modules wide. Codes can carry brand colors, rounded modules, or a small centered logo, but the underlying square shape and the three corner squares are always the same regardless of the payload.

### What information is inside a QR code?

Anything that can be written as a string of characters: a URL, Wi-Fi credentials, a phone number, an SMS template, an email draft, a vCard contact, a WhatsApp chat link, a payment link, or plain text. The most common payload is a URL (about 80% of QR codes in business use). The QR code itself is just a way to encode that string into a pattern a camera can read — it does not store images, video, or executable code.

### Can two QR codes look different but open the same page?

Yes. The QR specification includes eight masking patterns that get XORed onto the data area to avoid runs of same-color modules. The encoder picks whichever mask scores best on scan-friendliness rules, which means re-encoding the same URL can produce a visually different code that still decodes identically. Adding error correction, changing the color, embedding a logo, or rounding the modules also changes the visual without changing the payload.

### What is a real example of a Wi-Fi QR code payload?

A Wi-Fi QR code encodes a structured WIFI: string like WIFI:T:WPA;S:GuestNetwork;P:correct-horse-battery-staple;H:false;;. The fields are T (encryption type WPA/WPA2/WPA3/WEP/nopass), S (network name), P (password), and H (true if the network is hidden). Special characters in the SSID or password need to be escaped with a backslash. iOS 11+ and Android 10+ recognize the string and prompt the user to join the network without typing the password.

### How do QR codes for payments look different from URL QR codes?

Visually they look identical — same black-and-white grid, same finder patterns. The difference is in the encoded string. A payment QR can carry an EMVCo-standard merchant payload (used in Brazil's PIX, India's UPI, Singapore's PayNow), a direct app deep link, or a regular HTTPS URL that opens a hosted checkout page. The pattern reveals nothing about the destination — always preview the URL in your phone's scanner before tapping through.
