An email QR code contains a mailto: URI that opens a draft in a compatible email application. It can include the recipient address and optional subject or body, but it does not send the message automatically. The sender reviews the draft and chooses whether to send it.
Use the generator above to create the code, then follow this guide to keep the payload short, protect private information, provide a visible fallback, and test the final printed or digital version across the devices your audience actually uses.
How does an email QR code work?
An email QR code stores a standardized mailto URI rather than connecting directly to an email server. RFC 6068 defines the scheme and permits an address plus message header fields and a draft body.
A simple payload looks like mailto:support@example.com. Optional fields follow a question mark, for example ?subject=Product%20help&body=Order%20number%3A. Reserved characters and non-ASCII text need correct percent encoding, which the generator handles for the supported fields.
After scanning, the operating system passes the URI to an available email handler. A phone with no configured mail application, or a scanner with incomplete URI support, may not open the expected draft.
How to create an email QR code
Enter the final recipient and a concise draft, generate the symbol, and test the exact downloaded file.
- Select the Email content type in the generator.
- Enter a monitored recipient address.
- Add a short, specific subject such as “Product support request.”
- Use the body to prompt for non-sensitive details, not to collect secrets.
- Generate the code and preserve its quiet zone and proportions.
- Scan with representative iPhone and Android devices.
- Confirm the recipient, subject, line breaks, and body before downloading.
What should the subject and body say?
The draft should explain the intended request without pretending to speak for the sender. A good template reduces uncertainty but leaves room for the person to add context.
| Use case | Subject | Draft prompt |
|---|---|---|
| Product support | Help with [product] | Product model: / Order number: / Issue: |
| Event follow-up | Follow-up from [event] | Hello, we met at… |
| Accessibility feedback | Accessibility feedback | Page or feature: / What happened: |
| General inquiry | Website inquiry | Hello, I would like to ask about… |
Do not prefill a claim, endorsement, agreement, or consent statement that the sender may transmit without reading. RFC 6068 treats the URI as a template and discusses security concerns around content that can be hidden or difficult for a user to inspect.
Keep sensitive information out of the code
Anyone who can scan or photograph the QR code can read its complete mailto payload. Do not embed passwords, access tokens, patient details, payment-card data, private case histories, or confidential internal identifiers.
The email address itself also becomes public wherever the code is distributed. Use an appropriate role address such as support@ or events@ rather than a private employee mailbox when the material will be broadly visible.
Email transport and mailbox handling have their own privacy and security properties. The QR generator prepares the draft; it does not encrypt the resulting email or control how mail systems log and store it.
Why should the printed address remain visible?
Print the recipient address near the code so a person has a fallback and can verify the intended destination. The visible text helps when no email handler is configured, accessibility technology cannot use the image, the code is damaged, or the user prefers to type the address.
Add a specific call to action such as “Scan to email support” rather than an unexplained square. If the subject matters for routing, mention it in ordinary text too.
Compatibility and testing
Mailto is standardized, but the user experience still depends on the scanner, operating system, default application, and optional fields. Avoid claiming that every phone or desktop behaves identically.
- Test a phone with a configured default mail app.
- Test another platform or mail client used by the audience.
- Verify spaces, punctuation, line breaks, and non-English characters.
- Check that a long body has not made the code unnecessarily dense.
- Test the printed proof at its final size and in normal lighting; the printing guide covers file format and paper.
- Confirm the visible fallback address is correct.
Static versus URL-based contact workflows
A static mailto code is appropriate when the address and template will remain stable. Its payload cannot be edited after printing.
If teams, routing rules, consent text, or contact details may change, consider encoding a stable contact page on a domain you control. That page can offer email, form, telephone, accessibility, and privacy information while the printed URL remains constant.
A contact page adds a network dependency and should not be described as equivalent to a direct mailto action. Choose based on maintenance needs and user context.
Common email QR code failures
Most failures come from an invalid address, overlong payload, missing mail handler, encoding issue, or poor print design.
- Nothing opens: try another scanner and confirm a mail application is configured.
- Only the recipient appears: simplify the subject/body and test the generated URI in the target apps.
- Characters are corrupted: regenerate rather than manually editing the encoded payload.
- The code will not scan: restore strong contrast, square proportions, sufficient size, and the quiet zone.
- The mailbox changed: replace the static code or restore routing for the published address.
When an email QR code is the wrong choice
Use another workflow when the request needs structured data, immediate assistance, authentication, or sensitive information. A support form can validate order numbers and route categories more reliably. A telephone number is better for urgent, synchronous help. An authenticated portal is more appropriate for account, medical, financial, or legal records.
Email also assumes the scanner has a usable account and is willing to expose an address to the recipient. Offer an accessible contact page with alternatives when the audience or context is broad.
What is the short version?
Create a concise mailto payload, keep the public data appropriate, and display the destination address beside the code. Test the final file with more than one real email setup before printing. For a long-lived campaign with changing contact options, use a stable contact page you control rather than embedding a temporary mailbox.
References
- M. Duerst, L. Masinter, and J. Zawinski, “RFC 6068: The mailto URI Scheme,” Internet Engineering Task Force/RFC Editor, 2010.
- DENSO WAVE, “Generating a QR Code,” QRcode.com, accessed 2026.