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.
The Safari UA pattern
Safari's user agent contains an AppleWebKit token, a Version token giving the Safari release, and a trailing Safari token. The platform descriptor differs by device — a Macintosh descriptor on macOS, and an iPhone or iPad descriptor on iOS.
To distinguish Safari from Chrome, look for the Safari and Version tokens without a Chrome token, since Chrome also carries AppleWebKit and Safari tokens for compatibility.
- AppleWebKit + Version + Safari tokens
- Platform descriptor: Macintosh, iPhone, or iPad
- No Chrome token (which would indicate a Chromium browser)
The iPadOS desktop-class quirk
Since iPadOS began requesting desktop-class web pages by default, an iPad can present a user agent shaped like desktop Safari on macOS. This is intentional, so iPads receive desktop layouts, but it means UA-based device detection can count an iPad as a Mac.
If accurate tablet-vs-desktop counts matter, do not rely on the raw user agent alone for iPadOS. The exact current token shape is best confirmed against Apple's developer documentation, since Safari's UA details evolve.
How it appears in analytics and logs
A user agent with WebKit plus a Safari Version token but no Chrome token is typically Safari. On iPadOS, a desktop-class request can carry a Macintosh-shaped string, so an iPad may appear as a Mac.
Diagnostic use case
Recognise Safari traffic across macOS, iPhone, and iPad, and account for the iPadOS desktop-class user agent so you do not undercount tablets as desktops.
What WebmasterID can help detect
WebmasterID recognises Safari and WebKit-based clients server-side and records a coarse browser/platform category, so the iPadOS desktop-class quirk does not silently misclassify tablet traffic.
Common mistakes
- Counting iPadOS desktop-class requests as desktop Macs.
- Mistaking a Chrome-on-iOS or Chrome-on-Mac string for Safari because both carry a Safari token.
- Relying on an exact Safari version string that changes between releases.
Privacy and accuracy notes
Safari's UA describes the browser, not a person. Apple has long minimised the entropy in Safari's user agent for privacy. WebmasterID records a coarse browser category rather than the raw visitor string.
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.
- Browser user agents: how to read them
A browser user-agent string packs several tokens into one line: a legacy Mozilla prefix, a rendering-engine signature, the platform, and the browser itself. This page explains each part so you can read a UA without over-reading it, because the contents are client-controlled and can be copied by any client.
- Bot vs human traffic
Separating real browser visits from automation across devices.
Sources and verification notes
- MDN — User-Agent header
- MDN — Browser detection using the user agentiPadOS desktop-class behaviour; exact current token shape verify against Apple docs.
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.