Skip to main content
EZQR

Email QR Code

Email QR Code Generator

Encode a mailto: link — recipient, subject, and body all pre-filled — into a QR that opens the scanner's default mail app ready to send.

Free static QR codes. Sign up to unlock dynamic codes & analytics.

Your QR code will appear here

About Email QR Codes

Email QRs ride the mailto: URI scheme — the same protocol that powers every "email us" link on every website since 1995. The QR encodes mailto:[email protected]?subject=...&body=... and the phone hands the URI to whichever mail app the user has set as default — Apple Mail on iPhone, Gmail on Android, Outlook on either, Spark, Proton Mail, anything. A compose window opens with the recipient, subject, and body all pre-filled. The user reviews and taps Send.

The value isn't saving the recipient from typing your address — it's the categorization the pre-filled subject enables. A QR labeled "Scan to report a defect" that pre-fills subject=Warranty Claim — Product Defect routes straight into the right ticket queue without a human triaging it. A "Scan to apply" QR on a recruiting flyer that pre-fills subject=Application — Frontend Engineer lands in the recruiter's inbox already labeled. The fewer fields the scanner has to fill, the higher the conversion.

EZQR generates email QRs free with no watermark, no signup, and no expiration. Static codes encode the mailto: URI directly into the pattern — they survive cancellation, work on every phone, and don't depend on any server we run.

Walkthrough

How to Create a Email QR Code

  1. Set the recipient email address

    Use a monitored business inbox — support@, hello@, apply@ — not a personal address. The QR is only useful if the inbox is checked. For high-volume use, route to a help-desk system (Zendesk, Help Scout, Front) that creates a ticket on receipt.

  2. Pre-fill the subject line for categorization

    The subject is the single highest-leverage field. subject=Support — Order # lands in the right help-desk queue; subject=Feedback — Table 7 tells the floor manager which table sent it. Be specific enough to route the email without a human reading the body.

  3. Add a short body template (under 200 characters)

    Pre-fill a body skeleton: "Hi team — I have a question about ___. My order number is ___." Gives the sender a starting point without locking them in. Long body templates create dense QRs that scan poorly — keep the body short.

  4. Brand the code and download

    Brand colors, logo in the center (under 20% area), high-contrast modules. PNG for digital, SVG for print at any size, PDF for the print shop. Minimum 2.5 cm on business cards, 4 cm on packaging, 8 cm on signage.

  5. Test on iPhone and Android both

    Scan from an iPhone (Apple Mail compose should open), then from an Android (Gmail compose). Confirm the recipient, subject, and body all populate correctly. URL-encoding bugs in the body field break silently — a 30-second test prevents a 5,000-piece reprint.

Where it works

Email QR Code Use Cases

Customer support QRs on product packaging — subject=Support: Product XYZ — Order # lands in the support queue with order context already in the subject, cutting first-response time in half.

Restaurant table tents for feedback collectionsubject=Feedback — Table 12 tells the floor manager which table sent the complaint while the diner is still in the seat.

Hotel room cards for housekeeping requests — subject=Room 412 — Extra Towels routes to the housekeeping queue without front-desk triage.

Recruiting flyers at career fairs and university booths — subject=Application — Backend Intern 2026 lands in the recruiter's inbox already labeled, with the candidate's name from the body template.

Trade show booth cards routing to the right sales rep with a pre-filled subject — subject=Demo Request — Acme Corp skips the "let me forward this" round-trip.

Business cards with a "Scan to reach me" QR — pre-fills subject=Re: Met at <event> so context survives even if the recipient files the message a week later.

Real estate listing signs with subject=Showing Request — 1402 Ocean Ave letting prospects request a tour without typing the address or finding the right agent inbox.

Conference speaker handouts with subject=Follow-up — <Talk Title> letting attendees email the speaker for slides, references, or consulting follow-up.

Newsletter opt-in QRs on bookmark inserts and packaging stickers with subject=Subscribe — the subscriber just hits Send and the recipient adds them to the list.

Wedding RSVP cards with one QR per guest pre-filled with the guest name in the body — couples skip the manual "who responded" spreadsheet entirely.

What works in practice

Email QR Code Best Practices

Always use a monitored business inbox — support@, hello@. An unmonitored inbox wastes every printed flyer and erodes trust the moment the sender doesn't get a reply.

Pre-fill the subject line for routing. The subject is what triage systems and human first-responders read first; "Support Request" with no context routes worse than "Support — Order #1234".

Keep the body under 200 characters. Long pre-fills create dense QRs that scan poorly at small print sizes, and templates that feel pre-written get edited or deleted by the sender anyway.

URL-encode special characters in subject and body — spaces become %20, newlines become %0A, ampersands become %26. Reputable generators handle this automatically; verify by scanning the QR before scale-printing.

For high-volume support flows, route to a help-desk inbox (Zendesk, Help Scout, Front) that creates a ticket on receipt and auto-acknowledges the sender — turns the QR into a self-service support entry point.

Add a CTA: "Scan to email support", "Scan to apply", "Scan to RSVP". Naked QRs convert at half the rate of QRs with adjacent prompt copy that pre-frames the destination.

Print the email address in plain text below the QR — both as a fallback for failed scans and so phone-camera holdouts can copy-paste the address into their preferred client.

Use a dynamic QR ($5/mo Lite plan) if the destination inbox might change — staff rotation, team restructure, new help-desk vendor. The printed code stays; you repoint the destination from the dashboard.

Test on iPhone (Apple Mail), Android (Gmail), and at least one third-party client (Outlook or Spark) before scale-printing. Body-field URL encoding behaves subtly differently across mail apps.

Email QR Code FAQ

Common questions about generating, printing, and deploying these codes.

Related Articles

Related Industries

Related Guides

Related Tools

Ready to create your Email QR code?

Free, no watermarks. Generate and download in seconds.

Generate Free QR Code