QR Code Generator for Email

Most QR generators are built for posters. This one is built for the inbox. A QR code in an email has to survive a completely different gauntlet: HTML sanitisers that strip data URIs, Outlook rendering images inside tables, dark-mode inversion, clients that scale images down until the modules blur, and readers who are already on the phone they would have scanned with.

QR Code Generator for Email handles all of that. Encode a URL, email address, phone number, SMS message, WiFi handshake, or plain text, layer on UTM parameters so scans show up separately in your analytics, then copy email-ready HTML that includes an anchor fallback, descriptive alt text, explicit dimensions, and an Outlook-safe table wrapper. Export as PNG for hosting on your CDN or as SVG when the code will also be printed.

Everything is computed in your browser using a self-contained QR encoder — no API, no rate limit, no redirect domain that can disappear and take your printed codes with it. The codes are permanent and point directly at your destination.

• Six content types: URL, plain text, email (mailto with subject and body), phone, SMS, and WiFi network credentials — each with the correct payload format so scanners trigger the right action.
• Built-in UTM builder: Append utm_source, utm_medium, utm_campaign, utm_term, and utm_content to the encoded URL so QR scans are attributable and never collapse into direct traffic.
• Email HTML generator: Three copy-ready snippets — hosted image (works everywhere), Base64 data URI (self-contained), and Outlook-safe table — each with anchor fallback, alt text, and explicit width and height.
• PNG and SVG export: Download a raster PNG at your chosen resolution, or a vector SVG that stays razor sharp at any print size.
• Full error correction control: Choose L, M, Q, or H and see the resulting version and module count update live, so you can trade capacity against scan resilience deliberately.
• Colour and margin control: Set module and background colours with a live contrast warning, and adjust the quiet zone — the single most common cause of unscannable codes.
• Batch mode: Paste up to 50 URLs with optional labels and get an individually downloadable QR code for each — ideal for per-store, per-rep, or per-session campaigns.
• Live scan diagnostics: Version, grid size, byte capacity used, and contrast ratio are shown as you type, with warnings before you ship a code that will not scan.
• Zero data transmission: The encoder is pure client-side JavaScript. Nothing you enter is uploaded, stored, or logged.

1. Pick a content type. Choose URL for campaign links, or switch to Email, Phone, SMS, or WiFi to generate the right payload for that action.
2. Enter your destination. Paste the link or fill in the type-specific fields. The preview redraws on every keystroke.
3. Add UTM tracking. Open the UTM panel and set your source, medium, and campaign. Use a distinct utm_content such as qr-code so scans are separable from ordinary clicks in reporting.
4. Tune size, error correction, and colours. Export at roughly twice your intended display width, keep error correction at M for screen or Q for print, and leave the quiet zone at 4 modules.
5. Download the image. Take the PNG for hosting on your CDN, or the SVG if the code will also appear in print.
6. Copy the email HTML. Move to the Email Embed tab, paste the hosted image URL you just uploaded, and copy the snippet into your template. Use the Outlook-safe variant if your list skews corporate.
7. Test before you send. Send yourself a seed, then scan from a real phone in both light and dark mode, and confirm the tracking parameters land in your analytics.

Example 1 — Event check-in in a newsletter. You are sending a conference reminder to 12,000 registrants, and most read it on a desktop. Encode https://events.example.com/checkin with utm_source=newsletter&utm_medium=email&utm_campaign=summit-2026&utm_content=qr-code, export at 400 px, display at 200 px, set error correction to M. In your analytics the QR traffic now appears as its own utm_content row, so you can see that 1,840 attendees checked in via the scan rather than the text link — a figure that would otherwise have been buried inside direct traffic.

Example 2 — Mobile-only offer for a desktop audience. Your app-exclusive discount cannot be redeemed in a browser. Rather than asking desktop readers to find their phone and type a URL, embed a QR code pointing at the deep link, wrapped in an anchor so mobile readers can simply tap it. One asset covers both segments.

Example 3 — Printable warranty card. An order confirmation includes a print-at-home warranty card. Because it will be printed at roughly 3 cm, you download the SVG, raise error correction to Q so a smudge or fold does not kill the scan, and keep the quiet zone at 4 modules so the code survives being cropped near the page edge.

Example 4 — Fifty store locations at once. A retail chain wants a per-branch review link in a regional email. Paste all 50 URLs into Batch mode with the store name as the label, download each PNG, and drop them into a personalised template keyed on branch — a job that would otherwise mean fifty trips through a generator.

• Bridge the desktop-to-mobile gap: Recover the readers who open on a laptop but need to act on a phone, instead of losing them at the handoff.
• Attribute scans properly: UTM-tagged codes stop QR traffic from being misfiled as direct, so the channel finally shows its real contribution.
• Render correctly in every client: Anchor fallbacks, explicit dimensions, alt text, and an Outlook table variant remove the guesswork from cross-client testing.
• No dependency on a redirect service: Codes encode your URL directly. There is no third-party shortener that can rate-limit you, start charging, or go dark and brick codes already in the wild.
• Print-safe from the same tool: Vector SVG output plus adjustable error correction means one asset works on screen and on paper.
• Fast at volume: Batch mode turns a fifty-code chore into one paste.
• Completely private and free: Client-side encoding, no sign-up, no watermark, no expiry, no usage cap.