QR Code Device and OS Benchmarks: iOS vs. Android Scan Behavior

Short answer

In most Western markets, QR code scans split roughly 55–60% iOS and 40–45% Android, though this ratio shifts significantly by country, industry, and placement type. iOS users scan almost exclusively with the native camera app; Android users rely on a wider mix of the built-in camera, Google Lens, and third-party readers. This matters because each path delivers slightly different data to your analytics platform and behaves differently on landing pages that use contacts, payments, or progressive web app features.

How the device split breaks down

Global averages

Aggregated QR scan data across retail, events, and print campaigns consistently shows a slight iOS majority in North America, the UK, and Australia — countries where iPhone market share is highest. Android leads in most of continental Europe, Latin America, Southeast Asia, and sub-Saharan Africa.

Region	Typical iOS share	Typical Android share
United States	57–63%	37–43%
United Kingdom	50–56%	44–50%
Germany	35–42%	58–65%
Brazil	25–32%	68–75%
India	12–18%	82–88%
Japan	65–72%	28–35%

These are typical ranges across broad campaign types; your own campaigns will vary. Campaigns at premium retail or corporate events tend to skew more iOS. Campaigns at public outdoor locations or markets often skew more Android.

Industry variation

Device split is not uniform across industries. Some patterns observed consistently:

• Events and conferences: iOS share is often 60–70%, reflecting higher iPhone ownership among professionals in attending demographics.
• Restaurant and hospitality: Android share rises closer to parity, reflecting a broader general-public audience.
• Healthcare and government: Android is often the majority, especially in systems where Android devices are issued to frontline staff.
• Retail luxury: iOS share can exceed 70%, correlating with higher household income brackets.

Checking your own scan-level device data in Linkbreakers analytics is more reliable than applying any global benchmark to a specific campaign.

How users scan on each platform

iOS: native camera, always

Since iOS 11, the native iPhone and iPad camera app can decode QR codes without any additional app. Virtually all iOS scans arrive via com.apple.camera or Safari. Third-party QR reader app usage on iOS is below 5% in most campaign data — users almost never install a separate scanner.

Android: fragmented

Android scanning is more varied:

• Built-in camera: Available on most devices running Android 9 or later through Google's Camera app or OEM versions (Samsung, Xiaomi, Huawei). This is the most common path.
• Google Lens: Integrated into the Google search bar widget and Google Assistant. Contributes roughly 10–20% of Android scans in some data sets.
• Third-party apps: QR & Barcode Scanner, Kaspersky QR Scanner, and similar apps are still used by a meaningful share of Android users — estimated 5–15% of Android scans depending on the demographic.

Each scanner sends slightly different HTTP headers and user agent strings, which affects how analytics platforms classify the traffic. Scans via Google Lens may be reported differently than camera-native scans in some tracking setups.

What the device split means for your destination

Contact card (vCard) compatibility

If your QR code links to a vCard or contact card, iOS and Android handle the download differently. iOS opens .vcf files natively via Contacts. Android behavior depends on the device — some open it directly, others prompt the user to choose an app. This is one reason purpose-built contact card pages that render a mobile-friendly web UI outperform raw .vcf links: both platforms get a consistent experience.

Page speed sensitivity

Mobile users — both iOS and Android — abandon slow-loading pages quickly. The threshold is typically 2–3 seconds. Android devices span a wider hardware range than iOS, so median page load time on Android is often 15–25% higher than on iOS for the same page. If your QR landing page includes heavy media or JavaScript, Android users are more likely to drop off before engaging.

Limits and caveats

iOS Private Relay

Users on iCloud+ plans with Private Relay enabled route their traffic through Apple's anonymization network. This masks their IP address, which means city-level location data and ISP data in your analytics will be absent or inaccurate for those scans. As of 2026, Private Relay is enabled by a meaningful share of iPhone users. Location tracking from QR scans is affected by this for iOS users.

User agent spoofing and inconsistency

Some Android browsers send iOS user agent strings, and corporate security proxies can strip or modify user agent headers. Device classification in analytics is accurate for the large majority of scans, but edge cases exist. Treat device-level breakdowns as directional signals rather than exact counts.

Sample size requirements for reliable splits

A campaign with fewer than 200 scans will produce noisy device ratios. The split may appear 90/10 simply due to small sample size. Device benchmarks are meaningful at 500+ scans; stable at 2,000+.

In-app scanning contexts

Scans from in-app browsers (Instagram, WeChat, LINE) often report a modified user agent that analytics may not correctly classify as iOS or Android. Treat these as a separate, noisy segment rather than incorporating them into your iOS/Android split.

Frequently asked questions

Does iOS or Android produce higher post-scan conversion rates?

iOS users tend to convert at modestly higher rates on most action types — typically 5–15% higher for form fills and contact saves in broad campaign data. This likely reflects faster device performance, more consistent browser behavior, and the demographics of iPhone-heavy markets rather than anything platform-specific. For any specific campaign, check your own data rather than assuming the global trend applies.

Should I design my landing page for iOS first?

In North American and UK campaigns, optimizing for iOS first is a reasonable default given the user majority. But test on Android too: if your page has interactive elements, a contact save flow, or payment buttons, Android behavior can differ in ways that reduce conversions. QR code landing page best practices apply to both platforms.

Does Linkbreakers show device breakdown in analytics?

Yes. Each scan in Linkbreakers records device type (mobile, tablet, desktop), operating system (iOS, Android, Windows, macOS, etc.), and browser. This data appears in the scan analytics view for each QR code. For campaigns where destination experience differs by platform, you can use device conditions in workflows to route iOS and Android users to separate destinations.

Does the device split change over time?

Slowly. iPhone market share has been gradually increasing in several markets, shifting the split slightly toward iOS year over year. Short-term shifts in a single campaign are more likely to reflect the specific audience than any macro trend.

How does Android fragmentation affect QR scan reliability?

On very low-end Android devices (older CPU, limited RAM), complex QR codes — those encoding long URLs or using high error correction — may take longer to decode or fail intermittently. Keeping your QR code's encoded URL short (via a short link redirect rather than a long destination URL) reduces this risk. Dynamic QR codes solve this naturally since they encode only a short redirect URL.