The scanner opens its configured email app with these fields prepared.
Review the QR content and test the code before sharing it.
Complete the required fields
A ready-to-download QR code will appear here as soon as the profile is valid.
Enter a valid email address.
Create a mailto QR code with a recipient, subject, and optional message body.
No expiry is added. The generated code is static, so its encoded payload does not change after download. That does not guarantee the destination will remain useful forever. A website can move, a Telegram username can change, an email address can stop working, a Wi-Fi password can be replaced, and an event can be rescheduled without updating an already printed code. If the underlying information may change, plan how you will replace the code or point it to a destination you can maintain. Always rescan archived artwork before a new print run.
The scanning system needs an email application configured for mailto links. The QR code prepares a draft with the encoded recipient, subject, and message but does not send it automatically. Apps can handle line breaks, special characters, multiple recipients, and long bodies differently. Verify the recipient carefully, scan the downloaded file in representative mail apps, and review the prepared draft before sending.
Scan the finished QR code and confirm that its decoded text, destination, or prepared action is exactly what you intended. Check spelling, phone or email details, coordinates, event times, time zone, network name, security type, and any included password. A QR code can be technically valid while opening the wrong destination because the encoded source value was wrong. For print, test the final physical size, contrast, quiet zone, material, and surrounding design before producing multiple copies. Test the real downloaded PNG or SVG, not only the preview displayed on the page.
Use a dark foreground against a light background with strong contrast, preserve a clear quiet zone around all four sides, and avoid placing other shapes or text too close to the modules. Do not make the code smaller than the expected camera distance and printing quality can support. Dense payloads create more modules and usually need a larger physical size. Avoid glare, folds, curved surfaces, blur, and low-quality resampling. Test the final code at the real size and viewing distance with more than one representative device when possible.
Choose PNG for common digital use at a known pixel size, such as email, a web page, a document, or a social post. Choose SVG for print, signs, packaging, or layouts that may be resized because its vector shapes remain sharp at different dimensions. When placing either format, keep the aspect ratio, retain the quiet zone, and avoid heavy compression or effects that blur module edges. Export a final proof from the design application and scan that proof because conversion, resizing, and print production can change an otherwise valid source file.