A practical guide
Prepare an email QR code with one recipient, an optional subject and an optional message body. The output is a mailto URI rather than a web form. Subjects and bodies are percent encoded so punctuation and Unicode do not accidentally become extra query parameters. A subject cannot contain line breaks. The message body can contain multiple lines, which may help the scanner start a structured support request or quotation inquiry in their own mail application.
An email QR does not send mail, deliver an attachment or guarantee that a mail client is configured. The scanning device decides which application opens and how it presents the draft. The user can review or edit the message before sending it. Use a recipient address that you are willing to make public, since the address is readable from the image. Avoid sensitive personal data in a prefilled body. For business cards, compare this format with vCard: mailto prepares a message, while a contact card is intended to import several contact fields.
Your inputs, styling and logo are processed in this browser. Generating a code does not upload them or contact the encoded destination. There is no account, saved history, QR tracking service or subscription. Loading this website still requests its static files from the host; opening a link after scanning is a separate action that can contact another service. Clearing the workspace removes its current content and image references, but does not promise a forensic wipe of browser memory or files you already downloaded.
Choose among PNG, SVG, JPEG and WebP in the export panel. JPEG cannot carry a transparent background and uses white instead. Use a clear, non-sensitive filename and keep the downloaded image somewhere appropriate for its content. The export button generates the latest revision directly; a separate preview click is not required. A local decode check compares the downloaded design with the encoded bytes. If it fails, the tool stops rather than silently shortening the content or lowering error correction.
Before distributing or printing, scan the actual exported file with a phone your audience uses. Verify both its content and the intended action. Scanning conventions and application behavior can differ, and a successful software decode is not a universal camera guarantee. Retain enough surrounding space, use a light background and keep a copy of the source details so you can regenerate a static code when those details change.