Tablet user agents
iPad, Samsung Galaxy Tab, Amazon Fire, Lenovo Tab, Xiaomi Pad and Windows 2-in-1 strings, including the desktop-class ones.
2,680 user agents
0 matching user agents ·
| User agent string | Browser | Platform | Device | Actions |
|---|
Why tablets are the hardest form factor to detect
Tablets sit exactly where user agent detection is weakest. Three separate conventions are in play, and two of them actively disguise the device as something else.
1. Android tablets: detection by omission
An Android tablet is identified by what is missing. Chrome includes the token Mobile on phones and leaves it out on tablets — there is no positive tablet marker at all.
Phone: ... Chrome/131.0.0.0 Mobile Safari/537.36
Tablet: ... Chrome/131.0.0.0 Safari/537.362. iPadOS: deliberately indistinguishable from a Mac
Since iPadOS 13, Safari on iPad defaults to requesting desktop sites, and to make that work it sends a Macintosh user agent:
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/17.5 Safari/605.1.15Nothing in that string says iPad. The standard workaround is to check navigator.maxTouchPoints > 1 alongside a Macintosh platform — Macs report 0, iPads report 5. Apps requesting the mobile site still get the recognisable iPad string, so both forms appear in real traffic.
3. Windows tablets: no signal whatsoever
A Surface Pro sends the same user agent as a Windows desktop. There is no token to distinguish them, and no client hint that helps. Pointer media queries — (pointer: coarse) — are the only practical signal.
Fire tablets
Amazon's tablets run Fire OS, an Android fork, and identify themselves through a device code plus the Silk browser token. KFRAWI is a Fire HD 10, KFQUWI a Fire HD 8. Fire tablets can also run Chrome, in which case only the KF-prefixed model code gives them away.
Frequently asked questions
How do I detect an iPad reliably?
Combine two checks: the platform reports Macintosh or MacIntel, and navigator.maxTouchPoints is greater than 1. Desktop Macs report 0 touch points, iPads report 5. That pairing is the standard approach and has held up since iPadOS 13.
Why does my Android tablet get served the mobile site?
Almost always a detection rule matching on the word Android alone rather than on Android plus Mobile. Because Android tablets are identified by the absence of the Mobile token, any rule that ignores it treats every Android device as a phone.
Can I tell a Surface Pro from a Windows desktop?
Not from the user agent — they are identical. CSS media queries are the practical route: (pointer: coarse) matches touch-first devices and (any-pointer: fine) tells you a mouse or stylus is also available. That describes input capability rather than hardware, which for layout decisions is usually the more useful question anyway.
Other categories
Desktop & Laptop
Chrome, Firefox, Safari, Edge and Opera on Windows, macOS, Linux and Chrome OS.
8,989 user agentsMobile Phones
Android and iOS phones from Samsung, Apple, Google, Xiaomi, OPPO, vivo and more.
15,434 user agentsSmart TVs & Streaming
Samsung Tizen, LG webOS, Android TV, Roku, Fire TV, Apple TV and Chromecast.
86 user agentsGame Consoles
PlayStation 5 and 4, Xbox Series X|S, Nintendo Switch and Steam Deck.
20 user agentsWearables & XR
Apple Watch, Wear OS smartwatches, Meta Quest, PICO and Apple Vision Pro.
13 user agentsIn-App Browsers
Facebook, Instagram, TikTok, WeChat, LINE webviews and Electron desktop apps.
108 user agents