Skip to content
ImgKiloImgKiloOpen tools

Email QR Code Generator

Email QR code with prefilled subject and body

Fill the To, CC, BCC, Subject and Body. The generator builds a `mailto:` payload per RFC 6068 that iOS Mail, Gmail and Outlook all parse. The recipient scans and only has to hit Send.

Scan to email

What to encode

Style

Frame

  • Files never leave your device
  • Runs in your browser
  • Free, no signup

How it works

  1. 1

    Fill the email fields

    To is required. CC, BCC, Subject and Body are optional and prefill the composer.

  2. 2

    Check the mailto: payload

    The encoded URI is shown above the preview so you can confirm the encoding before printing.

  3. 3

    Download PNG or SVG

    PNG for digital, SVG for print. Both open the user's mail app with the message ready.

What this email QR generator does

Full mailto: support

To, CC, BCC, Subject, Body. URL-encoded automatically so spaces, `&` and line breaks survive the scan.

Works on every major mail app

iOS Mail, Gmail (web and app), Outlook (web and app). Older Android clients may ignore CC; we hedge in the FAQ.

Encoded payload is visible

Most generators hide the encoded `mailto:`. We show it so you can verify what scanners will receive.

Where this helps

Feedback

Feedback cards

Subject 'Feedback for [shop name]', body left blank. Diners send a sentence and you get the file.

Customer

Service renewals

Body 'Please renew my plan. Account: ABC-123.' One-tap reply renewals from the email itself.

Events

Lead capture at events

Body 'Send me the deck I saw at booth 14.' Replies arrive with context, your team triages fast.

Hiring

Job applications

Subject prefilled with the role title. Candidates attach a CV and send; the inbox auto-tags by role.

Support

Support escalations

Sticker on hardware: 'Help with this device'. Body asks for the serial number printed beside it.

Property

Real-estate inquiries

Yard sign QR opens 'Tell me about [address]'. Agents reply with the brochure within an hour.

Tips that help

  • 1

    Keep the subject under 50 characters

    Mobile inbox previews truncate beyond that. A short subject reads cleanly before the message opens.

  • 2

    Prefill the prompt, not the answer

    'My feedback:' invites the user to type. 'I love your shop' puts words in their mouth.

  • 3

    Use a dedicated inbox for QR-driven mail

    Auto-tag for the campaign. Keeps QR replies separate from your main inbox.

  • 4

    Test on iOS Mail and Gmail before printing

    Some Outlook builds strip the body. If your audience is Outlook-heavy, keep critical info in the subject.

How the email QR actually composes the message

The QR encodes a `mailto:` URI. When a phone camera reads it, the OS hands the URI to the default mail app, which parses the To, CC, BCC, Subject and Body parameters and opens the composer. The whole thing follows RFC 6068, the IETF spec for `mailto:`. No server is involved on our side.

The mailto: format up close

A full `mailto:` looks like `mailto:hello@example.com?cc=team@example.com&subject=Hello&body=Hi%20team`. Multiple recipients are comma-separated inside To, CC and BCC. Parameters after `?` are URL-encoded, so spaces become `%20` and `&` inside the body becomes `%26`.

Email QR code with prefilled subject and body

We do all the encoding for you. Type plain text in the body. The QR holds the encoded version, the user sees the decoded version in their mail app.

Some older Android mail apps ignore CC or BCC. The To, Subject and Body trio works everywhere. For maximum compatibility, keep the QR to those three fields.

Subject and body together carry the message

The subject is what your recipient sees in their inbox preview before opening. Keep it under 50 characters so it does not truncate on mobile.

The body is the prefilled message. If you want a one-tap reply ('Renew my service', 'Send me the brochure'), keep the body short and the action is obvious.

If the QR is for a survey reply ('My feedback:'), prefill the prompt so the user types underneath. The visible context inside the composer turns a blank screen into a guided one.

Where the email QR earns its place

Restaurant feedback cards: 'Tell us how the meal was'. The QR opens a prefilled message to feedback@; the diner adds two sentences and sends.

Service-renewal mailers: 'Renew my plan for another year'. The QR includes the customer's account number in the body so the team can match it.

Trade-show booths: 'Send me the deck'. The body lists the product, the date and the booth number; the lead's reply arrives with context.

Read more

What can go wrong (and how to verify)

The user has no default mail app set. iPhones default to Apple Mail; Androids prompt the first time. There is nothing the QR can do about this; surface a fallback email address in plain text on the same card.

Corporate mail clients strip the body. Some Outlook builds in regulated industries do this. Keep the subject self-explanatory so a stripped body does not break the flow.

Encoding mistakes. Always check the encoded payload above the preview. The visible `mailto:` should match what you typed, with `%20` for spaces and `%0A` for line breaks. If something looks off, the scan will too.

Frequently asked questions

Honest answers to what people ask before using this tool.

It opens the phone's email app with the To, CC, BCC, Subject and Body fields prefilled. The user only needs to tap Send. The encoded payload is a `mailto:` URI defined in RFC 6068, the same scheme `<a href="mailto:...">` links use.

Yes on iOS Mail, Gmail (web and app), Outlook (web and app) and most third-party clients. The `body=` query parameter is part of RFC 6068. Some corporate Outlook builds strip it; for those audiences, keep the subject line strong and the body short or empty.

Yes. Comma-separate the To, CC and BCC fields and the URI encodes them correctly. Apple Mail, Gmail and Outlook all parse multiple recipients from a single `mailto:`. We surface the encoded payload so you can verify the comma-list before printing.

Two common reasons. The body has unencoded `&` or `?` characters that break the URI; we handle this for you automatically. The other is a missing default mail app; Settings → Mail → Default Mail App needs to be set. On a fresh iPhone with no mail account, the scan opens iOS Mail's setup screen instead.

There is no platform limit; the practical limit is QR scan reliability. A `mailto:` with a 200-character subject and 1,000-character body produces a dense QR that struggles on phone cameras with imperfect focus. Keep total payload under 600 characters, or link to a hosted page from a shorter QR.

It is fine for short campaigns like a feedback form prefill or a service-renewal reply. It is not a replacement for a proper email marketing tool. There is no tracking, no unsubscribe handling, no list management. For lead capture, point the QR at a landing page form instead.

The scan happens offline. The email opens in the user's mail app and queues until they have network. If the QR points at a website link in the body, that link still needs network to open.

Not from a static `mailto:` QR. The scan happens entirely on the user's device. For tracking, point the QR at a hosted landing page that redirects to a `mailto:` link; the page hit is then visible in your analytics.

It is exactly as exposed as printing the address in plain text. Bots scrape QR images the same as text. Use a separate inbox for QR-driven mail if you want to isolate that channel.

Yes. The QR encodes the address you provide; whether that lands in a personal inbox or a shared Helpdesk queue depends on your mail server. Most ticketing systems (Zendesk, Help Scout, Front) accept inbound mail at a forwarded address with the subject preserved.

Further reading

Independent references if you want to go deeper on the formats and tradeoffs.

Related tools