An email QR code encodes a mailto: link with optional pre-filled subject and body. When someone scans it, their default email app opens with the recipient address, subject, and body already filled in. They tap “send” and the message goes out.
It’s a tiny piece of friction that often makes the difference between “I’ll email them later” and an email that actually gets sent. For support requests, lead inquiries, event RSVPs, and feedback channels, removing the typing — and especially the subject-line guessing — turns intent into action.
When to use an email QR code
The pattern: anywhere you currently write an email address on a sign, in print, or in physical materials, an email QR code makes that address one tap closer.
Specific cases that work well:
- Support contact signage — “Issues? Scan to email support” with a pre-filled subject like “Support request: [your name]”
- Sales lead capture — at trade shows, conferences, or storefronts. Pre-fill subject “Interested in [product]”
- Event RSVP and inquiries — pre-filled subject “RSVP - [event name]”
- Feedback channels — restaurants, hotels, retail stores. Pre-fill subject “Feedback: [location]”
- Job application QR codes — on hiring posters with pre-filled subject “Application: [position]”
- Email signatures — alternative to a phone number for “contact me” CTAs
- Real estate signage — “Scan to email the listing agent”
- Restaurant table cards — “Scan to email us about catering / private events”
For two-way conversation, email QR codes outperform contact forms because they:
- Use the user’s own email app, so they keep a copy in their sent folder
- Don’t require the user to enter their own email address (their app already knows it)
- Don’t depend on your website being up
- Work offline (the email queues until they have a connection)
How an email QR code works under the hood
The QR pattern encodes a standard mailto: URL:
mailto:support@example.com?subject=Support%20request&body=Hi%2C%20I%27d%20like%20to%20ask%20about...
Breaking it down:
mailto:— the protocol prefix that tells phones this is an email, not a web URLsupport@example.com— the recipient address?subject=...— URL-encoded subject line (spaces become%20)&body=...— URL-encoded body text
When a phone scans this, it doesn’t open a browser — it opens the email app directly. iOS uses the default Mail app (or Gmail, Outlook, etc. if set as default). Android does the same with whichever app is the default mail handler.
Static vs dynamic for email QR codes
Most email QR codes are best as static — your support address doesn’t change often, and the pre-filled subject is part of the link. Dynamic doesn’t add much.
The case for dynamic email QR codes:
- You want scan analytics (how often is the “email us” sign actually used?)
- You’re A/B testing subject lines or recipient routing
- You’re rotating recipients on a schedule (e.g., support staff rotations)
For 95% of uses, static is the right answer.
How to create an email QR code in QRSync
- Open the generator.
- Select “Email” as the QR code type.
- Enter the recipient email address —
support@yoursite.com. - (Optional) Add a subject line — pre-fills the email’s subject. Good for support routing or filtering.
- (Optional) Add a body — pre-fills the email’s body. Useful for adding context the user shouldn’t have to type.
- Customize the design — colors, logo, dot style.
- Test scan with your phone. Verify the email app opens, the recipient is correct, and the subject/body pre-fill correctly.
- Download in PNG, SVG, or PDF.
Design tips for email QR codes
A few notes on top of the general design guidelines:
- Use a clear call to action. “Scan to email us” or “✉️ Send us a message” tells users what the QR does. An unlabeled QR looks generic and gets skipped.
- Show the email address too. Print it under the QR — gives users a fallback and makes the destination transparent.
- Pre-fill the subject deliberately. A subject line saves both you (easier inbox filtering) and the user (one less thing to write). “Support: [issue]” is much better than no subject.
- Don’t over-pre-fill the body. A long pre-filled body feels presumptuous and gets deleted. Keep it short — maybe a salutation and prompt: “Hi, I’d like to ask about ___.”
Subject and body URL encoding
A few details that matter for technical users:
- Spaces become
%20in the encoded URL. - Line breaks become
%0A(encoded newline). QRSync’s generator handles this automatically when you press Enter in the body field. - Question marks, ampersands, and other special characters need encoding too — also handled automatically by QRSync.
- Length limit: there’s no hard limit, but emails with very long pre-filled bodies create dense QR codes that are hard to scan. Keep the body under 200 characters for clean scanning.
Common mistakes
- Encoding a website contact form URL as a
mailto:link. These are different! Use a URL QR code for forms; use an email QR code only when you literally want the user’s email app to open. - Using a non-existent or misspelled address. Scan + verify before printing — a typo means the email bounces silently.
- Pre-filling a body so detailed it sounds like you wrote the message. Users want to write their own thoughts. Pre-fill is for context, not the whole message.
- Forgetting to handle the response. If you put a “Scan to email us” sign in a high-traffic location, prepare for actual email volume. Auto-responders and SLAs matter.
A note on email volume
Email QR codes work best when there’s someone on the receiving end who actually reads the messages. If support emails sit in an unread inbox for a week, the QR campaign fails — not because of the QR, but because of the operational follow-up.
Before deploying email QR codes widely:
- Confirm the receiving inbox is monitored.
- Set up email filters using the pre-filled subject line to auto-route messages.
- Decide on an SLA for response time (24 hours? 4 hours?) and communicate it (“We respond within 1 business day”).
Ready to make yours?
Create your email QR code — free, takes about a minute. Pre-fill the subject line for easier inbox triage, and you’ll see the difference between a contact form (which gets the lowest-effort version of every question) and a pre-filled email (which gets people in their own words).