← All guidesURL/Phone/SMS/Email/Maps QR payloads: what scanners do after scanning
Practical payload formats (tel:, sms:, mailto:, geo:) and tips so users land on the expected action screen on iOS/Android.
Scanners don’t just “read a QR” — they interpret the payload into an action (open a website, call a number, compose an email).
Phone (dial screen)
tel:+14155552671
SMS (compose)
sms:+14155552671?body=Hello%20QRFlow
Email (compose)
mailto:hello@example.com?subject=Hi&body=Message
Maps (location)
https://maps.google.com/?q=48.8584,2.2945
Practical tips#
- Always test both iPhone and Android (behavior differs for sms/mailto parameters).
- Encode full international phone numbers with “+”.
- For Maps, using a normal HTTPS maps URL is the most universal.
Templates you can use#
Exact WIFI: payload format, what “Encryption” means, and how to avoid scan failures on iPhone/Android (special chars, hidden networks).
Which vCard fields actually get saved on iOS/Android, what to keep minimal, and how to avoid bloating the QR for better scans.
Generate a QR code for your Wi-Fi network to allow guests to join without manually typing the password.
How to create a URL QR code, shorten long links, and keep scans reliable.
When a text QR code makes sense and how to keep it scannable.
Create a Google Maps QR code for a location or directions, choose the right link, and print tips for signage.
Quick answers
Common questions
Which payload is most reliable?
Standard URL and tel: formats work best across devices.
Do SMS and email parameters always work?
Behavior varies by device, so test on iPhone and Android.
Which QR format works best?
Use standard formats like URL, WIFI, vCard, or wa.me and keep the data short.
How do I keep QR content scannable?
Remove extra fields, shorten URLs, and print larger for dense data.
Try it now
Generate QR codes locally in your browser — no uploads.