Wearable and XR headset user agents
Apple Watch, Wear OS smartwatches, Meta Quest, PICO, Apple Vision Pro and HoloLens strings.
13 user agents
0 matching user agents ·
| User agent string | Browser | Platform | Device | Actions |
|---|
Smartwatches
Watches rarely browse the open web, but they do fetch content — notification previews, link expansion and watch-face complications all generate requests.
Apple Watch: Mozilla/5.0 (Apple Watch; CPU WatchOS 11_2 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/11.0 Mobile/22S100 Safari/604.1
Wear OS: Mozilla/5.0 (Linux; Android 14; Wear OS 5.0; Pixel Watch 3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Mobile Safari/537.36Wear OS is the more detectable of the two: it inserts an explicit Wear OS token into an otherwise ordinary Android string. Match on that token rather than on the device name, which varies by manufacturer.
XR headsets
Headsets are a genuinely growing browsing surface, and their strings reflect an odd lineage. Meta's Quest browser is built on Chromium but historically borrowed Samsung Internet's codebase, which is why it carries both an OculusBrowser and a SamsungBrowser token. The VR token before Safari is the reliable form-factor marker.
Mozilla/5.0 (X11; Linux x86_64; Quest 3) AppleWebKit/537.36 (KHTML, like Gecko) OculusBrowser/34.0.0.2.30 SamsungBrowser/4.0 Chrome/126.0.6478.122 VR Safari/537.36Apple Vision Pro is the outlier: Safari on visionOS reports a standard Macintosh string with a visionOS suffix appended. Without that suffix it would be indistinguishable from a desktop Mac — and in some contexts the suffix is absent, so treat Vision Pro detection as best-effort.
Frequently asked questions
How do I detect a VR headset?
Check for the VR token, or for OculusBrowser, Quest and Pico specifically. For actually deciding whether to offer an immersive experience, the WebXR API is far more reliable than string matching — call navigator.xr.isSessionSupported('immersive-vr') and branch on the answer.
Why does the Quest browser mention Samsung?
Because it started as a fork of Samsung Internet, which was itself a Chromium fork. Meta kept the SamsungBrowser token for compatibility with sites that had already special-cased it, so the string now names three browsers at once: Oculus, Samsung and Chrome.
Does the Apple Watch really browse the web?
In a limited way. watchOS renders web content when you tap a link in a message or notification, using a WebKit view. It cannot be used for general browsing, but those requests do appear in server logs with the Apple Watch token.
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 agentsTablets
iPad, Galaxy Tab, Fire tablets, Lenovo Tab and Windows 2-in-1 devices.
2,680 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 agentsIn-App Browsers
Facebook, Instagram, TikTok, WeChat, LINE webviews and Electron desktop apps.
108 user agents