Cookie preferences
We use cookies for analytics. Privacy Policy You can accept or decline non-essential tracking.
smsto vs sms URI formats, iOS and Android message handling, pre-fill best practices, short codes vs long codes, and MMS limitations.
Go to tool
Create an SMS QR code with pre-filled phone number and message.
Two URI schemes exist for SMS QR codes:
smsto:+12125551234:Hello -- widely supported on both iOS and Android. The format is smsto:NUMBER:BODY.sms:+12125551234?body=Hello -- the RFC 5724 standard. Uses query parameter syntax for the body.SMS QR Generator uses smsto: because it has broader device compatibility, especially on older Android phones. The sms: format with ?body= works on newer devices but occasionally fails on Android versions below 10.
sms: and smsto: open the Messages app. The body is pre-filled correctly. iMessage or SMS is chosen automatically based on the recipient.smsto: opens the default messaging app (Google Messages, Samsung Messages, etc.). The body pre-fill works reliably. Some third-party messaging apps may ignore the body parameter.Always test on the actual device your audience is most likely to use.
The body text appears in the message field when the user opens the app. Best practices:
JOIN, STOP, ORDER 12345.For most small businesses, a regular phone number works fine. Short codes are for large-scale campaigns with thousands of opt-ins.
Standard SMS QR codes do not support attachments or images (MMS). If you need the user to send a photo (damage report, receipt scan), direct them to a web upload form via a URL QR instead.
Open SMS QR Generator, create a test QR with a short body, and verify delivery on both iOS and Android before launching your campaign.
This article is reviewed by the Tools Hub editorial team for factual accuracy, practical relevance, and consistency with current product workflows.
Last reviewed:
Create SMS QR codes with prefilled number and message. Download high-resolution PNG or SVG online.
mailto URI parameters, URL encoding rules, template vs freeform body strategies, email client compatibility, and QR density limits for print.
tel URI format rules, country code formatting, mobile-only limitations, fallback strategies for desktop, and call tracking via landing pages.
vCard 3.0 vs 4.0, required vs optional fields, photo encoding limits, iOS and Android compatibility, and batch generation for sales teams.