Tablet user agents
Tablets are the hardest device class to read from a user agent. iPadOS requests desktop-class pages by default, so an iPad can look like a Mac, and many Android tablets omit the Mobile token that phones include. This page explains why tablet detection from the UA alone is unreliable and how to handle it.
The iPad desktop-class quirk
Since iPadOS began requesting desktop-class web pages by default, an iPad commonly presents a user agent shaped like desktop Safari on macOS. This is intentional, so iPads receive desktop layouts, but it means UA-based detection can count an iPad as a Mac.
If accurate tablet counts matter, the raw iPadOS user agent is not enough on its own; you may need additional signals such as touch capability to separate iPad from a genuine Mac.
- iPadOS requests desktop-class pages by default
- An iPad can present a Macintosh-shaped user agent
- UA alone can miscount iPad as desktop
Android tablets and the missing Mobile token
Phones commonly include a Mobile token, and the convention is that Android tablets omit it. In practice this is inconsistent across devices and browsers, so the absence of a Mobile token is a hint toward a tablet, not a guarantee.
Because both major tablet platforms muddy the signal, treat tablet detection from the UA as approximate. Match on stable cues, corroborate with other signals where counts matter, and confirm specifics against Apple and Android documentation.
How it appears in analytics and logs
A desktop-class string may actually be an iPad, and an Android string without a Mobile token may be a tablet rather than desktop. The user agent alone cannot reliably confirm a tablet.
Diagnostic use case
Account for the iPad desktop-class quirk and Android tablets dropping the Mobile token so tablet traffic is not silently miscounted as desktop or phone.
What WebmasterID can help detect
WebmasterID parses device cues server-side into a coarse category and keeps ambiguous tablet strings in an honest bucket rather than forcing a desktop or phone label.
Common mistakes
- Counting iPadOS desktop-class requests as desktop Macs.
- Assuming every Android tablet reliably drops the Mobile token.
- Reporting precise tablet share from the raw user agent alone.
Privacy and accuracy notes
Tablet signals describe device class, not a person. Parsing into a coarse device category is privacy-safe; WebmasterID stores no raw visitor user-agent strings.
Related pages
- Mobile user agents: phones, tablets, in-app
Mobile user agents carry platform descriptors like iPhone or Android and often a Mobile token, but tablets and in-app browsers complicate the picture. An in-app browser (inside a social or messaging app) usually adds its own token to the string. This page explains the patterns and their pitfalls.
- Safari user agent on iOS and macOS
Safari's user agent is built around WebKit and a Version token, and differs between macOS and iOS. A notable quirk is that iPadOS can present a desktop-class Safari user agent, which can make an iPad look like a Mac in logs. This page covers the pattern and the platform-specific behaviour.
- Bot vs human traffic
Separate real visits across phones, tablets, and desktops from automation.
Sources and verification notes
- MDN — Browser detection using the user agentiPadOS desktop-class and Android tablet Mobile-token behaviour; verify against platform docs.
- MDN — User-Agent header
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.