Types of QR Codes: URL, Wi‑Fi, vCard, Email, SMS, and More
Compare QR payload types—URL, Wi‑Fi, vCard, email, SMS, phone, geo, and plain text—and when to use static vs dynamic for each.
QR codes all look similar on a poster or label, but they do not all do the same thing. What matters is the payload — the string encoded in the pattern. That payload might open a website, join Wi‑Fi, save a contact, start an email, or show plain text. Choosing the right type matters as much as colors or print size.
This guide catalogs common QR content types. It is not a rewrite of static vs dynamic QR codes; it explains which payloads belong where, when static encoding is enough, and when a URL-based dynamic wrapper helps you edit destinations and measure scans after print. Start from the General hub and what a QR code is.
What “type of QR code” actually means
People say “types of QR codes” in two ways. One is static versus dynamic — whether the pattern encodes final data or a short redirect you can change later. The other is payload format: URL, WIFI:, vCard, mailto:, and so on. This article focuses on payload formats.
A QR symbol is a container. The camera decodes bytes; the OS then opens a browser, offers Wi‑Fi join, prompts to save a contact, or shows text. For modules and decoding, see how QR codes work. For how much damage a logo or worn label can survive, see QR code error correction explained.
Static payload vs dynamic URL wrapper
- Static: The exact string lives in the printed code. Change the Wi‑Fi password or landing page and you must reprint.
- Dynamic (URL wrapper): The printed code encodes a short HTTPS URL that redirects to your destination. You can swap the target, add analytics, and keep the same artwork.
Dynamic wrappers shine for web destinations (menus, forms, PDFs, app store pages). They fit poorly when the phone must consume a native string offline — for example WIFI: or a full vCard with no network hop. Izoukhai’s unlimited dynamic QR generator is in the URL-wrapper category: editable destinations, real-time analytics, SVG export, unlimited codes and scans at $3.99/month or $39.99/year, and codes that keep working after you cancel.
URL QR codes (the most common type)
A URL payload is a web address, ideally with https://. Scanning opens the browser at that page. Use cases include product pages, digital menus, event registration, support portals, and campaign landings. Restaurants often encode a menu URL so they can update dishes without reprinting table tents — see dynamic QR codes for restaurants.
When to keep a URL static
Static URL codes work when the destination is permanent: a stable corporate homepage, a fixed public document URL, or a one-off flyer whose event will end before the URL might change. Prefer short URLs; long query strings raise module density and hurt small prints.
When a dynamic URL wrapper helps
Choose dynamic when you expect to fix typos or swap A/B pages after print, track scans (counts, devices, locations), route by device or region, or retire a campaign without dead links on packaging. Before mass printing, follow testing QR codes before you print and confirm size, contrast, and quiet zone on real phones.
Wi‑Fi QR codes (WIFI:)
A Wi‑Fi QR encodes credentials in a structured string (commonly WIFI:T:WPA;S:NetworkName;P:password;;). Compatible phones offer one-tap join. Hotels, coworking spaces, classrooms, and retail guest networks use them so visitors skip typing long passwords.
Static by design — and why that matters
Wi‑Fi payloads are almost always static. The phone needs the SSID and password immediately, often before the guest has internet. A dynamic redirect would require network access first — which defeats the purpose. If you rotate guest passwords weekly, regenerate and reprint (or refresh digital displays); do not expect to edit the same printed symbol later.
Security notes (without the full security deep dive)
Treat a Wi‑Fi QR like a password on a wall: anyone who photographs it can try to join. Use a guest network isolated from internal systems, rotate credentials when staff turn over, and never encode admin or payment-terminal networks. For phishing and malicious-code patterns, read QR code security risks and safe scanning. Do not paste production passwords into untrusted generators on shared computers.
Contact QR codes (vCard and MECARD)
Contact payloads let someone save your details with a scan. Two common formats appear in the wild:
- vCard (
BEGIN:VCARD…): Richer fields — name, phone, email, org, URL, address. Widely supported; larger payloads mean denser codes. - MECARD: A compact contact string used by many generators. Smaller than a full vCard, with fewer fields.
Where contact codes shine
Business cards, conference badges, booth banners, real-estate signs, and clinic desks. Keep fields minimal: name, role, one phone, one email, and a website. Extra notes and multiple addresses inflate density.
Static vs dynamic for contacts
A static vCard/MECARD embeds contact data in the code — changing your number means reprinting. A dynamic URL to a digital business card or CRM form keeps the printed code stable while you update details and measure opens. Pure contact strings remain best for offline save-to-contacts with no browser step.
Privacy and trust
Do not encode home addresses or private mobiles on public posters. On badges, use work contact info only. Label the intent (“Scan to save our clinic contact”) so the prompt feels expected — a theme also covered in QR code myths debunked.
Email QR codes (mailto:)
A mailto: payload opens the mail app with a prefilled address, and optionally subject and body. Uses include feedback on packaging, “email support” stickers on equipment, and small-event RSVPs.
Practical tips
- Prefer a monitored inbox, not a personal address that will change.
- Prefill a clear subject so tickets sort correctly.
- Not everyone has a mail app configured; some users will bounce.
Static vs dynamic: Static mailto: is fine for a stable support address. If you might switch vendors or want analytics, use a dynamic URL to a web form instead — forms also avoid depending on the user’s mail client.
SMS QR codes
SMS payloads use schemes such as sms: or SMSTO: with a number and optional body. Scanning opens Messages ready to send. Campaigns use them for keyword short codes, donation texts, or “text us for today’s special.”
Carrier short codes and regional behavior vary. Prefilling marketing copy can feel pushy; keep it short and consent-friendly. For rich, measurable campaigns, a URL to a mobile page often outperforms SMS-only flows. The SMS string itself is static — if the number or keyword will change, prefer a dynamic URL that explains how to text or collects the lead on the web.
Phone QR codes (tel:)
A tel: payload prompts a call to the encoded number — useful on van wraps, roadside-help stickers, after-hours clinic doors, and field-equipment labels.
Use international format when audiences may roam (+ and country code). Confirm the line is staffed when the code is visible. Like email and SMS, tel: is static; wrap with a dynamic “contact options” page if you need hours, chat, and call tracking together.
Geo QR codes (geo:)
A geo: URI encodes latitude and longitude (sometimes with a label). Scanning can open maps at that point — trailheads, pop-ups, temporary lots, and docks where a street address is ambiguous.
Support varies by phone and maps app. Many teams encode a normal maps URL instead — better UX and easier testing. Dynamic URL wrappers help when the venue moves (seasonal markets, touring shows).
Plain text QR codes
Plain text encodes any string without a special scheme: serial numbers, ticket IDs, coupon codes, or short notices. The phone usually displays the text or offers to copy it.
Use plain text offline, for internal ops identifiers, or when you should not depend on a third-party redirect. Avoid stuffing essays into a QR — density rises fast and long text is hard to read on a prompt. For long or changing content, link to a hosted document via URL. Plain text is static; for versioned instructions, encode a dynamic URL to the latest PDF or help article.
App store links and deep links
App promotion often uses:
- Store URLs: Links to the Apple App Store, Google Play, or another store listing
- Deep links / universal links: URLs that open a screen inside an installed app, or fall back to the store / web
A single printed code cannot be two native store URIs without logic in between. Common patterns: a smart landing page (often behind a dynamic QR) that detects the device; rare platform-specific print runs; or universal links configured in your app and site.
Dynamic wrappers excel here: one code on packaging, device-aware routing, and editable fallbacks after launch. Test on both major platforms before mass print, and place codes where hands and glare will not block them — see QR code print and placement.
Payment QR codes (high-level caveats)
Payment QR codes appear as banking-app identifiers, merchant codes at registers, and peer-to-peer strings. Prefer official provider flows; do not invent payloads from blog snippets. Static merchant codes aimed at personal wallets can be swapped by stickers — verify codes on terminals you control. For changing donations or invoices, a dynamic URL to reputable checkout is easier to audit than raw payment strings on marketing creatives. Compliance and fees differ by region; involve your payment provider before printing. Do not encode card numbers or one-time secrets on public materials.
Choosing a payload: a quick decision guide
| Goal | Typical payload | Static or dynamic? |
|---|---|---|
| Open a webpage or file | URL | Dynamic if you need edits/analytics; static if permanent |
| Guest Wi‑Fi join | WIFI: |
Static |
| Save contact offline | vCard / MECARD | Static; or dynamic URL to a digital card |
| Start email / SMS / call | mailto: / SMS / tel: |
Static; or URL to a contact hub |
| Show a map pin | geo: or maps URL |
Maps URL + dynamic wrapper is often better |
| Show an ID or short note | Plain text | Static |
| Drive app installs | Store / smart URL | Dynamic smart landing page |
| Take payment | Provider-specific or checkout URL | Prefer official flows; dynamic checkout URL when amounts change |
For campaign ideas across industries, browse QR code use cases for business. When the payload is a URL you will manage for months, an unlimited dynamic generator with analytics and post-print edits — such as Izoukhai — keeps artwork stable while content evolves.
Density, design, and testing across payload types
Richer payloads (full vCards, long tracked URLs, verbose Wi‑Fi strings) create denser matrices that need more physical size and clean contrast. Strip unused vCard fields, prefer short dynamic links, and export SVG when print quality matters. Error-correction level interacts with logos and wear — see QR code error correction explained.
Scan with multiple devices after design changes. Confirm Wi‑Fi prompts on the OS versions guests use, that mailto: opens the expected app, and that dynamic redirects resolve on cellular as well as Wi‑Fi. Testing is cheaper than reprinting.
Conclusion
“Types of QR codes” are really types of payloads. URLs dominate marketing and menus; WIFI: and vCard serve connectivity and networking; mailto:, SMS, and tel: trigger native apps; geo: and plain text cover maps and offline IDs; app and payment flows need provider-aware design. Use static encoding when the phone must act on the string immediately and offline. Use a URL-based dynamic wrapper for analytics, device routing, or edits after print.
Continue in the General section with static vs dynamic QR codes, how QR codes work, and QR code security risks and safe scanning. For URL-based campaigns that need unlimited editable codes, scan analytics, and SVG export — at $3.99/month or $39.99/year, with codes that keep working after cancel — try Izoukhai’s dynamic QR generator.