Prefill a recipient and message for email or text.
The email and SMS QR generator creates a ready-to-use message action. Choose email to prefill an address, subject and body, or SMS to prefill a phone number and text, then let someone scan instead of copying contact details from a sign or screen.
The QR code contains a standard mailto link or widely recognized SMSTO payload. It does not send the message, contact the recipient or route content through JsonKit; the scanning device opens its compatible email or messaging app and leaves the final action to the user.
These codes work well for support desks, feedback cards, event registrations, service requests and opt-in text campaigns. Keep the message concise so the QR symbol stays simple enough to scan reliably at the size you plan to use.
Email mode creates a mailto link with optional subject and body query parameters. SMS mode creates an SMSTO payload containing the destination number and message; both formats are widely recognized, though the exact app opened depends on the device.
Scanning opens a composed draft rather than transmitting anything automatically. The person scanning can review the recipient and message, edit the text, choose the appropriate account or SIM, and then decide whether to send.
Recipients and message bodies are encoded directly into the QR image in your browser. Remember that anyone who can see or scan the final image can recover the embedded content, so avoid placing private messages in public signage.
No. It opens a draft in a compatible app. The person scanning must review and send the message themselves.
No. JsonKit encodes the values locally and never sends them to a server or messaging provider.
Mobile operating systems and messaging apps interpret SMS QR payloads differently. Test the final code on the device types your audience is likely to use.
Email bodies can preserve line breaks through URL encoding. SMS payloads are normalized to a single line for broader scanner compatibility.
The behaviour of this tool and the claims on this page were checked against the specifications below on . Everything runs in your browser, so the output you see is exactly what the engine produced.
Found a wrong result or an outdated claim? Report an error and it will be re-verified.