Open a ready-to-edit email draft
An email QR code encodes a mailto URI so a compatible device can open its preferred mail app with the recipient, subject, and message body prepared. It is useful for product support, event responses, property inquiries, classroom feedback, and printed forms where typing an address introduces errors. The scanner still reviews and sends the message; activating the code does not transmit email automatically.
Tool Swim follows the mailto structure defined by RFC 6068. The recipient stays in the address portion, while subject and body values are UTF-8 percent-encoded as query fields. This preserves spaces, ampersands, question marks, line breaks, and non-English text without allowing them to be mistaken for URI separators. Blank optional fields are left out to keep the payload compact.
Write a draft that invites a real response
Choose a monitored inbox and a subject that helps the receiving team route the message. A specific subject such as “Warranty question — model A14” is more useful than “Hello.” In the body, provide a short prompt or placeholders for information the sender should add. Do not prewrite agreement, consent, a testimonial, or other language that the scanner might send without noticing.
Keep the draft brief because long text makes a denser QR code and some mail clients display composed URIs differently. If you need structured intake, encode a secure web form instead. A mailto code cannot attach files, confirm delivery, select a sending account safely, or guarantee that a mail client is configured on the device.
Compatibility and encoding details
Modern mobile operating systems commonly understand mailto links, but the selected app controls the final draft. It may normalize line breaks, warn about an unknown recipient, or ask the user to choose an account. Kiosk browsers and managed devices may block external app launches. Always include the printed email address nearby so the person can contact you without relying on the handoff.
The generator accepts one recipient and intentionally avoids cc, bcc, and arbitrary header fields. That keeps the interface predictable and reduces the risk of exposing addresses or creating a misleading message. For a group workflow, use a public team alias managed by your mail system rather than embedding several personal recipients into a widely distributed code.
Privacy boundaries of an email QR code
The payload is assembled and rendered in the browser, so the draft is not uploaded to a QR service. However, the exported image contains the recipient and every prefilled word in plain, decodable text. Do not include case histories, customer identifiers, medical details, private order numbers, authentication codes, or confidential context. Ask the sender to add sensitive information only through an approved channel.
Published inboxes can attract spam because bots and people can decode the address. Consider a role address, filtering rules, and a web contact form if abuse is likely. If the code appears on packaging or signage, decide who owns the inbox over the full lifetime of that material and document how messages will be handled when staff changes.
Design for reliable scanning
Start with dark modules, a light background, medium correction, and a four-module margin. A lengthy body increases density, so shorten the copy before increasing correction. Use SVG for print layouts and a high-resolution PNG for office documents. Never crop the white quiet zone or place the code directly over a photograph, even when the center still appears visually clear.
The contrast warning checks the chosen colors, but physical output adds variables such as toner spread, textured paper, glare, and low light. Brand colors should be tested on the actual stock. If the code must be small, simplify the subject and body or print the address and use a URL to a contact page instead.
Test the complete compose flow
Print a final-size proof and scan with iOS and Android devices that have different default mail apps. Confirm the correct recipient, subject, Unicode characters, punctuation, and line breaks. Send a test message from a non-staff account and verify that it reaches the monitored inbox, passes spam filtering, and receives any promised response or automatic acknowledgement.
Repeat the test from the actual placement distance and lighting. Ask a colleague to follow the instruction without coaching and note whether the purpose is clear. Keep the visible address as a fallback, include expected response times where appropriate, and revisit the code whenever the mailbox, routing rule, or ownership changes.
